Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
In admin/config/development/performance , choosing Javascript aggregation option has the effect that all CKEditor buttons disappear from all content edit pages.
Comments
Comment #1
marie_k CreditAttribution: marie_k commentedI have the same problem - does anyone know how to fix this?
Comment #2
jason.price CreditAttribution: jason.price commentedI am having the same issue, whenever I check aggregate JavaScript under performance CKEditor and other WYSIWYG editors disappear. What i also find is many of the items which before in the admin theme that where hidden or minimised are now unhidden, and some of the administration panel items, such as editing a user is now far longer in comparison. What would cause all this to heppen, to me this appears to prevent all JavaScript from running correctly.
Comment #3
HansKuiters CreditAttribution: HansKuiters commentedIs this issue addressed yet? I have this problem in 7.x-1.14.
Comment #4
EgbertB CreditAttribution: EgbertB commentedsame here
Error: TypeError: $.ui.dialog.overlay is undefined
Error: TypeError: Drupal.ajax is not a constructor
Comment #5
tlangston CreditAttribution: tlangston commentedSame here but using Wysiwyg with ckeditor source in library - not the drupal ckeditor. Exactly the same issue.
Comment #6
GoddamnNoise CreditAttribution: GoddamnNoise commentedSame problem here using ckeditor in libraries directory and the last version of the module (7.x-1.16)
Comment #7
wwalc CreditAttribution: wwalc commentedGo to admin/config/content/ckeditor/editg - scroll down to the bottom and find there "Aggregate ckeditor.js". Is it disabled in your installation? If it's enabled, then disable it so that ckeditor.js was skipped during aggregation.
Comment #8
GoddamnNoise CreditAttribution: GoddamnNoise commentedThe CKEditor aggregation is disabled. Once I found out that disabling javascript files aggregation it worked but it didn't when that aggregation was enabled, i've been digging a little deeper. I've found that the problem was a javascript file in a custom module. That javascript file was raising a Javascript error. This was preventing the rest of the aggregated javascript file to be executed and preventing CKEditor to load when javascript aggregation was enabled. I've fixed the javascript error and now CKEditor works ok with or without javascipt files aggregation enabled.
Comment #9
wwalc CreditAttribution: wwalc commentedThat's a very good point. Since "Aggregate ckeditor.js" is disabled by default, the most probable reason why CKEditor does not load when aggregation is enabled is a JavaScript error in other aggregated scripts.
Comment #10
GoddamnNoise CreditAttribution: GoddamnNoise commentedYes. Agree!.
Comment #11
Fiable.biz CreditAttribution: Fiable.biz commentedSo, how to find Javascript errors in contributed modules? And first, how to know which Javascript file is the culprit? Sorry for this question, whose answer seems probably obvious to many of you.
Comment #12
GoddamnNoise CreditAttribution: GoddamnNoise commentedYou can disable Javascript files aggregation and use Firebug or the browser's developer tools to see the Javascript console. If there is any javascript error, you will probably see it in the Javascript console, which will tell you the javascript file where it is happening.
Comment #13
wwalc CreditAttribution: wwalc commentedIf the JavaScript error occurs only when the aggregation is enabled, it might be a bit harder. You should still be able to see an information in the error console what part of code caused the issue. You should be able to locate what aggregated "source" file caused it, by searching for the same code in all files of your Drupal project. At least in theory, I did not have a similar issue for a long time.
Comment #14
PeterMK85 CreditAttribution: PeterMK85 commentedReopened the issue.
Comment #15
PeterMK85 CreditAttribution: PeterMK85 commentedProblem still persist:
Drupal 7.34
CKEditor (as module and in a modules'folder) / CKEditor 4.4.6
AdvAgg 7.x-2.7
Adminimal theme 7.x-1.5
If JS agg turn on, the CK loader not loading no JS errors in the console. Tried to turn on/off the CKeditor's aggregation option.
Anyone any idea?
Thx
Comment #16
Jieyyal CreditAttribution: Jieyyal commentedDisable Enable advanced aggregation option Or
Disable picture module seems fix this issue.
Still don't know why.
Comment #17
Pierrere CreditAttribution: Pierrere commentedI managed to get everything working with disabling this option in AdvAgg:
"Move all inline scripts to the bottom of the execution order" - (admin/config/development/performance/advagg/mod)
On a side note:
Disabling "Remove unused JavaScript tags if possible" helped to load CKEditor even with the above option enabled but still had problems inserting images via the "Insert" module. The editor was fully functional, but I could not manage to insert images. That script was terminally broken.
On another side note:
Bumping the admin interface down to Jquery 1.5 (without adjusting AdvAgg values) also helped loading the editor, but the insert error from above was also present.
For me and my customer, this is a much better option than to completely disable and then re-enable AdvAgg if they want to edit something. Choose your "solution" accordingly.
Comment #18
nghai CreditAttribution: nghai commentedIn my case the option : "Move all inline scripts to the bottom of the execution order" - (admin/config/development/performance/advagg/mod) was already disabled and none of the other options on that page is enabled still the bug is there.
As far as the JS aggregation is enabled the ckeditor does not load.
This problem should be because of any other JS error as mentioned in comment-8 or some conflicts with Advance aggregation module.
Comment #19
Rick Hood CreditAttribution: Rick Hood commentedThis is old but just reporting I had same issue and choosing Development (uncompressed) here fixed it: admin/config/development/jquery_update
That allowed me to aggregate JS without issues. Not sure why.