Jürgen Ragaller wrote:
[...]
- Would it make sense to disable move(up/down) and cut for live and
submitted documents/subtrees and to reset the workflow state after
copy to authoring|not live (for the default publication)?
IMO the target documents should indeed be in the authoring state.
Should I put it in bugzilla?
That would be great, thanks!
- I can only think of a clean workflow when a subtree has to have the
workflow state authoring before being cut or moved.
Hmmm, could you explain this? Why shouldn't it be allowed to copy
a submitted/live document?
I think, «copy» is fine (authoring state after the action).
When using «cut/paste» or «move-up/down» on a live-subtree doesn't one
loose connection to the live documents (how would these be deactivated
after a move elsewhere). The workflow state of the moved/copy-pasted
documents again would have to be changed to authoring | not live after
the movement.
You're right, we should disallow "cut" (as any delete operations) for
non-authoring documents (like in 1.2).
Thanks for your comments,
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
