Comments on: Authlogic Account Activation Tutorial

By: Ae

Ae — Wed, 18 May 2011 18:45:46 +0000

Great tutorial !
Many thanks to Rok for a nice auto log in after activation solution.

@joel Joseph
Tutorial was meant to be used with Rails 2. The sending mail process has changed in Rails 3. RoR website have a great tutorial on Action Mailer http://guides.rubyonrails.org/action_mailer_basics.html
hope that helps.

By: joel Joseph

joel Joseph — Thu, 24 Mar 2011 12:54:51 +0000

Hi, i am new to ror . i followed this tutorial to for user activation . but i am getting this error.

undefined method `deliver_activation_instructions’ for Notifier(id: integer, created_at: datetime, updated_at: datetime):Class

can you please help me out?,,,,,

By: Bogdan

Bogdan — Mon, 24 Jan 2011 00:17:02 +0000

@Daz: try adding following to config/routes.rb
match ‘register/:activation_code’ => “activations#new”, :as => :register

By: Daz

Daz — Fri, 10 Dec 2010 07:27:46 +0000

Yeah, thanks for the tutorial. I’m new to RoR and am trying to integrate this into Rails 3, and have a couple questions:

- should the activation url that gets sent to the new user look something like this:
http://127.0.0.1:3000/register.HAH88xS6gyT7SXsWKn4V
I’m unable to pull the activation_code from the url –> params[:activation_code] isn’t doing the trick in the ‘new’ method found in activations_controller.

-also, should I be expecting an email to be sent via Authlogic, or would there be additional work on my part?

any help is greatly appreciated.

By: Jonas

Jonas — Tue, 26 Oct 2010 17:51:14 +0000

Thanks for the tutorial, and thanks Rok for the tip on automatically creating user sessions. By calling activate! in the “new” controller method and using UserSession.create!(self) in the user model I bypass the confirm page entirely and just give the user a confirmation message in the flash….great! Eliminates a step for the user and the need for an extra view & method/route.

Its not quite as secure as making the user sign in again, but equally as secure as having the user set the password after confirmation, I believe.

By: Authlogic and Cucumber | Vincent Prouillet

Authlogic and Cucumber | Vincent Prouillet — Sun, 14 Mar 2010 00:45:13 +0000

[...] For the Authlogic part, i’ll just refer to others tutorials since there are very good ones out there ! First the basic installation : GitHub Authlogic, you can see how easy it is to set up a complete authentication system with this amazing gem. I then added the reset password functionality : Reset passwords with Autlogic. And then I wanted to activate accounts by an email : Account Activation with Authlogic. [...]

By: Ravindra Singh

Ravindra Singh — Thu, 14 Jan 2010 11:27:19 +0000

after using reset_perishable_token!
i am getting different value of perishable token in db and in the e-mail
and when user visit the link due to the unmatched values user get error user not find in my production log
why is this?
i am using exactly your code for activation_instructions

By: Jeremy Chatfield

Jeremy Chatfield — Mon, 11 Jan 2010 18:42:36 +0000

Thanks – very helpful article. If following this precisely, I think there’s a step or two needed for app/views/users . The form partial requests the password, but that’s not what the description of the process says. So we probably need to copy and trim the form (because views/users/edit.html.erb probably still needs to allow password updates, unless we have an openid record, while the new.html.erb needs to request only the email address?)

By: Ulf

Ulf — Sun, 03 Jan 2010 14:39:29 +0000

Thanks for your tutorial!

I try to write a controller spec for create. I wonder how signup! can be mocked/stubbed? Something like
User.stub!(:signup!).and_return(“true”)
doesn’t work.

By: Rok

Rok — Sun, 27 Dec 2009 14:44:05 +0000

Had the same issue as Jonathan, so I checked Authlogic docs, here’s my activate! and singup! methods

	def signup!(params)
		self.login = params[:user][:login]
		self.email = params[:user][:email]
		self.password = params[:user][:password]
		save_without_session_maintenance
	end
 
	def activate!
		self.active = true
		UserSession.create!(self)
	end