TinyMCE cache isn't dumped when new plugin is added

[Viper007Bond]

When a new TinyMCE plugin is registered, the cache should automatically be broken so that users don't have to hard refresh or dump their browser cache.

[Viper007Bond]

If someone uses my Viper's Video Quicktags plugin, dumps their cache so the buttons show up, and then disables my plugin, TinyMCE throws an error and won't show up unless the user clears their cache again.

This really needs to be fixed.

I'm thinking we tag a MD5 of the TinyMCE version, plugins, buttons, etc. onto the end of the URL much like we do with the cache file. That way if anything changes, it changes the JS URL much like the script loader does.

[DD32]

It appears that at least NextGen gallery uses the filter 'tiny_mce_version' to implement cache-busting capabilities.

It looks like to do it automatically would require to duplicate parts of tiny_mce_config.php or move parts of it into a seperate function in order to tell whats activated and what isnt. (Or, I guess just call the tinymce filters and md5 the result) - But given its part of tinyMCE itself, it doesnt seem worthwhile to mangle with its internals too much to that extent..

[Viper007Bond]

I'll definitely make use of that feature, although I think it'd be best if it was automatic. A simple MD5 of all of plugin/button filters though would solve it I'd think.

[azaozz]

The tiny_mce_version() is exactly for that and currently is being passed to all external components (js, css, html) for the editor. Also the compressed server side cache is now gone making it easier to refresh only the needed files and the init array is being generated from php (so it's always fresh).

Closing as invalid as the method of loading TinyMCE has changed, feel free to reopen if needed.