Plugin routes override application routes

+1 for this. During the process of converting Clearance to a Rails engine, we had to hack into the routes loading process so it was possible to override routes in the app's config/routes.rb with those set in the plugin.

The hack is the first tip listed here: http://giantrobots.thoughtbot.co...

+1 I'm working on a CMS plugin system that could really benefit from this.

+1

1. I've used the technique listed by here: Nick http://giantrobots.thoughtbot.com/2009/4/23/tips-for-writing-your-o.... It would be nice if that was the default.

+1 We're running into this problem with the Blacklight plugin where different sites need the ability to override routes.

+1 Fixing this would really help us out for Blacklight: http://projectblacklight.org

+1 to fix this - plugin route overrides are broken without this fix.

Maybe you want routes from the plugin to be loaded first or last. In my opinion there should be a convention to define which routes have to be defined at the beginning and which routes at the end.

Are you sure you want your routes to be loaded at the end if you have the default routes active? Some people doesn't remove them.

I've developed an engine called Typus (http://intraducibles.com/projects/typus) and a few months back some users complained about how routes worked because they where loaded after the routes of the application. Now routes are loaded normally with a :path_prefix and everything is working nice.

+1

+1 I'd like to see this as part of the core Rails because it makes building modular applications easier. I've built a small prototype of this as a plugin and it's working great with Redmine so far.

http://github.com/edavis10/prepend_engine_routes

Eric Davis

+1 we need this!

omega watch