#90832Resolve routePath by _aspects in Plugin RouteEnhancer
Description
With the “type: Extbase” Route Enhancer, it is possible to have various URL paths by mapping an “_arguments” to a “_controller”.
routes:
- { routePath: '/list/{page}', _controller: 'News::list', _arguments: {'page': '@widget_0/currentPage'} }
- { routePath: '/tag/{tag_name}', _controller: 'News::list', _arguments: {'tag_name': 'overwriteDemand/tags'}}
With “type: Plugin” it is not possible to create various routes.
A possible configuration would be to map an aspect to the path:
SomePlugin:
type: Plugin
routes:
- { routePath: "/{producer}", _aspect: { "producer": "producer" } }
- { routePath: "/{category}", _aspect: { "category": "category" } }
- { routePath: "/{producer}/{category}", _aspect: { "producer": "producer", "category": "category" } }
namespace: "tx_ext_pi1"
aspects:
producer:
...
category:
...Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch
- Commit message
-
[FEATURE] Resolve routePath by _aspects in Plugin RouteEnhancer Resolves: #90832 Releases: main