Releases: t3n/seo-routing
4.0.1
Add Flow 7.x compatibility
Merge pull request #23 from nlx-lars/feature/neos-7 !!! FEATURE: Add support for Neos 7
Handle redirect with componentContext
Merge pull request #19 from t3n/handle-redirect Handle redirect with componentContext
Adjust Response instead of creating a new one
Merge pull request #18 from t3n/adjust-response Adjust response instead of create a new one
Add Flow 6.x compatibility
Merge pull request #17 from t3n/tests Fix unit tests
Add Unit-Tests and check for blacklist
Merge pull request #4 from t3n/check-blacklist Check blacklist for toLowerCase-Routing
Document.yaml update
With the version before the RegEx has thrown validation errors though the uriPathSegment was correct.
Support older Http\Response versions
Merge pull request #2 from t3n/improve-support Support older Http\Response versions
Introduce toLowerCase-Routing
With this release another feature (toLowerCase
-Routing) has been added and the configuration has changed.
toLowerCase-Routing
This will redirect urls from http://dev.local/camelCase/
to http://dev.local/camelcase/
with your configured statusCode.
But be careful: if you have nodes in your instance with camel- or uppercase uriPathSegment
this will run into errors. So make sure to lowercase all of them.
In order to avoid camel- or uppercase uriPathSegment
for new nodes this package will restrict users to use a lowercase uriPathSegment
.
Configuration has changed
Instead of enabling or disabling the seo-routing, you have to pick the components you want to use. Available are:
toLowerCase
trailingSlash
By default toLowerCase
is disabled.
In v1.0.0 there was only trailingSlash
which was enabled like this:
t3n:
SEO:
Routing:
redirect:
enable: true
Now you have to update your setting:
t3n:
SEO:
Routing:
redirect:
enable:
trailingSlash: true
toLowerCase: true
1.0.0
Initial release of https://github.com/yeebase/Yeebase.SEO.Routing/tree/1.1.2 under a new namespace and package name