Ok, looking at the stack trace it definitely looks like it is loading
a class called Twitter::Client which has an intialize method that
doesn't take any arguments instead of the twitter4r gem version of the
class.
>> > > ArgumentError (wrong number of arguments (1 for 0)):
>> > > app/controllers/site_controller.rb:7:in `initialize'
>> > > app/controllers/site_controller.rb:7:in `new'
>> > > app/controllers/site_controller.rb:7:in `index'
>> > > haml (2.2.2) lib/sass/plugin/rails.rb:19:in
>> > > `process_without_compass'
>> > > /Library/Ruby/Gems/1.8/gems/chriseppstein-compass-0.8.10/lib/compass/
>> > > app_integration/rails/action_controller.rb:7:in `process'
If you open up a ./script/console prompt and type:
> Twitter::Client.new(:login => "somelogin", :password => "password")
Do you get the same ArgumentError?
If you open up a regular IRB without any Rails stuff loaded in what
happens when you run:
> require 'rubygems'
> require 'twitter4r'
> Twitter::Client.new(:login => "somelogin", :password => "password")
??
Thanks,