P.S.: Does anyone know what the new option "remove old container" or something like this does in the move process? The release.txt tells something about
better moving of pages... but what's better / why is it better / what does it do?
The back-end of the move feature was a bit refactored in order to better manage versioning operations (most of the CVS do even not support move operation. this is quite complex and tricky to implement with versioning support (unmove feature)).
But the "remove old container" feature is just a new option. In fact when you move a page, you only move the page field value (the A HREF link if you want) and the sub-page (the pid). However you may perfectly move a page inserted in a more complex container (e.g. an adressbook container with one of the field being a page field) to another "lighter" container (a simple navigation container with only one page field and no other field). Before 4.0.5 you were loosing the information contained in the old previous container after the move (automatic deletion of the old parent container even if it was containing perhaps other still useful information). Right now you have the choice of keeping the old parent container (for example the address entry in an adressbook list) while still being able to move the page elsewhere on the site.
However this operation still do not copy the other parent container value if the destination container is the same (you move a sub page of your adressbook entry on another addressbook template on the site. Then the destination container will not automatically copy the value of the previous parent container (e.g. name, addree, tel number,... fields)). In such a case you still have to use some Jahia event listeners in order to do it (cf. doc listing template where you can move a "doc_detail" to another similar doc_listing parent template without loosing the information in the parent container).
But for simple navigation operation with simple nav containers this is not really relevant.
Cheers St�phane
