Purge Cache Conflicts with the one with LS Cache (Admin bar cached)

  • Resolved Parsa R.

    (@parsar2025)


    1 month, 2 weeks ago

    Hey there.

    I tried to use Super Page Cache with LS Cache, so I disabled any page caching settings related to LS Cache and successfully connected Super Page Cache with CLoudflare.

    All was good until I saw some changes in LS Cache would be back to previous state after saving and hitting refresh, and after trying to purge cache (first LS Cache then Super Page Cache), it made the admin bar available to normal users! And sometimes after purging LS Cache only, it made the admin bar unavailable for everybody (including me the admin!).

    That’s a very big security risk and after trying to solve the issue on my own, and failing, I had to deactivate and reactivate the plugin (even rolled back to v 5.0.3) and it got worse (Super Page cache was shown and although deactivated, clicking on it from the admin bar led me to the plugin page!!). Above all, I tried the latest version one more time, and couldn’t get Super Page Cache enabled (it refreshed every time I hit enable, and the same page would show up again). so I had to remove it.

    What I’m asking for is a general, newbie friendly guide on how to set Super Page cache and LS Cache, so they would not conflict in any way. I really enjoyed connecting with Cloudflare seamlessly, but Since I’m using LS Cache and I need some of it’s other functionalities, I need help.

    P.S. I already went through Tom Dupuis’s article and support thread you went through in the forum. But unfortunately some of these issues were new and I couldn’t find a solution.

    I would really appreciate you help ??

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

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor iSaumya

    (@isaumya)

    Hi,
    You are not supposed to use more that one page caching system at the same time. If you are using LS cache with thsi plugin then you should only be using LS cache for static file optimization and nothing else.

    Also, there is no security risk cause even if the black bar is cached if any user clicks on it it will ask them to login, if you try in incognito window.

    Thread Starter Parsa R.

    (@parsar2025)

    Whenever I’m changing Super Page Cache plugin settings, in order for it to take effect, should I purge LS Cache first then Super Page Cache or vice versa? It seems like purging all cache using both plugins might cause issues.

    Also, I still have issues with Admin bar. The admin bar sometimes is not shown to me (admin user) and normal users, and some other times is shown to all (by sometimes I mean after different purge caches). I think it’s being cached.

    I read about it in FAQ, enabled Overwrite the cache-control header for WordPress’s pages using web server rules (LS Server v. is 6.1) and tried cloudflare page caching to bypass /wp-* but still not working.

    I was going through a lot of posts about Super Page Cache and LS Cache plugin. And my question is – Is it really worth using both the plugins. More I read and test I feel it creates more conflict and adds bloat to the wordpress installation.

    I feel one cache plugin is enough. If one is using LS Cache just for static files, I think its not worth it and we should stick with Super Page Cache. Or just use something which will serve static files and thats it.

    I would like to hear the developer’s view on that.

    Regards

    Vinay

    Plugin Contributor iSaumya

    (@isaumya)

    Fully agree with you @the8055. Should stick to using only one.

    Thread Starter Parsa R.

    (@parsar2025)

    I was able to find the solution for admin bar.

    It was Cloudflare’s Page Rule I set up called <<Cache Level = Cache Everything>> that caused that to happen. The whole page was getting cached and right after turning Cache everything on, it cached and showed it to all users.

    I had to turn it off for now, but I’m working on a solution I’ll share soon.

    I also have to mention that I had turned all cache related settings (like browser cache) off (although it was not related to page caching, preferred to use Super Page Cache for less conflict).

    Hopefully I’ll share the final solution to admin bar issue and put an end to this once and for all!

    Thread Starter Parsa R.

    (@parsar2025)

    I found a way to solve this irritating issue!

    When Cloudflare is set on “Cache Everything” it will truly do that and also cache admin bar when you are logged in. But I thought of a way to get around this and make Super Page Cache one step closer to serving it’s purpose (which is leveraging all Cloudflare’s features so we don’t have to pay for its premium).

    So I had to write a plugin!

    It simply checks the URL and sees if it has Super Page Cache’s “Cache Buster” which is “swcfpc=1” inside your URL. If it is there, it shows the admin bar, and the rest of the user won’t see it. as simple as that!

    That way you won’t have to worry about the admin bar being cached because whenever you want to use it, you can access it via YOUR_DOMAIN.com/?swcfpc=1 which is bypassed by Cloudflare.

    Keep in mind that you have to add a page rule to Cloudflare that bypasses the cache for ?swcfpc=1 parameter.

    For more info or using the plugin, you can check my GitHub with username parsar2025 (click on the username to directly fo to the plugin repo).

    Hope it helps.
    I would appreciate your feedback.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.