Drupal 7.14 - CKEditor was working fine, and quote literally suddenly and unexpectedly stopped appearing. I tried to upgrade, uninstall and reinstall, and checked all of my permissions and settings. I also tried the "new user" trick that I've seen throughout the CKEditor issue queue.

In an attempt to identify the issue I inspected the page element and checked the console to find these errors:

Failed to load resource: the server responded with a status of 406 (Not Acceptable) http://MYSITE.com/misc/jquery.cookie.js?v=1.0
Uncaught TypeError: Object function (j,s){return new b.fn.init(j,s)} has no method 'cookie' toolbar.js?mrla2l:29

Thank you for your assistance!

Comments

Looks like you don't have the mentioned file on the server or maybe it was somehow corrupted during the update. Did you try to upload it again?

Are you referring to the jquery.cookie.js file? That is in place and has been manually updated. That should not be the cause of the issue.

Is there a chance this could be the result of a hosting config change?

Category:bug» support
Priority:Major» Normal
Status:Active» Fixed

It's your server problem. The required jquery.cookie plugin does not load and causes error, which breaks JS so the editor does not appear.

Sent it off to hosting, let's see if they can get it fixed - thank you

FIXED - confirming that this was a hosting issue and has been resolved - thanks to all for your help!

Status:Fixed» Closed (fixed)

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

Status:Closed (fixed)» Active

Opening this back up.

I am experiencing this issue a second time now. The first time the hosting provider disabled mod_security plugin and resolved the issue. I am now with a different hosting provider and just had the site migrated to a dedicated server where I am now experiencing this problem. The hosting provider tells me it is not a server issue and that there is no way they could be the source of the problem, but the support guy I've been assigned does not seem to be the brightest crayon in the box. Are there any other alternatives to solving this or ways to quickly and easily diagnose the source of the issue? Or do I just need to throw this back at support and have them escalate the issue? It seems to me that the migration was the source of the issue.

Thanks!

Status:Active» Closed (fixed)

Closed and fixed again - hosting was just being stubborn - got the right guy, fixed it in a jif