[Plugin: WP Super Cache] On CMS site, sometimes caching blog front page instead of defined static pa

  • I’m using WP 2.3.3 for this CMS site because WordPress is bridged tightly with PHPBB3 and all the core customizations will make upgrading a pain. So, it’s possible that my issue is due to my antiquated WordPress, or related somehow to the integration with PHPBB3. But, I’ve seen a few reports of problems that appear similar to mine in this forum.

    I first installed the plugin on this particular site 2 days ago. It seems that after I activate WP-Supercache, the caching works fine for a few hours. Eventually however, and seemingly at random, on the site’s main page the cached front page of the blog is displayed instead of the static page that’s defined in WordPress. The issue can be resolved by clearing the cache.

    Since my client doesn’t update the home page often, I tried to get WP-Supercache to cache the home page “permanently”, or at least until the cache is cleared manually. When I activated “Lock Down mode” and entered a single slash to indicate that I wanted to lock down the home page, an index.html file was created under public_html… but when I activated lock-down mode tried to load the site, I couldn’t get anything but a blank page. To correct the problem I had to restore the default WP-Supercache configuration.

    I also tried changing the ownership and permissions of the cached index file (via SSH) after it had been created, hoping that it would not allow itself to be overwritten or deleted by the plugin, but so far that hasn’t worked.

    Finally, I tried adding /blog/ to the list of strings that will not be cached since all the URL’s for the blog pages include that string, but as I expected, that had no effect.

    Any ideas?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter alanpace

    (@alanpace)

    It appears that the problem I described above in too many words: WP-SuperCache starting to serve the wrong home page after a few hours– is related to the “Garbage Collection” problem mentioned elsewhere. The correct home page is restored when I delete *just* the expired files. If the expired files were deleted automatically (as they should be), that would correct the problem with the static home page.

    Thread Starter alanpace

    (@alanpace)

    It appears that I’ve solved this problem by disabling file locking. Since I made that change this afternoon, Garbage Collection of expired files has been working and the correct home page has been served.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘[Plugin: WP Super Cache] On CMS site, sometimes caching blog front page instead of defined static pa’ is closed to new replies.