This release rolls up a number of maintenance fixes to the Alfresco Enterprise Edition 3.2r release. This release replaces both Release 3.2 SP1 and Release 3.2 SP1.2 and resolves the performance degradation and content purging issues that were discovered in these releases.
If upgrading from 3.2 SP1, please perform the checks documented in the Known Issues section of the 3.2 SP1 release notes to ensure no data loss has occurred before continuing.
Please back up your database and content store before attempting to upgrade from a previous release.
For instructions on how to install Alfresco Enterprise 3.2 SP1.8, refer to the Alfresco Administering a Production Environment guide, available via the Alfresco Network.
This release requires the jTDS driver version 1.2.5 for compatibility with SQL Server, unlike version 3.2 Enterprise, which was certified with the Microsoft driver. We plan to certify future versions with jTDS.
The following known issues are associated with this release:
Missing Database Indexes
In issue ALF-3189 some tables were found to be missing indexes on some foreign key columns for non-MySQL databases. This has been rectified in Release 3.2 SP1.9.
When there are existing email templates in Alfresco 3.1.1 and then an upgrade is performed the templates are still present and in the same place as they were but can no longer be selected when specifying a template to use when creating a 'Send email to specified user' action in a rule. This problem does not occur on a clean installation of Alfresco, only an upgrade one.
A fix ALF-1816 is provided for this in 3.3 Community release, but please 'cut' and 'paste all' actions to move all custom templates from their 'Email Templates' folder to either the 'Invite Email Templates' sub-folder (if they are templates for site invitations) or the 'Notify Email Templates' sub-folder (if they are templates for notifications of new content). The standard product ones will have been moved automatically.
Edit online via CIFS is no longer supported
Due to heightened security in modern browser versions, we have removed cifs as a supported value of the <edit-link-type> element in web-client-config.xml. Allowable values are now http or webdav.
Major Fixed Bugs
Upgrade removes content if transaction retries are triggered
'patch.convertContentUrls' (3.3 Community, 3.2SP1) can result in 'No ContentData value exists for ID' errors
Content Cleaner cannot be enabled: Migrate pre-3.2 content URLs to new format
contentStoreCleanerJob leads to foreign key exception
Degradation of performance between 3.1.1 and 3.2x (observed in JSF)