Yeah, to clarify, I also have a Notifications model that contains all
of my email-related methods, so UserVerification is probably still
overkill for my purposes.
The SHA-1 key is stored in a field called unverified, so I can do this:
if @user.unverified?
# user isn't verified yet
else
# user is verified :)
end
I've also added a method that will allow users to resend the
verification email, if it fails to show up in a timely fashion.
Best,
Patrick
On Oct 11, 2006, at 2:36 PM, <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> wrote:
First, I wouldn't put it in the User model personally, simply
because it
doesn't really have anything to do with a User in the conventional OO
paradigm. It would be useful to have an method is_verified? that
checks
a :verified attribute though. With that said, here's an updated
description of UserVerification (i prefer it to UserVerification for
disambiguation with common rails terms):
_______________________________________________
Sdruby mailing list
[email protected]
http://lists.sdruby.com/mailman/listinfo/sdruby
