Old cached version of homepage loading for non-logged in users

  • Resolved N.A. Ferrell

    (@naferrell)


    4 years, 5 months ago

    This problem only applies to the homepage of my site. When non-logged in users try to access the homepage of my site on desktop, they are referred to a an old version of the page, this appeared at the end of code after I pulled up the F12 menu -> <! — WP Fastest Cache file was created in 0.54688620567322 seconds, on 12-06-20 15:26:35 –> == $9 … All other pages on the site work correctly. For example, if you navigate away from the homepage, the user goes to an up-to-date page using the new theme. But navigate back to the homepage and you get the old page. Shift + F5 does force the new homepage to appear, but I’ve found that browsers will still load the wrong one if you close and go in again. Issue does not seem to persist on mobile devices. There, clearing the cache once seems to make the correct version of the homepage appear in both regular and incognito windows (tested on Kindle Fire and had others test with phones).

    Here are some other facts about the issue and my unsuccessful efforts to resolve it:
    – I use WP Fastest Cache in conjunction with Automptimize to increase speed. Settings for WP Fasest Cache – Preload (home, posts, categories, pages), clear new post, clear update post, Gzip enabled, browser caching enabled
    – Webhost is Bluehost. Endurance cache for Bluehost is disabled. It has never been enabled.
    – Do not use a CDN. Began process of signing up with Cloudfare last week, but never completed set up and decided not to use it at this time.
    – On June 13, 1 day after the last cache file was created, I updated from PHP 7.0 to 7.3
    – After updating PHP, I switched from the free Bunny Press Lite theme to the paid Bunny Press theme
    – I did not disable WP Fastest Cache or Automptimize during switch
    – New theme has a “Output browser cache setting to .htaccess?” option, but I have it disabled. I have enabled load JS async from the theme, if that makes any difference.
    – I recognized the issue yesterday (June 16), did not notice before because it does not seem to affect logged-in users
    – Refreshed permalinks with cache off
    – Deleting cache in WP Fastest Cache and Autoptimize did not resolve the issue.
    – Uninstalling WP Fastest Cache did not resolve the issue
    – Reinstalling WP Fastest Cache and going into My PHP Admin to delete folder with cached files did not resolve the issue
    – I tried installing and using “Clear Cache for Me” plugin, but that did not resolve the issue.

    That is the issue as I understand it and all the steps I have taken to try to resolve it. I am out of ideas, so I would be grateful for any help pointing me to the issue, whether it is with WP Fastest Cache or something else. Ready to answer any questions if more information is needed.

    Full disclosure for any responses: I am not very technical and have no background with coding or programming.

    Thank you in advance for looking at my problem.

    • This topic was modified 4 years, 5 months ago by Jan Dembowski.
    • This topic was modified 4 years, 5 months ago by N.A. Ferrell.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter N.A. Ferrell

    (@naferrell)

    Addendum:

    Four additional points that may be relevant.

    1. I replicated the issue in the following browsers: Vivaldi, Chrome, MS Edge (non-Chromium version), and Avast. Also have the issue on my BlackBerry Classic (runs BB10), but have not tried clearing cache there.

    2. I have one plugin called “Blackhole for Bad Bots.” I had been running it without incident, but I read on the FAQ that a supplemental plugin is recommended for making it compatible with WP Fastest Cache. I downloaded and installed Blackhole Cache Helper last week, sometime before the 12th. Deactivating it did not resolve the issue.

    3. I restored a backup of the site from the 15th (after the theme switch) yesterday from Updraft in order to fix an issue with Twitter meta tags. As far as I know, it has nothing to do with the issue – but noting just in case it’s relevant.

    4. Using free version of WP Fastest Cache.

    • This reply was modified 4 years, 5 months ago by N.A. Ferrell.
    Plugin Author Emre Vona

    (@emrevona)

    there is a server-side cache system. you need to disable it.
    https://ibb.co/j6V5zrn

    Thread Starter N.A. Ferrell

    (@naferrell)

    Thanks for getting back to me. I was not able to figure out how to implement your solution. However, I had a friend look at it and after deactivating the plugin entirely (still installed, just not active) along with the two Blackhole plugins I noted before, followed by a backup restore from earlier in the day to resolve a redirect issue, the caching issue appears to be mitigated for now.

    Before closing the issue, may you point me to where I should look to implement your suggestion (bearing in mind that I don’t know any code)? As I noted, our site is hosted by Bluehost. Bluehost has an “Endurance Cache” option, but it has never at any point been enabled – precisely because I wanted the plugin to do that job and not have to worry about conflicts. In light of endurance cache being off, do you know where I might find the server-side cache system in the panel (or elsewhere) so I can disable it? Nothing that I can find in the Bluehost admin fields has the same menu as the picture you sent.

    Your plugin was producing great results for my site for over a month and I had no caching problems at all until the other day, so I would very much like to be able to safely re-implement it.

    https://ibb.co/ChTmFp7 (If it helps, this is a screenshot of what I was seeing in browsers when the old version of the homepage was being served)

    Thank you again for your help.

    Plugin Author Emre Vona

    (@emrevona)

    I do not read your answers. I wrote so simple thing. Just you need to disable the server-side cache system.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Old cached version of homepage loading for non-logged in users’ is closed to new replies.

Tags