Hi!
I am trying to understand the relation between copy/paste/move
actions and the workflow state in the admin/site area. I don't feel
relaxed yet when I use these functions in the default publication
(unchanged).
What I find strange:
1) click on subtree foo (all of its documents are live)
2) copy foo (here the Text is misleading, saying the document is
copied, but it is the subtree)
3) paste foo elsewhere
Result: all the documents of the foo-copy have still the workflow
state live (not true, I think)
- 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)?
- I can only think of a clean workflow when a subtree has to have the
workflow state authoring before being cut or moved.
- Authoring itself is not clickable but would have to be if one wants
to paste a subtree top the top level.
Does this make any sense?
Jürgen Ragaller
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
