Notes Fiona 6.7.1 Release · 2015. 4. 18. · Infopark CMS Fiona Fiona 6.7.1 Release Notes While...

Infopark CMS Fiona

Fiona 6.7.1 ReleaseNotes

Infopark CMS Fiona

Fiona 6.7.1 ReleaseNotes

While every precaution has been taken in the preparation of all our technical documents, we make no expressed or impliedwarranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequentialdamages in connection with or arising out of the use of the information or programs contained herein. All trademarksand copyrights referred to in this document are the property of their respective owners. No part of this publication may bereproduced, stored in a retrieval system, or transmitted, in any form, or by any means, electronic, mechanical, photocopying,recording, or otherwise, without our prior consent.

Fiona 6.7.1 Release Notes – © 2009 Infopark AG 3/19

Inhalt

1 New and Changed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.1 Improved Usability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.1.1 Renewed Design of the Wizard Selection Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.1.2 Using TinyMCE HTML Editor in Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.1.3 Presetting Additional Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.1.4 Storing Images as Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1.5 Markdown Editor Displays Field Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1.6 Tabbed Details Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.2 Extended Template Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.2.1 Improved Editing Elements in the Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.2.2 Better @ References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.2.3 Local Export Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.2.4 Parameterizable Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.3 Wizard Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.3.1 Description and Sort Criterion for Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.3.2 Creating a Single Checkbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.3.3 Styles for Text Input Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.3.4 Shared Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.3.5 Optional Form Validation with Wizard Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.4 System Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.4.1 Improved Stability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.4.2 Database Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.4.3 New Certificate for the External Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.4.4 Read Permissions in the Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.4.5 Structured Link Functions (Callbacks) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.4.6 Easy Integration of Notification Functions (Post Action Callbacks) . . . . . . . . . . . . . . . . . . . . 10

1.4.7 Extended Tcl Formatters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.4.8 Extended External Preprocessor Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.4.9 Better LDAP integration with Content Management Server . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.4.10 Configuration Files of the User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.5 Infopark Rails Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.6 Third-Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.7 Other Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13


2 Fixed Bugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.1 CMS Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.2 System Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.3 Rails Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.4 Portal Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3 Important Notes on Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.1 Java API Uses Java Generics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.2 Storing User Portlet Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.3 Update Rails Database Tables of the CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.4 Database Transaktionen Handling in the Portal Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.5 Read Permissions in the Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.6 Changed Name Space of Standard Formatters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.7 Required Database Option for Sybase Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.8 Official Support for Microsoft SQL Server 2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4 Known Bugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

New and Changed Features


11 New and Changed Features

1.1 Improved Usability

1.1.1 Renewed Design of the Wizard Selection Page

In the editorial system, the design of the Wizard Selection start area was renewed:

1.1.2 Using TinyMCE HTML Editor in Wizards

TinyMCE, a JavaScript WYSIWYG HTML Editor, can now be integrated into wizards much easier.

1.1.3 Presetting Additional Fields

In file formats, the file field Ignore on export (suppressExport) can now be preset.

The sort citeria (sortKey1, sortKey2, sortkey3) as well as their individual sort mode (numeric,

alphanumeric) can now also be preset in file formats.

1.1.4 Storing Images as Resources

It is now possible again to store images in CMS files of the Ressource (generic) type in order to offer

them for download, for example. To enable this functionality, please set the system configuration

entry content.genericDocumentsCanContainImages to true.

1.1.5 Markdown Editor Displays Field Title

In the Markdown Editor, the title of the field that is being edited is now displayed.

1.1.6 Tabbed Details Overview

The details overview can now also be provided with tabs to save space when displaying field sets.

1.2 Extended Template Language

1.2.1 Improved Editing Elements in the Preview

Editing elements (markers) in the preview can now be positioned dynamically and enhanced with

effects. These markers will no longer corrupt the layout since they float on top of the content to be

edited.

1.2.2 Better @ References

Now @ references can not only be placed at the beginning of an attribute value but anywhere inside

the value. Furthermore, attribute values can now contain any number of @ references. As a result,

attribute values can be constructed from static or dynamically generated text, or both. This became

possible by a new syntax. @ references now have the format @{variable} instead of @variable.

Previously, layout developers proceeded as follows to assign a combination of static and dynamic text

to attribute values:

<npsobj modifyvar="set"

varname="cssClass">box obj_<npsobj insertvalue="var" name="id"/></npsobj>

<div class="@cssClass">

By using the new @ references, the same effect can be achieved much easier:



<div class="box obj_@{id}">

With the new @ references, the field or variable name is always enclosed in braces. The previous form

is no longer supported.

