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.
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
... or am I missing your point ?
-g
On Apr 9, 2009, at 2:08 PM, Matteo Pelucco wrote:
Hi all, I don't know if it has been already said, but:
"moving an activated node from JCR Browser (website) doesn't
deactivate the activated ones".
E.g.:
AUTHOR INSTANCE
- (A) parent
- (A) child1
- (A) child2
-(A) parent2
PUBLIC INSTANCE
- (A) parent
- (A) child1
- (A) child2
-(A) parent2
moving child1 (A) below parent2 generates a status like this:
AUTHOR INSTANCE
- (A) parent
- (A) child2
-(A) parent2
- (N) child1 *not activated*
PUBLIC INSTANCE
- (A) parent
- (A) child1
- (A) child2
-(A) parent2
So, child1 is not deactivated.
It is normal? It is a bug?
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
