New and Changed Features

CMS Fiona 6.6.1

Version Comparison Wizard

CMS Fiona now includes a wizard for comparing any two versions of a CMS file such as the draft and the released version. This makes it possible to quickly detect the changes made to any field, which reduces, for example, the effort required for proof-reading.

Saving the contents of the editors

The content being edited with the HTML editor, for example, can be saved to the draft version using the Save button so that you can preview your changes without having to close the editor. This analogously applies to the internal editor, the Microsoft HTML editor, and the Applet for external editors.

Link lists can be sorted

The links contained in link lists can now be sorted comfortably.

Support for MySQL

If a MySQL database is used, the port can now also be configured. This makes it possible to use MySQL servers not running on the standard port 3306.

Furthermore, the settings required for the MySQL database were changed.

Select no workflow

If a workflow had been assigned to a file, it was possible to choose a different workflow later on, however, it was not possible to remove it from the file. In the corresponding dialog, Edit file field 'workflow', you can now optionally choose N/A to specify that editing the file should not be subject to a workflow.

File formats can be renamed

File formats can now be renamed using the objClass set command. Thus, the formats can subsequently be named according to the Rails convention (CamelCase), for example. For renaming a format, the renameObjClass procedure should be used since it also reindexes the affected files and displays the list of scripts, layouts and configuration files that need to be adapted manually.

Username is visible in the user interface

The current user's login is now visible in the Content Navigator's menu bar. (Id: 9480)

Rails Connector for CMS Fiona

Improved performance on binary data delivery.

The controller supports conditional requests now (If-Modified-Since header). This enables the browser cache.

Binary data may be delivered by the HTTP server using the XSendFile plugin. Thus the mongrel is no more blocked by delivery and the system can handle more requests.

Further Changes

• The parameters used when connecting the Portal Manager to an LDAP/ADS server are now documented in the configuration file pm.xml. This file is located in the Portal Manager web applikation.

• Under Solaris, Sybase 15 is no longer supported.

• In an xmlBlob of a content, the element name for the target of a link contained in a link list is always target now. In previous versions, linkTarget had to be used when the key was set, and target when it was read.