feat: adjust localization #32
Merged
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
niccofyren
commented
Oct 11, 2024
| @@ -140,7 +141,24 @@ | |||
| # Internationalization | |||
| # https://docs.djangoproject.com/en/4.2/topics/i18n/ | |||
|
|
|||
| LANGUAGE_CODE = "en-us" | |||
| # Default language code used on content | |||
| LANGUAGE_CODE = "no" | |||
There was a problem hiding this comment.
This fixes any new articles being created
Comment on lines
+159
to
+160
| ("no", "Norwegian"), | ||
| # ('en', "English"), |
There was a problem hiding this comment.
This triggers "locale migration option" on existing content and makes sure only Norwegian locale is available for now
olemathias
approved these changes
Oct 11, 2024
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.
Backend part of: gathering/tgno-frontend#57
Default site locale during setup was english so we both need to change default to Norwegian and change locale on existing content. We use
wagtail.localesboth to avoid having to write migrations for each locale config change, and since it seems to handle default locale change gracefully.Once release we need to (before frontend can be released)
nolocale viahttps://www.tg.no/api/v2/news/?fields=locale