On 8/29/07, Peter Bex <[EMAIL PROTECTED]> wrote: > Sometimes running script/console reveals these errors by displaying > a message somewhere. Other times, it does not. Try removing the > observer loading statement and run script/console and refer to > the class. That should trigger it to autoload, and if there's an > error it will show up. Rails only drops errors in some circumstances, > not in others.
You'll need to be careful in this case, because it's the fact that the observer causes the model to be loaded *before* the rest of environment.rb has been processed that could be causing the problem. But, yes, script/console is your friend. You could also try commenting out anything after the end of the initializer block to see if your model has any hidden dependencies that it isn't explicitly declaring. -- * J * ~ _______________________________________________ Engine-Users mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