When migrating, @ references that have the previous format and are contained in layouts and HTML

documents are automatically converted to the new format.

1.2.3 Local Export Variables

In the modifyvar set NPSOBJ instruction, export variables can now be marked as local. An example:

<npsobj modifyvar="set" varname="foo" local="true">bar</npsobj>

The attribute local is also available in modifyvar append instructions. However, with this

instruction, a variable only becomes a local variable if it does not already exist as a global variable. In

other words: global variables remain global even if local has been specified.

In conjunction with parameterized calls to layouts, local variables help to better separate sublayouts

from the layouts calling them. This makes the layout structure clearer and, as a consequence, easier to

maintain.

1.2.4 Parameterizable Layouts

When calling (including) a layout by means of an insertvalue template instruction, a static or

dynamically generated text can be passed to it. For this, the text can be placed into the content

of the insertvalue template instruction. In the layout called, the text can be retrieved by

querying the local variable npsobjContent. For an example, please refer to the description of the

insertvalue template instruction.

This new functionality makes it possible to use layouts in different contexts without the need to define

global variables for passing arguments to them. This reduces the complexity of layout files.

Furthermore, pure textual data can be passed to a layout as arguments using tag attributes. An

example:

<npsobj insertvalue="template" name="TemplateName" showbody="1" person="@{author}" />

The arguments as well as the npsobjContent variable are treated like local export variables. They

are only available while the included layout is evaluated and are only accessible by this layout. For an

example and further explanations, please refer to the documentation of the insertvalue template

instruction.



1.3 Wizard Handling

1.3.1 Description and Sort Criterion for Wizards

A wizard configuration may now include the descriptions property to provide short descriptions in

addition to the wizard's name. An example:

<bean id="createStatistics"

class="com.infopark.cm.htmlgui.browse.menuaction.CustomCommand">

<property name="titles"><map>

<entry key="de" value="Dateistatistik anzeigen"/>

<entry key="en" value="Show File Statistics"/>

<entry key="fr" value="Afficher les statistiques du fichier"/>

<entry key="it" value="Mostrare le statistiche del file"/>

<entry key="es" value="Mostrar estadísticos del fichero"/>

</map></property>

<property name="descriptions"><map>

<entry key="de"><value>

Wie viele Dateien wurden in einem bestimmten Zeitraum angelegt und freigegeben?

</value></entry>

<entry key="en"><value>

How many files have been created and released in a given period of time?

</value></entry>

</map></property>

<property name="selectionType" value="none"/>

<property name="command" value="createStatistics::render"/>

<property name="dialog" value="true"/>

</bean>

Furthermore, the new property sortKey can be used to define the order in which the wizards are

displayed in the Wizard Selection start area. The wizard are sorted by their sortKey in alphabetically

ascending order.

1.3.2 Creating a Single Checkbox

In wizards, the new wizard function checkBox can be used to create a single checkbox.

1.3.3 Styles for Text Input Fields

In wizards, the CSS class as well as the style attribute can be specified for text input fields (date, file,

text, textarea). Example:

::layout::fileField myUpload "File field" class "myCSS" \

style "background-color: red"

1.3.4 Shared Wizards

Wizards are now read in by a script shared among the CMS instances: share/script/cm/

serverCmds/wizards.tcl. This Tcl file sources all the wizards found in the directories share/

script/cm/serverCmds/wizards and instance/script/cm/serverCmds/wizards.

The instance-specific files instance/script/cm/serverCmds/wizards.tcl are no longer required

and should be deleted after individual (not wizard-related) changes that were made to them have



been transferred to other script files. If instance-specific versions of this script exist, a corresponding

entry in the log file of the CM will be made.

1.3.5 Optional Form Validation with Wizard Buttons

As a default, the GUI validates the contents of wizard dialog forms when the user clicks a

wizard button. This behavior can now be switched off, to ensure, for example, that subdialogs are

opened immediately even if the form contents contains errors.

1.4 System Functionality

1.4.1 Improved Stability

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 Infopark’s Rails Connector. Operations

like these now use less memory and utilize subprocesses.

1.4.2 Database Support

The supplied Oracle adapter for Infopark 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.

1.4.3 New Certificate for the External Editor

A new certificate has been provided for the Java applet used to run a client application for editing

content (“external editor”).

1.4.4 Read Permissions in the Preview

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.

1.4.5 Structured Link Functions (Callbacks)

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.

1.4.6 Easy Integration of Notification Functions (Post Action Callbacks)

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.



1.4.7 Extended Tcl Formatters

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.

