Details
-
Improvement
-
Resolution: Outdated
-
Major
-
None
-
None
-
None
Description
In prior versions of Magnolia the activation of website subtree used to guarantee the full coincidence between this subtree on aithor and public. I think it's exactly what common user expects from activation. Now behavoir of activation is different, and the full coincidence between this subtree on aithor and public depends on previos history of this subtree.
For example (see attach)
1) Activate /0 incl subpages
2)Move /0/2/5 to /0/1
3) Activate /0/2 incl subpages
In prior versions of Magnolia "5" would get deactivated during step 2). Now it doesn't, so on public in /0/2 we see tree subpages in 5-3-4 order (btw it's very hard to explain to customer it's not a bug). It looks very unexpected and very hard to fix in big sites for editor, who knows nothing about "5" and where it is now.
If 3,4 and 5 are not of type CONTENT, but CONTENTNODE everything will work just as expected: on public in /0/2 we see two subpages.
I suggest to make activation logic for CONTENT equal to one for CONTENTNODE, so in my example "5" will be removed from public not after step 2, as it used to in prior versions, but after step 3. The only problem i see is in setting correct activation status to 5 (btw if 3,4 and 5 are not of type CONTENT, but CONTENTNODE activation status of "5" is incorrect after step 3 - yellow instead red).
If it is not possible to remove current activation logic, mayde it is posibble to give administrators possibility to switch between current logic adn the one i've just described?