CODEWITHSUNDEEP
ruby-on-rails-3
at8eqeq3
at8eqeq3

Reputation: 163

wrong number of arguments (3 for 1) after upgrading rails from 3.1.1 to 3.1.3

I have upgraded my rails 3.1.1 application to rails 3.1.3, and now, on every request, it answers only wrong number of arguments (3 for 1). Unfortunately, it doesn't says where the error was, and application trace is empty. I think there's some compatibility problem, but I really don't know where to dig.

There are my Gemfile and a framework trace: https://gist.github.com/1519479

Thanks for any help.

Upvotes: 4

Views: 680

Answers (1)

KL-7
KL-7

Reputation: 47618

Run bundle show and check version of omniauth gem. May be while upgrading rails you updated omniauth as well.

Version 1.* of omniauth requires separate gem omniauth-twitter for twitter authentication. As you don't have it in your Gemfile it tries to load as middleware Twitter class from twitter gem that would cause similar error.

To avoid issues like that in the future consider using "~> 0.2.6" for gems versioning instead of ">= 0.2.6". It protects you from unexpected major releases of gems you're using.

Upvotes: 6

Related Questions