starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

UI Enhancements for Translation feature #9050

New Issue
Closed
opened 2025-12-29 20:44:49 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:44:49 +01:00
Owner
Copy Link

Originally created by @AnythingOverIP on GitHub (Jan 5, 2024).

NetBox version

v3.7.0

Feature type

Change to existing functionality

Proposed functionality

As I discovered in https://github.com/netbox-community/netbox/issues/14708, having ENABLE_LOCALIZATION set to False (default), translation features are not applied, but the user still has access to the Language field in User Preferences..

I would like to suggest the following changes:

  • In /user/preferences/ when ENABLE_LOCALIZATION is set to false, have one of the following:

    • Hide the language field
    • Have it grayed-out.
    • Have a mention that this field is not applied until Localization is enabled by an admin.

  • Have the available language list display both the language names in current language and in native name. This would allow a user to change it to something he would know (as an example, Cyrillic alphabet is not a given for everyone).
    As an example:
    image image

  • Allow the user to change language from login page (same as the light/dark option already available). Could be by a small drop-down in the footer showing the language list as above (or only the ISO 639 abbreviations for a minimalist approach).

  • Allow the Admin to choose which languages are available to the users (either using configuration.py or UI (/core/config/).

  • Allow the admin to have Login, Footer and Maintenance banners showing in user's language.

Use case

This would enhance user experience and make that great new feature even more enjoyable.

Database changes

none AFAIK

External dependencies

none AFAIK

Originally created by @AnythingOverIP on GitHub (Jan 5, 2024). ### NetBox version v3.7.0 ### Feature type Change to existing functionality ### Proposed functionality As I discovered in https://github.com/netbox-community/netbox/issues/14708, having `ENABLE_LOCALIZATION` set to False (default), translation features are not applied, but the user still has access to the Language field in User Preferences.. I would like to suggest the following changes: - In /user/preferences/ when `ENABLE_LOCALIZATION` is set to false, have one of the following: * Hide the language field * Have it grayed-out. * Have a mention that this field is not applied until Localization is enabled by an admin. - Have the available language list display both the language names in current language and in native name. This would allow a user to change it to something he would know (as an example, Cyrillic alphabet is not a given for everyone). As an example: ![image](https://github.com/netbox-community/netbox/assets/25624251/4a933bcb-7bcf-4a1d-80e4-fb2fb93ce278) ![image](https://github.com/netbox-community/netbox/assets/25624251/4653ba29-91bd-4e69-8044-60a1fcde9d52) - Allow the user to change language from login page (same as the light/dark option already available). Could be by a small drop-down in the footer showing the language list as above (or only the ISO 639 abbreviations for a minimalist approach). - Allow the Admin to choose which languages are available to the users (either using `configuration.py` or UI (/core/config/). - Allow the admin to have Login, Footer and Maintenance banners showing in user's language. ### Use case This would enhance user experience and make that great new feature even more enjoyable. ### Database changes none AFAIK ### External dependencies none AFAIK
adam added the type: featurestatus: needs ownerpending closurecomplexity: low labels 2025-12-29 20:44:49 +01:00
adam closed this issue 2025-12-29 20:44:49 +01:00
adam commented 2025-12-29 20:44:49 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Apr 3, 2024):

Good suggestion. Thanks for the specificity and for the mocked-up screenshots in particular.

@jeffgdotorg commented on GitHub (Apr 3, 2024): Good suggestion. Thanks for the specificity and for the mocked-up screenshots in particular.
adam commented 2025-12-29 20:44:50 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 21, 2024):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 21, 2024): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:44:50 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 20, 2024):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Sep 20, 2024): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label complexity: low pending closure status: needs owner type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9050
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?