Re: [Zope-dev] zope collector is broken
I'm sorry, i'm unable to reprovoke the problem! Is there anything unusual about how you were submitting? Did you try more than once, to see if the problem is consistent? On Fri, 07 Dec 2001 11:43:52 -0500, Chris Deckard wrote:
I tried submitting a new issue to the Zope collector at 11:42AM EST. Here's the traceback and error message:
Zope Error Zope has encountered an error while publishing this resource.
Error Type: WorkflowException Error Value: No workflow provides the "request" action. [...] WorkflowException: (see above)
-- Ken klm@zope.com
I tried multiple times. I tried again this time, but deselected the "security related" checkbox. It went in. The issue _is_ security related, though not something that makes zope insecure. Thanks, -Chris Ken Manheimer wrote:
I'm sorry, i'm unable to reprovoke the problem! Is there anything unusual about how you were submitting? Did you try more than once, to see if the problem is consistent?
On Fri, 07 Dec 2001 11:43:52 -0500, Chris Deckard wrote:
I tried submitting a new issue to the Zope collector at 11:42AM EST. Here's the traceback and error message:
Zope Error Zope has encountered an error while publishing this resource.
Error Type: WorkflowException Error Value: No workflow provides the "request" action. [...] WorkflowException: (see above)
-- Ken klm@zope.com
-- -------------------------------------------------------------------- Christopher N. Deckard | Lead Web Systems Developer cnd@ecn.purdue.edu | Engineering Computer Network http://www.ecn.purdue.edu/ | Purdue University ---- zlib.decompress('x\234K\316Kq((-J)M\325KM)\005\000)"\005w') ---
On Fri, 7 Dec 2001, Christopher N. Deckard wrote:
I tried multiple times. I tried again this time, but deselected the "security related" checkbox. It went in. The issue _is_ security related, though not something that makes zope insecure.
Aha! My fault - it had neglected a setting in the collector workflow. I've corrected that now - people should be able to submit new security-related items. I also set your issue to security-related. Thanks for reporting this, and the clues to track it down! -- Ken klm@zope.com
Okay it seems fixed, but I wanted to mention a similar user-experience problem in CMF and workflows in general: Suppose a user clicks "publish" in the action box, enters his comment and then clicks the "Publish" button. And the re-clicks on the "Publish" button (either because he double-clicked, or because he retried because the process seemed slow). Then the first click will correctly change the object state, and the second click will be unable to "publish" because from the "public" state there is (obviously) no further "publish" transition. So the user will get a message like the one below. Because I saw that these double-clicks are somewhat frequent in our case, I put a try: except: in content_status_modify. Florent Christopher N. Deckard <cnd@ecn.purdue.edu> wrote:
I tried multiple times. I tried again this time, but deselected the "security related" checkbox. It went in. The issue _is_ security related, though not something that makes zope insecure.
Thanks, -Chris
Ken Manheimer wrote:
I'm sorry, i'm unable to reprovoke the problem! Is there anything unusual about how you were submitting? Did you try more than once, to see if the problem is consistent?
On Fri, 07 Dec 2001 11:43:52 -0500, Chris Deckard wrote:
I tried submitting a new issue to the Zope collector at 11:42AM EST. Here's the traceback and error message:
Zope Error Zope has encountered an error while publishing this resource.
Error Type: WorkflowException Error Value: No workflow provides the "request" action. [...] WorkflowException: (see above)
-- Ken klm@zope.com
-- -------------------------------------------------------------------- Christopher N. Deckard | Lead Web Systems Developer cnd@ecn.purdue.edu | Engineering Computer Network http://www.ecn.purdue.edu/ | Purdue University ---- zlib.decompress('x\234K\316Kq((-J)M\325KM)\005\000)"\005w') ---
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
-- Florent Guillaume, Nuxeo (Paris, France) +33 1 40 33 79 10 http://nuxeo.com mailto:fg@nuxeo.com
Florent Guillaume wrote:
Okay it seems fixed, but I wanted to mention a similar user-experience problem in CMF and workflows in general:
Suppose a user clicks "publish" in the action box, enters his comment and then clicks the "Publish" button. And the re-clicks on the "Publish" button (either because he double-clicked, or because he retried because the process seemed slow). Then the first click will correctly change the object state, and the second click will be unable to "publish" because from the "public" state there is (obviously) no further "publish" transition. So the user will get a message like the one below.
Because I saw that these double-clicks are somewhat frequent in our case, I put a try: except: in content_status_modify.
For one of my applications (not CMF based), I use unique form ids to catch if a form is submitted twice. I also use a bit of javascript to ignore a second click on the "submit" button, which reduces the load on the form-ids manager. I'd post the javascript... but I can't find it just now. It is just a three-liner to set a variable when the button is first clicked, and only allow the submit action to run if the variable is unset. Actually, now that CST is in the Zope core, I should rewrite the form-id manager to take advantage of that. -- Steve Alexander
participants (5)
-
Christopher N. Deckard -
Florent Guillaume -
Ken Manheimer -
Ken Manheimer -
Steve Alexander