Details
-
Bug
-
Resolution: Fixed
-
Critical
-
5.1
-
None
-
5.1 RC2 Enterprise Edition
-
-
Empty show more show less
-
Yes
-
5.1.1
Description
When I import a previously exported file, the new nodes are created alright, but their publication state is equal to the nodes I've exported. Their publication state, however, should be "unpublished" instead.
This is also bad because it leads to supposedly "weird" behavior, which in fact wouldn't be seen as weird if I knew the actual publication state of the pages I work with. As an example, if I change a child page in the imported tree and try to publish the change, I'm told that the parent page is actually not yet published. Since it looks published, however, this is confusing.
Steps to reproduce:
- Export the "article" page hierarchy of demo project (see Screenshot 1.png
). - Select the demo feature root page, then import the XML file you've just exported (see Screenshot 2.png
). - The imported sub tree shows a wrong publication state. In this case, all pages look published (see Screenshot 3.png
).
The behavior above is correct. We want by default preserve activation state, but we decide to do the behavior configurable. If someone wants have content "unpublish" he can add
Checklists
Attachments
Issue Links
- is related to
-
MAGNOLIA-5351 Moved or deleted items (pages, components) do NOT update activation status
-
- Closed
-
-
MAGNOLIA-7160 Imported files inherit the status of original files
-
- Open
-
- relates to
-
MAGNOLIA-5119 Set proper activation status in bootstrap files
-
- Closed
-