#129 — WorkflowException

by Jonathan Steffan — last modified Jan 08, 2009 04:07 PM

State	Resolved
Version:	—
Area	Functionality
Issue type	Bug
Severity	Medium
Submitted by	Jonathan Steffan
Submitted on	Jan 17, 2008
Responsible	Tim Hicks
Target release:	—

Return to tracker

Traceback (innermost last):
  Module ZPublisher.Publish, line 119, in publish
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 42, in call_object
  Module Products.Five.browser.metaconfigure, line 417, in __call__
  Module Shared.DC.Scripts.Bindings, line 313, in __call__
  Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
  Module Products.PageTemplates.PageTemplateFile, line 129, in _exec
  Module Products.CacheSetup.patch_cmf, line 120, in PT_pt_render
  Module zope.tal.talinterpreter, line 271, in __call__
  Module zope.tal.talinterpreter, line 346, in interpret
  Module zope.tal.talinterpreter, line 891, in do_useMacro
  Module zope.tal.talinterpreter, line 346, in interpret
  Module zope.tal.talinterpreter, line 536, in do_optTag_tal
  Module zope.tal.talinterpreter, line 521, in do_optTag
  Module zope.tal.talinterpreter, line 516, in no_tag
  Module zope.tal.talinterpreter, line 346, in interpret
  Module zope.tal.talinterpreter, line 957, in do_defineSlot
  Module zope.tal.talinterpreter, line 346, in interpret
  Module zope.tal.talinterpreter, line 536, in do_optTag_tal
  Module zope.tal.talinterpreter, line 521, in do_optTag
  Module zope.tal.talinterpreter, line 516, in no_tag
  Module zope.tal.talinterpreter, line 346, in interpret
  Module zope.tal.talinterpreter, line 861, in do_defineMacro
  Module zope.tal.talinterpreter, line 346, in interpret
  Module zope.tal.talinterpreter, line 957, in do_defineSlot
  Module zope.tal.talinterpreter, line 346, in interpret
  Module zope.tal.talinterpreter, line 536, in do_optTag_tal
  Module zope.tal.talinterpreter, line 521, in do_optTag
  Module zope.tal.talinterpreter, line 516, in no_tag
  Module zope.tal.talinterpreter, line 346, in interpret
  Module zope.tal.talinterpreter, line 536, in do_optTag_tal
  Module zope.tal.talinterpreter, line 525, in do_optTag
  Module zope.tal.talinterpreter, line 346, in interpret
  Module zope.tal.talinterpreter, line 949, in do_defineSlot
  Module zope.tal.talinterpreter, line 346, in interpret
  Module zope.tal.talinterpreter, line 854, in do_condition
  Module Products.PageTemplates.Expressions, line 211, in evaluateBoolean
  Module zope.tales.tales, line 696, in evaluate
   - URL: index
   - Line 25, Column 6
   - Expression: <PythonExpr ( view.workflow_state()=='published')>
   - Names:
      {'container': <WeblogEntry at /www.fedoraunity.org/blog-test-one/test-blog>,
       'context': <WeblogEntry at /www.fedoraunity.org/blog-test-one/test-blog>,
       'default': <object object at 0xb7f5c528>,
       'here': <WeblogEntry at /www.fedoraunity.org/blog-test-one/test-blog>,
       'loop': {},
       'nothing': None,
       'options': {'args': (<Products.Five.metaclass.SimpleViewClass from /var/lib/zope/lib/python/quills/app/browser/weblogentry_view.pt object at 0x12b6dc4c>,)},
       'repeat': <Products.PageTemplates.Expressions.SafeMapping object at 0x14a87d0c>,
       'request': <HTTPRequest, URL=http://fedoraunity.org/[…]/weblogentry_view>,
       'root': <Application at >,
       'template': <ImplicitAcquirerWrapper object at 0x1363022c>,
       'traverse_subpath': [],
       'user': <PloneUser 'jon'>,
       'view': <Products.Five.metaclass.SimpleViewClass from /var/lib/zope/lib/python/quills/app/browser/weblogentry_view.pt object at 0x12b6dc4c>,
       'views': <zope.app.pagetemplate.viewpagetemplatefile.ViewMapper object at 0x132aecec>}
  Module zope.tales.pythonexpr, line 59, in __call__
   - __traceback_info__: ( view.workflow_state()=='published')
  Module <string>, line 0, in ?
  Module quills.app.browser.weblogview, line 90, in workflow_state
  Module Products.CMFCore.WorkflowTool, line 268, in getInfoFor
WorkflowException: No workflow provides '${name}' information.

Added by Jonathan Steffan on Jan 17, 2008 04:13 AM

Responsible manager: tim2p → (UNASSIGNED)

This is for Quills 1.6beta product release on Plone 3.0.5

Added by Erik Forsberg on Jan 27, 2008 05:56 PM

I also got this error, but was able to work around it by going into the ZMI->portal_workflow and assign a new workflow '(Default)' to the weblog type. I then clicked "Update Security Setting". This made all my blog entries go into draft state, so I hade to change the state of all of them to appear in the blog view.

Added by Erik Forsberg on Jan 27, 2008 06:01 PM

Added by (anonymous) on Jan 27, 2008 07:26 PM

Yes, this fixes the issue. We had an old Quills installed in the instance at one point and for some reason the workflow was being set to quills_workflow.

Added by Tim Hicks on Mar 26, 2008 06:50 PM

Issue state: unconfirmed → open

It sounds like there is a missing migration step to switch objects from the old quills workflow to the standard plone workflow. I'm afraid I don't have the time to address this, but I'd be happy to discuss what needs doing with anyone.

Added by Tim Hicks on Jul 04, 2008 05:19 PM

Issue state: open → resolved

Responsible manager: (UNASSIGNED) → tim2p

I have made a checkin to the trunk (aka 1.7 post beta 1) that should/may address this. See:

http://dev.plone.org/collective/changeset/66171

It should ensure that all entries that were previously published under the quills_workflow get republished under that standard plone workflow by the migration. Migrations get run on reinstall via the QI tool.

An svn checkout of Products.Quills/trunk should give you this change. Alternatively, you can wait for the next 1.7 release to be cut.

Added by Tim Hicks on Jul 08, 2008 03:34 PM

I've released the Products.Quills 1.7.0b2 egg with this fix in now.

Added by Reed O'Brien on Aug 24, 2008 05:44 AM

I still get this error migrating from an unknown older version of quills.

It appears that removeQuillsTool gets called before migrating; and that the quils_workflow is removed with/by the tool. Thus there is no quills_workflow when fixUpWorkflows is called.

I moved the fixup before the remove and the upgrade works. Ugly and not the best way, but solved for this one migration....

No responses can be added.