Part of Backdrop Core Since v1.2

The CKEditor module for Drupal is no longer needed for Backdrop CMS.

The ability to use a Rich-Text editor has been included in Backdrop since version 1.2.

Upgrade Instructions: 

There is no upgrade path for the CKeditor module yet. Please follow this issue for progress on the upgrade path. Until the upgrade path is complete...

If you are running the CKeditor module on a Drupal 7 site:

  1. Note the editor configurations you have applied to each editor, and which editor is applied to each text format.
  2. Disable and Uninstall the CKeditor module from Drupal 7.
  3. Upgrade your site to Backdrop CMS.
  4. Manually re-configure your text formats in Backdrop to match your notes form step 1.

Caution when switching an existing site from no text editor to CKEditor

When Backdrop uses no Text Editor for long text fields, the text is saved without any filtering. This is deliberate and based on the philosophy that Backdrop should preserve the original text input in the database. (See more in the documentation page on "Text Formats, Editors & Filters.")

So, for example, when "Convert line breaks into HTML (i.e., <br> and <p>)" output filter is enabled when a text format uses no text editor (as in the "Filtered HTML" text format), the HTML tags will not be saved in the database. Instead, the output filter will add them at display time.

However, when a site is set up with a Text Editor -- such as CKEditor -- enabled, that situation changes. CKEditor does save the line breaks as HTML tags in the database.

One problematic consequence occurs when a site with many nodes saved without a text editor then enables CKEditor, and then someone goes to edit one of those previously-saved nodes. At this point, CKEditor will pull the old field data from the database, and will combine all the text without HTML line break tags into the same paragraph. An old node with only paragraphs in it will suddenly have only one paragraph containing all the text.

There is currently no automated way to fix this. Some suggestions are posted at forum thread, "Editing nodes makes them lose formatting".

Site administrators should be aware of this potential problem that could result from changing text format settings to include the use of a Text Editor and weigh the difficulty against the benefit of much easier node editing.