Release Notes / Version 12.2412.0
Table Of ContentsFixed: LinkBalloon closes when a drag and drop started in CoreMedia Studio.
There was an issue while dropping contents into the RichText editor. The editor’s link balloon would close on the first drag attempt. This issue is now fixed.
(CMS-26944)
Added Protected Users
A list of protected users and groups can be defined in the application.properties from the Studio server now. The members are marked with a lock symbol and tooltiop and the deletion action is disabled then.
The CoreMedia Blueprint system users and groups are already part of these lists.
(CMS-25937)
Fixed Layout Bug That Would Freeze The Studio Due To Maximum Call Stack Size Exceeded
We fixed a bug related to the WorkAreaTabBar where the layouting mechanism would run into a "maximum call stack size exceeded" error leading to a Studio freeze.
(CMS-25928)
Content Lists In Start Workflow Forms Are Now Colorful Again
The content lists in the start-workflow forms were no longer colorful since the Studio refresh for 2401. There are now, once again.
(CMS-25824)
Fixed Bug That Broke Keyboard Navigation Through Document Forms
We fixed a bug where opening the third tab of a content type (which is when tab reuse kicks in) broke the keyboard navigation through the document form (with the TAB key).
(CMS-25722)
Removal: Deprecation for SiteModel's siteIndicatorDepth in Multi-Site for Studio Client
We removed the deprecation notice for
siteIndicatorDepth
as part of the
SiteModel
in Studio Client.
As part of this change cm validate-multisite
got
extended by a new issue code:
MS-VALIDATION-4009 – DISCOURAGED_PROPERTY_VALUE
The new issue-code is reported at level INFO
and is
triggered, when using a siteIndicatorDepth
different to 0
(zero).
Motivation
As part of CMS-9521
we deprecated
siteIndicatorDepth
for 2001.1 and changed the
default to 0
(zero) rather than
1
(one), as we got aware that many editors
struggled with site indicators being hidden in the "depth"
of a site – which in the end caused corrupted sites.
Nevertheless, migrating existing content from a depth 1 to depth 0 may raise considerable migration effort, as you have to move all site indicators up one level in one step (while stopping editorial work) and then republish all your sites.
Because of this, we decided to remove the deprecation notice, so that
we will support site indicator depths different to
0
also on in the future. The default which ships
with CoreMedia Blueprint will stick to the recommended default
0
, though.
(CMS-25647)
IntegerPropertyFields do not have an underline
Layout underline problem of IntegerPropertyField fixed.
(CMS-25613)
Fixing a related teaser overlay mechanism resolved this behavior
The behavior is resolved by fixing a related bug of the teaser overlay mechanism: The teaser overlay was not reset when the source text gets empty.
(CMS-25570)
Fix for JPEG Image Upload Failure
JPEG images which have density metadata outside allowed range (1..65535) could not be uploaded and showed an exception javax.imageio.metadata.IIOInvalidTreeException: Xdensity attribute out of range in Studio Server log. With the fix, the system now retries upload of the image without any metadata, effectively falling back to default values. Additional JPEG image metadata will be lost in that case.
(CMS-25403)
Added option to show home folder
A setting has been added to the user preference, that allows to show the "Home" folder as part of the library. The setting is limited to administrative users and allows to access the home folders of all users.
(CMS-25135)
Improved Acrolinx Plugin
Added support for text area fields.
Created updated release for 2310.
(CMS-25130)
Postprocess web manifests to customize the app menu entries
The section Customizing Entries to the Apps Menu in the Studio Developer manual has now a new subsection Postprocessing App Manifests, which describes how to use a build postprocess script to manipulate the web manifests in order to customize the app menu entries.
(CMS-21746)
Content Hub: Delete temporary files after import
The Content Hub uses temporary files while importing blobs. Those temporary files are now correctly deleted after the import.
(CMS-21492)