Looks like symfony framework. It uses the same solution ton handle actions.
2007/12/10, Federico Cargnelutti <[EMAIL PROTECTED]>: > > > Hi, check out this message: > > > http://www.nabble.com/Re%3A-Using-Zend_Config---Changing-a-module-behaviour-p14136772s16154.html > > > digitalus_media wrote: > > > > i want to add a layer to my cms that will allow myself and other > > developers to add custom logic to their sites core functionality and > > look-feel without hampering updates. > > > > I have a few ideas that i have played with that are working fairly well, > > but would really appreciate any input on a more elegant solution. > > > > my solution basically has a core module and a cms module (among others). > > the cms module has all of the same controllers as the core module, but > > each of them simply extend the core controller. > > > > the pro of this approach as i see it is everything still works the way a > > zf developer would expect and that the developer has the option at any > > time to either use an existing action or add their own (which could run > on > > its own or could inject some logic, then call the parent action). > > > > i have also considered a controller plugin that would evaluate that the > > module / controller / action / view exist, and if not redirect the > request > > to the core module. > > > > any input is much appreciated!!!! > > > > -- > View this message in context: > http://www.nabble.com/best-practice-for-overriding-controllers-tp14230636s16154p14247534.html > Sent from the Zend Framework mailing list archive at Nabble.com. > >
