Module not compatible with newest version of TinyMCE?

Posted by datenwerk_vienna on October 19, 2010 at 1:14pm

I just installed WYSIWYG 1.33.2.11 on a fresh Drupal 6.19.
I wanted to use it in combination with TinyMCE, so I downloaded that too (version 3.3.9.2), unzipped it and uploaded it to the specified folder (sites/all/libraries/tinymce).
However, I cannot really TinyMCE, as WYSIWYG tells me following error: "The version of TinyMCE could not be detected."
I double-checked all the paths and it seems right to me, even the library can be found under the specified path (sites/all/libraries/tinymce/jscripts/tiny_mce/tiny_mce.js).
Whats the problem? Is the module not compatible with the newest version of TinyMCE anymore?
Or have I made a stupid mistake which I cannot see?

Cheers

Comments

It's simple

Posted by TwoD on October 19, 2010 at 3:00pm

The problem is simple; Wysiwyg could not detect the installed version of TinyMCE, just like the message says. You've most likely installed it correctly, or it would be listed as "Not installed", but when Wysiwyg attempted to figure out what version it is, it found no version string in TinyMCE's files.

Wysiwyg checks the beginning of the minified main TinyMCE file, but since it's all one line we don't want to read all of it into a variable for comparison so we just take the X first characters.

What has happended is simply that the new minor version of TinyMCE pushed the version information further into the file than we had anticipated, so Wysiwyg misses it.
This was fixed by increasing the number of read characters to 200, to give some room for future offsets. That fix was comitted to CVS and is now part of the -dev snapshots.
This minor version just fixes bugs so no further changes were needed.

When Wysiwyg is unable to determine the installed version of an editor I would recommend trying with an older release of that editor. If that is not acceptable - say the release fixed a bug which was causing you major problems - I would recommend to first test the latest -dev snapshot to see if this has already been fixed. If not, check the issue queue for recent issues related to the editor (filter using the Component field). If none can be found, the please file a new one to alert us about this. We might just have missed that there was a new release out.

Creating patches for compatibility with new minor versions of an editor is usually very easy and takes short time. A new major version might introduce a new API, do we'll have to rewrite the JavaScript part of the integration, which of course takes a bit longer...