Bug 888504
Summary: | Horizon: language settings are not saved | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Yaniv Kaul <ykaul> |
Component: | python-django-horizon | Assignee: | Matthias Runge <mrunge> |
Status: | CLOSED ERRATA | QA Contact: | Nir Magnezi <nmagnezi> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.0 (Folsom) | CC: | jkt, jpichon, mlopes, mrunge |
Target Milestone: | beta | Keywords: | i18n, Triaged |
Target Release: | 4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python-django-horizon-2013.2-4.el6ost | Doc Type: | Bug Fix |
Doc Text: |
Prior to this update, the Dashboard cookie containing user preferences would not persist after logout. Consequently, user preferences such as language needed to be reconfigured.
With this fix, the Dashboard cookie persists and user preferences are retained after logout.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-12-19 23:53:36 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Yaniv Kaul
2012-12-18 19:35:22 UTC
Horizon doesn't use a database and doesn't persist any information. User settings such as the language and the timezone are stored in the cookie: if the user logs out then the cookie is lost and the information would need to be set again. I think there are discussions about perhaps storing that kind of user-information in Keystone in the future, but I don't think it's going to happen soon. Verified NVR: python-django-horizon-2013.2-5.el6ost.noarch Verification Steps: =================== 1. Changed Language, Timezone and Items Per Page in Settings page. 2. Logged out 3. Logged in Result: ======= All settings were saved. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2013-1859.html |