OpenCms 6.2 BETA release notes
OpenCms 6.2 BETA adds several useful features to OpenCms that are not available in version 6.0.
Who should use this 6.2 beta version?
This is a beta version. Please don't expect it to be perfectly stable. Having said that, we believe that 6.2 beta may be stable enough to be used in a production system. If and how you should use this version depends on what your goals are:
- If you starting a new OpenCms project now, you may consider using this 6.2 beta and not 6.0.
- If you are running a website based on OpenCms 6.0, and you want to upgrade, you should wait until the final 6.2 release is available.
When will the "final" release of OpenCms 6.2 be available?
End of March 2006.
You can help speeding up the process of development by providing feedback for this release and the following releases, especially regarding bugs. In case you find any bug, please use the OpenCms bugzilla to document it, or at least post a note to the opencms-dev mailing list. The more feedback and code contributions are made, the faster we can fix the issues and finish the development.
The most important changes the 6.2 beta release compared to the 6.0 version:
Major new features
- 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
- Much improved search index admininstation interface
- More options for generating accessible website content
- New frontend module to display photo albums conveniently on a website
- New Content check tool to validate file contents and properties
- All list displays in the Workplace offer a print version
- Image galleries now show a thumbnail of all the images in the gallery
- In the Workplace Explorer, it is now possible to select resources by right-clicking on the resource name
- The Workplace Explorer tree now shows the resource state for new and changed resources
- It's possible to enable Link or Gallery dialogs in XML content WYWIWYG fields
- XML content WYWIWYG fields use the user configured editor (if possible)
- Added <cms:decorate> tag for parsing and decorating HTML content
- It is now possible to select 'individual' or 'shared' property mappings for XML content
- Workplace explorer resources to display can now be configured using a Collector
- New project file list
- New option to export webuser data
- New option to export a folder recursively or not
- Project resources can now be modified in the project management "Edit project" dialog
- Added "before publish" event
- Fixed issue #514 & #937: new 'Database Connection Validation' dialog added to setup wizard
- Fixed issue #1006: it is now possible to use 3 letter locales (e.g. like "ast")
- Fixed issue #1020: undo changes now also works with shared properties
- Fixed issue #1021: file parameter of the cms:property and cms:decorate tag is always toLowerCase()
- Fixed issue #1024: parent group is shown correctly in the group overview
- Fixed issue #1027: new folder permissions test added to setup wizard
- Fixed issue with removing temporary flag after editing content
- Fixed issue with linebreaks in HTML-Converter
- Fixed issue in locale handler if non-existant resource has been requested
- Fixed issue in FlexController that sometimes caused NPE errors during system startup
Support of new database versions
- MySQL 5.0.x
- Oracle 10g
- MS SQL Server (contributed by Andras Balogh, experimental)
For a complete list of features of OpenCms 6 compared to older versions, have a look at the OpenCms 6.0.0 release notes.
OpenCms 6.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 to the new 6.2 release, we will provide an upgrade wizard for the final 6.2 release. No wizard is provided for this OpenCms 6.2 beta release.
Compatibility with Java versions, Servlet containers and databases
OpenCms 6.2 beta 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 beta works "out of the box" with Tomcat 5.0.x and Tomcat 5.5.x. Others have reported deploying 6.0.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 contributed thanks to Antonio Core. maxDB support has been contributed thanks to Clovis Wichoski and Fabiano Rech. MS SQL server support has been contributed thanks to Andras Balogh. We still are looking for volunteers to support testing the stability of the PostgreSQL, maxDB and MS SQL server releases.
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 release is "build_6_1_8". Development of the 6.2 version is done in CVS "dev_6_0_1" branch. This branch will be merged to CVS HEAD when the final 6.2 release is available.
How you can help
Contributions to the OpenCms core development are most welcome. Please contact email@example.com in case you are interested in supporting the development of OpenCms 6, or give your feedback on the opencms-dev mailing list.
Please use our Bugzilla to report bugs in this release: