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
My plan for the major update I'm currently working on is to no more force redirecting (if no valid langauge is detected) - instead the extension will offer the following configuration-options to control redirection behaviour:
Never redirect
Only redirect if a matching language is found
Always redirect
While option 1 and 3 are pretty self-explanatory option 2 is easier to understand when having a look at the upcoming "language-detection-stack" explained here. Choosing this option means the following:
If no distinct valid frontend language-code was detected in the URL (either as query string, in the path or by domain-mapping) the extension will try to find a matching language elsewhere. There are two methods (cookie and browser settings) that could deliver a matching language and having selected option 2 simply means that a redirect will only happen if one of these methods returns a matching language. Meaning that visitors, that don't seem to accept any of the offered languages could be offered a list of all available languages instead of simply redirecting them to the default language.
Another configuration-setting I plan to offer is the way how redirecting happens. According to the different url-structures explained in the language-detection-stack it makes only sense to support all 3 of them:
domain.tld → domain.tld/xy/
domain.tld → domain.tld?language=xy
domain.tld → domain.xy
While options 1 and 2 will simply work out of the box option 3 will require another step - setting up your own domain-language-mapping. For a better understanding what that's about I'll simply include a preview-screenshot of the current state of version 2's configuration-settings:
Hey @Cinamonas,
I agree with your changes here, that's already on my todo list as well.
According to semantic versioning, new version should be 2.0.0 though, since this is a breaking change.
The text was updated successfully, but these errors were encountered: