Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Beginning on September 9, 2022, this module's dependency on Drupal core's ckeditor module is now reinterpreted as a dependency upon the contrib ckeditor module as a result of Ensure that ckeditor does not get special core treatment. This is a change in Drupal.org's infrastructure and does not reflect any changes made by this module. As a result, it is no longer possible to support the core version of ckeditor.
When updating to 8.x-3.x from 8.x-2.x, there is no automated upgrade path. Site owners will need to manually verify and update their site configuration. In most cases, only minor changes will be required.
The difference between the two branches is that 8.x-3.x supports JSON objects and arrays and 8.x-2.x does not. As a result, the config values must now be formatted as valid JSON.
Beginning in 8.x-2.1, CKEditor settings are now added using hook_editor_js_settings_alter(), which means they are added after all CKEditor Drupal plugins have provided their settings. This guarantees that settings defined by CKEditor custom config override settings provided by CKEditor Drupal plugins. Previously, this was not the case, specifically with regard to core's Internal plugin. The following settings can now be managed with CKEditor custom config without the use of a core patch:
Note about update.php:
The primary difference between CKEditor custom config 8.x-2.x and 8.x-1.x is that custom configuration is now stored with the configuration of individual editors instead of being stored globally. During the upgrade process, the global configuration is copied to all CKEditor editors.
The primary difference between CKEditor custom config 8.x-2.x and 8.x-1.x is that custom configuration is now stored with the configuration of individual editors instead of being stored globally.