Bug #30929
Routing does not always work if splitString is optional
| Status: | Resolved | Start date: | 2011-10-14 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Bastian Waidelich | % Done: | 100% |
|
| Category: | MVC - Routing | |||
| Target version: | - | |||
| PHP Version: | Complexity: | |||
| Has patch: | Affected Flow version: |
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.
Associated revisions
[BUGFIX] Routing does not always work if splitString is optional
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").
This change fixes this by always matching against the complete
routePath with an improved RegEx.
Resolves: #30929
Change-Id: Iae4ba2652c08e8a0ba468076ae5dec6008f0ea47
History
#1 Updated by Mr. Hudson almost 4 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 almost 4 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 almost 4 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset ce14c0003eb87316e760985c7fa59cbee5af1a72.