Doh, forgot to include the link:
http://www.openplans.org/projects/remember/lists/remember/archive/2006/12/1166184414100

-Tim

On Fri, 2009-06-12 at 21:24 +1200, Tim Knapp wrote:
> Hello again,
> 
> I found this post in the remember mailing list archives and thought it
> might be related to my issue so I checked my classes and I don't have
> any BaseObject classes overriding the remember ones. I also tried
> manually setting up the schema by importing the schema from
> member_schema and assembling it as per the member module in remember but
> still no 'id' field :(
> 
> All the other fields appear fine.
> 
> -Tim
> 
> On Fri, 2009-06-12 at 20:35 +1200, Tim Knapp wrote:
> > On Thu, 2009-06-11 at 16:14 -0500, Info wrote:
> > > Tim,
> > > 
> > > In your custom member class, try overriding the showPasswordField() 
> > > method that membrane or remember defines and be sure to return True.  
> > > Just paste this into your class definition in the area where you define 
> > > your custom methods:
> > > 
> > >     def showPasswordField(self):
> > >         #If this method returns True, then the password entry field is 
> > > made visible on the edit form.
> > >         return True
> > > 
> > > 
> > > I think that's the secret little gotcha you're running into.  I've had 
> > > to use this before, myself.
> > 
> > Thanks Ken, this worked a treat and now the password fields show
> > (funnily enough I had tried this earlier but it didn't work, which was
> > probably related to another issue in my Remember-based class).
> > 
> > Now, though, the username (id) field still doesn't show. I've edited the
> > reg_form.cpt and got it to show 'all' the fields (i.e. remove the
> > regfield check) and even then it doesn't show the username field. I
> > debugged the initialisation of the remember-based class and the 'id'
> > field is definitely in the schema. Any further clues?
> > 
> > /me carries on debugging.
> > 
> > Thanks,
> > Tim
> > 
> > > 
> > > Ken Wasetis
> > > 
> > > 
> > > Tim Knapp wrote:
> > > > Reporting again from the front-line ;)
> > > >
> > > > After having a look back over my remember modules it occurred to me that
> > > > the problem may well be in the way I've set them up as I realised that
> > > > none of the standard remember fields were showing on the reg_form, e.g.
> > > > username, password, although email was, which is a default one.
> > > >
> > > > I've setup my remember-based classes as follows: I have a
> > > > 'base' (Products.subscribemember.content.basesubscribemember), which
> > > > contains the base schema (a bunch of fields that are shared between the
> > > > 2 remember classes), and a
> > > > 'Individual' (Products.subscribemember.content.individual) and an
> > > > 'Organization' type (Products.subscribemember.content.organization). At
> > > > this stage I put a 'BaseSubscribemember' class in the 'individual'
> > > > module with its InitializeClass method being called (as per the standard
> > > > BaseMember class in remember). This subclasses
> > > > Products.remember.content.member.Member and then the 'Individual' class
> > > > subclasses the BaseSubscribemember class (copied here[1] for your
> > > > viewing pleasure). The classes are also defined in a configure.zcml in
> > > > the 'content' folder (just the Individual and Organization classes mind
> > > > you, not the BaseSubscribemember class). But as I say, the username and
> > > > password fields don't show. Any clues on what I'm doing wrong?
> > > >
> > > > Thanks,
> > > > Tim
> > > >
> > > > [1] http://duffyd.pastebin.com/f6ba0ca55
> > > >
> > > > P.S. I've not had these kind of issues on Plone 3.2.2 with remember 1.1.
> > > >
> > > > On Thu, 2009-06-11 at 17:50 +1200, Tim Knapp wrote:
> > > >   
> > > >> Hello again,
> > > >>
> > > >> Just further to this thread, is this branch[1] the one to use for the
> > > >> latest updates to the Plone 2.5-compatible version of remember? Just I
> > > >> note that the last changes to this branch was 10 months ago, which in
> > > >> the scale of things isn't really too old :)
> > > >>
> > > >> Thanks,
> > > >> Tim
> > > >>
> > > >> [1] http://dev.plone.org/collective/browser/remember/branches/1.0
> > > >>
> > > >> On Thu, 2009-06-11 at 16:50 +1200, Tim Knapp wrote:
> > > >>     
> > > >>> Hi,
> > > >>>
> > > >>> I've tried to set the validate_email value to False in both the GS
> > > >>> profile and in code as follows (in the test fixture setup):
> > > >>>
> > > >>>         # don't send emails out by default
> > > >>>         ptool = getToolByName(self.portal, 'portal_properties')
> > > >>>         ptool.site_properties.validate_email = False
> > > >>>         self.portal.validate_email = False
> > > >>>
> > > >>> As you can see I've set both the property in site_properties and on 
> > > >>> the
> > > >>> portal root itself as it seems that these values changed between Plone
> > > >>> 2.5 and 3 and the code checks both. But no matter how I set it, the
> > > >>> password fields don't show up on the reg_form. All my other fields are
> > > >>> fine.
> > > >>>
> > > >>> I also put a pdb in the showPasswordField in remember.content.member 
> > > >>> but
> > > >>> this code doesn't even get called. Any clues?
> > > >>>
> > > >>> Thanks,
> > > >>> Tim
> > > >>>
> > > >>>
> > > >>>
> > > >>> --
> > > >>> Archive: 
> > > >>> http://www.openplans.org/projects/remember/lists/remember/archive/2009/06/1244695860553
> > > >>> To unsubscribe send an email with subject "unsubscribe" to 
> > > >>> [email protected].  Please contact 
> > > >>> [email protected] for questions.
> > > >>>
> > > >>>       
> > > >>
> > > >> --
> > > >> Archive: 
> > > >> http://www.openplans.org/projects/remember/lists/remember/archive/2009/06/1244699451588
> > > >> To unsubscribe send an email with subject "unsubscribe" to 
> > > >> [email protected].  Please contact 
> > > >> [email protected] for questions.
> > > >>
> > > >>     
> > > >
> > > >
> > > >
> > > > --
> > > > Archive: 
> > > > http://www.openplans.org/projects/remember/lists/remember/archive/2009/06/1244750366059
> > > > To unsubscribe send an email with subject "unsubscribe" to 
> > > > [email protected].  Please contact 
> > > > [email protected] for questions.
> > > >
> > > >
> > > >
> > > >
> > > >   
> > > 
> > > 
> > > --
> > > Archive: 
> > > http://www.openplans.org/projects/remember/lists/remember/archive/2009/06/1244754879212
> > > To unsubscribe send an email with subject "unsubscribe" to 
> > > [email protected].  Please contact 
> > > [email protected] for questions.
> > > 
> > 
> > 
> > 
> > --
> > Archive: 
> > http://www.openplans.org/projects/remember/lists/remember/archive/2009/06/1244795841989
> > To unsubscribe send an email with subject "unsubscribe" to 
> > [email protected].  Please contact 
> > [email protected] for questions.
> > 
> 
> 
> 
> --
> Archive: 
> http://www.openplans.org/projects/remember/lists/remember/archive/2009/06/1244798735364
> To unsubscribe send an email with subject "unsubscribe" to 
> [email protected].  Please contact 
> [email protected] for questions.
> 



--
Archive: 
http://www.openplans.org/projects/remember/lists/remember/archive/2009/06/1244799008921
To unsubscribe send an email with subject "unsubscribe" to 
[email protected].  Please contact 
[email protected] for questions.

Reply via email to