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.
When enabled boxes with CiviCRM and ckeditor, it breaks CiviCRM WYSIWYG as CiviCRM is using its own copy of ckeditor.
The culprit is boxes' hook_footer() that adds "window.CKEDITOR_BASEPATH" to every page.
Comment | File | Size | Author |
---|---|---|---|
#2 | boxes_civicrm_wysiwyg_conflict-2175471-2.patch | 818 bytes | kienan |
#1 | boxes-civicrm_wysiwyg-2175471-1.patch | 1.61 KB | ckng |
Comments
Comment #1
ckngSee attached patch.
Comment #2
kienan CreditAttribution: kienan commentedRe-rolled the patch to apply against latest 7.x-1.x-dev.
Comment #4
happysnowmantech CreditAttribution: happysnowmantech commentedI encountered this problem, applied the patch, and verified that it resolved the issue.
Other symptoms of this bug include browser console errors similar to this:
Also updating the issue title to add more info.
Comment #5
happysnowmantech CreditAttribution: happysnowmantech commentedComment #6
adixon CreditAttribution: adixon as a volunteer commentedConfirming the rerolled patch resolved my identical issue, also reported here: https://civicrm.stackexchange.com/questions/25955/unable-to-use-ckeditor...
Curiously - the issue did not arise on the affected site until last week, though I've been using CiviCRM and boxes on it for serveral years.
Comment #7
jackalope CreditAttribution: jackalope commentedConfirming that as @happysnowmantech and @adixon say, patch #2 fixes Boxes issues with CiviCRM.
In my situation the text fields for "Pre-form Help" and "Post-form Help" on profile settings pages were mysteriously disappearing before I applied the Boxes patch, even though those no fields on that Civi screen use CKEditor or any other WYSIWYG!
Comment #8
jackalope CreditAttribution: jackalope commentedAh, actually never mind that last bit--turns out those profile fields do indeed use the WYSIWYG, which is now working properly thanks to that Boxes patch! (Not sure why the patch is failing tests, though...)
Comment #9
jadag88 CreditAttribution: jadag88 commentedI'm still having this issue with Drupal 8 and CiviCRM 5.27.3. On the data entry forms for CiviCRM contribution pages and event pages, some of the input blocks are set to be hidden (e.g. Complete Description, Introductory Message, Footer Message), so no information can be input or changed. Drupal has made CKEditor part of core, but CiviCRM still has its own version of CKEditor. I can't find a way to make this patch work with our situation. What I ended up doing is turning off CKEditor in CiviCRM/Customize Data and Screens/Display Preferences--I changed Wysiwig Editor to Textarea. That leaves CKEditor from Drupal available for Drupal text entry and I will have to enter my own html for Civi text.