Studio Developer Manual / Version 2310
Table Of ContentsUpgrading to CKEditor 5 may be effortless, when you neither adapted content forms in CoreMedia Blueprint nor adapted the CKEditor 4 integration. The more adaptations you applied, the more complex an upgrade from CKEditor 4 to CKEditor 5 may get.
This section will guide you through the upgrade processes as good as possible with the following assumptions:
You received CoreMedia Blueprint with CKEditor 5 enabled by default.
To untangle upgrade to CKEditor 5 from general development in CoreMedia Studio you downgraded to CKEditor 4 for production use as described in Section 10.2.1, “Downgrading to CKEditor 4”.
In previous versions you added custom forms based on CKEditor 4 components, such as the
RichTextPropertyFieldbased on CKEditor 4.You applied Studio plugins to conditionally change the appearance of certain editors in CoreMedia Studio content forms.
You applied custom configuration based on CKEditor 4 plugins provided by CoreMedia, such as custom mapping for symbols on paste.
You added plugins provided for CKEditor 4 and adapted the integration into CoreMedia Studio especially by adapting the toolbar based on Ext JS.
You have developed custom plugins for CKEditor 4, integrated them to CoreMedia Studio and adapted the toolbar based on Ext JS accordingly.
If any of these do not apply, your upgrade path is shortened, and you may skip the corresponding section.
