> > On 08.09.2009, at 11:13, Andreas Weder wrote: > >> [...] >> Then I have to tell him that his media people can delete nodes >> without him >> being able to say anything about it. They might even only do so >> accidentally >> and change the published website immediately. > > Well, > #1 If the media people don't have the right to delete anything, you'll > need to hire an extra editor who's sole job will be "garbage > collection" ;-)
:-) That's not my intention, I prefer garbage collectors I don't have to hire. My point is: deleting a node should result in a deletion request, at least in a workflow-enabled magnolia instance. The current user experience is not consistent in this regard. All other operations on nodes result in a change request and have to be accepted or rejected. Deleting a node has an immediate effect and thus breaks a basic concept. > #2 If you absolutely need to prohibit a group of people from deleting > nodes you could do this with a custom tree configuration where the > delete commands are missing in the menus. Ah, good idea, thanks for the pointer. I'll look into that. Will, will you be attending this weeks' MC? I'll be there on Thursday only. If you are as well, we could continue our discussion there. ;-) Andreas -- Andreas Weder Senior IT Consultant mp technology consulting GmbH Brauerstrasse 60 CH-8004 Zürich, Switzerland [email protected] Phone: +41 43 322 04 82 Fax: +41 43 322 04 09 http://www.mptechnology.ch ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
