Release Notes / Version 11.2310
Table Of ContentsFixed 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)
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)