James Adam wrote:
> If you look at the paths of the files in the error you're getting, it
> looks like Rails 1.0 is still being loaded. Did you freeze the gems
> from your own machine? It might be worth double-checking which version
> of Rails you have frozen into your /vendor/rails directory...
> 
> - james
> 
> On 4/21/06, Justin Chen <[EMAIL PROTECTED]> wrote:
>> #<NoMethodError: undefined method `clear!' for Controllers:Module>
>> "/usr/local/lib/ruby/1.8/webrick/httpserver.rb:104:in
>> "/usr/local/lib/ruby/gems/1.8/gems/rails-
>> If i remove the "engines" plugin, the server seems to work fine again so I'm
>> [email protected]
>> http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
>>
>>
>>
> 
> 
> --
> * J *
>   ~



I have similar problem Im dealing with load path problems after install 
plugin engines.

My apps works fine in my Windows, but fails in Shared Hosting, but only 
if has engines plugins installed.
The engines plugins changes the reference path to load rails from 
freezed rails (or my custom gem dir) to shared hosting rails 1.0 path.
Without engines plugins, the app runs fine.

Context:
Deploy from Windows -> Shared hosting

rake freeze_gems

rake deploy

runs ok

On linux box

plugin install engines

Fails I got:

NoMethodError

undefined method `const_load!' for Controllers:Module

RAILS_ROOT: ../config/..
Application Trace | Framework Trace | Full Trace

/usr/local/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/dispatcher.rb:71:in 
`prepare_application'
/usr/local/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/dispatcher.rb:37:in 
`dispatch'
dispatch.cgi:10

/usr/local/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/dispatcher.rb:71:in 
`prepare_application'
/usr/local/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/dispatcher.rb:37:in 
`dispatch'
dispatch.cgi:10

Pedro Visintin
http://blogs.onrails.com.ar



-- 
Posted via http://www.ruby-forum.com/.
_______________________________________________
engine-users mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org

Reply via email to