#1375
  • Created on
    2012-12-03 20:29
  • Reported by
    kajkandler
  • Status
    Fixed
  • Priority
    Normal (3)
  • Assigned to
    -
  • Milestone
    -
  • Plan Level
    -
  • Due Date
    -

Attachments

Related Tickets

Add new subtask or bug

Update to project state results in NoMethodError

I updated my Tracks App from 2.0 to 2.1 with Mysql and any change of the status of the project (incl. reviewed) results int his error.
Processing ProjectsController#update (for 71.174.238.87 at 2012-12-03 21:24:26) [PUT]
  Parameters: {"_source_view"=>"project", "wants_render"=>"true", "0"=>"_", "1"=>"s", "2"=>"o", "3"=>"u", "4"=>"r", "5"=>"c", "6"=>"e", "7"=>"_", "8"=>"v", "9"=>"i", "project"=>{"name"=>"XXXXXXXXXXXX", "state"=>"completed", "description"=>"", "default_tags"=>"completed", "default_context_name"=>"@Computer"}, "10"=>"e", "11"=>"w", "12"=>"=", "13"=>"p", "14"=>"r", "15"=>"o", "16"=>"j", "17"=>"e", "18"=>"c", "19"=>"t", "id"=>"1", "authenticity_token"=>"NaXLQVS20OLiZNfvCdkhybbQdf+1C/JQdkbDGBFvQrE="}

NoMethodError (undefined method `unscoped' for #<Class:0x7f367617e7e8>):
  /usr/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:170:in `method_missing'
  /usr/lib/ruby/gems/1.8/gems/acts_as_list-0.1.8/lib/acts_as_list/active_record/acts/list.rb:325:in `update_positions'
  app/controllers/projects_controller.rb:193:in `update'
  /usr/lib/ruby/1.8/phusion_passenger/rack/request_handler.rb:95:in `process_request'
  /usr/lib/ruby/1.8/phusion_passenger/abstract_request_handler.rb:207:in `main_loop'
  /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:374:in `start_request_handler'
  /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:332:in `handle_spawn_application'
  /usr/lib/ruby/1.8/phusion_passenger/utils.rb:184:in `safe_fork'
  /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:330:in `handle_spawn_application'
  /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in `__send__'
  /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in `main_loop'
  /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:196:in `start_synchronously'
  /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:163:in `start'
  /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:209:in `start'
  /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:262:in `spawn_rails_application'
  /usr/lib/ruby/1.8/phusion_passenger/abstract_server_collection.rb:126:in `lookup_or_add'
  /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:256:in `spawn_rails_application'
  /usr/lib/ruby/1.8/phusion_passenger/abstract_server_collection.rb:80:in `synchronize'
  /usr/lib/ruby/1.8/phusion_passenger/abstract_server_collection.rb:79:in `synchronize'
  /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:255:in `spawn_rails_application'
  /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:154:in `spawn_application'
  /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:287:in `handle_spawn_application'
  /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in `__send__'
  /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in `main_loop'
  /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:196:in `start_synchronously'
  /usr/lib/phusion_passenger/passenger-spawn-server:61

Rendering /var/www/tracks/TracksApp-tracks-1b6a18b/public/500.html (500 Internal Server Error)
User picture
  on 2012-12-03 20:38 *
By kajkandler
Same error happens when I try to create a new project
User picture
  on 2012-12-04 14:24 *
By zoombody
Version set to 2.1
Version set to 2.1
User picture
  on 2012-12-04 14:32 *
By zoombody
Are you sure all your ruby versions are straight on the system? This looks similar to this thread on the mailing list: https://groups.google.com/d/topic/tracksapp/SHFY1TUytdE/discussion

For Tracks 2.1 you need to be running Ruby 1.8.7.
User picture
User picture
  on 2012-12-04 14:37 *
By zoombody
Did you preserve the salt in config/site.yml when upgrading? https://groups.google.com/d/topic/tracksapp/INrkKjYPK6M/discussion
User picture
  on 2012-12-04 14:38 *
By zoombody
And did you run bundle exec rake db:migrate RAILS_ENV=production?
User picture
  on 2012-12-07 20:38 *
By kajkandler
Yes, I copied the site.yml from the old version.

Yes, I ran bundle exec rake db:migration .... on my mysql db after migrating the data from the sqlite3 db that could not be upgraded (TRACKS-1374). But that might be a hint. Is the salt used for anything but password encryption? I was able to work with my existing login.
User picture
  on 2012-12-07 21:02 *
By kajkandler
Status changed from New to Accepted
Status changed from New to Accepted
Well, it was the act_as_list version "~>0.1.4" that needed to be restricted to "0.1.4" in my Gemfile.

Thanks, now it seems I'm in business again.
User picture
  on 2012-12-07 21:13 *
By zoombody
Status changed from Accepted to Fixed
Status changed from Accepted to Fixed
(The fix was #1376.)

Great. Did that take care of #1374 as well?