TYPO3 Core

I did some debugging here. There was a bug in array handling (inflateParameters() vs inflateNamespaceParameters()), which you fixed lately and which before that resulted in $routeArguments not being reduced by $dynamicArguments. All arguments were handled as static arguments. As in my example configuration above, not all parameters(Lehrgang) have an aspect. They are therefor treated as dynamic. Dynamic parameters - after the fix - lead to the cHash calculation.

I changed my configuration to have an aspect for every parameter. With this all parameters are static.

• I am wondering, if the documentation for SimpleEnhancer is correct? It does not have an aspect in the example given. It should generate a cHash. https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ApiOverview/Routing/AdvancedRoutingConfiguration.html#simple-enhancer
• tx_myext_lehrgaenge/action or tx_myext_lehrgaenge__action has no effect in this situation
• using the ExtbaseEnhancer may be more appropriate, but I should always be able to use the SimpleEnhancer, right?

Using ExtbaseEnhancer would fix the part on the missing mapper definition for tx_myext_lehrgaenge[controller] in your site configuration - basically since the controller-action pair needs to be explicitly given in the route configuration.