Hi,
I have created a block called quote, and in the backend it calls the CSS like this:
https://example.com/wp-content/themes/theme-name/blocks/quote/quote.css?ver=6.4.2
The 6.4.2 is the current WordPress version.
But this causes issues because I want to update the file, but the file is now cached in browsers. How can I force this to change the version number?
Thanks
Shaun
If you are using block metadata as described here then you will need to alter the url string the version https://developer.wordpress.org/block-editor/reference-guides/block-api/block-metadata/ using a filter on this hook https://developer.wordpress.org/reference/hooks/style_loader_src/ this page has an example of removing the version https://wpadminify.com/kb/how-to-remove-version-from-style-and-script-from-page-source/.
If you are calling call wp_enqueue_style() directly then you can supply a version values.
You’ll also need to version your css file and change the version number every time you update it.
Yes, I noticed this too @shauny and thanks @hube2 for the info. Adding what I’ve found to this to hopefully help. First up, this is a known issue apparently. So, if anyone wants to follow it or contribute to fixing it, please check it out.
Until it is fixed, if you are simply removing the query string as John mentioned, your browser like will still cache the CSS file (mine does, so I have to resort to CTRL+F5 hard refresh on every change). You really do need the automatic cache busting that WP already does for JavaScript assets added in block.json. Until then, the only other thing you can do is add and adjust the “version” setting in your block.json file each time you change something. That would mean doing something like this:
"version": "0.1.3"
