Release Notes / Version 11.2310
Table Of ContentsRemoval: Deprecated TabManager Classes/Interfaces
The following deprecated classes/interfaces have been removed from `editor-components`:
TabManager
TabManagerImpl
Follow Section, “Removal: Deprecated TabManager Classes/Interfaces” for upgrade information.
(CMS-19921)
Removal: CommerceConnection#getVendorXXX Methods
The following methods of the interface
com.coremedia.livecontext.ecommerce.common.CommerceConnection
were removed without replacement:
getVendorPropertiesgetVendorVersiongetVendorUrl
(CMS-19750)
Removal: Studio Packages Proxy App
The Studio Packages Proxy App has been removed. The new plugin mechanism can be used instead. See documentation for details.
(CMS-19698)
For contents having a data-property, the links for those blobs are now rendered instead of simple content links
Render links for blobs in the headless richtext instead of the previous content links which weren`t optimal for content types like CMDownload or CMPicture where you might just be interested in the link to the data.
(CMS-19669)
Removal: Legacy Search Facets API from Studio
The support for the legacy commerce search facets had been removed from the Studio client and backend. The facet editor for product lists does only support the multi-facet selection from now on.
Follow Section, “Removal: Legacy Search Facets API from Studio” for upgrade information.
(CMS-19295)
Studio Client Resource Bundle Changes
In the process of pulling features out of the editor-components module in order to make them available for the new Workflow app, many changes to resource bundles had to be made (these changes are in addition to the changes that happened due to the new content type localization mechanism). As the list is too extensive for a release note, we refer to this link to a Coremedia Help Center article.
(CMS-18728)
Moved: Modules Moved to new Package
The following modules have been moved to the new npm package
@coremedia/studio-client.main.ckeditor4-components
LinkAction.ts
LinkActionBase.ts
PasteContentAction.ts
PasteContentActionBase.ts
AddCKEditorPluginsPlugin.ts
AddCKEditorPluginsPluginBase.ts
CoreMediaRichTextArea.ts
CoreMediaRichTextAreaBase.ts
CustomizeCKEditorPlugin.ts
RemoveCKEditorPluginsPlugin.ts
RemoveCKEditorPluginsPluginBase.ts
CKEditor_properties.ts
PropertiesAction.ts
PropertiesActionBase.ts
RichTextAction.ts
RichTextActionBase.ts
RichTextActionToggleButton.ts
RichTextMenuCheckItem.ts
RichTextMenuCheckItemBase.ts
RichTextMenuItem.ts
TableAction.ts
TableActionBase.ts
TeaserOverlayPropertyField.ts
TeaserOverlayPropertyFieldBase.ts
TeaserOverlayStyleSelectorBase.ts
RichTextPropertyField.ts
RichTextPropertyFieldBase.ts
RichTextArea.ts
(CMS-18571)
Deprecation: Configuration hideIssuesButton in Control Room
Deprecated configuration hideIssuesButton of
com.coremedia.cms.editor.controlroom.workflow.translation.DefaultTranslationWorkflowDetailForm
as it has no effect anymore. The property will be removed in the next
major release
(CMS-18021)
BooleanPropertyField Label Changes
We fixed a bug where BooleanPropertyFields had no tooltip. For this, we changed an internal plugin of the field. To this end, resource bundles need to be adapted to display the correct field labels.
Follow Section, “BooleanPropertyField Label Changes” for upgrade information.
(CMS-20399)
ILinkListWrapper Manipulation Methods Are Now Asynchronous By Signature
We needed to change the behaviour of #setLinks(), #addLinks(), #addLinksAtIndex(), #moveLinks(), #moveLinksToIndex() and #removeLinksAtIndex() for some important implementations of ILinkListWrapper to be asynchronous. As a consequence, we changed the signature of these methods to return a Promise. In custom implementations where no asynchronicity is needed, the code can simply be changed as in the following example.
Follow Section, “ILinkListWrapper Manipulation Methods Are Now Asynchronous By Signature” for upgrade information.
(CMS-19108)
Fixed Inconsistent Usage of ILinkListWrapper#acceptsLinks
The function ILinkListWrapper#acceptsLinks had
unclear documentation and therefore was neither used nor implemented
consistently.
The most common use case was to only pass the links to be added to the link list like the first sentence of the documentation applied.
Some usages also prepended the existing links of the link list to the links to add before passing the array to the function. This has implied that all links are meant to be replaced.
Follow Section, “Fixed Inconsistent Usage of ILinkListWrapper#acceptsLinks” for upgrade information.
(CMS-18849)
Simplified Most of the Configuration to [ExtConfig]
We simplified most of our configuration for Ext-Components from [Bindable] to [ExtConfig]. In case you are not working only with our Public API (and not, for example, with native JavaScript in Studio) this has no impact. Otherwise you might need to change access to configuration in your native JavaScript from "getSomeConfig" and "setSomeConfig" to "someConfig".
(CMS-16977)
