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.3 SP1, refer to the Alfresco Administering a Production Environment guide, available via the Alfresco Network.
The following known issues are associated with this release:
Tightened Validation of Content Models
The fix to ALF-680 means that some custom content models that may have previously worked with earlier releases will now be rejected on start up of the Alfresco server with the following message
org.alfresco.service.cmr.dictionary.DictionaryException: 06010000 Cannot define class c as namespace n is not defined by model m
It is now only possible to create model elements whose namespace is also defined by the containing model. The reason for this tightened validation is that previously it was possible to define duplicate model elements (in particular properties, associations) without knowing it.
In order to fix any failing content models you will need to
Edit all constraint, type, aspect, child association, association and property definitions in the model XML file so that their name uses a namespace prefix mapped to a unique namespace defined by the model.
Start up the Alfresco Server to ensure that the new model is now valid.
To fix up the database:
Create a new node of each of the fixed types with each of the fixed aspect types and fixed association types to ensure that all the new qname_ids now exist in the database.
For changed node types and aspects
Look up the old and new qname_ids
Update the qname IDs in the alf_node and alf_node_aspects tables directly
For changed child associations, associations and properties
Look up the old qname_id of the child association, association or property
Look up the node_id of the owning node type or aspects from the alf_node or alf_node_aspects tables by qname_id
Update the qname_id of all the child associations, associations or properties with that old qname_id and node_id
Major Fixed Bugs
Below please find a list of major issues fixed in 3.3 SP1 Enterprise. For a full list of closed / fixed issues, please see JIRA issue tracking system.
Impossible to create web content based on DevCenter.xsd web form on WebSphere/DB2 tier
patch.db-V3.2-AddFKIndexes is failing on MSSQL Server 2008 on upgrade to 3.3.1 E build 95
XSS attack is made in Wiki tab if First/Last user name contain xss
Oracle/DB2/SQLServer/PostgreSQL are missing indexes to support many FK constraints
TransferService - typo causes transfer target password to be taken from transfer target username (ie. admin / admin works) causing security hole
Freemarker causes NPE while deploying 3.3 enterprise onto WebSphere 18.104.22.168
Would like LDAP users to be able to add items to their profile such as a picture, skype details etc. (Explorer Client)
Script error at the' Create Category' form
Wrong precedence ticket based authentication/jsessionid cookie authentication
CMIS checkin of a non-versionable document should make it versionable
Script error at the 'Records Category View Details' page
It's impossible to destinate any action with data list item (IE6 specific)
Cannot find class org.alfresco.config.JBossEnabledWebApplicationContext
alfresco-global.properties' missing settings for JODConverter
XSS attack is made when a rule is being deleted
java.lang.NullPointerException when using NTLM auth and client which does not have cookie support
Update incorrect mimetypes (Excel and Powerpoint) ...
Bitrock installer: there is no virtual Tomcat and console mode scripts.
JBoss: Cannot create GoogleDocs documents
Select > None feature for Data Lists not working across multiple pages in IE