Activation of subnodes fail when parent node has been renamed but change has
not been activated
-----------------------------------------------------------------------------------------------
Key: MAGNOLIA-2896
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2896
Project: Magnolia
Issue Type: Bug
Components: admininterface
Affects Versions: 4.1.1, 3.6.4
Reporter: Timo Pulkkinen
Assignee: Philipp Bärfuss
Didn't find this reported earlier, so here comes:
Steps to reproduce:
1. Create a simple hierarchy of pages, e.g.:
/parent/
/parent/child1
/parent/child2
2. Activate all nodes
3. Rename node parent to something else, e.g. parent2
=> After this parent2 is indicated to be changed after last activation (but
not deactivated)
=> Statuses of children are unchanged and appear to be public
4. Try to activate some of the child nodes, e.g. 'child1'
=> At least in version 4.1.1 activation fails with parent not found
exception message
The problem is resolved if the parent node is re-activated but this operation
apparently is not intuitive to the user and causes confusion.
Possible fixes:
* Preferably make node to be reactivated automatically after renaming if node
is already active
-Pros: Prevents deactivating by accidental renaming impossible
or:
* Deactivate whole subhierarchy if parent is renamed
- Cons: Accidental renames may cause large number of content to disappear
temporarily from public site
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
