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.
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.
If Rails support is activated in your CMS, please reinitialize your Rails tables in the database of the CMS using the CM -railsify command.
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.DatabaseUserDirectorycom.infopark.pm.DatabasePreferencesStoragedataSourcetransactionManagerYour own code for accessing a database is not affected by this change. Therefore, it does not need to be modified.
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.
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.
With Sybase Database Server, it is required to activate the select into option for the CMS databases.
We now officially support Microsoft SQL Server 2008 as a database for 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.