Table of Contents
by Jeff Teeters
This is the 4.2 release of the ArsDigita Community System (ACS). The previous release was 4.2 beta. This release has minor documentation changes, bug fixes, and some new URI utility procedures (see below). For a complete list of bugs fixed in 4.2, please visit the SDM page for 4.2.
Note: The version numbers of ACS packages are *not* necessarily correlated with the ACS release number. The release number of a package will be increased only in proportion to the significance of the changes made. If there are no changes to a package the version number of the package is unchanged.
Similarly, the version of the ACS release is increased according to the quantity and significance of the changes. This release is designated as 4.2 because only minor changes were made since the previous release (4.2 beta).
URI utility procedures. Procedures to parse URIs (Uniform Resource Identifiers) and resolve relative URIs are included in file packages/acs-tcl/tcl/uri-procs.tcl. Thanks to Aaron Swartz for contributing these routines.
Minor documentation changes. Minor changes were made to documentation in the acs-content-repository and acs-templating packages.
Bug fixes. See the SDM for 4.2 for a list.
ACS Content Repository. Release number increased from 4.1.2 to 4.1.3. Minor changes to documentation.
ACS Core Documentation. Release number increased from 4.1.1 to 4.1.2. Using new company logo on pages.
ACS Tcl. Release number increased from 4.1.2 to 4.1.3. In file tcl/apm-file-procs.tcl, modified call to function ad_find_all_files to include option: "-check_file_func apm_include_file_p". This filters out non-APM (e.g. CVS files). Modified tcl/security-procs.tcl to prevent an invalid token_id from being cached. Added file tcl/uri-procs.tcl.
ACS Templating. Release number increased from 4.1.2 to 4.1.3. Minor changes to documentation formatting.
Other packages. Packages included with this release and which did not change from the previous release (4.2 beta) are listed below, along with their version:
In order to run ACS 4.2, you must be running:
AOLserver and the Oracle driver are obtainable from http://www.arsdigita.com/download/. Developer versions of Oracle are available for download from Oracle Technet. A version of ACS 4.0 that runs on PostgreSQL is under development by the OpenACS team.
Please make sure that you have fully upgraded your system to ACS 4.2 beta before upgrading to ACS 4.2. For instructions on how to upgrade to 4.2 beta, please see the 4.2 beta release notes included in the 4.2 beta distribution. In order to upgrade your server, you should:
Stop your server.
Obtain the ACS 4.2 distribution from http://www.arsdigita.com/acs-repository and replace all the files in your ACS 4.2 beta system. If you have customized any of the ACS 4.2 beta files, please make sure that your work is not lost when extracting the archive. The recommended approach in this situation is use a local cvs repository for your project, extract the tar.gz file to a temporary directory, then do a cvs vendor import to your repository from a the extracted files. Another approach is to to update your files using CVS through the public server :pserver:anonymous@cvs.arsdigita:/usr/local/cvsroot using the tag acs-4-2-R20010417. However getting the files by cvs using the tag at arsdigita.com will not include the html documentation because the html documentation is not stored in the arsdigita cvs repository but instead is generated outside the repository (from xml files) when a release is created. For further information on CVS, please consult CVS and 4.0 Client Development.
Restart your server.
Login as a System Administrator and go to /acs-admin/apm. Click Install Packages and wait for the installer to load.
A list of packages that need to be upgraded and enabled will appear. Click on the Next button.
A list of three data model scripts will appear for "ACS Content Repository 4.1.3". These should be already loaded, but it does not hurt to load them again. Leave the checkboxes selected. Click Install Packages and the upgrade will proceed.
Restart the ACS server.
Any feedback or comments about the ACS can be sent to acs@arsdigita.com. Please report all bugs with the ArsDigita Software Development Manager (SDM).