close

Filter

loading table of contents...

Release Notes / Version 11.2310

Table Of Contents

CoreMedia Studio Client

CoreMedia CKEditor 5 Plugins Updated

The CKEditor 5 Plugins provided by CoreMedia have been updated to 14.1.1.

This release addresses an issue that may occur while editing links within CKEditor 5: Having a link like:

<a xlink:href="https://e.org/" xlink:show="new">Link</a>

you may end up with mouse interaction or cursor movement, having a trailing (or leading) corrupted link like:

<a xlink:href="https://e.org/" xlink:show="new">Link</a><a xlink:href="" xlink:show="new"></a>

An update is recommended, as well as updating ckeditorDefault.ts to incorporate the required configuration (details below).

Details

The new release ships with a new plugin LinkAttributes, that allows to register attributes as "belonging to a link". Having this, such attributes share the same behavior as the "href" attribute, for example, like: Removed when "unlink" is invoked, share so-called two-step-caret-movement at the beginning and end of a link (decides, if newly typed text still belongs to the link or shall not be part of the link) and aligned focus management on mouse-click at end or beginning of link, which assumes to be "outside" of the link.

As part of this update, attributes that previously may have caused "links without or empty href" by the actions described above have been registered to be valid only in context of links. This applies to:

  • xlink:type: a fixed attribute, registered by the Rich Text Plugin.

  • xlink:actuate: represented as data-xlink-actuate in data view and editing view. Configured in ckeditorDefault.ts (see Upgrade Information below)

  • xlink:title represented as title in data view and editing view. Configured in ckeditorDefault.ts (see Upgrade Information below)

Follow Section, “CoreMedia CKEditor 5 Plugins Updated” for upgrade information.

(CMS-22761)

Updated Taxonomy/Topic Pages Administration Access

Since the 2110 release, the access to topic pages and the taxonomy manager is not configurable via content anymore. Instead, user groups must be added to the jangaroo.config.js file of the corresponding studio-client module. These files and the documentation have been updated with default groups and the removed from the demo content.

(CMS-21494)

Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.