I can't help with this as I have tweaked the create code so it is non-standard. Is there a before_filter in UsersController, if so then it may be failing in there.
2009/3/27 elliottg <[email protected]> > > It looks like I have a "Filter chain halted" error going on that is > not allowing the user to be created. > > Thanks for all the help. > > On Mar 27, 1:27 pm, elliottg <[email protected]> wrote: > > Doh... I just found it, right after my last post. > > > > Thanks for getting back to me. > > > > I am assuming that somehow @user is being returned or something? > > Because, assigns(:user) is being called on the next line?? > > > > Is that the case, and further any ideas why its coming up Nil? Testing > > in script/console test shows that creating a new User works fine and I > > know the fixture data is in the users table as it should be? > > > > Thanks a ton > > > > On Mar 27, 1:15 pm, Colin Law <[email protected]> wrote: > > > > > If you look down the end of the file with that code in you will find > the > > > definition of create_user. At least in my version anyway. I found it > by a > > > global search, but I realised when it found it that I should have > looked in > > > that file first. > > > > > 2009/3/27 elliottg <[email protected]> > > > > > > Any thoughts on this? > > > > > > Basically, I just need to know what "create_user" is doing? Is it > > > > creating a new User based upon the users.yml fixture that the test > > > > suit is loading, or is it something else? I couldn't find reference > > > > for this "dynamic??" method anywhere. > > > > > > def test_should_require_login_on_signup > > > > assert_no_difference 'User.count' do > > > > create_user(:login => nil) > > > > assert assigns(:user).errors.on(:login) > > > > assert_response :success > > > > end > > > > end > > > > > > On Mar 26, 5:12 pm, elliottg <[email protected]> wrote: > > > > > I have been working with restful_authentication. I have made some > > > > > changes to it and now I'm trying to get all the default tests that > > > > > came with the plugin to pass. > > > > > > > Here's one of the tests that error out: > > > > > > > def test_should_require_login_on_signup > > > > > assert_no_difference 'User.count' do > > > > > create_user(:login => nil) > > > > > assert assigns(:user).errors.on(:login) > > > > > assert_response :success > > > > > end > > > > > end > > > > > > > This is the error: > > > > > NoMethodError: You have a nil object when you didn't expect it! > > > > > You might have expected an instance of ActiveRecord::Base. > > > > > The error occurred while evaluating nil.errors > > > > > > > When using running debugger and checking in on assigns(:user) it > > > > > returns nil, so I assume this is the trouble. > > > > > > > Finally here's my question, what is "create_user" doing? Is it > > > > > creating a new User based upon the users.yml fixture that the test > > > > > suit is loading, or is it something else? I couldn't find reference > > > > > for this "dynamic??" method anywhere. > > > > > > > Thanks > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
