Hi,
I just had to upgrade from the TinyMCE module to WYSWYG. A very simple process, I might add.
I ran into a problem, though, which seems tinyMCE specific. When the page loads, the WYSIYWG editor doesn't load. Checking the log I get the following error: Error: this.contentWindow is undefined
The curious thing is that if I Disable rich-text (the same error appears again here), then re-enable rich-text again, the editor loads fine, and the error doesn't re-appear until the next page-load.
This happens both in Safari 3.2.1 as well as Firefox 3.0.7
I'm using WYSIWYG 5-1.1 and TinyMCE 2.1.2
Any thoughts? Is the drupal related, or is it TinyMCE specific?
Comment | File | Size | Author |
---|---|---|---|
#9 | wysiwyg-HEAD.migration-remove.patch | 2.77 KB | sun |
#4 | Picture 1.png | 123.99 KB | moonray |
#4 | Picture 2.png | 65.91 KB | moonray |
#4 | Picture 3.png | 82.38 KB | moonray |
#4 | Picture 4.png | 60.44 KB | moonray |
Comments
Comment #1
moonray CreditAttribution: moonray commentedAdditional info:
The version of TinyMCE we were running before the module switch was also 2.1.2. It broke due to an upgrade of jQuery Update module. I'm guessing this issue is related to jQuery somehow as well.
Comment #2
moonray CreditAttribution: moonray commentedLooks like it's an incompatibility with the settings saved by the old TinyMCE module.
If I edit and submit each profile on http://dia/admin/settings/wysiwyg/profile the error goes away.
So, the migration code probably needs a bit of looking at.
Comment #3
sunCan you post your old tinymce profile configuration, please?
Comment #4
moonray CreditAttribution: moonray commentedFind screenshots attached.
Plus this is the php for the visibility:
Comment #5
sunThank you. Just an idea: Could you also post an export of the tinymce* database tables? (only the two tables prefixed with "tinymce_", defining the profiles and user roles associations) That would make testing and fixing the migration path a lot easier. If you can, please do an _uncompressed_ SQL export and attach it here (e.g. in phpMyAdmin, go to the database; On the table overview page, select the two tables and click on the "export" icon below the table list).
Comment #6
moonray CreditAttribution: moonray commentedMy previously reported "fix" didn't quite work. The only way to get it to work flawlessly was to completely uninstall the wysiwyg module, then enable it and set ip up from scratch.
Below is my mysql output from the old tinymce setup.
(sorry, didn't have access to a phpmyadmin type interface)
Comment #7
moonray CreditAttribution: moonray commentedI've marked this issue as critical. No matter what I've tried, I couldn't get it to work properly.
Reverting to tinyMCE and applying the following pathc got it to work perfectly. http://drupal.org/node/235972#comment-882611
Until this is resolved, wysiwyg is not a usable module.
Comment #8
shaisachs CreditAttribution: shaisachs commentedI am having a similar problem in FF2, FF3, and Safari on the Mac. For the most part I don't see the problem in FF 3 on the PC, but it does show up there from time to time (immediately after deleting/setting up a profile, or when I hard refresh a page using control F5). I think this is also preventing me from saving links, because if the editor shows up fine when I first load the edit form, then I can create links with no trouble. But if I have to click Disable a coupe of times to get it to load, the links don't save.
Relevant details:
Drupal 6.9
TinyMCE 2.1.3
Wysiwyg API 6.x-1.x-dev as of about 2009-04-20 7:45 am
Also using IMCE 6.x-1.1, along with the IMCE Wisywyg bridge module, v. 6.x-1.0
Comment #9
sunRe-considered: We just remove the migration path. tinymce module is old. People who did not migrate yet, have to install from scratch (like everyone else).
Comment #10
sunThanks for reporting! Committed to all branches.
A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.