This is in Mag 3.6.5, right?
We observed the same behavior. In 3.6.3 moving a page deactivated it.
Now in 3.6.5 one gets a deactivation warning, but then it's yellow and
we also hat the case where the new order was not reflected on the
public instance. I don't have enough "hard facts" to open a JIRA issue
yet though.
-will
On 09.04.2009, at 14:08, 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]>
----------------------------------------------------------------
