gab81

if anyone has a fix for “when updating or adding a post, it causes the whole pre-loaded page” gone that would be great!

thanks,
Gab

please let me know, this is really annoying when you update a post, all the cache is gone.

thanks

cheers Kimberly, why dont you share? still no news from the author.

thanks,
Gab

found the problem, i had so many of wp_cache_full_preload_hook jobs, deleted all of them with “Advanced Cron Manager” and works as a charm now!

found the problem, i had so many of wp_cache_full_preload_hook jobs, deleted all of them with “Advanced Cron Manager” and works as a charm now!

if you put a lower value, say 1000 that works

do i need to check PHP and block the execution of the preload or is it a cron job anywhere i can cancel and then re-initiate?

so for example on site 1 (not working properly), i set preload to 5000 and i get this:

Full refresh of cache in 24 hours 48 minutes and 55 seconds.

which is wrong, it’s approx 1470 minutes and not 5000

not ticked – so another small bug for WP Super Cache…

hi all, you guys here seems to know lots about this plugin, was just wondering if you knew about these 2 things – while we wait for the other answer about the new bug with the index pages…

1) is it possible to preload also mobile pages? when I use the preload function it only preloads desktop posts, not a deal breaker but that would be nice

2) when updating or adding a post, it causes the whole pre-loaded pages to have a .needs.rebuild – wouldn’t it be logic to have just the new post or newly modified post to be reached instead?

thanks

indeed – not resolved but continues on other thread

confirmed the issue, it’s more random, i think it’s related to what afavinger said.

so i disabled cache rebuild for now..

i personally noticed that index gets deleted when i login to the admin..

anyone?? tnx

that happens if you change something on a single post – then the plugin will want to update all the others as well, if you click on “preload cache”, that usually does the trick.

but it also depends if you are using preload, it could be the garbage collector that has just ran as well and wants to update.

IF you enable preloading posts, the garbage collector doesn’t really matter.

you can try to contact the author I guess…

my theme is mobile friendly, caching works fine and generates index-mobile etc, that is OK.