[MAGNOLIA-2189] Imported node incorrectly shown as activated Created: 19/Jun/08  Updated: 23/Jan/13  Resolved: 20/Jun/08

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.6-m1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Philipp Bärfuss
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-2190 Incorrect activation status of subnodes Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

When exporting previously activated node, such node will be again shown as activated after reimporting even if it is actually not activated.



 Comments   
Comment by Philipp Bracher [ 20/Jun/08 ]

You have to use the correct import files. It might be that you import the data on the public as well (or the public is kept as is). This will be solved once we have a mechanism for synchronizing instances. But otherwise you never know if the status is correct (as making it deactivated by default might be wrong as well)

Comment by Jan Haderka [ 21/Jun/08 ]

I disagree, it would be correct in case UUID stays the same, but in my case I imported again while original content was still in place so it got assigned new uuid and in this case it should be definitively deactivated since even if doing the same on public you will never get same uuid.

Generated at Mon Feb 12 03:34:17 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.