alchemistGM

Good info, thanks. Good to know about WP Cron potentially getting crowded out also.

thanks, will check those out

just deactivating supercache may not be enough, here are some additional tips:
https://www.ads-software.com/extend/plugins/wp-super-cache/other_notes/

That’s okay, I was juat wondering if anyone using that feature had discovered real-world values that worked for them. From you, I am taking the defaults as my best probable guidance ??

With supercache, things seemed to expire in an hour no matter what we set in settings, but with W3 Total cache I’m happy to report that nothing seems to be expiring prematurely, so I think we’re okay on that.

Thanks; I’m loving it!

Well I tried 10 seconds between batches and 20 files per batch. but nothing happened. Ist there a “go” command to make it begin priming the cache?

Also still have not found out where to set cached pages to never expire, (or expire far into the future). I could set garbage collection to be very long between but GC might be triggered at other times than when scheduled.

Yes this confused me for a while too, but I think it was intended as a master switch that could disable caching without messing up your individual settings. I have not tested it much but glad to hear it will get improvement or clarification in the next update. I think it’s a great idea, I was just never confident I understood it so I left it alone.

If you’re able to use php code you could do a check of the environment variables to determine the url you are at, which can be used to discover the outermost container page. There may be a way to check parent page or ancestors which could work also.

okay, thanks!

There is support for targeting a post by post number or range. If your custom post types are numbered in a certain range it seems you could target those custom post types as a group using the post number to isolate them.

I am just getting started with this and that is my planned approach.