The problem is the whole thing happens with the call to Rails::Initializer.run in environment.rb. Plugin config comes after that call, and thus after the call to after_initialize. Worse, the plugins themselves are loaded /during/ the call, so we can't even make people put their config somewhere else in the file.
Mislav Marohnić wrote: > On Dec 11, 2007 9:33 AM, Nathan Weizenbaum <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > It looks like this is still run before the configuration section of > environment.rb, so no luck :-(. > > > I'm looking at Initializer code, what you said can't be true: > http://dev.rubyonrails.org/browser/trunk/railties/lib/initializer.rb#L84 > > The only thing that happens /after/ `after_initialize` is > "config/initializers/*.rb" application initializers. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/haml?hl=en -~----------~----~----~----~------~----~------~--~---
