[Zope-CMF] Zope as theatre

Adam Fields fields@surgam.net
Fri, 22 Feb 2002 21:28:08 -0500


Adam Fields says:
> Searching for "deleting default_workflow" yields but one result (<a
> href="http://www.unblinking.com/heh/googlewhack.htm">googlewhack, sort
> of</a>), which says that you should delete the standard
> "default_workflow" and create a new one with the id
> "default_workflow":
> 
> http://www.zopezen.org/SDot/1000270556/index_html

Actually, the more helpful advice here is changing the
AUTO_MIGRATE_WORKFLOW_TOOLS setting in CMFCore/WorkflowTool.py.

Looking at the code for that, there's an explicit section on
regenerating the default_workflow if it doesn't exist, but only if
that variable is set to 1.

Delving a bit deeper, I suspect what's happened here is that since the
workflow state is stored with each object, you're getting two
workflows, even though the object doesn't currently use
default_workflow, because it's been "marked" previously by the
default_workflow (I'd check this by seeing if you get the problem on
objects created after you made the workflow change). It's not clear to
me how to delete workflow information from existing objects - you
might be able to do this easily with an external method. I'd have a
look at the code in CMFDefault/DefaultWorkflow.py to see what it's
doing when it sets the default workflow.

But this is all conjecture on my part.