I have Rails 1.1.2 installed and froze my app to 1.0 by checking it out
into the vender directory. Maybe it’s coincidence, but now when trying
to do rake migrate I get this:
rake migrate --trace
(in /home/beet/workspace/)
rake aborted!
superclass mismatch for class OrderedOptions
/usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/ordered_options.rb:27
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in require' /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:147:inrequire’
/usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support.rb:36
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in require' /usr/lib/ruby/gems/1.8/gems/activerecord-1.14.2/lib/active_record.rb:30 /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:inrequire’
/usr/lib/ruby/site_ruby/1.8/rubygems.rb:182:in activate' /usr/lib/ruby/site_ruby/1.8/rubygems.rb:181:inactivate’
/usr/lib/ruby/site_ruby/1.8/rubygems.rb:167:in activate' /usr/lib/ruby/site_ruby/1.8/rubygems.rb:166:inactivate’
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:26:in require' /home/beet/workspace/Rakefile:10 /usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:1828:inload_rakefile’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:1900:in `run’
/usr/lib/ruby/gems/1.8/gems/rake-0.7.1/bin/rake:7
/usr/bin/rake:18
I haven’t been able to dig up much on this other than one suggestion
that it’s caused by a naming conflict between a migration and a model
with the same name, but I don’t have any such naming conflicts.
Does anyone have any insights as so what might be causing the superclass
mismatch?
Anyone had this happen, or have an idea what might cause it to happen?
It’s a real spanner in the works.
Mark B. wrote:
I have Rails 1.1.2 installed and froze my app to 1.0 by checking it out
into the vender directory. Maybe it’s coincidence, but now when trying
to do rake migrate I get this:
rake migrate --trace
(in /home/beet/workspace/)
rake aborted!
superclass mismatch for class OrderedOptions
I faced the same problem. Anybody solved this already?
Mark B. wrote:
Anyone had this happen, or have an idea what might cause it to happen?
It’s a real spanner in the works.
Mark B. wrote:
I have Rails 1.1.2 installed and froze my app to 1.0 by checking it out
into the vender directory. Maybe it’s coincidence, but now when trying
to do rake migrate I get this:
rake migrate --trace
(in /home/beet/workspace/)
rake aborted!
superclass mismatch for class OrderedOptions
I’m using the same environment - ruby 1.8.5 and rails 1.2.1.
I was using rails 1.1.1 when I ran rails, then
upgraded to 1.2.2 and had the same superclass misatch … OrderedOptions
issue.
Could not start script/server.
I found that config/environment.rb still had the line:
RAILS_GEM_VERSION = ‘1.1.1’
even tho’ I had upgraded to 1.2.1.
I changed this to
RAILS_GEM_VERSION = ‘1.2.1’
and voila, all is well.
Frédéric Bruneteau wrote:
I have a similar problem.
I use ruby 1.8.5 and rails 1.2.1
and when I run the script “public/dispatch.cgi”,
I have a similar error at line 28 (not 27) of ordered_options.rb
(activesupport 1.4.0) :
./public/dispatch.cgi
I have a similar problem.
I use ruby 1.8.5 and rails 1.2.1
and when I run the script “public/dispatch.cgi”,
I have a similar error at line 28 (not 27) of ordered_options.rb
(activesupport 1.4.0) :
./public/dispatch.cgi
/usr/local/lib/ruby/gems/1.8/gems/activesupport-1.4.0/lib/active_support/ordered_options.rb:28:
superclass mismatch for class OrderedOptions (TypeError)
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
gem_original_require' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:inrequire’
from
/usr/local/lib/ruby/gems/1.8/gems/activesupport-1.4.0/lib/active_support/dependencies.rb:496:in
require' from /usr/local/lib/ruby/gems/1.8/gems/activesupport-1.4.0/lib/active_support/dependencies.rb:343:innew_constants_in’
from
/usr/local/lib/ruby/gems/1.8/gems/activesupport-1.4.0/lib/active_support/dependencies.rb:496:in
require' from /usr/local/lib/ruby/gems/1.8/gems/activesupport-1.4.0/lib/active_support.rb:37 from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:ingem_original_require’
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
require' ... 8 levels... from /usr/local/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:42:inrun’
from ./public/…/config/environment.rb:13
from ./public/dispatch.cgi:3:in `require’
from ./public/dispatch.cgi:3
Does anyone have an idea ?
Maybe if you run sudo grep -r "OrderedOptions" . in your ruby project folder, you would see that other class have the same name as OrderedOptions if you found it, you should change the file’s name.