1.4.8 Extended External Preprocessor Interface

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.

1.4.9 Better LDAP integration with Content Management Server

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.

1.4.10 Configuration Files of the User Interface

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.



1.5 Infopark Rails Connector

A new version of Infopark Rails Connector is available, featuring even faster development and

extension of modern web applications. The new version consists of two easy installable and

configurable components, one for the base functionality, the other for numerous included website

features.

In the new version of Infopark Rails Connector, great value was attached to immediate utilizability of

all functions. By means of the add-ons included, web pages can be made commentable and ratable,

for example. RSS feeds can be made available in a convenient way. The PDF generator allows for

transforming CMS content into PDF files using individual XSL layout templates. Furthermore, user

registration, logging in and out as well as password requesting are available. For those user-specific

functions the new integrated interface for Infopark Online Marketing Cockpit can be used. Lively

portals on which interaction with and among visitors is a central concept, can be developed rapidly.

Also, the interplay of Rails Connector and Infopark CMS Fiona was improved. In the preview,

transparent edit markers and individual marker menus can be provided to make editorial work more

pleasant and efficient and to benefit from existing resources such as wizards for content acquisition.

Having increased productivity in mind, the Rails Connector was also equipped with an easy-to-use

template language, Liquid. Like CMS Fiona’s template language, Liquid offers convenient means of

layout creation to web developers. It facilitates dynamic access to content and its flexible integration

into web pages.

Particularly in combination with Online Marketing Cockpit, Infopark Rails Connector offers interesting

possibilities for personalization and targeted communication with the users of services on the web. The

new search engine optimization functions round off the picture. These functions can help to improve

the visibility of services on the web.

1.6 Third-Party Software

In Infopark CMS Fiona 6.7.1, the following third-party software was updated to the specified versions:

• Autonomy (formerly Verity) KeyView Export SDK: 10.8.0

• ImageMagick: 6.4.4

• Edit-on pro (EOP, integrated HTML editor): 5.3.245

• Trifork Application Server: 4.1.32

• Apache Velocity: 1.6.2

The Velocity Template Language is used for displaying the details views in the GUI and serves as

the Portal Manager’s standard template language. For the syntax changes since version 1.5 please

refer to the Velocity change log.



Third-party software absolutely required for operating Infopark CMS Fiona 6.7.1 (system requirements)

is now always installed when the CMS is set up. It is no longer possible to choose the add-on packages

to be installed. Use symbolic links if you need to use other versions of the software supplied with the

CMS.

1.7 Other Changes

• For smaller software packages, the PDF version of the documentation (which is the same for all

supported platforms) is a separate package now.

• If you log into the Search Server (SES) using the Tcl client, anonymous is now displayed as the user

name in the prompt. An example:

anonymous@localhost:3012 default(SES)>

• The config/mimeTypes.xml configuration file now also includes entries for the file name

extensions tif and tiff.

• The preview_mongrel script was replaced in version 6.7.0 by mongrel_rails start.

Fixed Bugs


22 Fixed Bugs

2.1 CMS Functionality

• Due to a wrong configuration example, Basic authentication or NTLM authentication sometimes

caused problems with failed authentication processes. In these cases the proper error page is now

displayed instead of an empty page. (ID 11167)

• In the search dialog of the editorial system, the calendar for entering date values now works again.

(ID 11451)

• The title of the baseGroup field group can now be edited again. (ID 11550)

• Field values can now also be edited by means of a wizard opened from within a details view.

(ID 11536)

• The GUI now properly indicates whether the fields permaLink, title, channels, and mimeType

are obligatory fields. (ID 11551)

• When using Internet Explorer 6 (on the client side) and Tomcat (on the server side), user names can

now be selected again to add them to a user group, for example. (ID 11596)

• The GUI now delivers valid Expires headers again. The invalid header had caused restrictions

when editing content or the configuration. Furthermore, the GUI pages are now always updated

after changes have been made to the content. (ID 11610)

• The statistics function no longer counts committed versions as archived versions but as draft

versions. (ID 11616)

• The “Errors in version” are now also displayd for empty linklists that ought to be not empty.

(ID 11673)

• When creating a new file, it inherits only those access permissions from its parent that are relevant

for its type. (ID 11732)

• Multi-selection field can now be edited properly using checkboxes. (ID 11807)

• A memory leak in the GUI was fixed. When logging on and off frequently, this leak caused the GUI

to respond slowly or to stop working. (ID 11817)

• Errors during the authentication process in the GUI are now displayed properly again and do not

lead to empty pages or redirection loops. (ID 11857)

