OpenCms 6.2.1 release notes

OpenCms 6.2.1 is a maintenance release which fixes several issues reported in OpenCms 6.2.0. OpenCms 6.2 adds several useful features to OpenCms that are not available in version 6.0.

The most important changes the 6.2 release compared to the 6.0 version:

Major new features (in OpenCms 6.2)

• Multiple selections and operations in the Workplace Explorer
• Native image scaling and manipulation
• Visual ("diff" like) comparison of document versions
• Integration of the popular FCKeditor for WYSIWYG editing
• Added "move content up and down" function to the XML content editor
• Much improved search index administration interface
• More options for generating accessible website content

Resolved Issues in 6.2.1 compared to the 6.2.0 release

• Added fix for "concurrent resource creation" issue
• Fixed issue with old version of cached content definition after a nested XML subschema was changed
• Fixed issues with special characters in help texts of XML content editor
• Fixed issue in CmsHtmlConverter with variable line separator length in UNIX / Win environments
• Fixed issue with missing "Lock" entry in context menu for image resources
• Fixed issue with VFS resource state being set wrong in combination with operations on new siblings
• Fixed issue #1129: DB Table name length for project name was too short
• Fixed issue with secure site in SSL and redirects
• Fixed some small issues with the update wizard
• Fixed issue #1150: binary distribution usable only with Java 1.5 (with new special Java 1.4 download)
• Fixed issue #1138: custom JSP error handler page now return the original error status code

For a list of features of OpenCms 6 compared to version 5, have a look at the OpenCms 6.0.0 release notes.

Backward compatibility

We recommend everyone who uses an earlier version of OpenCms to update to this 6.2.1 release. In case you are using one of the previous versions (OpenCms 6.0.x, 6.2 beta or 6.2.0), there have been several issues fixed in this 6.2.1 release. If you still use OpenCms 5.0.x, you should definitely consider an update since the 6.2 version is much more advanced and stable.

OpenCms 6.2.1 should be highly backward compatible with all 6.0 versions. Certain minor API changes have been made, so some adjustments may have to be done for code that uses more advanced API functions. All Templates should be backward compatible without changes.

To upgrade an existing OpenCms 6.0.x, 6.2 beta or 6.2.0 to the new 6.2.1 final release, an easy to use upgrade wizard is provided.

Compatibility with Java versions, Servlet containers and databases

OpenCms 6.2 requires Java 1.4.x or Java 1.5.x. It won't work with Java 1.3.x. We have tested only with SUNs version of the JDK. However, OpenCms has no dependencies to sun.* packages so it should in theory run with all compliant JVMs.

We have tested this release on the Tomcat servlet engine and to some extend on JBoss 4.0. OpenCms 6.2 works "out of the box" with Tomcat 5.0.x and Tomcat 5.5.x. Others have reported deploying 6.x versions successfully on other servlet containers like BEA Weblogic and SunONE.

On the database side, we have tested with MySQL 4.0, MySQL 4.1, MySQL 5.0, Oracle 9.x and Oracle 10.x. PostgresSQL support has been tested and improved by Ivan Codarin. maxDB support has been contributed thanks to Clovis Wichoski and Fabiano Rech. Experimental MS SQL server support has been contributed thanks to Andras Balogh. We still are looking for volunteers to support testing the stability of the maxDB and MS SQL versions.

Regarding version numbers and CVS build tags

In case you want to check out OpenCms from the CVS, please keep the following in mind: The CVS tag for the 6.2.1 release is "build_6_2_1". Development of the next OpenCms release is done in the "DEV_7_0" branch. Upcoming development version will use the version numbers 6.3.x for the next time and will be likewise tagged in the CVS.

How you can help

Contributions to the OpenCms core development are most welcome. Please contact the core development team on the opencms-dev mailing list.

Please use our Bugzilla to report bugs in this release: http://bugzilla.opencms.org/