root index.html is deleted unpredictably after the last update

Yup I’m experiencing the same issue, very annoying ?? and yeah I thought at first it was when I logged in but now I realized it happens all the time.

Everything else is cached properly, it’s just index.html and index.gz that keeps being deleted.

I’m having the same issue as well. Everything appears to be cached normally, only the front page disappears from the cache unpredictably.

I see the exact same issue? Did you guys figure out what’s wrong?

Thanks!

I bumped into this myself on version 1.4.6.
It appears to be triggered by posting to a php file in the root directory.
I noticed these files triggering the delete of my cached root page (only on a POST, not on a GET):
wp-login.php
xmlrpc.php
wp-cron.php

And if you think you’re the only one hitting you login page, better double check your server logs as you may have a bot hitting that page behind your back trying to break in… ??

In the plugin file wp-cache-phase2.php, the method that’s doing the delete is: function wp_cache_ob_callback

the code block down on line 317 is being entered:

if ( is_array( $do_rebuild_list ) && false == empty( $do_rebuild_list ) ) {

i temporarily updated my code to skip that rebuild logic when the current page is one that’s flagged to not cache. so my line 317 became:

if ( is_array( $do_rebuild_list ) && false == empty( $do_rebuild_list ) && wp_cache_is_rejected($_SERVER['REQUEST_URI']) == false ) {

Don’t yet know if this will have any negative side-effects (such as stranding old cache page copies), but I’m preloading the cache regularly so those cache page copies will still update with each preload run.

Finally after pulling my hair out for two days, I’ve come across this thread ! I’m facing the same issue and I thought I was doing something wrong.

If indeed it is a bug, it is clearly not fixed yet.

What have you guys done about it ? @mike.banavige, I’m going to try your solution. Have you found anything better since ?

just to say that mike.banavige’s solution works. But definitely not good that no one from actual plugin responded… ??

This is recorded as a formal issue at https://github.com/Automattic/wp-super-cache/issues/84

I have copied the potential fix above to this issue in the hope that it prompts someone to look at it.

Seems enabling direct cache files for home page (/) solves the issue.

Hello, is it possible that I still have this issue now ? OR has it been fixed ? Thanks.