This release has been tested on the following stack:
DB: MySQL 5.1 and PostgreSQL 8.4
App Server: Tomcat 6
JDK Version: 1.6 u19
Server OS: RHEL5 and Win2008
Note, latest patches are always recommended.
The Simple Edit option in the Share client supports Windows only and requires Internet Explorer 6 or higher to be installed on the client machine.
To use the Simple Edit option, you must install the SharePoint Protocol Support AMP.
An issue has been discovered in the virtualization server, a *temporary* workaround is to explicitly set 'alfresco.jmx.dir' with absolute directory path to the location of the 'alfresco-jmxrmi.password' file.
eg. add following to 'alfresco-global.properties' and replace <absolute_path_to>
This will be fixed in the forthcoming 3.3g Community release.
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.
ML Text Properties
MLText properties (Title and Description) can sometimes appear to lose data when saving and viewing a document's metadata across two different browsers.
This occurs when the browsers are using different language preference settings i.e. one browser is set to 'English-United States' whilst the other is set to 'English-British'. The properties are saved successfully, but to the relevant locale. Non MLText properties such as Name and Author will not show this behaviour.
To guarantee all users consistently see the same values ensure all browsers are using the same language preference configuration.