Migration fails

1 view
Skip to first unread message

lfranklin

unread,
May 16, 2008, 11:20:12 AM5/16/08
to BrainBuster Discussion
I installed the plug-in successfully and went to run the migration
when I got the following error:

E:\Lumatila\CharlesRiverWebConnections\NETRA\trunk>ruby script
\generate brain_buster_migration
./script/../config/../vendor/plugins/brain_buster/lib/
brain_buster_system.rb:13:in `included': undefined method
`append_view_path' for ActionController::Base:Class (NoMethodError)
from ./script/../config/../vendor/plugins/brain_buster/init.rb:
4:in `include'
from ./script/../config/../vendor/plugins/brain_buster/init.rb:
4:in `load_plugin'
from ./script/../config/../vendor/plugins/brain_buster/init.rb:
4:in `class_eval'
from ./script/../config/../vendor/plugins/brain_buster/init.rb:
4:in `load_plugin'
from c:/ruby/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/
initializer.rb:401:in `load_plugin'
from c:/ruby/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/
active_support/core_ext/kernel/reporting.rb:11:in `silence_warnings'
from c:/ruby/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/
initializer.rb:401:in `load_plugin'
from c:/ruby/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/
initializer.rb:185:in `load_plugins'
... 8 levels...
from c:/ruby/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/commands/
generate.rb:1
from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:
27:in `gem_original_require'
from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:
27:in `require'
from script/generate:3

E:\Lumatila\CharlesRiverWebConnections\NETRA\trunk>

As you can see I'm running Rails 1.2.3 on Windows XP. Let me know
what might be causing this problem.

Thanks!

lfranklin

unread,
May 16, 2008, 9:14:57 PM5/16/08
to BrainBuster Discussion
I get the same error on my Debian production system running Rails
1.2.3.

Rob Sanheim

unread,
May 19, 2008, 10:07:34 AM5/19/08
to brainbust...@googlegroups.com

Hi,

It looks like the change I made to brain buster to play nice with the
latest in Rails 2.0+ has broken backwards compatibility with 1.2.x and
older. You could try changing the view_path code to directly modify
the view_paths instead of using append_view_paths. Otherwise, you are
kinda stuck unless you can upgrade to Rails 2 or wait till it gets
patched.

thanks,
Rob

http://robsanheim.com
http://thinkrelevance.com

Reply all
Reply to author
Forward
0 new messages