Bug #87782
closed
Page type is not added to query string parameters
0%
Description
If the page type decorator is at least once, unmapped page types silently get truncated and produce faulty URLs. While I understand the purpose of this, I think someone should be able to disable this behavior, e.g. by setting default: null.
Additionally, page types can't be re-mapped in an URL (e.g. where the page type must be at the beginning of the route), any other argument doesn't get replaced.
Example:
routeEnhancers:
MyIdentifier:
type: Simple
routePath: '/{page_type}/{uuid}'
_arguments:
page_type: 'type'
uuid: 'uuid'
With that configuration, page_type is replaced (and processed), but uuid is not replaced and the value gets attached as a GET argument.
Updated by Benni Mack over 3 years ago
- Status changed from New to Needs Feedback
Hey Andy,
I guess these are two issues, right? The first one should be solved in latest v9.5.x releases, the second one is only possible with a custom Enhancer + Middleware for the time being. I guess we'd need "routePreProcessors" for that :) As the existing logic is super huge and flexible, adding more to the Route Logic is possible, but I guess part of a bigger job, if somebody is up for it, yes, otherwise I think this could / should be doable in an extension for the time being.
Updated by Christian Kuhn about 2 years ago
- Status changed from Needs Feedback to Closed
hey. i hope it's ok to close here for now: the issue has been partially solved, the second part is a bigger task that may need bigger refactoring, but can be done with in extension for now.