woahdae
Fri, 02 Jan 2009 13:21:13 -0800
> I currently have an app that works and as soon as I install the > activescaffoldexport plugin, I start receiving the same error. Will > post if I find a solution
This is triggered by active_scaffold_export/lib/config/core.rb because for some reason if you declare ActiveScaffold::Config::Core at any point other than in the active_scaffold itself, the rails app will use that ActiveScaffold::Config::Core class and ignore the active_scaffold one. Not sure why this is, but I'm also not sure where any of the require statements are in active_scaffold. I follow the plugin loading from init.rb through active_scaffold/environment.rb, including a require on active_scaffold.rb, but there aren't any requires to things in config, etc. My guess is that they must be loaded implicitly somehow, and if you explicitly require a file defining ActiveScaffold::Config::Core, the real ActiveScaffold::Config::Core is never implicitly loaded. Anyways, the punch line is that if you put an explicit require at the top of active_scaffold/lib/active_scaffold.rb, all is well. ex: <code> require File.dirname(__FILE__) + '/active_scaffold/config/core' </code> maybe something similar is going on with the fsck editor plugin (I don't use it, so I wouldn't know) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ActiveScaffold : Ruby on Rails plugin" group. To post to this group, send email to activescaffold@googlegroups.com To unsubscribe from this group, send email to activescaffold+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/activescaffold?hl=en -~----------~----~----~----~------~----~------~--~---