• @donncha

    I recently decided to upgrade my server and to try to get to the new standard for WP on PHP and MySQL. Yes, I should have done this a long time ago but everything was working perfectly until now.

    Following upgrading my server and PHP to 5.6.xx and MySQL to 5.7 I then upgraded WordPress and plugins.

    I found a strange new behavior on Super Cache – it is rebuilding the home page cache following every page load. So, it sends the old super cache file and then rebuilds a new one. This is very strange because I currently have it configured to not time out cache and to not rebuild cache. I did that so I could have a chance to debug the various coding issues caused by the upgrades without totally disrupting my sites.

    Any reason you can think of that would cause this behavior??

    Thanks,
    Pat

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter wlpdrpat

    (@wlpdrpat)

    @donncha Would this option cause the behavior I described:

    Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated. (Recommended)

    I have selected the above option because it is recommended but I didn’t think this would cause the supercached files to be rebuilt every time someone accesses the page. Is that what it is supposed to do?? If so, why?? I thought the whole point of cached pages was to reduce load on the server. This option, if it does what I described, would appear counterproductive to server resources, ie creating a new cached page every time the page is accessed.

    Please let me know if that is the case.

    Thanks,
    Pat

    @wlpdrpat – Did the debug log say why the front page cache file was being deleted/put in rebuild mode? Maybe some new plugin you have is triggering an action that’s causing this.
    Or the front page cache file isn’t being saved at all. Might be worth opening a command line in that directory and seeing the files generated there while you hit the front page.

    Thread Starter wlpdrpat

    (@wlpdrpat)

    @donncha I’m using advanced caching with mobile device support. So, it creates 2 HTML files (desktop and mobile). The issue is occurring on a multisite network but is only affecting one particular site. I checked a few of the other sites and it’s not happening on those.

    So, I would assume you are correct that it is related to some plugin conflict or at least that is the direction I am working.

    Part of the reason I hate upgrading multisite installations is that the individual sites all have unique issues to address. Se la vie.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Multisite Caching Issue’ is closed to new replies.