-
-
Notifications
You must be signed in to change notification settings - Fork 413
Switching language in the settings does not immediately become active #5161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Milestone
Comments
TheWitness
added a commit
that referenced
this issue
Jan 16, 2023
Switching language in the settings only becomes active after removal of session cookie
@paulgevers, please test with the latest settings.php in the 1.2.x branch. |
TheWitness
added a commit
that referenced
this issue
Jan 19, 2023
TheWitness
added a commit
that referenced
this issue
Jan 19, 2023
@TheWitness I was finally able to check it. I'm sorry to say but with only commit 446c1d6, it doesn't seem to work for me. |
@paulgevers, could you provide a screen2gif of the UI action? |
vokoscreenNG-2023-01-19_21-04-35.webm |
Okay, I addressed a different issue, but same process. On it. |
TheWitness
added a commit
that referenced
this issue
Jan 21, 2023
This will make sure a refresh happens when any of the three values change. Should be good enough.
TheWitness
added a commit
that referenced
this issue
Jan 22, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
While debugging issue #5160 I noticed that if I switch the language in the settings.php page, they do not become active. I can active the language by clearing my session cookie.
To Reproduce
Go to '/cacti/settings.php'
Change the value under 'language' and set 'Auto Language Detection' to
Disabled
Hit the
Save
buttonSee the pop-up window appearing in the original language.
Expected behavior
Selected language becomes active immediately
Desktop (please complete the following information)
OS: Linux on Debian
bookworm
Browser: Firefox
Version: 102.6.0esr
The text was updated successfully, but these errors were encountered: