Please follow the instructions posted in the other threads or follow those on the FAQ Page. You just need to force a refresh for the browser to load the right resources.
I did clear the cache form the plugin, that did not help, but clearing te browser cache did the job. However, something like this should not happen after a plugin update in my opinion…..
Thanks, you were just answering before I replied.
Well, great now, thanks for all the extra ‘tools’. 😉
Actually is such a common issue that made it jump at the top of the FAQ page.
Things are pretty simple, the browser tends to cache as much as possible (to optimize speed) and in combination with all sorts of so called “optimizations” (like removing query strings on backend and so on) the results are pretty obvious: disaster and panic. If a plugin author makes a change in a JS file (which is pretty common) and the browser continues loading the older version from cache, the result is pretty obvious.
