The stability of mass operations was improved. This affects operations such as dump and restore), full indexing, large migration steps, and database table creation for our Rails Connector. Operations like these now use less memory and utilize subprocesses.
The supplied Oracle adapter for CMS Fiona now supports Oracle 11.
The supplied Sybase adapter is now linked against the Open Client Library of Sybase 15. Older Sybase versions are no longer supported.
A new certificate has been provided for the Java applet used to run a client application for editing content (“external editor”).
In der preview of the editorial system, the read permissions of the CMS users or of the live users or both can now be taken into account. Both permission types are now handled by the authorizationManager. Please also see the Notes on Upgrading.
The
linkCallback procedure
was extended and is now able to call a custom function for each link tag to process. This makes the code more transparent and easier to maintain.
So-called
Notification
Commands can be registered by placing them into the instance
directory
instanceName/script/cm/serverCmds/notifications/.
For details, please refer to the file
share/script/cm/serverCmds/notificationCmd.tcl.
The script supplied for e-mail notification purposes,
share/script/cm/serverCmds/notifications/emailNotification.tcl,
already works like this and can be used as an example for your own
notification commands.
By means of a so-called formatter in layouts, i.e. in NPSOBJ instructions, field values can be formatted before they are inserted into the output file.
The supplied blobLength formatter with which file sizes can be formatted was extended by options for changing the measurement units, for example.
The RFC-822 formatter (for formatting date values) now has options related to the way the seconds and the year are output.
External preprocessors may now return a filed value as a file, indicating this with encoding="stream". Also, encoding="base64" may be used. It is required to set the MIME type of the converted or generated data.
In the configuration of an external preprocessor, the arguments to be passed to the preprocessor program can now be specified unambigously. If, in an existing configuration, more than one argument is passed to the program, this configuration change must be applied.
Properties of LDAP users or groups that have been assigned to fields in the Content Managment Server
by means of the
LDAP
configuration options userAttributeMapping and
groupAttributeMapping, respectively, can now be queried
using the
User
management API functions userWithLoginGet and
groupWithNameGet, respectively.
The GUI configuration files itemRegistry.xml, inspectorRegistry.xml, and searchRegistry.xml are now UTF-8 encoded. If you have individual (modified) versions of these files, please convert them to UTF-8 and adapt their XML declarations:
<?xml version="1.0" encoding="UTF-8"?>Under Unix, you can use the recode command to convert the files. Under Windows, any character encoding converter can be used that supports the source encoding and UTF-8 as a destination encoding.
Furthermore, an identifier was changed in the searchRegistry.xml file. Instead of
<property name="labels">now the following is used as a standard for the localized titles of search parameters:
<property name="titles">>If you modified this file, please adapt it manually.