Understanding Version used in query strings

  • Hi, I’m sorry if this has been answered previously but I couldn’t find it. I recently switched a site from using W3TC to WP Rocket. One difference I noticed is that W3TC seemed to add it’s own unique value to the query string for static resources like css and js files. This value would be changed every time I “busted” the browser cache by selecting “update media query strings”.

    With WP Rocket, this doesn’t seem to be the case, it uses (or rather leaves) the default query string like “?ver=2.1.8”.

    My question is, if I manually update a file (ex. a stylesheet) and then upload it via SFTP…how can I increment that to ?ver=2.1.9 so that it will “bust” the browser cache of return visitors?

    For example, if I didn’t even use a plugin and simply added the expires headers in my htaccess manually, then whenever I updated a file manually how would I ensure it had a new “version” reflected in the query string? From what I can see the version is hard coded to the version of the plugin or theme which owns the file, I’m not sure if I can alter this? Do I just adjust the commented version within the file itself?

    Thanks to anyone who can explain this to me! I wish WP Rocket would simply append the unix timestamp for the last modified date/time of each file, that would make it so much easier…

Viewing 1 replies (of 1 total)
  • Moderator bcworkz

    (@bcworkz)

    There should be some way to flush the cache so that a new cache is rebuilt from your updated files, regardless of what version number appears. I would expect that new cache will send the proper headers to cause browsers to refresh their content. The details of what happens are unique to WP Rocket, so if you need further explanation or confirmation, I suggest you inquire at the dedicated support forum for WP Rocket.

Viewing 1 replies (of 1 total)
  • The topic ‘Understanding Version used in query strings’ is closed to new replies.