cancel
Showing results for 
Search instead for 
Did you mean: 

NONE of my Alfresco 1.4 customizations work in 2.0!

alexr
Champ in-the-making
Champ in-the-making
I have posted several request on this forum now, asking why my 1.4
(webclient) customizations don't work in 2.0.

Even the following addition (to make all content versionable) to the contentModel.xml file:

<mandatory-aspects>
   <aspect>cm:versionable</aspect>
</mandatory-aspects>

Doesn't work in 2.0 although it works fine in 1.4

Adding custom mime-types and custom contentmodel doesn't work either in 2.0 the way it worked in 1.4
Furthermore adding the contentmodel as defined for 1.4 throws the following error in 2.0:

Please correct the errors below then click OK.
<<<<<<<<<<<
    * A system error happened during the operation: Transaction didn't commit: Integrity failure
>>>>>>>>>>>

The only advise I got on the mime-type extension post was to check the WiKi. Which I did, but found nothing different then what I already knew and tried.

I cleared the Tomcat work directory for Alfresco and removed the Webapps entry for Alfresco then restarted Tomcat. But no effect!

I checked all the documents of Alfresco, but see no change to the way I implemented those customizations.

Is there a 1.4 to 2.0 migration document which explains what the differences in customization are.

Please help (desperate cry),

Kind regards,

Alex
4 REPLIES 4

derek
Star Contributor
Star Contributor
Hi,
We're not aware of any issues or significant changes.
Post the stack trace, in case there is some deeper incompatibility between the 2.0 and your data.  Or at least, post the integrity messages, along with the pertinent sections of your model.
Regards

alexr
Champ in-the-making
Champ in-the-making
Hi Derek,

Besides the customization on "always versioning" as described in this post (which is a simple
setting) I have problems in 2.0 to implement custom mime-types for
MS Visio and MS Project and to implement our custom model which extends "cm".
Both are described in the following Alfresco forum links.

http://forums.alfresco.com/viewtopic.php?t=5049&highlight=

http://forums.alfresco.com/viewtopic.php?t=5050&highlight=

The content model name has been renamed to "blabla".

Somehow I get the feeling that some changes have been made to the way one needs to implement models/aspects etc. between version 1.4 and 2.0

There is no current data besides checking in test documents in a clean repository. So there is no conflict with existing data.

I don't get a stack-trace. Is there a way to get more trace/logging info on
the Alfresco server for these issues?

I also tried file-comparing on 1.4 and 2.0 versions of the (xml)files involved (as shipped with the product, so not the customized ones), but they look quite similar.

No clue here.

Again on version 1.4 all customizations work perfectly, but on version 2.0 they don't.


Kind Regards,

Alex

alexr
Champ in-the-making
Champ in-the-making
After some Sherlock Holmes work I found out that a number of xml configuration files have become more restrictive since 1.4
Some values or relations that were ignored in 1.4 are definetly used in 2.0
and will cause failure to start the alfresco application when encountered.

Fixed those integrity issues and customizations are up-and-running in 2.0 at this moment.

Kind regards,

Alex
:wink:

steve
Champ in-the-making
Champ in-the-making
Hi,

Could you post your fixes please?

Thanks,

Steve