slight model change to tgext.registration2
alexbod...@gmail.com
hello friends,
as i'm maintaining tgext.registration2, entirely based on tgregistration from patrick lewis, i'm reviewing the code here and there.
one idea that popped on the top of my head was to remove the pending user registration table, and just keep a new record in the email changing table, with a null email field. this record will be needed to have the validation key.
the new user could be differentiated from others by the existence of this record, and his/her unverified group membership.
it could be very profitable that the user may login and do certain actions on the site, like buying and paying, things already more identity confirming than email validation.
open to your input,
--
alex
Lloyd Kvam
You risk having accounts where the email address does not work because
it was mis-typed or bogus. For my applications, that's unacceptable. I
realize that some applications may not require working email, but please
do not remove the ability to prevent logins until the email address is
validated.
> open to your input,
alexbod...@gmail.com
as i said, i'd rely on the registrant getting already membership to some 'unverified' groups, and the identity/repoze system is clever enough to restrict the user's access based on this membership or it's missing.
you could redirect this user, after login, to a validation remainder page, and even lock him/her there.
>> open to your input,
>
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups "tg-registration" group.
> To post to this group, send email to tg-regi...@googlegroups.com
> To unsubscribe from this group, send email to tg-registrati...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/tg-registration?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>
--
alex
Lloyd Kvam
> as i said, i'd rely on the registrant getting already membership to
> some 'unverified' groups, and the identity/repoze system is clever
> enough to restrict the user's access based on this membership or it's
> missing. you could redirect this user, after login, to a validation
> remainder page, and even lock him/her there.
The current registration does exactly what I need as delivered. I do
not need to worry about people with invalid email addresses.
If your changes improve things for most people I'll cope. I appreciate
your doing the work to improve the registrant module.