Issue with WP Super Cache

  • Resolved JawaScript

    (@crimsonguard)


    4 years, 10 months ago

    Hi
    Thank you for this plugin but I ran unto an issue I’m not sure how to deal with.

    Rebusted adds a ?ver=-b-modified-[file-last-mod-date] query string to each CSS/JS called, which is great to force browser cache refresh.
    But WP Super Cache (like other page caches I guess) caches the page with the ?ver and won’t update it before the page cache is expired or manually replaced.

    That means when I update a CSS file, I have to refresh my page cache (potentially the whole site) if I want Rebusted to do its job.
    Not sure if it works the same with other page caching systems (WP Rocket, W3 Total Cache, etc.)

    Am I right or am I missing something?
    Thanks

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Simon Prosser

    (@pross)

    Your cache is doing what it is supposed to do, hard caching the page output.

    This tool is for developers to aid editing stylesheets etc when the versions for those files do not change, or for sites on 1c per year hosting that are behind ultra-aggressive server-side caching to pack in the 2 billion sites on their aging panel servers.

    tldr if you are developing your site, turn off the caching

    Thread Starter JawaScript

    (@crimsonguard)

    Hi Simon

    I understand that both plugins do their job, I was just wondering how other devs deal with this.
    Considering my CSS/JS can change almost every day (on the most busy sites I work on at least), that means I should empty the page cache each time…
    Is this what you advise?
    What’s important to me is that users get the latest CSS/JS without sacrificing too much speed.

    Not sure I got the part about cheap hosting though…

    Plugin Author Simon Prosser

    (@pross)

    Are you absolutely sure you need a static page cache? Either you are on a chocolate server or you are getting millions of hits per day?

    Thread Starter JawaScript

    (@crimsonguard)

    Well, that’s the first time I ever hear that one should not use page caching (on static pages at least). xD
    But this is interesting and I’d be glad to read your comments against this comon practice.
    On my clients projects (which are on different types of hosts, including dedicated), I can see the difference in page load with/without page cache.

    Plugin Author Simon Prosser

    (@pross)

    Well it used to be, years ago when I first started using WP, way back in the days when there was no plugins repo! Back then you ONLY added a cache plugin, or enabled the built in WP static cache ( yes it used to exist ) only when your site actually needed it, if you got _slashdotted_ etc.. These day it seems people install WP then install a cache plugin before even adding content lol

    A properly setup budget VPS will handle 1000s of hits per hour. I have a site that gets 30+ hits per *second* that has no caching.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Issue with WP Super Cache’ is closed to new replies.