I'm not clear what you're suggesting.
Currently there are two methods. sendValidationEmail takes a user and sends him
an email. signup has a nested function, testSignup, which (1) sets validated
based on skipEmailValidation, and resets uniqueId; (2) if skipEmailValidation
log in; otherwise sendEmailValidation.
Are you saying to make testSignup an overridable method? Wouldn't something
finer-grained be better?
-
David Pollakfeeder.of.the.be...@gmail.com wrote:
Sounds like a worthy addition. I'd suggest that rather that doing more
flags that you create a validation function that people can replace with
whatever they want... by default that function looks at the current
skipEmailValidation flag.
On Tue, Jul 28, 2009 at 1:07 PM, Naftoli Gugenheim naftoli...@gmail.comwrote:
Hi. I would like to customize the way that user registration is validated
by email. For example, require the admin to validate users.
Here are some possible approaches:
1. Set skipEmailValidation to true and build the mechanism from scratch in
the subclass.
2. Override signup, and implement it similar but different.
3. Add a flag to lift to leave the user NOT validated, but not to send the
email. Then either send the email manually, or provide a way for the admin
to validate users.
4. Provide a hook to directly specify who the email should go to.
What do people think?
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
