CK Editor Disappear (cause found) [#1196956]

After upgraded to the newly lanuched (2 days) version 6.x-1.4, the CK Editor disappears sometimes. Firebug caught the below error:
uncaught exception: [CKEDITOR.resourceManager.load] Resource name "tableresize" was not found at "/sites/all/modules/ckeditor/ckeditor/plugins/tableresize/plugin.js?t=B5GJ5GG".
I put the CKEditor files to sites/all/libraries/ckeditor and specifed in the CKEditor module setting page that the path should be "%l" << the library path. However from the error above it seems that the module still try to get the CKEditor files from the folder within the module. After I copy another copy of the files to the folder inside the module, the CKEditor appears again.

Comments

Comment #1

dczepierga CreditAttribution: dczepierga commented 22 June 2011 at 19:40

Status:

Active

» Postponed (maintainer needs more info)

Yes i can confirm this bug, it is related with this issue: #1192676: Fix is_dir() function error and broken pagebreak button
It was fixed and commited to GIT, so pls try last DEV version of CKEditor module and write here does help or not in your case.

Greetings

Comment #2

goldoak jp CreditAttribution: goldoak jp commented 23 June 2011 at 14:29

I tried dev version and it eliminates the error but the editor does not show up on textareas specified.

Reference to include textarea has changed now to include the theme name, so I tried adding that version (with theme name) but editor still doesn't show up where it should.

How do I get it back?

Comment #3

goldoak jp CreditAttribution: goldoak jp commented 23 June 2011 at 14:36

I found that adding the theme name to the include list in the global profile did the trick.

In the default profile the theme name is not added, but the editor now shows for the textareas specified.

Comment #4

Ashlar CreditAttribution: Ashlar commented 24 June 2011 at 19:03

The updated Dev version fixed the problem. Thanks for the help!

Comment #5

dczepierga CreditAttribution: dczepierga commented 24 June 2011 at 19:29

Status:

Postponed (maintainer needs more info)

» Closed (fixed)

Ok so i mark this issue as fixed.

Greetings

Comment #6

jmmec CreditAttribution: jmmec commented 26 June 2011 at 02:53

I picked up the latest "dev" today (6/25/2011) and have discovered another way of creating the bug described above: it seems the Drupal CKEditor is saving the entire path information, which is fine, unless you develop your website on one machine, and then transfer it to another machine with a different directly hierarchy (which is what I do).

When I transferred the site to another server, CkEditor would not display (the error at the top of this thread was displayed in firebug), except I noticed that the directory path given was for my development server, and not for the production server, which explains why the file couldn't be found.

To "fix" the problem on my production server, I went to "Admin / CKEditor" and then clicked "Edit" to edit my profile (e.g. "Advanced") and then clicked "Save" at the bottom. Now CKEditor will display on my production server as expected.

Thanks

Comment #7

jasonabc CreditAttribution: jasonabc commented 7 October 2011 at 23:58

@jmmec - thanks mate. Was getting the exact same issue - in this case it was a DNS change from a temporary access domain (http://someI.P./~mysite/) to a full .com domain name. CKEditor was saving the /~mysite/ path which was hosing it after the DNS had changed. I implemented your suggestion and that fixed it - thanks for posting!

Comment #8

robertstaddon CreditAttribution: robertstaddon commented 28 October 2011 at 20:47

I just upgraded to the latest 7.x-1.4 release and had the same thing happen. CK Editor fields just disappeared. Same firebug error being generated. The "fix" from @jmmec of resaving all my profiles worked perfectly. Thank you!

Comment #9

drasgardian CreditAttribution: drasgardian commented 8 January 2012 at 23:41

Thanks @jmmec for the "fix".

It would be nice if ckeditor just cached those path details so that when moving sites it would only need a cache clear.

Comment #10

jackalope CreditAttribution: jackalope commented 11 January 2012 at 21:28

Status:

Closed (fixed)

» Needs work

I experienced the same problem and JavaScript error after updating to 7.x-1.6; jmmec's solution worked (thank you!) but I agree that something still needs fixing here!