I've run into some problems related to module-specific commands, see below:
[b]Findings[/b] As found in my previous post, context (originating tree) is lost when activating over workflow. Thus, the same publishing (the one transfering files to the public instance as opposed to commands doing other activation tasks) activation command will be used for all trees using workflow. The data:dataTypes tree (catalog?) and the media tree both use custom publishing activation commands (TypeActivateCommand and MediaActivationCommand respectively). [b]Implications[/b] Custom publishing activation commands and workflow is mutually exclusive. Thus, for a tree you can choose to either have custom publishing activation command, or workflow, but not both. Thus, it is not possible to set up workflow for data:dataTypes and media trees. [b]Suggestions[/b] There should be better separation between workflow and activation commands. Ideally they should exist on different layers of the execution phases. [b]Questions[/b] Is my reasoning above correct? How can I configure workflow for data:dataTypes and media trees? Are there any other trees whose configuration get in the way of workflow in similar or other ways? Best regards Mike -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=ee4ce885-0410-4e20-b0bc-555e27fac065 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
