Release Notes / Version 10.2010
Table Of ContentsContent Server Database Change
When the
Content Server
starts the first time after upgrading from version 2004 or 2007, it will automatically adapt database tables and remove existing unique constraints for the
versionUuid_
column of all document type tables. For Microsoft SQL Server and IBM DB2, and when upgrading from 2007.1, wrong unique constraints are also removed from the
uuid
column of tables
CmUsers
and
CmGroups
.
Follow Section, “Content Server Database Change” for upgrade information.
(CMS-18049)
Update of mongo-java-driver
The mongo-java-driver 3.11.2 has been updated to mongodb-driver-legacy 4.1.0 and mongodb-driver-core 4.1.0. This change required breaking changes as several classes and methods have been deprecated.
Follow Section, “Update of mongo-java-driver” for upgrade information.
(CMS-17590)
Fix for possible false calculation of Dependent Content for Synchronization-Workflow
When you use the Synchronization workflow from version
2007.1
, it is necessary to reupload the
synchronization.xml
, to ensure that dependent content is calculated correctly for synchronization. Also the class
DefaultStartSynchronizationWorkflowFormBase
was adapted to ensure that values of additional workflow fields, implementing the
IAdditionalWorkflowDisplayFieldMixin
are passed to the Synchronization workflow (the Translation workflow is not affected by this).
(CMS-17933)
Corba over SSL
The SSL encryption of CORBA traffic was broken, so that a configured SSL port just served unencrypted data, equivalent to the clear text port. This has been fixed now.
(CMS-17723)
Publisher monitoring
The JMX monitoring interface records failed publications due to an unavailable Master Live Server as failed publications now. Previously, such publications were not counted at all.
(CMS-16763)
translate.xliff.export.excludeContentName defaults to true
Because translating content names may harm your system, the default for
translate.xliff.export.excludeContentName
has been changed from
false
to
true
. Having this, content names will by default not be part of your XLIFF anymore.
Follow Section, “translate.xliff.export.excludeContentName defaults to true” for upgrade information.
(CMS-16730)
Localization Workflows: Automatic merge of Annotated LinkLists
In translation workflows, annotated LinkLists (CMTeaser#targets and CMCollection#extendedItems) were not merged automatically in previous releases, which lead to problems in derived content. Reason was, that the properties have been marked as "translatable" in the document type definition (blueprint-doctypes.xml). Now the "translatable" attribute has been removed to enable the automatic merge, and the improved merge algorithm for struct lists is configured for translation and synchronization workflows. To enable translation of the property CMTeaser#targets.links.callToActionCustomText, it is configured as "translatable expression". Note that the changed merge algorithm implicates a different merge behaviour for synchronization workflows.
(CMS-16514)
cm serverimport: No Suppressed Errors Anymore
Prevoiusly,
cm serverimport
may have ignored errors on import silently unless you set the
--halt
option. Now, you will always get a warning on any error.
Follow Section, “cm serverimport: No Suppressed Errors Anymore” for upgrade information.
(CMS-11155)