Bug 54231 – Changing locale does not work for UMC backend processes in Portal

Bug 54231 - Changing locale does not work for UMC backend processes in Portal


Summary:	Changing locale does not work for UMC backend processes in Portal

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	UMC (Generic)
Version:	UCS 5.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:	UMC maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2021-12-09 15:51 CET by Dirk Wiesenthal
Modified:	2021-12-19 13:00 CET (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	1: Cosmetic issue or missing function but workaround exists
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.023
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dirk Wiesenthal

2021-12-09 15:51:50 CET

The new portal can change the locale without recreating a session.

But this means that no UMC process knows of a locale change in the frontend.

This results in the frontend being in the correct locale, but responses from the backend are in the old locale - if the module has been opened before.

Logging out and logging in is the only way of correcting it (or a UMC module timeout).

Comment 1 Florian Best

2021-12-13 12:05:22 CET

(In reply to Dirk Wiesenthal from comment #0)
> The new portal can change the locale without recreating a session.
yep

> But this means that no UMC process knows of a locale change in the frontend.
hm - because it is not communicated?!

> This results in the frontend being in the correct locale, but responses from
> the backend are in the old locale - if the module has been opened before.
If you change the Accept-Language header newly opened modules should use the new locale.
For already opened module this should also happen but doesn't work in UDM e.g. where the strings are translated at import time.
For this one could use `UMCP GET newsession` - which is e.g. used after an AppCenter app installation.

> Logging out and logging in is the only way of correcting it (or a UMC module
> timeout).
As above, there might be other ways than logging out.