| Summary: | Pages/Additional contents/CMS page default language link should still allow to the change language | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Pascal Uphaus <pascal.uphaus> |
| Component: | I18N/L10N | Assignee: | Bugs List <koha-bugs> |
| Status: | CLOSED INVALID | QA Contact: | Testopia <testopia> |
| Severity: | minor | ||
| Priority: | P5 - low | CC: | f.demians, victor |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Pascal Uphaus
2022-12-02 16:04:25 UTC
Got confused as well. On the rest of the Koha, when changing the language, one is redirected to the homepage. Then it's usual use the back button of the browser, and with additional content(CMS pages) it's necessary for the OPAC to have the direct URL otherwise it's not possible to find back the page. But then one triggers the language reset. I think the confusion is that the default language URL is meant to reset the language. But then if one wants to check the translation of the additional content, it's expected to use the language switches instead of the link in the additional content interface. And then when using the language switch it's expected to back to the page to check if the right language is shown and oops it's reset and the language. I don't know how the UX should be avoid this but this is at least to document the confusion that can arise, we though the translation mechanism of additional content was broken and didn't notice the two URL in the additional content interface are different. Actually the link doesn't reset the UI language, we got confused. It just the additional contents part of the page. Which made us think that the additional contents translation logic didn't work. (In reply to Victor Grousset/tuxayo from comment #2) > Actually the link doesn't reset the UI language, we got confused. It just > the additional contents part of the page. > > Which made us think that the additional contents translation logic didn't > work. So could this be closed? I can't get back to what was confusing. "default language URL" ??? "the link in the additional content interface" There doesn't seem to be such a thing related to languages. So I can't find what I was writing about ^^" Anyway, comment 2 seems to show that the UI language wasn't changing, only the CMS part of the page. So no issue. |