Closed gorisken closed 4 years ago
The "GetPage" attempts to get the current culture in this order:
If these context are not set based on the URL Prefix, then you will get the default culture. You will need to tell the MVC site "this is the culture" based on your pattern (culture prefix). You can do this through a couple ways:
I recommend #2 personally, however be aware that #2 will ONLY affect the GetPage operation, and not anything else, so you will still need to somehow set the CurrentUICulture and CurrentCulture so other elements have the context of what language to select.
We have setup the dynamic routing with multi culture suppot by using the recommended URL pattern /{% DocumentCulture %}{% NodeAliasPath %}.
In the implementation we used 2 ways:
We can visit the different languages, so that part works, but the content of the page is always the default language.
Is this a bug, or are there additional settings necessary to solve this?