New and Changed Features

HTML user interface

Infopark CMS Fiona 7 includes a Ruby gem for in-place editing that can be utilized if your content is delivered by a Rails application. After integrating the gem into the application, content can be comfortably edited directly on the web pages.

The standard HTML user interface has been extended. It now conforms to the latest HTML 5 standards, avoiding display errors in current web browsers, particularly when previewing HTML5 pages by means of Microsoft Internet Explorer.

A new user interface theme has been made available and set up as the default theme. As already with Fiona 6, a CMS administrator may change the interface style according to desire by adapting the contents of the webapps/GUI/NPS/themes-7.0.0 instance directory. Furthermore, themes can now build on one another on several layers.

A new action, "Download" is available. Combined with "Upload", it lets you edit binary content using local applications. The Java applet for editing such content locally cannot be used anymore. "Download" only works for objects with draft versions.

Navigating the preview changes the browser address bar accordingly (and not, as before, only the menu). When navigating to a page not based on a CMS object anymore, icons indicate the last viewed CMS object in the path.

The HTML editor previously included in Fiona, "Real Objects Edit On Pro", is no longer distributed by Real Objects and therefore no longer supplied. The TinyMCE HTML editor is automatically used as a replacement.

All the links pointing to a CMS file can now be edited in one step for assigning them a new link destination. Therefore, it is no longer necessary to first deactivate the link destination and then select it using the "Unreachable Link Destinations" dialog.

External links cannot be checked with Fiona anymore. The "Unreachable Link Destinations" dialog (on delivery not part of the menu) thus only reveals CMS objects that are link destinations but inactive or excluded from the export.

Extended server support

Java 8 is now supported.
Oracle 12 is supported.
MySQL 5.6 is supported.

Software updates

The version of the supplied Trifork server is now 4.1.40. A change log is included.

The version of the integrated Tcl package is now 8.6.4.

The version of the integrated TinyMCE HTML-Editor is now 4.1.8.

The supplied image editing software, ImageMagick, was updated to version 6.9.1 (Windows only). For Linux, we recommend to install a more recent version originating from the distribution instead of using the supplied version.

Server

The Linux version of Infopark CMS Fiona 7 requires SUSE Linux Enterprise Server 12, 64 bit, as the underlying operating system.

Dumped data originating from previous Fiona versions are supported if their database scheme is compatible to the current one. With Fiona 7, this applies to dumps created by Fiona 6.7.2 or later.

The clearUsermanCache command no longer merely clears the internal caches. Additionally, the external user management services integrated with Tcl now execute the clearCaches method. This way, utilizing the latest user administration data can be enforced.

By means of the userWithLoginGetLogin Userman API method, the "canonical" variant of a user's login can now be made available for ADS/LDAP. This is particularly advantageous if different spelling is permitted when logging in, or if a single-sign-on solution presents the user name differently from what the Tcl client expects for logging in.

As part of the Tcl update, extensions such as Tcllib were updated as well, making it necessary to also adapt custom CMS extensions based on Tcl. The libxml-based TclDOM version is no longer included in Fiona 7.0.0.

The Tcl scripts for transferring data by means of the Content Service are no longer included. Related to this, TclCurl, too, is no part of the server anymore. The Content Service API made available as part of the HTML user interface, however, is still present and has not been modified.

A large amount of JavaScript code used by the user interface has been consolidated in the  application.js file. This makes it easier to adapt the code should future browser versions require this.