Hi Hans, I think you skipped last step: On existing (already bootstrapped) Magnolia instance: delete or reconfigure the commands under config: modules/adminInterface/commands/website so that they don't start the workflow. Take the config: modules/adminInterface/commands/default/activate node as an example if reconfiguring the activation command. and you might want to also check for the /modules/data/commands/activate and /modules/dms/commands/activate ... those all might point to workflow which you don't want to anymore.
HTH, Jan On Jul 21, 2011, at 6:50 PM, Hans Wichman wrote: > Hi list, > > I deactivated the workflow module, as described here: > http://documentation.magnolia-cms.com/cookbook/workflow/disabling-workflow.html > > And now the whole activation mechanism stopped working: > 2011-07-21 18:41:54,026 ERROR > info.magnolia.cms.servlets.MVCServletHandlerImpl : can't call command: > activate > java.lang.NoSuchMethodException: > info.magnolia.module.admininterface.trees.WebsiteTreeHandler.activate() > > Any ideas? I’d like to enable the standard activation mechanism again… > > Regards, > JC > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
