Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I'm using Drupal 6.6 and just updated to using version 6.x-0.5 of wysiwyg with TinyMCE 3.2.1.1. I have it setup to display the rich-text editor by default.
When I open a create content page that uses the wysiwyg editor, if I click on the "Disable rich-text" link, the editor switches back to the normal textarea; however, if I then try to click on the "Enable rich-text" link, it remains stuck on the textarea and doesn't switch back to TinyMCE.
Firebug reports that "element is undefined" on the following code:
var classes = element.className.split(' ');
in wysiwyg.js at line 158.
The javascript error occurs regardless of whether I'm using Firefox 3 or IE 7.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | wysiwyg-HEAD.one-format.patch | 1.49 KB | sun |
Comments
Comment #1
igwk CreditAttribution: igwk commentedInterestingly enough, the rich-text editor can be disabled and re-enabled just fine as long as the user is logged in as the admin user. If the user is anonymous or authenticated (but not admin), the wysiwyg editor cannot be re-enabled.
Comment #2
sunTrue, confirming. This bug occurs when only one input format is available to the user. getParams(), when invoked by AttachToggleLink(), seems to be unable to find the input format element (a DIV in this case) to parse the parameters from.
Comment #3
sunBetter title.
Comment #4
sunCommitted attached patch to all branches.
Comment #6
livingegg CreditAttribution: livingegg commentedThanks for this patch it worked perfectly. Just an FYI, but it was not included in the 5.x-0.5 version of wysiwyg.