Closed edwinsiebel closed 7 years ago
Good catch!
Glad to help.
Will you be commiting the fix to the WordPress repo soon? Then we can update our sites using the plugin, without clients needing to cleanup their cache files.
@goldenapples has access to that
Thanks for catching this. I can push it to the repo later today, but unless the version number is bumped again, it won't show as an automatic update, so I'm not sure if it'll fix the problem for end users. We'll have to release as 0.7.3 I believe.
We pull it in via wpackagist so I guess that will work for us, however no for all the other who work via automatic updates. Guess a version bump will be necessary.
Don't forget to update the SHORTCODE_UI_VERSION as well :cheeky:
We'll have to release as 0.7.3 I believe.
Maybe we could modify the current tag and and trunk.
Maybe we could modify the tag's and and trunk's source.
That could be worth the try.
I'll give that a shot. It won't register as an auto-update for users who have already updated to 0.7.2, but it will make any new updates bust the browser caches automatically.
This is updated in the plugin repository now: https://plugins.trac.wordpress.org/changeset/1649978/
@goldenapples, thanks that worked perfect for us!
The SHORTCODE_UI_VERSION should also be updated accordingly, to cache bust the affected javascript file(s) in the latest version (0.7.2).