Hmm, this change actually seems to do the opposite of what the comment says. I get a “stack level too deep” error because Engines::RailsExtensions::AssetHelpers is included at server startup and subsequent requests (not the first request though). Thus, the asset helper methods get alias_chained again every time and an endless loop results.

When I revert that change and have Engines.init called only on plugin loading stage that behaviour vanishes.

The plugin’s init.rb file gets eval’d only once anyways, so I don’t get the rational behind this change at all … maybe that was one beer to much though ;)

config.after_initialize shouldn’t be fired after every request – only at the end of initialization… hmm. Can you confirm that this block is called after every request?

Ok, you’re right, I were wrong. I still had this block from the Engines list in my development.rb which caused the difference:

config.after_initialize { Dependencies.load_once_paths = [] }

This causes Engines to be reloaded.

I still don’t get the rational behind that change though. :)