On 08.09.2009, at 13:58, Andreas Weder wrote:
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.
Well, come to think of it, that should actually be possible too. You
can trigger an arbitrary command from a menu item. So you might as
well be able to trigger a "deleteRequest" workflow command. However:
What happens with the node while the request is open? It would be nice
if it would not be displayed by the tree. That could be rather tricky...
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. ;-)
No, unfortunately I won't be able to make it - bad timing. But to all
who will attend: Have a great conference!
-will
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
