-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
If browser not set to a locale with strings, templated text appears #8884
Comments
@adpavlov try:
|
Sorry, not sure I know where to issue those commands. I'm using docker image from dockerhub, not building it myself. |
Do you see any errors in the browser console on page load? (Cmd + Opt + J, I believe) |
nothing except insecure protocol warning.
|
We weren't able to reproduce this using the default install settings and mac os 10.15.7: We'll try and find a box with macos 11+ and double-check. That said, have you made any kind of change to the installer, configs, deployment, etc. that might help us reproduce this? |
No, the only changes are replaced awx zip file and container itself |
Hmmm.. Are you referring to the downloadable .zip release from github? What version did you upgrade from? Did the version you're upgrading from have any installer changes? What steps / shell commands did you run for the upgrade. |
yes, just replaced zip and docker tar.gz from which I import from 15.0.1 to 16.0.0. This is the flow that I do from like version 8 I believe.
|
Running on Ubuntu 20.04.1 LTS in docker container. Upgraded using: Also settings page is not working correctly: Applications and Credentials Types pages have also problems: |
This is starting to look like upgrades are a factor. Can you post logs from the browser network tab? Which browser are you using? |
Have you modified the nginx config any? That'll help narrow this down. |
Also, which installation method? (docker or k8s)? |
as for me I tried Safari, Firefox, Edge. |
Dont know if its worth to metion: I am logging in via LDAP. |
This is my inventory file for installation. |
Thanks for the info, everyone. So far, the common factor between all of these occurrences seems to be the docker compose installation method - this helps us know where to look first. |
is there any way to get one's browser to do english only for one url, and one's "normal" language for anything else? |
wouldn't the easiest / most logical solution be just to fall back to english if the browser asks for a locale without strings? |
Yes - In previous versions, the ui would default to a locale with strings (e.g: Currently, the ui always tries to use the browser's preferred locale, even if there aren't any translation strings available for that locale in the catalog. This is problematic because if there aren't any strings available, you'll just see the raw javascript variables. To address this bug, we'll update the client so that it retains the behavior from previous versions. |
👋 Hello, everyone. Thanks for all of the helpful information you provided. We've created a patch for this bug and it will be included in the next AWX release. |
i would like to say at this point that I find the new UI much more pleasing, especially on a phone or similar. |
To test: |
Coverage added |
Edit: My problem was that I needed to run I'm currently seeing this issue on 17.0.1. My browser is set to English. The fix from the merge above appears in this version of the code. When I run the UI in development mode via For some transparency, I'm building my own production bundle of the UI because I need to customize it. Once built, I copy the UI build into a Docker image based on |
👋🏼 Hi, I am having the described issue on AWX v16, and wanted to ask whether there are plans to backport this patch. I am seeing the issue on an Ubuntu 22.04 using Gnome with Chrome Version 106.0.5249.119 (Official Build) (64-bit) and English locale. Firefox and other browsers work fine. |
ISSUE TYPE
SUMMARY
ENVIRONMENT
STEPS TO REPRODUCE
Upgrade AWX to 16.0.0
EXPECTED RESULTS
Normal UI
ACTUAL RESULTS
Some elements are not decoded properly
ADDITIONAL INFORMATION
The text was updated successfully, but these errors were encountered: