Sounds good to me. On Tue, Dec 2, 2008 at 11:51 AM, Matthew Weier O'Phinney <[EMAIL PROTECTED]> wrote: > -- Matthew Weier O'Phinney <[EMAIL PROTECTED]> wrote > (on Monday, 01 December 2008, 11:50 PM -0500): >> -- Jordan Moore <[EMAIL PROTECTED]> wrote >> (on Monday, 01 December 2008, 08:24 PM -0800): >> > The route that fails is as follows: >> > >> > <routes> >> > <homepage> >> > <type>Zend_Controller_Router_Route_Static</type> >> > <route></route> >> > <defaults> >> > <action>homepage</action> >> > </defaults> >> > </homepage> >> > ... >> > </routes> >> > >> > The only configuration-type changes I make to the front controller is >> > setting the default module to "public" and turning on >> > "prefixDefaultModule". I'm not removing default routes. >> >> Okay, I've verified this, and will look into it more closely first thing >> in the morning. However, I have one caveat: not providing a default for >> the controller parameter in your route -- paticularly in static routes >> -- is a bad practice, and one we have certainly never intended to >> support. (I would have expected the above to fail previously, to be >> quite honest.) That said, I will look to see if there is a solution that >> addresses both the issue report for which the solution broke your code >> as well as your own use case. >> >> In the meantime, setting the 'useDefaultControllerAlways' front >> controller parameter to true in your bootstrap: >> >> $front->setParam('useDefaultControllerAlways', true); >> >> is a quick fix for your situation. > > I've discussed this with several others, and we all feel that this > particular case represents both an edge case *and* bad usage of static > routes. Static routes should always minimally define the controller and > action parameters as default values; without this information, the > dispatcher simply does not have enough information to choose the correct > dispatchable. > > I have created an issue, ZF-5140, to track the addition of a note to > this effect in the manual. > > >> > Also, every other route that is identical to the above route (with the >> > exception of the route path) fails to be routed (i.e., is routed to >> > the default controller/action). If you need entire list of routes, I'd >> > prefer to take this correspondence off of the mailing list. >> > >> > On Mon, Dec 1, 2008 at 7:41 PM, Matthew Weier O'Phinney >> > <[EMAIL PROTECTED]> wrote: >> > > -- Jordan Moore <[EMAIL PROTECTED]> wrote >> > > (on Monday, 01 December 2008, 07:02 PM -0800): >> > >> Sorry for the delayed response. >> > >> >> > >> Apparently this was happening because I wasn't specifying the >> > >> controller for that route (it previously defaulted to "index"). This >> > >> seems like a significant change for a mini release. >> > > >> > > Yes, it is a significant jump for a mini-release, but I *need* a >> > > reproduce case so I can understand exactly what has changed. Can you >> > > please provide this? >> > > >> > > The issue you reference, ZF-3465, was a fix for when the *default* >> > > routes are removed -- and you have not indicated if your situation falls >> > > under that umbrella or otherwise. I need a reproduce case -- your set of >> > > routes, and the specific route that fails -- so that I can determine the >> > > scope of the change and whether a rollback is necessary, a patch to the >> > > changeset, or if it's a documentation issue. >> > > >> > > >> > >> On Mon, Dec 1, 2008 at 6:21 PM, Matthew Weier O'Phinney >> > >> <[EMAIL PROTECTED]> wrote: >> > >> > -- Jordan Moore <[EMAIL PROTECTED]> wrote >> > >> > (on Monday, 01 December 2008, 02:52 PM -0800): >> > >> >> Removing the 3 lines of code in Zend_Controller_Request_Abstract that >> > >> >> reference ZF-3465 fixes it. >> > >> > >> > >> > Still need the static route that triggers the issue... I'd rather have >> > >> > *both* issues resolved, not just one ;) >> > >> > >> > >> >> On Mon, Dec 1, 2008 at 2:10 PM, Jordan Moore <[EMAIL PROTECTED]> >> > >> >> wrote: >> > >> >> > I've got a couple of apps with a static route that is an empty >> > >> >> > string. >> > >> >> > This route is used for the base of the domain ("/"). After >> > >> >> > upgrading >> > >> >> > to 1.7.1, the route no longer matches requests for the base of the >> > >> >> > domain. >> > >> >> > >> > >> >> > On Mon, Dec 1, 2008 at 1:54 PM, Wil Sinclair <[EMAIL PROTECTED]> >> > >> >> > wrote: >> > >> >> >> Hi all, >> > >> >> >> >> > >> >> >> It is my pleasure to announce the release of Zend Framework >> > >> >> >> 1.7.1! You >> > >> >> >> can download this new mini release from the ZF download site: >> > >> >> >> >> > >> >> >> http://framework.zend.com/download/latest/ >> > >> >> >> >> > >> >> >> A list of all issues resolved in this release can be found at: >> > >> >> >> >> > >> >> >> http://framework.zend.com/issues/secure/views/IssueNavigator.jspa?reques >> > >> >> >> tId=10912 >> > >> >> >> >> > >> >> >> We'd like to once again thank our generous Zend Framework >> > >> >> >> contributors >> > >> >> >> for all the effort they have put in to this release and the >> > >> >> >> project as a >> > >> >> >> whole. Enjoy! >> > >> > >> > >> > -- >> > >> > Matthew Weier O'Phinney >> > >> > Software Architect | [EMAIL PROTECTED] >> > >> > Zend Framework | http://framework.zend.com/ >> > >> > >> > >> >> > >> >> > >> >> > >> -- >> > >> Jordan Ryan Moore >> > >> >> > > >> > > -- >> > > Matthew Weier O'Phinney >> > > Software Architect | [EMAIL PROTECTED] >> > > Zend Framework | http://framework.zend.com/ >> > > >> > >> > >> > >> > -- >> > Jordan Ryan Moore >> > >> >> -- >> Matthew Weier O'Phinney >> Software Architect | [EMAIL PROTECTED] >> Zend Framework | http://framework.zend.com/ >> > > -- > Matthew Weier O'Phinney > Software Architect | [EMAIL PROTECTED] > Zend Framework | http://framework.zend.com/ >
-- Jordan Ryan Moore