I'm stumped!
ckeditor module 1.1 working for months with ckeditor 3.1.x and drupal 6.17
I upgraded to ckeditor 3.3.1 then it stopped working when the node type is story and you are in edit mode (no issues when you create a new story node).

When I say "doesn't work" I mean the textarea is replaced by the editor, the toolbar is loaded, but I cannot write anything inside (a sort of greyed out), clicking any of the buttons of the toolbar has no effetct, except for the source code button, which works as expected and shows the code.
I attached a screenshot of the issue.

I already tried to:

- switch to the garland theme: same problem

- use different browsers: Firefox 3.6.3 mac, Safari 5 mac, the latest Chromium mac, to no avail

- clear the browsers' cache and remove all cookies… nope

- use a different computer, same thing

Can anybody replicate the issue?

Thank in advance…

CommentFileSizeAuthor
ckeditor-issue.png29.6 KBgabble
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

wwalc’s picture

wwalc CreditAttribution: wwalc commented

Sounds bad. Check: #843610: Spellchecker causing load problems? and try disabling scayt.
Also please try the latest dev release of the CKEditor module.

Let me know if that helped.

gabble’s picture

gabble CreditAttribution: gabble commented

Solved!

I installed the latest dev version of the module.

Adding:
CKEDITOR.config.scayt_autoStartup = false;
to ckeditory.config.js
or:
config.scayt_autoStartup = false;
in the "Custom javascript configuration", /admin/settings/ckeditor/edit/[role]

has no effetct.

Any hints?

wwalc’s picture

wwalc CreditAttribution: wwalc commented

Great! If you have the latest dev then scayt is enabled / disabled in the administration section (in each CKEditor profile).

gabble’s picture

gabble CreditAttribution: gabble commented

At this point I don't know if scayt is the actual culprit.

Thank you man! :-)

gabble’s picture

gabble CreditAttribution: gabble commented

Can I safely update the module to version 1.1 ?

http://drupal.org/node/739534

Does v1.1 include the fixes above?

Thank you… :-)

mistywindow’s picture

mistywindow CreditAttribution: mistywindow commented

I'm having the same problem. I reinstalled Drupal but the problem returned. It seems to be related to content because it affects some nodes but not others.

Deleting the content in Source mode brings the WYSIWYG function back. But pasting the code back in kills it again.

Associated problem. The "switch to rich text editor" link doesn't change to "plain text" so when I click on it I get a second (and third...) rich text window.

Any progress?

dczepierga’s picture

dczepierga CreditAttribution: dczepierga commented
Status: Active » Closed (fixed)

Pls update CKEditor module to DEV version and CKEditor plugin to last version, there everything seems to work.
If u had still problem with it, pls reopen this issue.