OpenCms 6.2 release notes
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
- 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
- New frontend module to display photo albums conveniently on a website
- New frontend module containing the new resource type "layout pattern page" that allows content
to easily create new web pages from from predefined paragraph layouts
- 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 WYSIWYG fields
- XML content WYSIWYG fields use the user configured editor (if possible)
- Improved XML content editor dynamic HTML generation for element operation buttons and localized help texts
- Added <cms:img> tag that automatically generates HTML for scaled images
- 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
Added several new mime type settings to the "mimetypes.properties" file
- Fixed issue #878: PostgreSQL now uses the right db name during installation (thanks to Ivan Codarin)
- Fixed issue #995: improved scrubbing of statically exported files
- Fixed issue #999: addCookie() and sendRedirect() can now be used on a JSP page
- Fixed issue #990: it is now possible to set the status code in a JSP using the CmsJspBean
- Fixed issue #1001: added confirmation to lock dialog if a folder contains already locked resources
- Fixed issue #1002: static export does not produce NPEs in BackupHandler anymore
- Fixed issue #1004: editor preview button is now working even if the edited file is expired
- Fixed issue #1010: PostgreSQL user / group delete problems are solved (thanks to Ivan Codarin)
- Fixed issue #1015: simultaneous creation of new XML content resources with frontend direct edit button is now possible
- Fixed issue #1030: detail issues fixed in the 'Administration view' list
- Fixed issue #1032: needless module sub-directories are skipped during setup
- Fixed issue #1033: Setup wizards now checks for image scaling issues
- Fixed issue #1035: long project names do not make 'Preferences' and 'Exit' buttons disappear anymore
- Fixed issue #1043: Html from FCKeditor and XML contents is now re-formatted while saving, so that "diff" can be used
- Fixed issue #1047: change MySQL tables from MEDIUMBLOB to LONGBLOB to allow resources of size > 16MB
- Fixed issue #1049: multi copy & move operations now work with relative paths
- Fixed issue #1051: Administration menu width is now adjusted during refresh
- Fixed issue #1052: FCKeditor now shows new unpublished images in WYSIWYG view
- Fixed issue #1064: font modifications in upload applet to let it work on systems without the Verdana font
- Fixed issue #1092: WYSIWYG editor property popup window now has scrollbars to avoid problems accessing ok/cancel buttons
- Fixed issue #1105: Added entry for MS IE 7 in editor_configuration.xml
- Fixed issue #1106: User name validation is now always using the same constraints
Improvements to database support
- MySQL 5.0.x
- Oracle 10g
- PostgeSQL 7 + 8 issues fixed (thanks to Ivan Codarin)
- MS SQL Server (contributed by Andras Balogh, experimental)
For a list of features of OpenCms 6 compared to version 5, have a look at the OpenCms 6.0.0 release notes.
We recommend everyone who uses an earlier version of OpenCms to update to the 6.2 release. In case you are using one of the previous versions (OpenCms 6.0.x or 6.2 beta ), there have been a lot of issues fixed in the final 6.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 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 or 6.2 beta to the new 6.2 final release, an easy to use upgrade wizard is provided. The update wizard can automatically update OpenCms version 6.0.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4 and 6.2 beta to 6.2 stable.
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 release is "build_6_2_0". Development of further releases will be done in the CVS HEAD until further notice. Upcoming development version will use the version numbers 6.3.x 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/