Here is a proposed change by soey: http://gist.github.com/258869

The monkey patch of ActionController::Base.perform_action in rest_auth_features_helper.rb needs to updated to work with Rails 2.3.4+

Just downloaded and found that “s.files =” in this spec should be updated! Many files are misssing, I used a Dir[‘/’] and resolved, but this won’t work in github, you ca use this patch:

commit d11f2c70eddbd2b524319fd58b50c5533c00594d Author: Elia Schito <perlelia@gmail.com> Date: Tue Mar 31 17:15:51 2009 +0200

Updated the file list in gemspec

diff -git a/restful-authentication.gemspec b/restful-authentication.gemspec index 79db5e9..3a23a75 100755 -- a/restful-authentication.gemspec + b/restful-authentication.gemspec @ -10,7 +10,7 @ Gem::Specification.new do |s| s.description = %q{This widely-used plugin provides a foundation for securely managing user.} s.email = %q{railsjedi@gmail.com} s.extra_rdoc_files = [“README.textile”] - s.files = [“CHANGELOG”, “README.textile”, “Rakefile”, “TODO”, “generators/authenticated/authenticated_generat + s.files = %w”CHANGELOG generators generators/authenticated generators/authenticated/authenticated_generator.r s.has_rdoc = true s.homepage = %q{http://github.com/technoweenie/restful-authentication} s.rdoc_options = [“—main”, “README.textile”]

Have you enabled the “gem” feature in the project? (I know it’s a silly question… but… who knows…)

Is it just me or does the validates_length_of :name … need a allow_nil => true as well, because the rspec tests are failing (telling me “name ist too long…”) when passed nil values for name

Is it just me or does the validates_length_of :name … need a allow_nil => true as well, because the rspec tests are failing (telling me “name ist too long…”) when passed nil values for name

Is it just me or does the validates_length_of :name … need a allow_nil => true as well, because the rspec tests are failing (telling me “name ist too long…”) when passed nil values for name

looks like a slightly incorrect copy-paste from the previous revision’s line 112… should probably just use either stringify_keys or symbolize_keys

Can someone please explain why this line has params[‘password’] repeated at the end? Is is a special trick? Wouldn’t it be sufficient just to have ~ params[‘confirm’] ||= params[‘password’]? Just trying to understand it. Thanks.

Awesome, thanks for the quick fix ;)

Crud, I thought this was out of rake’s purview — don’t know what gave me that idea. Until it’s moved to the right place I’ve at least re-namespaced it all.

Please note that the timestamps in the above output are actually parts of my shell prompt.

It seems as though this commit borked the db migration…

mdarby@macbook:~/Desktop/temp: ./script/generate authenticated user sessions \ 23:39:47 —include-activation \ —rspec

…

mdarby@macbook:~/Desktop/temp: rake db:migrate 23:40:50 (in /Users/mdarby/Desktop/temp) cd /tmp/empty_app rake aborted! No such file or directory – /tmp/empty_app

(See full trace by running task with —trace)

cool. /em points to the new tracker — if your snags were “interesting”, open an issue; describe your solution; and then I’ll close it. Then everyone is a little smarter.

Thanks for the updated page. It helped me with some stuff I was getting snagged on.

No, your are not the only one…. Actually I had to leave only html there.. otherwise it won`t work in IE. Some guys on the IRC channel said IE sends a * wildcard in the request… or something as stupid as that…

Am I the only person who is having IE problems with this line? After a redirect, IE always gets request_http_basic_authentication complete with a ghetto login box. I guess the accepts headers aren’t being sent by IE on redirect?

Whatever is happening, it’s definitely not responding to format.html.

Whenever you are trying to make the activation code try removing the enter command and pasting this in:

aasm_event :register, :success => :make_activation_code do

If you do it on the event block, it appears to fire the method correctly. I found this in the rspec tests of the aasm code. You should take a look for more examples.

Issues: 1. When User is created the record is properly updated from ‘passive’ to ‘pending’ BUT the “make_activation_code” is not called as expected given “:enter => :make_activation_code.” I had to put a before_filter in my User class to call “make_activation_code” to get things to work.

2. Same problem when moving from ‘pending’ to ‘active’. The state is changed when user.activate! is called … but the “do_activate” method is not called.

What gives? Am I missing something???

Thanks

jerome,

For item #2 the stateful option wraps the find in a find_in_state so it does check the state of the user.