[MAGNOLIA-5375] Add configuration possibility to ImportCommand to change activation state to "unpublish" after import Created: 03/Oct/13 Updated: 26/Sep/17 Resolved: 16/Oct/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.1 |
| Fix Version/s: | 5.1.1 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Andreas Weder | Assignee: | Milan Divilek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | usability | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
5.1 RC2 Enterprise Edition |
||
| Attachments: |
|
||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||
| 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
|
||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Sprint: | 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:
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 |
| Comments |
| Comment by Andreas Weder [ 03/Oct/13 ] |
|
Attached the XML file I've imported. |
| Comment by Daniel Lipp [ 11/Oct/13 ] |
|
those tickets somehow conflict with each other |
| Comment by Daniel Lipp [ 11/Oct/13 ] |
|
Reverting for now as it needs further discussion... |
| Comment by Milan Divilek [ 16/Oct/13 ] |
|
By default import command preserves activation state, but added new configuration property forceUnpublishState. If forceUnpublishState is set to <code>true</code> then activation state of node will be change to unpublished during import. |