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?
the reg form is supposed to construct itself from the AT schema... any field
for which a) "regfield" is set to a true value and b) the current user has
edit privileges should be showing up.
have you customized the schema at all? if so, is regfield=1 set on your
custom fields?
your "user" is actually anonymous at this point.. he's trying to join the
site. this is why the "new" state has wide open permissions, even anonymous
users can edit. this is also why the member objects are immediately pushed
out of "new" and into "pending" as soon as the submitted member data passes
validation. have you customized the member workflow at all? have you
verified that your member objects are editable by anonymous users when they're
in the initial state?
the template that is rendered to produce the registration form is
reg_form.cpt, in the remember skins. it's basically a modified version of
base_edit, fine tuned to support the rules described above. if none of the
above suggestions leads anywhere, you should start with that template. try
inserting some debug information. check out the variable initialization stuff
that's in very first tag (especially "fieldsets" and "fields") and see if you
can figure out why those aren't returning the results you're expecting.
[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 :)
yes, that's the correct branch for Plone 2.5 compatibility. it's no longer
actively maintained, however, just as Plone 2.5 is no longer maintained. bug
fixes are welcome, of course.
good luck!
-r
--
Archive:
http://www.openplans.org/projects/remember/lists/remember/archive/2009/06/1244753751886
To unsubscribe send an email with subject "unsubscribe" to
[email protected]. Please contact [email protected] for
questions.
