Grégory Joseph ha scritto:
Hi Matteo,
Well.. "it's not a bug, it's a feature" ;)
You have to activate child1 now, and it will appear in the right place.
If all you want to do is hide it, you can simply de-activate it.
Hi Grégory,
it sounds me a "strange" feature.
I don't know enough about the reasons which brought to that feature, but
I say that when you move an activated node, you stop to be consistent
between instances, because you have nodes on public instance potentially
no more removable (with standard deactivation, you can remove then with
public instance .magnolia access).
So, imagine something like this.
I'm an author.
I have a protected area (e.g. /protected) and a public area (e.g.: /home).
If you have pages activated under /home and you want to make them
protected, you simply think: just move them! The result: the moved pages
are still available on public area! And also (once activated) on
protected area, so you can think to be safe, but you aren't!
Prior to 3.6, moving was de-activating immediately, but, correct me if
I'm wrong, this was just a wrong behavior...
See http://jira.magnolia-cms.com/browse/MAGNOLIA-2173
You say: Well, deactivation doesn't happen anymore indeed, but we still
get the alert box!! this is VERY confusing.
This is what I see on my 3.6.3...
Matteo
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
