You could turn deactivate into a command chain and add your own command to it. The default deactivate command in /modules/adminInterface/commands/default/deactivate is a single command. Compare it to the activate command in /modules/adminInterface/commands/website/activate. You will see that activate is actually a chain of three commands: version, startFlow and alert. Try creating a similar chain for deactivate under website, adding your own command. You can test by copying the alert command to your new chain. Change the message to read "Deactivated" or something like that and try deactivating a page. You should see a popup message.
http://documentation.magnolia-cms.com/reference/commands.html#Chaining_commands --Antti On Nov 9, 2010, at 2:38 PM, Kjell Arne Arvesen wrote: > Hiya. > > We want to register a new command that should be run everytime a website node > is deactivated. > Now we wanted to use the workflow strategy, but we notice that the > DeactivationCommand.class is not triggered by a workflow (except in some > instances). > > So my question to the community is; where should we register our commands? > Should we use the observation module? Create/edit a workflow? > > Best regards, > -- > Kjell Arne Arvesen > Solutions Engineer | +47 40 60 11 27 > Iterate AS | www.iterate.no > The Lean Software Development Consultancy > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
