OpenCms version 5.0 beta 2 released
Alkacon Software together with the OpenCms Group has released version 5.0 beta 2 of OpenCms, one of the leading open source content management solutions. This version is a major step towards the final release of OpenCms 5. It adds a number of important features especially for the JSP integration and caching mechanism. The most visible change from previous versions is the new structure of the OpenCms workplace in the virtual file system (VFS), which now has a much more streamlined directory layout. A long list of minor enhancements and fixes completes this release.
OpenCms 5.0 beta 2 is Open Source software published under the LGPL license. The software is freely available from the OpenCms website. The OpenCms 5.0 beta 2 includes all features from the last "major" release 4.6.1, the FLEX alpha 1, the 4.7.7 version and of course the 5.0 beta 1. It's at last as stable as all of these earlier versions. I encourage everyone to try this version and provide feedback on the opencms-dev mailing list.
OpenCms 5.0 beta 2 supports Java 1.4. and 1.4.1. Because of required features related to file encoding and JDBC we recommend not using earlier releases of Java.
The almost complete list of changes and improvements in OpenCms 5.0 beta 2:
- JSP now support nested includes with XMLTemplates
- The JSP cms:include tag functionality has been extended, the include target can now be set from a property, from an expression in the tag's body or from a request attribute
- More new and improved JSP tags for easier template development
- Exception handling in JSP now directly points to the problem (even if it is in an included element)
- The FlexCache for caching of JSP now implements a LRU policy and can be fully configured in the opencms.properties
- A new class com.opencms.flex.jsp.CmsJspActionBean provides access to the OpenCms taglibs features through JSP scriplet code
- The new, streamlined 5.0 workplace directory layout is in place
- The new "directory translation" feature allows setting resource name translation rules in opencms.properties for backward compatibility
- The "file name translation" feature automatically replaces illegal characters (e.g. space, ? or &) in uploaded file names and in extracted ZIP files, rules can be set in opencms.properties
- The default file name for a directroy (the page that is displayed if a user just requests a directory name, usually "index.html") can now be defined in the opencms.properties and in the folder property default-file
- The handling of default files (like "index.html") has changed: if a default file was found it is now returned directly by OpenCms (in previous versions a redirect to "index.html" was send)
- The default file encoding is now UTF-8 for better international support, please note that this change is preliminary and subject to further observation
- A default index.jsp "Welcome to OpenCms" page is now included in a new installation with a simple default template
- New "replace" feature in the workplace context menus, it's now possible to replace e.g. an image in the VFS by an uploaded image with a different name directly, keeping the VFS name and file properties
- If you upload a file in the workplace and a file with the same name already exists, you are now asked if you want to overwrite it (instead of OpenCms throwing an exception)
- New "touch" feature in context menus allows setting of the file "last changed" timestamp
- When exporting files with the "Database export" feature, you can now set a max age for the content to export, i.e. export only files that have changed after a specified date
- Page body files (now stored in /system/bodies) are now automatically exported when a "page" type file is exported
- The <stylesheet> tag in XMLTemplates can now also be defined in the mastertemplate (in addition to the frametemplate)
- The <stylesheet> tag in XMLTemplates (for display of the style sheet in the HTML editor) can now start with a "/"
- Added an option to the HTML editor to remove the "new body" function while keeping the body selector (to be used with default bodies)
- Module management: Added support for "simple" modules
- When importing resources the content of files is converted if the encoding parameter does not exist in the xml- or meta-tag, this should provide the ability to import content exported from 4.x versions into a 5.0 system
- If the property definition for a property of an imported resource does not exist, it will be created during the import
- Fixed some issues in the HTML editor with the new link dialog, it's now also possible to add links to images
- The locale "uk" has been renamed to "en"
- Usage of methods deprecated in Java 1.4 has been removed where possible
- Issues with XML export of filenames that use special characters (like umlauts) have been resolved
- Issues with XML export or registry with special characters (like umlauts) have been resolved
- Fixed ElementCache for DumpLauncher, for dumped elements no file.encoding translation is allowed
- Fixed ElementCache for MethodElements, switched handling from byte to String
- Fixed a bug in the cache settings that prevented PDFs from offline projects to be displayed in Acrobat Reader
- Refactoring of constant names for VFS paths and directories in com.opencms.workplace.I_CmsWpConstants
- Some cleanup of code and JavaDoc documentation in packages *.core and *.flex (still a long way to go here)
- Additional options for the setup wizard to enable / disable Flex JSP and directory translation options included
- The deprecated FOP based PdfLauncher was removed
- The login dialog page has moved to /system/login, it now features improved behaviour for active sessions
- Changed the workplace style sheet to fix problems displaying special characters like german umlauts
With the new release, Alkacon Software continues it's increased efforts in adding and enhancing support for the standard JSP and JSP Taglib technology in OpenCms. Alkacon has also started to improve the OpenCms workplace with a lot of features that make life and work with OpenCms easier. The team at Alkacon continues working towards the final release of the 5.0 version.