You got me thinking about dependent gems that I'm using (rather than 
rails) and it turns out that the problem is caused by a gem called 
google-spreadsheet-ruby (it allows you to access and parse google 
spreadsheets from ruby). This gem defines String.force_encoding for Ruby 
1.8, however, rails is using this method to test whether it's running on 
top of Ruby 1.8 or Ruby 1.9 - so it think's it's using Ruby 1.9 when 
actually it's using Ruby 1.8, and then quickly hits problems and 
crashes.

I've notified the author of the gem and suggested a solution, and I've 
patched my own app for now as well (to undefine this method entirely as 
the gem is an unused dependency in my project) and everything's working 
again. :-)
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to