I was kind of surprised that in all of the documentation for TG, there is nothing that handles this common pattern
* visitor fills out form w/name + email * system creates an account, sends out a verification email * user clicks link in email to verify / activate account * user now has a nice account If someone were able to document this, I think it would be a GIANT benefit - thats the core of just about any webapp. I've been playing around with the identity in 0.94, and it seems that the TG idiomatic way to approach this would probably be to have a useraccount class in model.py be a subclass of TG_User, and add a 'verified' field + whatever else. but i'm beginning to think that maybe this should be built into TG instead -- maybe have a TG_UserVerified class or something similar that inherits from TG_User and is then subclassed in model.py -- and developers would just list the template for the email in the subclass. in any event, if there already is an idiomatic way to approach this in TG, its not easily found - and if there isn't, i think it would be key to add it. thoughts? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
