I am by no means an expert, but can this possibly be some type of
inheritance problem?

-----Original Message-----
From: Mark Phillips [mailto:mark@...] 
Sent: Sunday, January 06, 2008 9:18 AM
To: Remember (Plone) email list
Subject: [Remember Mailing List] Re: Need Help with Workflow

On Sat, 2008-01-05 at 18:09 -0700, Mark Phillips wrote:
> I created a brand new site:
> Plone 2.5.5,
> CMF-1.6.4,
> Zope (Zope 2.9.8-final, python 2.4.4, linux2), Five 1.4.2, Python 
> 2.4.4 (#1, Jan 5 2008, 12:49:13) [GCC 4.1.3 20071019 (prerelease) 
> (Debian 4.1.2-17)], PIL 1.1.6 membrane 1.0 remember 1.0b1
> 
> I then tried to use member_approval_workflow, and it worked. I then 
> created a new product based on the sampleremember product (see 
> attached ahsmember). All I did was take the sampleremember product, 
> add some fields and validators to the product, and changed the name 
> from sampleremember to ahsmember in the various files. I was able to 
> load ahsmember using GenericSetup extension profile as described in 
> the documentation for remember.
> 
> When I click the join button, I get my form with the updated fields 
> and the validators seem to work. However, I do not get the 
> member_approval_workflow anymore. I seem to have a fractured version 
> of member_auto_workflow because I get the message:
> Welcome!
> You have been registered as a member.
> 
> You will receive an e-mail shortly containing a URL that will allow 
> you to set your password. When you receive this e-mail, please follow 
> the link to complete your registration process. NOTE: The password 
> reset URL will expire in 168 hours. If your password reset request 
> expires, you may use the "Forgot your password" link to generate 
> another password reset request.
> 
> but no email is sent. (I got a password email when just using the 
> membrane/remember products and member_approval_workflow after the new 
> member was approved).
> 
> What do I need to do (leave out some bits and pieces?) to my ahsmember 
> product to get this member type to use the member_approval_workflow?
> 
> I did check the port_workflow tab, and AHSMember is setup to use 
> member_approval_workflow, as well as Member.
> 
> Thanks!
> 
> Mark
> 
> P.S. The log from importing ahsmember:
> =================================================================
> Step: rolemap
> =================================================================
> rolemap: Role / permission map imported.
> 
> =================================================================
> Step: properties
> =================================================================
> properties: Nothing to import.
> 
> =================================================================
> Step: remember-useradder
> =================================================================
> 
> 
> =================================================================
> Step: toolset
> =================================================================
> toolset: Nothing to import.
> 
> =================================================================
> Step: cssregistry
> =================================================================
> resourceregistry: Stylesheet registry: Nothing to import
> 
> =================================================================
> Step: content_type_registry
> =================================================================
> 
> 
> =================================================================
> Step: propertiestool
> =================================================================
> propertiestool: Nothing to import.
> 
> =================================================================
> Step: skins
> =================================================================
> skins: Skins tool imported.
> 
> =================================================================
> Step: actions
> =================================================================
> 
> 
> =================================================================
> Step: controlpanel
> =================================================================
> 
> 
> =================================================================
> Step: action-icons
> =================================================================
> Action icons: Nothing to import.
> 
> =================================================================
> Step: typeinfo
> =================================================================
> types: Types tool imported.
> types: 'MemberDataContainer' type info imported.
> types: 'AHSMember' type info imported.
> 
> =================================================================
> Step: plone_various
> =================================================================
> 
> 
> =================================================================
> Step: workflow
> =================================================================
> workflow: Workflow tool imported.
> 
> =================================================================
> Step: membranetool
> =================================================================
> catalog: Catalog imported.
> catalog: MembraneTool settings imported.
> 
> =================================================================
> Step: factorytool
> =================================================================
> 
> 
> =================================================================
> Step: jsregistry
> =================================================================
> resourceregistry: Javascript registry: Nothing to import
> 
> =================================================================
> Step: memberdata-properties
> =================================================================
> memberdata: Nothing to import.
> 
> =================================================================
> Step: mailhost
> =================================================================
> 
> 
> =================================================================
> Step: catalog
> =================================================================
> 
> 
> =================================================================
> Step: content
> =================================================================
> 
> 
> =================================================================
> Step: plone-final
> =================================================================
> 
> 
> =================================================================
> Step: membrane-sitemanager
> =================================================================
> 
> 
> =================================================================
> Step: plugins
> =================================================================
> 
> 
> =================================================================
> Step: remember-setupplugins
> =================================================================
> 
> 
> =================================================================
> Step: portal_form_controller
> =================================================================
> CMFFormController: Nothing to import.
> 
> 
> 
An update to this problem....

1. I deleted and reinstalled my plone site (see above). I then installed the
sampleremember product (unchanged version 1.1), changed the workflow in
portal_workflows to member_approval_workflow, and it worked. Emails were
sent, and the member approval used the member_approval_workflow.

2. I then deleted and reinstalled the plone site. I took the sampleremember
product and made 3 changes (see attached) - a. replaced the schema with my
schema b. added the file for the validators (called in the schema) c.
updated __init.py__ to import the validators file.

I then installed the new sampleremember product, set the workflow in
portal_workflows to member_approval, tried to join the site, and same
problem - the workflow used to join the site is member_auto and not
member_approval. The password is not emailed to the user. If I go in to
site-setup and reset the password, that works - an email is sent and the
user can change the password.

So, what is wrong with my schema? Why does a change to a schema impact the
internal workings of the workflows? 

Thanks for any light you can shed on this problem. 

Mark

--
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.




-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.