Grégory Joseph ha scritto:
Well, you either de-activate them, or move AND activate the move.
No, I simply move one node from one place to another.. no explicit de-activation.
When you add or edit a page on your author instance, these changes are not activated (visible on public instance) immediately, why would that be the case when moving a page, which is just another modification to a page ?
I basically agree with you, but the point is that in my example "child2" can not be deactivated anymore with standard commands. You must go on public instance and then delete it. In other words: looking only the activation lights (red / green / yellow) there are no awareness of "pendling" pages on public instance(s).
Anyway, knowing that, it is only a best-practice to follow: when you move a green node, first deactivate it :-)
Yes your author and public instances are not in synch anymore, just like when you add/edit a page, which is the whole point of having separate instances in the first place, no? ;)
Yes, but from my point of view it is not the same having (1) a new page (red) e.g. a draft page on author without having the matching page on public than having (2) a page on public without the possibility to edit it on author. It is "normal" effect on a generic two-instance environment, but it sounds strange over an "Author-Public(s)" environment.
But, I repeat myself, this issue can be avoid with some knowledge and best-practices...
Matteo ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