• In the GUI, the sorting settings can now be reset to the standard values. (ID 11904)

• Due to an update of the Velocity engine the GUI responds much faster to parallel requests for

preview pages. (ID 11922)

• Checking layouts now also works if a layout contains an insertvalue template instruction

which includes the key parameter whose value, however, is an invalid name (such as the name of

a nonexisting field). The layout checker points to this error by means of a corresponding message.

(ID 12223)

Fixed Bugs


2.2 System Functionality

• The master/slave handling of the CM, TE, and SES was improved. It no longer creates unfounded

log entries reporting “broken pipes”. (ID 6636)

• When indexing fails, the original data meant to be indexed is still available and not modified.

(ID 7379)

• The master processes of the CM, TE, and SES now remove their slave processes properly. (ID 8345)

• During the incremental export, mirror files are now removed properly from the search index.

(ID 10761)

• During migration, GUI roles that no longer exist are now removed from the user settings.

(ID 11402)

• The process of updating the database tables for the Rails Connector (using CM -railsify) can now

be restarted and will be continued after it was interrupted. (ID 11527)

• The LDAP integration in the Tcl user manager now accepts dashes in filters (and thus in LDAP

attribute names). (ID 11554)

• Floating licenses now work again. (ID 11578)

• After deleting links, the Content Manager (CM) now always writes the updated content data into

the Rails Connector’s database tables. Thus, the Rails Connector no longer receives outdated links

from the database. (ID 11583)

• The GUI no longer considers licenses containing special characters (such as umlauts in the owner

element) to be invalid. (ID 11587)

• The number of log entries produced by the HTML user interface (GUI) in the info log level was

decreased to reduce the system load. (ID 11650)

• The preprocessor API of the Search Server (SES) can now be used for processing indexing requests

again. (ID 11669)

• The Tcl command indexAllObjects no longer uses too much memory and now works

without problems, even with large amounts of data. The command no longer checks whether

the user executing the command has the administration permission for the files. Therefore,

indexAllObjects can only be executed by a superuser. (ID 11700)

• The CMS processes now recognize whether a database connection to a MySQL-Server has been

interrupted. No further database operations are performed over broken database connections.

(ID 11725)

• The XML interface now properly converts HTML entities such as >, <, &, and ".

(ID 11745)

• The Search Server no longer crashes when it attempts to index empty ressource files with a text

MIME type such as text/html. (ID 11779)

• The Tomcat application server no longer rejects valid licenses. (ID 11802)

• The LDAP/ADS Tcl user manager integration reuses connections, which are also recovered in case of

server side failures. (ID 11947)

• Changes to mirror files now have the proper effect on the parent folder when exporting

incrementally. (ID 12205)

• After changing the live read permission of a file the corresponding entries in the Rails tables are

now updated. (ID 12208)

• Export errors no longer cause the Template Engine’s incremental export to slow down. (ID 12221)

• The rc.npsd start script now waits five seconds before it starts the Trifork application server. This

makes it more likely that port 8070, which was occupied by a previously running Trifork server

instance, was released in the meantime. (No ID)

Fixed Bugs


• Files that were created by means of a wizard can now again be selected using npsGuiControl/

npsSelect. (No ID)

2.3 Rails Connector

• The Rails Connector tables objs and preview_objs now both have the new columns valid_from

and valid_until including proper indexes. Due to this, the validity of documents with respect to

time can now be checked faster. (ID 11539)

• When creating folders, their file path information is now properly wrtten to the Rails Connector

tables. (ID 11569)

• When using the Rails Connector and its action markers (for editing), displaying the preview no

longer produces the following error message: “java.lang.IllegalArgumentException: Class not

supported: org.json.JSONObject$Null”. (ID 11589)

• The values of the keys sortKey1, sortKey2, and sortKey3 are now correctly determined so that

lists sorted by date are displayed as desired. (ID 11907)

• A new column, is_edited, was added to the Rails Connector tables objs and preview_objs.

(No ID)

2.4 Portal Manager

• The number of user-specific portlet settings that can be stored in the file system is no longer

restricted to 31999. (ID 11559)

• In the FilesystemPreferencesStorage bean, threads are now synchronized less frequently to

prevent deadlocks. (No ID)

Important Notes on Upgrading


33 Important Notes on Upgrading

3.1 Java API Uses Java Generics

If you have Java projects, please note the following when translating projects that use the former API:

• If errors such as “Generics are not supported in 1.4” occur please change the target version of your

project to Java 6.

• If warnings such as “References to generic type should be parameterized” or “Some input files use

