Bug #1264

Routes with default values for "multiple route part" segments are not resolved correctly

Added by Bastian Waidelich almost 7 years ago. Updated almost 5 years ago.

Status:Resolved Start date:2008-08-11
Priority:Must have Due date:
Assigned To:Bastian Waidelich % Done:

100%
Category:MVC
Target version:-
PHP Version: Complexity:
Has patch: Affected Flow version:

Description

With the new possibility to add multiple route parts in one URL pattern segment (see #1250) a new issue emerged:
The route "[firstName]-[lastName]/[@action]" is not resolved correctly if defaults are set for lastName and @action and lastName is empty in request URL (e.g. "john-/list").
This happens because static route part handler cuts first url segment from request path when matching the hyphen.

Associated revisions

Revision 4a3a0742
Added by Bastian Waidelich almost 7 years ago

  • FLOW3: (MVC) Added new property "lastRoutePartInSegment" to F3_FLOW3_MVC_Web_Routing_StaticRoutePart to indicate whether a route part is the last in the current url segment. This fixes #1264.
    Routing classes are quite messy and complex at the moment. Refactoring and cleanup is needed!

History

#1 Updated by Bastian Waidelich almost 7 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100

Applied in changeset r1120.

Also available in: Atom PDF