Hi there
wishlist’s assets are always included using plugin’s version, in order to bump assets any time a new update comes
So it shouldn’t be required to clear browser cache in order to load latest version of the plugin assets
Are you sure the problem comes from one of our assets? Are you removing assets versions from urls using any dedicated tool?
Thread Starter
wpawd
(@wpawd)
We hide the wordpress version from the html with a security plugin, but thats all, no other assets are removed.
Still, this worked fine before the update of wishlist. After the update it works only when we do not hide the wordpress version with the plugin. When we hide the wp-version, then the browser cache has to be deleted to make it work again. Which we can do, but not the user. Also, we cleared all server caches which could potentially serve outdated content. Does not help either.
After the update it works only when we do not hide the wordpress version with the plugin
We include all plugin’s assets with plugin’s version, not WP one (that would be default if you do not specify any asset version)
Are you sure this same security plugin doesn’t remove version from all assets?
That would explain the problem: asset url should automatically change any time a new version of the plugin is installed, and that should be enough to force browsers download a new copy of the scripts/stylesheets
If you remove versions from your urls, to improve caching, this is a to-be-expected side effect
Anyway, apart from increasing assets version, there is not much that we can do to prevent this kind of issues on plugin’s side