unchecked or unsafe operations” we recommend to switch over to Java Generics in your code.

As an alternative, you might also suppress the warnings by means of the

@SuppressWarnings("unchecked") annotation in the source code, or by using the -nowarn

compiler parameter.

3.2 Storing User Portlet Settings

Due to file system restrictions, storing user settings in the file system using the

FilesystemPreferencesStorage bean is no longer supported in productive use. We recommend to

store user settings in a databse instead.

3.3 Update Rails Database Tables of the CMS

If Rails support is activated in your CMS, please reinitialize your Rails tables in the database of the CMS

using the CM -railsify command.

3.4 Database Transaktionen Handling in the Portal Manager

In the Portal Manager, database transactions are now handled by the Spring framework. Please

activate in the file instanceName/webapps/*/WEB-INF/pm.xml the beans required for the database

functions you use. Then configure the following:

• com.infopark.pm.user.DatabaseUserDirectory

• com.infopark.pm.DatabasePreferencesStorage

• dataSource

• transactionManager

Your own code for accessing a database is not affected by this change. Therefore, it does not need to

be modified.

Important Notes on Upgrading


3.5 Read Permissions in the Preview

The permission filter com.infopark.cm.htmlgui.browse.preview.PermissionFilter was

removed from the file instanceName/webapps/GUI/WEB-INF/pm-filter.xml. Please use the

authorizer com.infopark.cm.htmlgui.browse.preview.Authorizer in authorizationManager

instead for the file read permissions of the CMS users (if desired, in additon to the read permissions of

the live users) to be taken into account in the preview.

3.6 Changed Name Space of Standard Formatters

All standard formatters (however, not the ones for formatting dynamic links) are now in the

::formatter name space. For example, the name of the Tcl procedure defined for the phpVardef

formatter is now ::formatter::phpVardef.

When migrating, the registration of the supplied formatters in the system configuration is

automatically adapted. Custom formatters (in the script subdirectory of the CMS instances) and their

registration need to be adapted manually.

3.7 Required Database Option for Sybase Databases

With Sybase Database Server, it is required to activate the select into option for the CMS

databases.

3.8 Official Support for Microsoft SQL Server 2008

Infopark now officially supports Microsoft SQL Server 2008 as a database for Infopark CMS Fiona. From

this release, older versions of SQL Server are no longer supported. However, no technical reasons are

currently known that speak against using SQL Server 2000 or 2005.

Known Bugs


44 Known Bugs

• If the path of a portlet web applikation is contained in the path of another one, (as with /

default/PM-PL and /default/PM-PL-Copy, for example), the portlets of both web applications

are no longer displayed. (Id: 10531)

• Searching for files using obj where condition {objClasses is objType} does not yield

mirror files to whose original file the specified file format has been assigned. (Id: 10553)

• If a CMS file which opens another file in an iframe is displayed in the preview, the file opened in

the iframe shows up in the history as well. (Id: 10758)

• With wizards that use npsField type="file" to upload a file, the second and every following

attempt to use the corresponding form page causes an empty ticket ID to be created. This prevents

the file from being uploaded. (Id: 11404)

• The attempt to delete a mirror folder that is no link target but contains implicit mirror files that

are linked causes a wrong error message to be displayed. This mesage erroneously reports that the

mirror folder cannot be deleted because it is a link target. (Id: 11396)

• When editing links by means of the link editing dialog of the GUI opened from within the HTML

Editor (EOP), special characters in the link titles such as umlauts are encoded incorrectly. (Id: 11315)

• Wizards have a selectionType property that indicates the range of CMS files to which the

wizard can be applied (none, single, list). If a wizard whose selectionType is none is called

via an npsgui element that has been integrated into a page to provide an editing element

(action marker) then the CMS file ID of the respective page is always passed to the wizard

procedure, ignoring the none setting. Thus, if the same wizard can be called via the menu or

toolbar, a different number of arguments is passed to the wizard procedure, depending on how

it is evoked. As a workaround, set the selectionType of the wizard to single or modify the

wizard procedure so that it handles its second argument, which depends on the selectionType,

correctly. (Id: 11842)

• With Microsoft HTML Editor, links and images cannot be inserted into the HTML text. Also, existing

links and images cannot be modified. (Id: 11935)

Notes Fiona 6.7.1 Release · 2015. 4. 18. · Infopark CMS Fiona Fiona 6.7.1 Release Notes While...

Documents

Transcript of Notes Fiona 6.7.1 Release · 2015. 4. 18. · Infopark CMS Fiona Fiona 6.7.1 Release Notes While...