CoreMedia DXP Release Notes, Version 7.5.44-17
2.2. Improvements and Changes | 2.2.27. Release 7.5.18

Destroy Intermediate Versions: The destruction of intermediate versions during publications has been adapted to match the multi-site set up. Thus, it respects versions which are referred to from derived contents.

As a consequence the flag to enable/disable the destruction of intermediate versions has been changed from false/true to off/dumb/strict for publisher properties as well as JMX configuration.

For JMX a new three-state property DestroyIntermediateVersions got introduced while the old property DestroyIntVersions is marked as deprecated. For migration purpose the old flags false/true are still supported and are mapped to false=off and true=strict. The dumb mode uses the old implementation which ignores any version references.

Clean Versions: As for the destruction of intermediate versions also the command line tool cleanversions has been adapted to match the multi-site setup. Thus, the warning in the [Content Server Manual] not to use cleanversions in multi-site setup has been removed accordingly.

Unlike the version cleanup on publication (destruction of intermediate versions) cleanversions only takes current versioned references into account. Thus, reverting changes in derived contents might result in broken versioned links. Having a reasonable time scale in the keep-days option will reduce the possible impact of this destruction.

The Site Manager supports some features which do not reliably work with 64 bit JVMs (e.g. MS Word based spell checking) . Therefore, it shows a warning popup when it is started with a 64 bit JVM. The warning can be suppressed by setting editor.omit-java-vm-check=true in the editor.properties.

Apache Solr has been updated to version 4.10.1.

The class PreferencesUtil provides two utility methods for reading and writing complex objects in the preferences struct: getPreferencesJSONProperty and updatePreferencesJSONProperty. These methods serialize JSON objects to a proper struct stored in the user preferences document.

The new methods are used for saved searches, open tabs, and dashboard widgets. Please make sure that states reported by your custom search filters, tab types, and widgets use only strings, integers, booleans, and arbitrarily nested arrays and objects of such values. Because these are the only types of objects that can be reliably serialized to JSON strings (the procedure used for state persistence so far), it is highly likely that no migration effort will be necessary.

The page grid property field provided in CoreMedia Blueprint has been replaced by a new component in the base modules. The pageGridPropertyField provided by module bpbase-pagegrid-studio-plugin is a significantly more robust reimplementation of the old property field. You should remove the existing page grid property field from your project and use the new field instead.

The localization methods for layouts, placements, and view types have been modified. View types can now be localized in the file BlueprintViewtypes.properties instead of the file Blueprint.properties. A new resource bundle BlueprintLayouts.propertieshas also been added.

See the [CoreMedia LiveContext for IBM WebSphere Commerce Manual] for details about the usage of the placements property field and about localization and configuration options.

The placements property used to support two outdated data formats for the placements struct. In order to consolidate the persistent state, a migration tool has been added that converts all existing placements to the most recent format. To this end, the module cms-tools-application provides the tool migrateplacements, which can be run once during an update to the current CMS version. You can start the tool using the command cm migrateplacements -u admin, in which case the tool will convert all placement structs stored in the property placements of documents of type CMChannel. By adding the option -t <type> the tool can be applied to another document type instead.

There is a new setting in the user preferences to disable element highlighting on mouse hover in the Studio preview.

Certain animations (i.e. zooming images on mouse hover) have been disabled inside the embedded preview to avoid issues with element highlighting inside the preview. A generic configuration mechanism has been introduced to add custom CSS and JavaScript to the previewed documents while displayed in the CoreMedia Studio. Please refer to the CAE developer manual for further details.