Feature #2142
closedChange the way plugin routes are integrated
Description
Plugin's routes can today ( r1977 ) be handled thanks to a hook in the config/routes.rb :
class MyRoutes < Redmine::Hook::Listener
def routes(context)
context[:map].resources :mymodel
context[:map].connect 'mypath/:blah', :controller => 'mycontroller'
#etc.
end
end
Redmine::Hook.add_listener(MyRoutes)
Maybe it is possible to use Engines system to handle each plugin's routes, with "map.from_plugin" method :
- in config/routes.rb
It has been discussed here in the forum. Maybe it would be easier to use for plugin developpers, but I'm not 100% sure routes overriding will produce the same effect.
Updated by Eric Davis about 18 years ago
- Status changed from New to Closed
- Target version set to 0.8
- % Done changed from 0 to 100
- Resolution set to Fixed
I really like your suggestion and changed the way plugin routing works in r1991. Plugins' routes.rb are now added automatically to Redmine's routing, including the ability to override Redmine's default routing.
Here's an example I put in a plugin to override the home page with the project list.
Updated by Eric Davis about 18 years ago
Updated by Jean-Baptiste Barth almost 17 years ago
Just a quick note here since I may not be the only one to miss that : this way to configure routes in plugins has changed with r2887. You should have a look at this thread where Eric explains how to update your plugins.