These are the release notes for Red Hat Content Management System 6.1. They contain an overview of Red Hat CMS 6.1, an installation reference, a list of known issues, and an enumeration of significant changes since Red Hat CMS 6.0.
The Red Hat CMS 6.1 is a full-fledged content management system that manages the content creation and delivery processes of a web site. CMS enables an unlimited number of people to easily create content for a website, have the content be approved by an administrator, and published live on the website.
Red Hat CMS also has built-in support for templating, content lifecycle management, permissioning, and user-defined content types. For more information, visit http://www.redhat.com/software/rha/tech/.
CMS 6.1 is a significantly improved version of CMS that features numerous usability enhancements, an improved publishing API, and notable performance improvements. The focus of this release is on stability, performance, and ease-of-use.
Specific improvements in CMS 6.1 include:
The CMS user interface has been enhanced to provide additional usability. Improvements have focused on reducing the number of clicks required to perform common actions (e.g., authoring content), increasing the amount of useful information presented to the user (e.g., breadcrumb navigation, item summary pane display), and improving the configurability of the user interface to display information (e.g., default home folders, sortable columns).
An open source WYSIWYG editor (HTMLArea 3.0 RC1) is now used instead of a plain HTML text area for users who directly author content. The WYSIWYG editor supports Mozilla 1.3+ and Microsoft Internet Explorer 5.5+. A text area is automatically displayed for older browsers. Prior versions of CMS had a less-functional WYSIWYG editor that only worked on Internet Explorer 5.5. Also refer to Section 1.7 Known Issues for a browser detection problem.
Templating now supports direct uploading of XSL templates for any template context. Previously, XSL templates required uploading a JSP template that invoked the XSL. Now, custom XSL can be uploaded for any content type or content item.
The publishing API has been updated to provide explicit support for associations between top level items.
Performance throughout the CMS has been enhanced. The authoring UI was profiled to improve multiuser performance. Another area of performance improvement is in p2fs (publish-to-filesystem).
Category Purposes are now replaced by use contexts, which enable multiple category hierarchies per content section.
Content types are now shipped as separate, independent packages. Administrators can selectively install and/or upgrade content types.
The authoring UI for the formbuilder has been improved to simplify form creation. A new XML generator for formbuilder provides independence from Bebop XML, enabling web designers to more easily style form items. The new form items also allow the specification of a CSS class for each form item. A new HTTP post form processing action that sends data directly to a remote server has been added. Custom XSL can be uploaded for individual form items.
This release includes a rewritten CMS Administrator Guide, CMS User Guide, and CMS Developer Guide..
All bug fixes available in the CMS 5.2.x and 6.0.x errata series as of 1 March 2004 have been merged into this release. See the CMS 5.2.x and 6.0.x release notes for details of specific fixes.
Red Hat Web Application Framework 6.1 is copyrighted 1999-2004 by Red Hat Inc. It is released under the CCMPL 1.0. The text of the CCMPL 1.0 can be found at http://www.redhat.com/licenses/ccmpl.html.
The CCMPL is based on the OSI-approved IBM Public License Version 1.0 (http://www.opensource.org/licenses/ibmpl.html). The IBM Public License is a true open source license that requires open-sourcing of any modifications or other "derivative works."
The most recent installation documentation is available at http://rhea.redhat.com.
CMS 6.1 requires a complete and working installation of WAF 6.1.
Documentation for Red Hat CMS, including installation guide, Javadoc, developer guide, and engineering standards, can be found at http://rhea.redhat.com.
Upgrading is a one-way, irreversible process. Thoroughly test the upgrade on a backup copy of your database before upgrading your production system. Carefully read the following instructions before attempting the upgrade process.
You must completely upgrade your server to CMS 6.0.1 (not 6.0.0) prior to upgrading to 6.1. A complete upgrade requires you to run the schema upgrade files for your database, starting your server, and shutting it down. You must start your server on 6.0.1 at least once prior to upgrading to 6.1.
You must upgrade WAF to 6.1 before upgrading the CMS. This should be done automatically with the ccm upgrade command as discussed in the WAF release notes only if your CMS installation does not have user-defined content types (UDCT).
If your CMS has UDCTs, you need to perform the following steps to upgrade WAF:
Run ccm-core/default/upgrade/6.0.1-6.1.0/dot-step-1.sql against your schema. This file is shipped as part of WAF.
pushd /tmp jar xvf /usr/share/java/ccm-core-version-sql.jar ccm-core/default/upgrade/6.0.1-6.1.0/dot-step-1.sql psql < ccm-core/default/upgrade/6.0.1-6.1.0/dot-step-1.sql popd
Run the WAF upgrade command:
ccm upgrade ccm-core --from-version 6.0.1 --to-version 6.1.0
After upgrading WAF to 6.1, upgrade CMS by executing the following steps.
Initialize the 6.1-related configuration infrastructure; the \ has been added for printing purposes, the command is one continuous line:
ccm load --config --init ccm-cms \ ccm-cms-types-agenda \ ccm-cms-types-article \ ccm-cms-types-event \ ccm-cms-types-job \ ccm-cms-types-legalnotice \ ccm-cms-types-minutes \ ccm-cms-types-mparticle \ ccm-cms-types-newsitem \ ccm-cms-types-pressrelease \ ccm-cms-types-service \ ccm-cms-types-formitem \ ccm-cms-types-formsectionitem \ ccm-cms-assets-fileattachment
If you ran ccm-core/default/upgrade/6.0.1-6.1.0/dot-step-1.sql, you must run ccm-core/default/upgrade/6.0.1-6.1.0/dot-step-2.sql against your schema. This file is shipped as part of WAF. Otherwise, skip this step and proceed to the next step.
pushd /tmp jar xvf /usr/share/java/ccm-core-version-sql.jar ccm-core/default/upgrade/6.0.1-6.1.0/dot-step-2.sql psql < ccm-core/default/upgrade/6.0.1-6.1.0/dot-step-2.sql popd
Execute the ccm upgrade command for CMS:
ccm upgrade ccm-cms --from-version 6.0.1 --to-version 6.1.0
You will not be prompted. This will upgrade any existing items to the 6.1 publishing API and then run schema upgrades. The amount of time that this upgrade will take is proportional to the number of content items in the system.
Upgrade file attachments. This must be executed in a separate ccm upgrade command since this package depends on the upgraded schema.
ccm upgrade ccm-cms-assets-fileattachment --from-version 6.0.1 --to-version 6.1.0
Run the publishing API upgrade. The amount of time the publishing API upgrade takes is proportional to the number of content items in your database.
Upgrade the multi-part articles package:
ccm upgrade ccm-cms-types-mparticle --from-version 6.0.1 --to-version 6.1.0
Manually migrate the contents of your 6.0 configuration file (enterprise.init) that are related to CMS initialization to the CMS-specific enterprise.init. For more information on customizing the enterprise.init, refer to the Red Hat Web Application Framework Installation Guide.
Set other configuration settings for your new 6.1 installation.
ccm set --interactive
Run ccm hostinit with the --clean flag:
ccm hostinit --parameter http-port=9090 --parameter shutdown-port=9091 --clean
A shell script that contains all the steps above is provided in doc/example-upgrade.sh. This shell script is provided as an example only, and should not be used without thorough testing and verification on your specific installation.
Please be aware that a number of APIs and systems have changed significantly in CMS 6.1. These changes are identified below; some of these changes may require you to update the code in your system.
The publishing API has changed. See the Javadoc for more details. In particular, the signature for ContentItem#copyProperty has changed, the PublishedLink class has been introduced to represent associations between ContentItem, and the CustomCopy interface has been added.
All previous CMS domain objects that defined a static TYPE constant have been changed to define a BASE_DATA_OBJECT_TYPE constant instead. Any code that relied on TYPE will need to be recompiled. See BZ 109206.
At server startup, the following warning appears:
com/arsdigita/content-section/ContentSection.pdl: line 115, column 37 [warning]: table already has primary key: com/arsdigita/content-section/ContentSection.pdl: line 41, column 38
This is expected behavior.
The WYSIWYG editor, HTMLArea, does browser detection based on build date to identify Mozilla browsers instead of version. Versions of Mozilla that have been built after the Mozilla 1.3 release (e.g., Mozilla 1.0.2) will be erroneously given the WYSIWYG editor, even though the editor does not support the browser. A similar effect occurs with Internet Explorer detection. The WYSIWYG editor does not verify that the Internet Explorer version is 5.5 or greater, so Internet Explorer 5.0 is also erroneously given the incorrect editor.
Please file bug reports in the Red Hat Content Management System section of http://bugzilla.redhat.com/bugzilla.
Last modified: $DateTime: 2004/04/07 13:22:42 $