CKEditor not working on any page/form

[Coleman Watts]

Unfortunately I can't tell much from that trace either - seems to be all internal functions and I don't see any reference to Civi code. Any chance of logging into your site to poke around?

[emilyf]

Finally resolved this one. Took my civi install to a clean Drupal 7 site and error did not persist, so at that point knew there was some change in Drupal code on my site causing the problem. After quite a bit more troubleshooting narrowed it down to a bug in boxes module. We have submitted a patch to fix this here:
https://drupal.org/node/2175471

[emilyf]

Interesting, this fix resolved it for me on Civi 4.4 but after I apply the fix to my 4.3.5 site and go to display settings to set "ckeditor" back, the change won't take. It just sticks at "tinymce"...have you seen that problem before? I am going to upgrade this site tonight to 4.4 but am wondering if this inability to select it is a bug with 4.3?

[emilyf]

Sigh.

I just completed the upgrade to 4.4.3 on my site, and still no matter how many times I try to resave civicrm/admin/setting/preferences/display?reset=1 to use ckeditor, it sticks at "tinymce". I have cleared templates_c as well as my drupal cache.

Can I force change this in the database somewhere?

[emilyf]

After waiting 30 minutes, ckeditor has just appeared. I have no idea what finally caused the change to "take"...I had cleared templates_c, cleared my full drupal cache. Made no other changes on the site, just came back about 30 minutes later and it was looking correct. That seems odd to me, so I wanted to post this back up as the behavior doesn't seem like it should not take the change on the display preferences page. Seems to me that is buggy behavior...has it been seen before?

[Coleman Watts]

I've seen something similar - after an upgrade the editor sometimes disappears and only comes back after clearing caches and/or switching to a different editor and back again. So far it's been to elusive to find the cause. As with your situation, it always ends up working properly after a bit of fiddling and then we lose motivation to try to break it again

[lolas]

I had this problem on one site which was upgraded from 4.1.6 to 4.4.6. The older version used the kama skin and the newer version used the moono skin.

Cleared all the caches, it was near the end of the day so I came back to the site the next day and the problem still showed. Finally it turned out to be a browser caching problem and clearing the browser cache or switching to another browser worked.