When I try to edit a node in FF3 using FCKeditor, it refuses to update it, the node content just stays the same as it was.
when I press submit I notice firebug giving a JS error, if I quickly press escape (to keep the next page from loading up) I can open firebug and the error shown is the following:

FCKeditorAPI.GetInstance(fckLaunchedJsId[i]) is undefined

personally, I think the excerpt module is causing this
when I disable rich editing before pressing submit, the node does update
when I try to disable rich editing on both the teaser and the body field, only the body-field get FCK disabled, pressing the other "disable rich text..." link causes the following error

oEditor is undefined

when I use Chrome, it acts like it should...

tried digging trough the issue list, but can't find anything related

Comments

soghad’s picture

Title: Unable to edit node in FF3 » Unable to edit node in FF3 (or FF2)

I am having the same trouble with FF2 and the 6.x-1.3-rc1 release.

I am only having the problem on pages where more than one textarea appears.

soghad’s picture

Title: Unable to edit node in FF3 (or FF2) » Unable to edit node in FF3
Version: 5.x-2.2-rc1 » 6.x-1.3-rc1

Scratch the previous comment about FF2. I forgot that I had upgraded. I downgraded to FF2 and everything works fine.

The problem does appear to occur only on pages with multiple textareas, however.

I was not able to reproduce the problem on FF 3.0 on RHEL 5. I'll test on FF3/Mac as soon as possible.

soghad’s picture

