Well, seems like it was a wetware error:
Somehow the 'state' for administrator was never set to 'active'.
Anyway, still am curious about the Agility tutorial where it has 2
methods
with the same name. It explains in the tutorial the reason for this is
in case
an inactive user tries to reset password. But how is this actually
handled
by Hobo: having 2 methods with the same name? Method overloading?
Excerpted from Agility tutorial:
+ transition :request_password_reset, { :active=> :active }, :new_key
=> true do
+ UserMailer.deliver_forgot_password(self, lifecycle.key)
+ end
transition :request_password_reset,
{ :inactive=> :inactive }, :new_key => true do
(...no more of snippet in the example)
Cheers,
Jet
--
You received this message because you are subscribed to the Google Groups "Hobo
Users" 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/hobousers?hl=en.