Using Wysiwyg 6.x-2.0 my admin/settings/wysiwyg page has
Filtered HTML TinyMCE 3.2.4.1 Edit Remove
Full HTML TinyMCE 3.2.4.1 Edit Remove
PHP code no editor
When I attempt create (or edit) a page I see no Rich Text editor. There is the link Disable rich-text and when I click on it I see:
Drupal.wysiwyg.instances[params.field] is undefined
http://yoursite.co.uk/sites/all/modules/contrib/wysiwyg/wysiwyg.js?L
Line 162
Drupal.wysiwyg.instances[params.field].editor = 'none';
Something is wrong here. :(
Comments
Comment #1
hershel commentedI now installed FCKeditor 2.6.4 and the editor works. Clicking the Disable rich-text gives the same error, but it works--both disabling and enabling work.
The error is not precisely the same actually. Now it's:
on line wysiwyg.js?L (line 128) whereas the error with TinyMCE is on line 162. Both errors appear actually, at different times.
Comment #2
twodThat's a bit odd, looks like the editor instance parameters were not registered by Wysiwyg API when the editor was attached.
Do you have any other modules which change things on the edit node page, or which runs a lot of JavaScripts?
Have you tried disabling all buttons and plugins? That should return the editor to the default toolbar in which it should always work.
If you have the Firebug extension for Firefox, could you please put a breakpoint right on the line where the error is, and reload the page.
That should stop script execution there so you can see what the value of
paramsis at that moment.You could of course also edit the file and insert some code to alert/print out the variable. But it's supposed to be an object with several properties so it's easier to set a breakpoint and use Firebug's watch feature.
Comment #3
twodI'd like to figure this out as soon as possible but I'm afraid I can't do much without more info.
Comment #4
hershel commentedSorry didn't see your comments til now. Now that I have FCKeditor on the site, if I enable TinyMCE, nothing happens--no error yet also no tinymce. Just a regular textarea.
If you want to examine the site in question, email me offline.
Comment #5
twodI'll send you an email when I get back home after the weekend.
Until then I've got some more questions and I need to repeat some.
Do you use a custom theme? If so, does it print out the contents of the PHP variables correctly so all scripts are included (see FAQ)?
Have you tried with Garland and disabling all the buttons/plugins?
Which exact version(s) of TinyMCE did you test with?
Was it working with an earlier version of Wysiwyg module?
Comment #6
hershel commentedUsing zen subtheme. Of course all scripts are included. Otherwise FCK wouldn't work. :)
> Have you tried with Garland and disabling all the buttons/plugins?
No.
> Which exact version(s) of TinyMCE did you test with?
The latest download from their site, as of last week.
> Was it working with an earlier version of Wysiwyg module?
On other sites yes, I believe so. This is a brand new site, so no, not here.
Comment #7
sunThen please test with Garland first.
Comment #8
hershel commentedUsing Garland and TinyMCE has no buttons nor plugins enabled. I disabled these modules:
Nice Menus
Thickbox
Hierarchical Select Taxonomy
Hierarchical Select
just in case. Still FCK works fine and TinyMCE doesn't work. Now however I don't see an error--it just doesn't work--nothing happens. Behavior is the same with Garland or my Zen sub-theme.
If I browse to /sites/all/libraries/tinymce/jscripts/tiny_mce/tiny_mce.js I see
var tinymce={majorVersion:"3",minorVersion:"2.4.1",releaseDate:"2009-05-25"Comment #9
sunIt seems you are the only one who is able to replicate this issue, so I can only guess that you have some other, conflicting modules installed.
Sorry, without further information this issue can only be marked as won't fix.
Feel free to re-open this issue if you want to provide further information. Thanks.
Comment #10
haggins commentedI've got exactly the same issue. There's a fresh drupal 6.19 installation with only Wysiwyg module enabled and TinyMCE doesn't show up. Only the "Disable rich-text" link is shown.
Comment #11
haggins commentedHa! Got it! It's because WYSIWYG settings page provides selection of many languages that aren't really available. So i choose "de" and got a lot of log entries like this one:
Maybe the ui should only provide a selection of installed languages?
edit: closing this issue again since there is already an issue about limiting language selection: #362318: Limit wysiwyg language selection to available languages
Comment #12
haggins commented