Re: [collective-cmfmember] Re: Cannot view fields in CMF Member

[Rob M. <ra...@bu...>]

On Jan 11, 2005, at 4:15 AM, Stephen Kenworthy wrote:

> Rob Miller wrote:
>
>> this is probably workflow related.  are you using the 
>> 'member_auto_workflow' for your member type?  one thing to be aware 
>> of is that this contains an auto-transition that will transition the 
>> member object to the 'public' state as soon as all the fields 
>> validate.  this means that if all of your req'd fields are on the 
>> first schemata, then when you click 'next' the validation will 
>> succeed, and the auto-transition will be fired.  problem is, that 
>> means the anonymous user filling out the reg form no longer has edit 
>> rights to the member object.  this may be what you're seeing.
>> this is a known issue... there is a related (though not very clear) 
>> collector issue here: 
>> http://plone.org/development/teams/developer/groups/issues/83.
>> in any event, i'd look more deeply at the behaviour you're seeing, 
>> looking in particular at the associated workflows and the workflow 
>> states of your member objects as you work through the process.  you 
>> may discover a simple workaround for your needs.  alternatively, 
>> please feel free submit issues to the collector: 
>> http://plone.org/development/teams/developer/groups.  there's a 
>> cmfmember track happening at the san jose sprint at the end of this 
>> month, we hope to tackle most of the collector issues at that time.
>> -r
>
> Thanks for the help Rob. I found it very insightful. I was using the 
> member_auto_workflow but am just about to begin developing my own one.

great!  for workflow development, you'll want to know about the 
DCWorkflowDump product.  once it's installed, it adds a "dump" tab to 
the ZMI for every workflow.  on this tab you'll be able to click a 
button to generate the python source code for the workflow object.  
this lets you create your workflow in the ZMI, then generate the 
corresponding python that can be used to create the workflow for future 
installations.  we use it for all of the cmfmember workflow 
development.

good luck,

-r