CoreMedia Content Cloud v11 Upgrade Guide / Version 2110
Table Of ContentsTill the production-ready release of the new richtext editor in CoreMedia Studio you must still use CKEditor 4 in production. Some classes have been moved to a new package, so you have to adapt your extensions, when you have used these classes.
In CoreMedia Content Cloud v11, there are only a few minor breaking changes related to the richtext editor code. The following
classes have been moved to the new package @coremedia/studio-client.main.ckeditor4-components
:
AddCKEditorPluginsPlugin.ts
AddCKEditorPluginsPluginBase.ts
CKEditor_properties.ts
CoreMediaRichTextArea.ts
CoreMediaRichTextAreaBase.ts
CustomizeCKEditorPlugin.ts
LinkAction.ts
LinkActionBase.ts
PasteContentAction.ts
PasteContentActionBase.ts
PropertiesAction.ts
PropertiesActionBase.ts
RemoveCKEditorPluginsPlugin.ts
RemoveCKEditorPluginsPluginBase.ts
RichTextAction.ts
RichTextActionBase.ts
RichTextActionToggleButton.ts
RichTextArea.ts
RichTextMenuCheckItem.ts
RichTextMenuCheckItemBase.ts
RichTextMenuItem.ts
RichTextPropertyField.ts
RichTextPropertyFieldBase.ts
TableAction.ts
TableActionBase.ts
TeaserOverlayPropertyField.ts
TeaserOverlayPropertyFieldBase.ts
TeaserOverlayStyleSelector.ts
TeaserOverlayStyleSelectorBase.ts
Adjust your dependencies and imports accordingly if you are using some of the plugins, actions or components in your Blueprint code.
The deprecated abstract function registerRichTextSymbolMapping
in
EditorContext
has been removed. Please set symbolFontMapping
in CKEditor-Config via
customizeCKEditorPlugin
instead.