Bug #30929

Routing does not always work if splitString is optional

Added by Bastian Waidelich about 10 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
Should have
Assignee:
Bastian Waidelich
Category:
MVC - Routing
Target version:
-
Start date:
2011-10-14
Due date:
% Done:

100%

Estimated time:
PHP Version:
Has patch:
Complexity:

Description

If the route part following an identity route part optional like

{post}(.html)

the IdentityRoutePart creates a correct link but matching of the URI without the optional part fails, if the dynamic part contains the split string (in this example if the post contains the string ".html").
Instead always the complete request path should be matched against.

#1

Updated by Mr. Hudson about 10 years ago

  • Status changed from Accepted to Under Review

Patch set 2 of change Iae4ba2652c08e8a0ba468076ae5dec6008f0ea47 has been pushed to the review server.
It is available at http://review.typo3.org/5447

#2

Updated by Mr. Hudson about 10 years ago

Patch set 3 of change Iae4ba2652c08e8a0ba468076ae5dec6008f0ea47 has been pushed to the review server.
It is available at http://review.typo3.org/5447

#3

Updated by Bastian Waidelich about 10 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF