Skip to content

Sync UI language selection with user profile settings#14151

Open
Gpetrak wants to merge 7 commits intomasterfrom
ISSUE_14150
Open

Sync UI language selection with user profile settings#14151
Gpetrak wants to merge 7 commits intomasterfrom
ISSUE_14150

Conversation

@Gpetrak
Copy link
Copy Markdown
Member

@Gpetrak Gpetrak commented Apr 20, 2026

This PR was created according to this issue: #14150

Checklist

Reviewing is a process done by project maintainers, mostly on a volunteer basis. We try to keep the overhead as small as possible and appreciate if you help us to do so by completing the following items. Feel free to ask in a comment if you have troubles with any of them.

For all pull requests:

  • Confirm you have read the contribution guidelines
  • You have sent a Contribution Licence Agreement (CLA) as necessary (not required for small changes, e.g., fixing typos in the documentation)
  • Make sure the first PR targets the master branch, eventual backports will be managed later. This can be ignored if the PR is fixing an issue that only happens in a specific branch, but not in newer ones.

The following are required only for core and extension modules (they are welcomed, but not required, for contrib modules):

  • There is a ticket in https://github.com/GeoNode/geonode/issues describing the issue/improvement/feature (a notable exemption is, changes not visible to end-users)
  • The issue connected to the PR must have Labels and Milestone assigned
  • PR for bug fixes and small new features are presented as a single commit
  • PR title must be in the form "[Fixes #<issue_number>] Title of the PR"
  • New unit tests have been added covering the changes, unless there is an explanation on why the tests are not necessary/implemented

Submitting the PR does not require you to check all items, but by the time it gets merged, they should be either satisfied or inapplicable.

@Gpetrak Gpetrak added this to the 5.1.0 milestone Apr 20, 2026
@cla-bot cla-bot Bot added the cla-signed CLA Bot: community license agreement signed label Apr 20, 2026
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request implements a user language preference system by introducing a new ProfileLanguageMiddleware, updating the profile form and admin interface, and adding a view to handle language selection. Feedback focuses on ensuring the user profile remains the source of truth for language settings, avoiding constant duplication, and persisting language changes to the database for authenticated users.

Comment thread geonode/base/middleware.py Outdated
Comment on lines +111 to +116
lang = request.session.get(SESSION_LANG_KEY)

if not lang:
lang = getattr(request.user, "language", None)
if lang:
request.session[SESSION_LANG_KEY] = lang
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The current logic prioritizes the session value even if the user's profile language has been updated (e.g., via the profile edit form). For authenticated users, the profile should be the source of truth to ensure consistency across the application. Additionally, this suggestion avoids redundant session writes by only updating the session if the value has actually changed.

Suggested change
lang = request.session.get(SESSION_LANG_KEY)
if not lang:
lang = getattr(request.user, "language", None)
if lang:
request.session[SESSION_LANG_KEY] = lang
lang = getattr(request.user, "language", None)
if lang and request.session.get(SESSION_LANG_KEY) != lang:
request.session[SESSION_LANG_KEY] = lang

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The proposed change would re-sync the session from the DB on every request and undo user language changes from the UI, so I’m keeping the current logic

Comment thread geonode/people/views.py Outdated
return qs


SESSION_LANG_KEY = "language_override"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The constant SESSION_LANG_KEY is already defined in geonode/base/middleware.py. It should be imported from there to avoid duplication and maintain a single source of truth.

Suggested change
SESSION_LANG_KEY = "language_override"
from geonode.base.middleware import SESSION_LANG_KEY

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Comment thread geonode/people/views.py
Comment on lines +181 to +182
if lang_code and check_for_language(lang_code):
request.session[SESSION_LANG_KEY] = lang_code
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To fully synchronize the UI language selection with the user profile as intended, the selected language should be persisted to the user's profile when they are authenticated. This ensures the preference is preserved across different sessions and devices.

Suggested change
if lang_code and check_for_language(lang_code):
request.session[SESSION_LANG_KEY] = lang_code
if lang_code and check_for_language(lang_code):
request.session[SESSION_LANG_KEY] = lang_code
if request.user.is_authenticated:
request.user.language = lang_code
request.user.save(update_fields=["language"])

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would change the semantics of the topbar switcher from a session-only override to a persistent profile update. So I will keep the current approach.

@Gpetrak Gpetrak marked this pull request as ready for review April 21, 2026 07:19
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 21, 2026

Codecov Report

❌ Patch coverage is 31.42857% with 48 lines in your changes missing coverage. Please review.
✅ Project coverage is 52.59%. Comparing base (94ca636) to head (80b537e).
⚠️ Report is 3 commits behind head on master.

❗ There is a different number of reports uploaded between BASE (94ca636) and HEAD (80b537e). Click for more details.

HEAD has 1 upload less than BASE
Flag BASE (94ca636) HEAD (80b537e)
7 6
Additional details and impacted files
@@             Coverage Diff             @@
##           master   #14151       +/-   ##
===========================================
- Coverage   74.62%   52.59%   -22.03%     
===========================================
  Files         958      958               
  Lines       57891    58110      +219     
  Branches     7889     7930       +41     
===========================================
- Hits        43202    30564    -12638     
- Misses      12927    26103    +13176     
+ Partials     1762     1443      -319     
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@giohappy giohappy removed this from the 5.1.0 milestone Apr 22, 2026
@Gpetrak Gpetrak linked an issue Apr 23, 2026 that may be closed by this pull request
Comment thread geonode/settings.py
)

# This setting includes supported Maptstore language choices in a DB-based format
PROFILE_LANGUAGE_CHOICES = tuple((code.split("-")[0].lower(), label) for code, label in MAPSTORE_DEFAULT_LANGUAGES)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can't we use the get_2letters_languages utils with some changes?

Copy link
Copy Markdown
Member Author

@Gpetrak Gpetrak Apr 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mattiagiupponi thanks for the comment. Ini my opinion, the idea in this setting is to completely be synced with the Mapstore supported languages. I'm afraid that if we use / modify this method, we will add a bit of complexity and it will not such clear that the source of truth here is the supported Mapstore language.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed CLA Bot: community license agreement signed enhancement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Sync UI language selection with user profile settings

3 participants