You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The below refers to URLs with a limited set of parameters.
... or how to get rid of cHash in the URL.
There are a number of related questions online (e.g. on Stackoverflow, on Forge) and there is some explanation, but some of it is vague and not definitive. It might be a good idea to add the information to the docs
when a cHash is added to the URL
how to get rid of the cHash (reqirement, aspect, ...?)
Related docs / information
The requirements section exactly specifies what kind of parameter should be added to that route as regular expression. This way, it is configurable to only allow integer values for e.g. pagination. If the requirements are too loose, a URL signature parameter (“cHash”) is added to the end of the URL which cannot be removed.
The below refers to URLs with a limited set of parameters.
... or how to get rid of cHash in the URL.
There are a number of related questions online (e.g. on Stackoverflow, on Forge) and there is some explanation, but some of it is vague and not definitive. It might be a good idea to add the information to the docs
Related docs / information
https://docs.typo3.org/m/typo3/reference-coreapi/10.4/en-us/ApiOverview/Routing/AdvancedRoutingConfiguration.html?highlight=advanced%20routing#simple-enhancer
So what is too loose?
https://stackoverflow.com/questions/57649210/typo3-routeenhancer-with-custom-valuemapper#comment101766166_57649210
Here, the solution is to implement StaticMappableAspectInterface: https://stackoverflow.com/questions/59643974/typo3-cms-9-lts-cacheable-extbase-action-but-no-chash-with-new-routing
Some solutions use a workaround:
e.g. here:
http://typo3.3.n7.nabble.com/routeEnhancers-Extabase-cHash-loswerden-tp292271p292275.html
Is it necessary to do this or would a requirements section work as well?
Links
questions / answers:
The text was updated successfully, but these errors were encountered: