• Resolved trishahdee

    (@trishahdee)


    My client’s website has a strange delay between when a change is made and when it shows up on the frontend. The only plugin being used that I’ve never used before is WordFence so I’m hoping you can tell me if it is the cause.

    When an Admin is logged in and makes a change, we can go to the frontend of the website and see the changes. However, if we logout and go to the frontend, the new changes are not there. It takes up to an hour for it to “let go” and then the changes can be seen. The site is acting like it is on a CDN (content delivery network) but I don’t see the DNS directed to one.

    I’ve checked the WordPress plugins and the WordPress files on the server looking for anything that looks like caching and have found none.

    Because, whatever it is, knows when an Admin is logged in, it seem it should be something to do with WordPress. It’s not part of Core WordPress so it could be a plugin. And the only plugin used on this website that I’ve never used before is WordFence Security. I have searched their documentation and can find no mention of caching being an option with it.

    I’m at a loss. Can you tell me if anything in WordFence would cause such behavior?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hey @trishahdee,

    Wordfence does not cache files. Your issue could be caused by one of the following:

    1. You’re logging in and out (and viewing your pages) using the same browser mode. Suggest logging in and making your changes in Incognito or Private Mode – and viewing your changes in regular mode. Clear all cache first. In both modes, press CTRL + F5 (twice) to properly clear your browser’s cache.
    2. You may have server-side caching activated and are not purging it after making your changes. Contact your host, they should be able to help you.
    3. You may be using a CDN – which is not automatically purging your cache each time you make a change (logged in or not). Are you using a CDN? If so, are you clearing its cache?
    4. You’re not properly clearing your browser’s cache – or – your browser’s settings are blocking your changes. Again, press CTRL + F5 (twice) to properly clear your browser’s cache.
    5. The pages you’ve modified are not yet published (saved as draft only).
    6. You’re using a plugin (other than Wordfence) that is causing the issue. Did you perform a plugin conflict test?
    7. Does your theme include a caching feature? If so, are your clearing it after making your changes?

    Hope this helps a bit.

    Cheers!

    Thanks for reaching out.

    Wordfence does not include caching so the problem is definitely originating elsewhere. You might check the .htaccess file and look to see if there are caching instructions left from a cache plugin. Uninstalling the cache plugin may not have removed changes from that file resulting in it telling your browser to cache the page much longer than it should.

    Mia

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Does WordFence have it’s own caching?’ is closed to new replies.