Hello all,

At my little talk about the hierarchy in the datamodule at the conference last 
week, an interesting question was asked. We set up the types in hierarchy, and 
the Tree Gui forces/guides the user to follow this hierarchy. (If type b is a 
child of type a, the user can only create nodes of type b as a child of nodes 
of type a.) But in the context menu the 'move' option exists, which gives the 
user the possibility to mix up this hierarchy.

What to to with this problem? Adapting the behaviour of the move and copy 
command is not the way to go surely. What about this possibility:

Add a property to the DataModule with name "allowNodeCopyMove", default this is 
set to false. This removes the move and copy command from the Data tree context 
menu and function bar. Order cannot be changed in the tree, but in case of 
emergency you can do that in the JCR browser of the datamodule.  You can give 
webeditors the permission on the tree, but not on the JCR browser for example. 
If you trust the webeditor or your code does not rely on a strictly maintained 
hierarchy structure, the allowNodeCopyMove can be set to true.

Please share your views on this issue.

There is also the "sort by name" issue. I think it should be allowed to be set 
only on the type which is the root in a tree of types. The actual sorting is 
done for the whole tree, not per type within that tree. Another problem then 
comes up: you can have two root types sharing the same rootpath. If type I has 
the sort set to true, and type II does not, what to do then with that sorting? 
I am not at all convinced of the use of sorting by name anyway. These views 
will probably only be seen by webeditors or developers, using the nodes in the 
website has nothing to do with the sorting in the tree in AdminCentral.

Again, please share your views on this issue please.

Regards, Bert


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to