Fixed issue with culture not set when doing internal redirects due to public access #11262
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Set culture from domain when internal redirecting due to public access
nikolajlauridsen
approved these changes
Oct 5, 2021
nikolajlauridsen
deleted the
v9/bugfix/11227_GetDictionaryValue_not_working_when_Restrict_Public_Access_is_setup
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #11227
When rewriting the published content due to public access. E.g. redirect to login page, the culture was not specified. Thereby the dictionary item culture falled back to the default from config. If is not the correct one, no translations was shown.