There was a patch put into FCKeditor 2.6.3 (FCKeditor Ticket #1907). I was able to correct this problem by undoing the patch, which requires modification of line 38 of the fckeditorcode_gecko.js.

More information is available at:

http://www.fckeditor.net/forums/viewtopic.php?f=6&t=10109&start=10&st=0&...

The patch details can be found at:

http://dev.fckeditor.net/attachment/ticket/1907/1907.patch

wwalc’s picture

I installed the latest Firefox (3.0.1) on WinXP/SP3, Drupal 6.4, FCKeditor module 6.x-1.3-rc1, FCKeditor 2.6.3, CCK 6.x-2.0-rc6.
Created custom content type with 4 text fields and everything works fine (using Garland theme, no other additional modules).

Are you using the latest FF 3?

soghad’s picture

I'm on 3.0.1 XP/SP2 at work and am having this trouble on FF 3.0.1 / Mac at home as well.

I am developing a custom module, but will try CCK and try to match your configuration to see if the problem goes away. If it does, maybe I can figure out what I'm doing differently that is causing the problem.

soghad’s picture

A clean install of drupal w/ FCK + CCK did not solve this issue for me.

wwalc’s picture

@sog_hadgraft: do you perhaps have a test account there so that I could see that bug live? (if possible, use contact form to mail me directly)

soghad’s picture

Good news - I'm pretty sure I've figured out what's going on. Firebug is causing the problem. I found this out after testing on another machine that I'd never touched. After disabling Firebug 1.2.0 on my computer, the problem goes away entirely.

Thanks very much for your efforts on this.

wwalc’s picture

Close, but it must be something else. I have FF 3.0.1 with Firebug 1.2.0, DOM Inspector 2.0.0 and Web Developer 1.1.6 and can't reproduce it.
Perhaps it's Firebug + something else?

soghad’s picture

I uninstalled all other add-ons and still have the problem, but you've helped me narrow it down a little further.

The problem seems only to occur when the Firebug script debugging panel is enabled. If I disable that, all is well. I also tried this on a "clean" computer that has not been used for development and got the same result.

wwalc’s picture

Wow... while working on some other issue, I've installed a different theme (Zen Classic sub-theme) and now I can confirm that I'm seeing exactly same error.
I have custom content type with 4 text fields, FCKeditor loads on all of them, but when I try to switch from FCKeditor to plain textarea I get a javascript error.
It happens only on a second or third textarea (randomly), only when Firebug is enabled and only in FF3.
Reverting patch 1907 solves this issue.

Some more details: FCKeditor_OnComplete( editorInstance ) is executed four times (as expected), but in line 89 of fckeditor.utils.js oEditor is undefined. After further debugging it turned out that FCKeditorAPI is defined, but FCKeditorAPI.GetInstance( js_id ) does not return a valid object.

WiredEscape’s picture

Drupal 5.10
FCKeditor 2.6.3
FCKeditor-module 5.x-2.2rc1
ZEN 5.x-1.1
WinXP/SP3
Firefox 3.0.3

Also experiencing this problem.

Getting “oEditor is undefined in fckeditor.utils.js line 62” javascript error.

Inconsistently won't switch to plain text editor or save page. Only on pages with 2 or more textareas. Error thrown when clicking on “Switch to plain text editor” link for other than the first textarea. If the 2+ textarea does switch to plain text editor, the page will save. If textarea element is excluded in profile Visibility settings no errors. Firebug on or off makes no difference.

No errors with IE7.

paulmckibben’s picture

I get the same issue with:
Drupal 6.4
FCKeditor 2.6.3
FCKeditor module 6.x-1.3-rc1
custom theme
Firefox 3.0.3
Ubuntu 8.04 (Hardy)

With multiple text areas in a CCK node type, I have the same "oEditor is undefined" error when I try to switch to plain text. Also, I am unable to save the node.

Switching to FCKeditor 2.6.2 seems to take care of the problem. At the moment, my multiple text areas seem to be working.

wwalc’s picture

Priority: Normal » Critical

Similar issues reported on dev.fckeditor.net:
http://dev.fckeditor.net/ticket/2519
http://dev.fckeditor.net/ticket/2529
http://dev.fckeditor.net/ticket/2566

Probably it has something to do with this changeset: http://dev.fckeditor.net/changeset/2188
If anyone is able to check if reverting this change in 2.6.3 solves this problem then let me know.
Remember that when you change the code in _source directory, it is not loaded automatically, more info can be found here: http://docs.fckeditor.net/FCKeditor_2.x/Developers_Guide/Customization/S...
Basically, you should go into "modules/fckeditor.fckeditor/editor" directory, backup fckeditor.html file and rename fckeditor.original.html to fckeditor.html. Note that this will slow down FCKeditor significantly.

wwalc’s picture

wwalc’s picture

yang_yi_cn’s picture

Is that change made in fckeditor cvs fixing it?

http://dev.fckeditor.net/changeset/2562

wwalc’s picture

Yes, it should fix it. You can try the latest "Nightly Build" of FCKeditor and report your findings. Remember to clear browser's cache after upgrading.

wwalc’s picture

Status: Active » Fixed

I have checked the nightly build of FCKeditor and cannot replicate this issue anymore.
Marking as fixed, please either download the nightly build or wait for 2.6.4 (http://www.fckeditor.net/download).

Feel free to reopen this issue if you're still experiencing the same problem in FF3 after upgrading (and clearing browser's cache).

seutje’s picture

awesomeness!!

Bartezz’s picture

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

pragna’s picture

Assigned: Unassigned » pragna
Category: bug » support
Status: Closed (fixed) » Active

hello

I faced same problem , but I solved it. That is occured by use of firebug. In ff browser click on firebug icon and disable

"console panel is disabled"
=>console
=>script
=>Net

you can solve your problem by using above way.

seutje’s picture

Assigned: pragna » Unassigned
Category: support » bug
Status: Active » Postponed (maintainer needs more info)

pragna, are you sure you're using the latest version of FCK (and I don't mean the drupal module)?

turning off firebug is hardly a fix if you ask me

putting it back to unassigned bug report

pragna’s picture

hi
yes, I am sure and no need to turning off firebug but if you enable

"console panel is disabled"
=>console
=>script
=>Net
above option in firebug then just disable it and try once.

wwalc’s picture

Status: Postponed (maintainer needs more info) » Fixed

This issue existed in 2.6.3 and has been fixed in the latest version of FCKeditor (the editor). Please reopen this issue only if you confirm that this bug still exists in 2.6.4 Beta.

seutje’s picture

yeah that's what I was thinking, I've tried endlessly but I can't replicate this bug anymore

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.