[MNT-7376] ACP export/import - aspects info is lost during process and node versions are not imported Created: 19-Oct-09  Updated: 19-Mar-13  Resolved: 03-Oct-11

Status: Closed
Project: Service Packs and Hot Fixes
Component/s: Repository
Affects Version/s: 3.0, 3.2
Fix Version/s: 4.0

Type: Service Pack Request
Reporter: Jakub Sobolewski (Inactive) Assignee: Closed Issues
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Bug Priority:
Category 2
ACT Numbers:

14233, 34965 

Testcase ID:

Explorer-2389


 Description   

Simple test case:
1) Create space and some text content.
2) Add versioning support for this content and update it to create new version.
3) Export space and content to ACP
4) Delete space
5) Import from ACP

After import cm:versionable aspect is lost. Info about aspect is written in XML (inside ACP) but it is not restored... also only latest version of content is exported.

Is this behavior correct ?

If not this is a serious issue... if I want to update data model on production (change some types for instance) Alfresco won't let me if there is any data in repository referencing changed type... The only solution is to export data, change data model and re-import data. That would be OK but because of this issue there will be huge data loss (all node version history is gone) and this is not acceptable :/

Alfresco Labs 3 Stable, Ubuntu Server 8.10
Same issue on 3.2

Regards



 Comments   
Comment by Heiko Robert [ 26-Feb-10 ]

please include also in the analysis/solution: categories, translations
they also have big issues in export/import and should be handled in the same way

Thx Heiko

Comment by Jan Vonka [ 20-Apr-10 ]

Duplicate (refer to ENH-329)

Comment by Niyi (Inactive) [ 11-May-10 ]

Jan -

I can't seem to locate the issue that you're referring to. How do I view this issue? (ENH-329)

Thanks.

Comment by Ravi Manthena [X] (Inactive) [ 02-Sep-11 ]

Assigned to Alfresco QA Team for retesting in enterprise head build 409 onwards

Comment by Alfresco QA Team (Inactive) [ 08-Sep-11 ]

Validated on Alfresco Enterprise v4.0.0a build 409 (r30055), Tomcat, PostgreSQL, Java (all installer deployed), WinXP, FF 5.0.

Steps to reproduce:
1. Export some space containing content with multilingual aspect, version history and categories added.
2. Import content into another space.
3. Verify that content has multilingual aspect, version history and categories.
Actual result: the content is not multilingual any more, has no category. Version history include only latest version.

Thank you, NataliaGu.

Comment by Steve Rigby [X] (Inactive) [ 08-Sep-11 ]

Issue still present.

Comment by Ravi Manthena [X] (Inactive) [ 15-Sep-11 ]

Assigned to Alfresco QA Team for retesting using Head Build 463

Comment by Alfresco QA Team (Inactive) [ 30-Sep-11 ]

The issue is reproduced on Alfresco Enterprise v.4.0.0a (b487), RHEL 5.5 x64bit, MySQL 5.5, mysql-connector-java-5.1.17-bin.jar, Tomcat 6.0.29, JDK 6 u22 x64, Alfresco+ OpenLDAP, Client: Wondows XP, FF 6.0.2
After importing the content is not multilingual any more, has no category. Version history include only latest version.
Thanks, NataliaGu.

Comment by Ravi Manthena [X] (Inactive) [ 07-Oct-11 ]

Assigned to Alfresco QA Team for retesting

Please make sure you are using the following build 532 and also make sure the subversion revision number is 30975 or less.

Comment by Alfresco QA Team (Inactive) [ 12-Oct-11 ]

Validated on Alfresco Enterprise v4.0.0b build 532, RHEL 5.5 x64bit, MySQL 5.5, mysql-connector-java-5.1.17-bin.jar, Tomcat 6.0.29, JDK 6 u22 x64, Windows XP, FF 5.0.
Closed according to https://issues.alfresco.com/jira/browse/ALF-672?focusedCommentId=126799&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-126799
NataliaGu

Generated at Thu Aug 05 15:28:07 BST 2021 using Jira 7.13.15#713015-sha1:7c5ddd2c3e1709974ae9c48c17df8edd3919fe2c.