close

Filter

loading table of contents...

Release Notes / Version 11.2304

Table Of Contents

CoreMedia Studio Client

Embedded images in richtext are now referenced by relative URI

Images embedded in richtext were rendered with an URI relative to the host which caused issues with local development setups were Studio was running with a context (e.g. localhost/studio). Now images embedded in richtext are rendered with a relative URI.

(CMS-22630)

Change in Data Types / Flavors of Drag Data and Clipboard Items

Previously, when dragging/dropping and copy/pasting remote beans like content items and users/groups, the drag/drop events' dataTransfer property and the items (IClipboardItem) of the clipboard contained a "cm/uri-list" type/flavor (containing a list of {$Ref: uri} objects). This is now deprecated. Instead we now support different flavors with more specific context:

"cm-studio-rest/uri-list": a list the remote bean URIs as understood by the Studio Rest service

"cm-content/uuid-list": a list of content UUIDs as understood by the content server

"cm-member/uuid-list": a list of user/group UUIDs as understood by the user managemenr server

(CMS-22626)

Simplify Configuration for Local Studio Client Development against Server with Custom Path Prefix

For Studio Client development using pnpm ... start with a proxyTargetUri containing a non-empty path prefix ( https://mydomain.com/some-path/rest ), previously, you had to change the default for proxyPathSpec from /rest/ to /rest and use a proxyTargetUri without a trailing slash. Any other configuration would result in errors. To simplify the configuration for such setups and at the same time be backwards-compatible, the values for proxyTargetUri und proxyPathSpec are now robust against presence of a trailing slash. In practice, this means you can always keep the default for proxyPathSpec ( /rest/ ) and it does not matter whether your proxyTargetUri ends with a slash or not.

(CMS-22559)

Improved studio-client development documentation

A wrong command was listed for starting studio and an obsolete note box was removed about a "--" which is no longer needed.

(CMS-22555)

Fixed German Labels

Fixed issues with German labels on the login mask and user-manager.

(CMS-22481)

Editor contents in new HTMLFragments are now editable

The Slim editor was missing a crucial plugin, that did not allow to edit contents in new HTMLFragment editors.

(CMS-22456)

Added missing favicon in Workflow App

Missing workflow favicon has been added.

(CMS-22446)

Problems starting (remote) apps with devDependencies

Only relevant when using the experimental custom apps feature: Packages not located in the workspace are downloaded from an NPM registry. If this is the case for an app and the package contains "devDependencies" the studio-client could not be started.

(CMS-22365)

Fixed An Issue Where Drag&Drop Between Content App and Workflow App Did Not Work

In case the apps where running via "http" and not on "localhost" drag&drop between content app and workflow app was not working.

Note: Such a setup is only recommended for testing or development purposes not for production!

(CMS-22363)

CKEditor 5: Drag & Drop of contents from external systems into RichText and Link Balloon

It is now possible again to drag and drop contents into CKEditor 5 components like in CKEditor 4. When a content from a thirdparty system (e.g. a commerce system or a content-hub provider) is dropped, the content will be imported into the CMS and linked or embedded in the like a content.

(CMS-22313)

Fixed Document Lifecycle Status Icon

Fixed the update of the status icon located before the locale switcher.

(CMS-22305)

Fixed Notifcation Error for Custom Notifications

Fixed an error thrown by custom notifications that want to use the default notification wrapper for displaying the notification details.

(CMS-22304)

Fixed Issues Tooltip

Added missing linebreaks in issues tooltip.

(CMS-22272)

Fixed Initialization of FolderChooserList

The chooser is only initialized with the calculated path if no other value was set through the bindTo expression of the component.

(CMS-22201)

SASS file check in jangaroo build does now respect custom SASS Namespace

In case a custom sass namespace was set in the jangaroo.config.js of a package the SASS file check might have reported a false positive about unused sass files inside the package. This has been fixed now.

(CMS-21883)

Documentation: Added Hints on Handling of EXIF Orientation in Image Metadata

Hints on handling of EXIF orientation in metadata of images uploaded to the CMS have been added to Studio User Manual.

(CMS-19374)

Added Optional Force Collapse State

In case the initial expanding of property editors is too time consuming (especially on older hardware), the premular configuration can be changed, so that all editors stay collapsed on opening.

(CMS-19100)

Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

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