[quote]Are there any other modules where I should add the commands in their respective modules, or is the adminInterface module the recommended way to go? [/quote] Personally I prefer each module having own catalog and keeping definition under own module node. It makes life much easier in case you need uninstall the module.
[quote]Custom publishing activation commands and workflow is mutually exclusive.[/quote] I don't see why. Yes, I have read what you wrote above, but as also Natascha pointed out you can chain commands (this is what /modules/admininterface/commands/website/activate is doing) and on top of that you can also invoke commands from within workflow. So you can move original data/dms/simpleMedia activation commands under different names, replace them with workflow and then from within workflow you check if property "repository" in context has value website/data/dms/simpleMedia and invoke original activation command for given workspace/tree as appropriate. Just in case syntax for invoking command in workflow is command-[catalog-]commandName. Similar works also for extra props that might be injected in command context by tree classes - you can always add them via workflow definition or by using custom command and chaining commands together (all commands in a chain share same context so whatever one puts in the context others will see). HTH, Jan -- 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]> ----------------------------------------------------------------
