![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
5.1 |
|
Assignee:
|
Unassigned |
|
Attachments:
|
Screenshot 1.png, Screenshot 2.png, Screenshot 3.png, website.demo-project.about.xml |
|
Components:
|
pages app |
|
Created:
|
03/Oct/13 4:03 PM
|
|
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
![]() ).
|
|
Environment:
|
5.1 RC2 Enterprise Edition
|
|
Fix Versions:
|
5.1 |
|
Project:
|
Magnolia UI
|
|
Labels:
|
usability
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Andreas Weder
|
|
Security Level:
|
Public |
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <
[email protected]>
----------------------------------------------------------------
