OpenCms 6.2.2 release notes

July 21, 2006

OpenCms 6.2.2 is a maintenance release which fixes several issues reported in OpenCms 6.2.1. 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 configurable validation handler for user and group name
• Improved caching of XML Content definitions by adding a cache to the "unmarshal" factory methods
• Fixed issue with workplace localization that required all explorer related key to be in a single package
• Fixed issue with static export not deleting parameter versions of exported files
• Fixed some localization issues in the XML content widget implementations
• Fixed issue with synchonization during static export blocking the "clear cache" event
• Fixed issue #1078: Custom implementations of CmsWidgetDialog are now able to provide a custom Title
• Fixed issue #1131: Problems with CmsFileUtile#readFully() (thanks to the contribution of Jason Trump)
• Fixed issue #1148: image.size property is now updated when using replace() operation
• Fixed issue #1151: Exception when accessing file properties if TemplateOne module not installed
• Fixed issue #1155: Oracle DB contraints are not longer violated during OpenCms setup
• Fixed issue #1156: The Setup is trying to drop DB when it doesn't exist
• Fixed issue #1157: JavaScript for displaying explorer view is crashed when resource title ends with "/" ,"\" chars
• Fixed issue #1163: NULL_PROPERTY now uses equals() to check for identity, also has a name set to avoid NPE
• Fixed issue #1167: build-single.xml ClassNotFoundException (thanks to the contribution of Harald Brabenetz)
• Fixed issue #1168: JavaScript error when closing database import/export report
• Fixed issue #1173: CmsSynchronize called CmsRequestContext#saveSiteRoot() multiple times
• Fixed issue #1174: Cache key in Flex request "params" without parameter
• Fixed issue #1178: Updated PDFBox.jar to 0.7.2 version to avoid issues with certain PDFs during search indexing
• Fixed issue #1183: CmsJspActionElement.getContent(String) generates NPE for XML Content
• Fixed issue #1186: Help bubble popup: Wrong display position using nested XML content
• Fixed issue #1187: '&' Character in project name gives "String index out of range: -1"
• Fixed issue #1188: Wrong resource link in contenttools module
• Fixed issue #1190: Multiple access control and input validation vulnerabilities
• Fixed issue #1195: default locale while creating a XmlPage is missing
• Fixed issue #1196: Wrong cast in CmsNewsletter has been removed

• Fixed issue #1197: Static export on demand does not scrub parameter based image versions

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.2 release. In case you are using one of the previous versions (OpenCms 6.0.x, 6.2 beta, 6.2.0 or 6.2.1), there have been several issues fixed in this 6.2.2 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.2 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, 6.2.0 or 6.2.1 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.2 release is "build_6_2_2". 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/

Back to the news overview