Personal tools
You are here: Home Lists ZPUG DC List Archives 2005 2005-11 Workflow that worked in 2.0.5 does not in 2.1.1 / David Diskin <david.diskin@verizon.net>
Navigation
Log in


Forgot your password?
New user?
Mailing Lists
You can read our ZPUGDC mailing list archives online.
You can subscribe to our mailing list:
Book Review

The Definitive Guide to Plone

Reviewer: joel
 

Workflow that worked in 2.0.5 does not in 2.1.1 / David Diskin <david.diskin@verizon.net>

Workflow that worked in 2.0.5 does not in 2.1.1
David Diskin <david.diskin(at)verizon.net>
2005-11-26 21:50:10 [ FULL ]
I recently migrated a site from 2.0.5 to 2.1.1.  I have most things  
working now, but I'm stymied by one thing.  I created a  
members_only_folder that I associated with a members_only _workflow.   
I did this by copying/pasting and renaming the folder_workflow and  
modifying permissions for the states so that Anonymous can't view or  
access anything.  This worked fine for members_only_folders in 2.0.5,  
but Anonymous users can view/access contents in members_only_folders  
in 2.1.1.  This is a critical feature of the site that I need to get  
working.  Does anyone have an ideas about what the problem might be  
or how I should go about this differently?   Thanks,

David

==============================
David Diskin, david.diskin(at)verizon.net

Re: [ZPUGDC] Workflow that worked in 2.0.5 does not in 2.1.1 / Alex Clark <aclark@aclark.net>

Re: [ZPUGDC] Workflow that worked in 2.0.5 does not in 2.1.1
Alex Clark <aclark(at)aclark.net>
2005-11-28 11:23:22 [ FULL ]
David,

Are you saying that when you transition an object that the permissions are
not getting set properly? Does it work if you go in and set it by hand? 

You need some way of getting under the hood. Not being familiar with your
site (and being unaware of any issues regarding workflow, 2.0.5 -> 2.1.1)
I would have to suggest the sledgehammer approach:

Export the workflow to the filesystem (using something like this:
http://www.zope.org/Products/CMF/docs/devel/content_devel_guide/dumpDCWorkflow.py/view,
although I think there's a better workflow dumper available, i can't remember
the name).

Remove the custom workflow from your migrated site.

Create a filesystem product containing your custom workflow and install that
in your migrated site.

Run in debug mode, print objects to event.log (via context.plone_log(object)),
and see if you can figure out where/what it/is going wrong. OR (and this is
probably 
"The Right Way(TM)" to debug,) learn how to use a debugger such as pdb or the 
one that comes with WingIDE...

Anyway, back to the actual problem.

Is it possible that the workflow was not migrated properly or at all to begin
with?
It sounds to me like the behavior you are experiencing is that of an object
with
no workflow and/or the default workflow.

Alex

On Sat, Nov 26, 2005 at 10:55:33PM -0500, David Diskin wrote:[...]
[...]

Powered by Plone, the Open Source Content Management System

This site conforms to the following standards: