Elio Bischof 74479bd085 fix(login): avoid disallowed languages with custom texts (#9094) ...

# Which Problems Are Solved

If a browsers default language is not allowed by instance restrictions,
the login still renders it if it finds any custom texts for this
language. In that case, the login tries to render all texts on all
screens in this language using custom texts, even for texts that are not
customized.

![image](https://github.com/user-attachments/assets/1038ecac-90c9-4352-b75d-e7466a639711)

![image](https://github.com/user-attachments/assets/e4cbd0fb-a60e-41c5-a404-23e6d144de6c)

![image](https://github.com/user-attachments/assets/98d8b0b9-e082-48ae-9540-66792341fe1c)

# How the Problems Are Solved

If a custom messages language is not allowed, it is not added to the
i18n library's translations bundle. The library correctly falls back to
the instances default language.

![image](https://github.com/user-attachments/assets/fadac92e-bdea-4f8c-b6c2-2aa6476b89b3)

This library method only receives messages for allowed languages

![image](https://github.com/user-attachments/assets/33081929-d3a5-4b0f-b838-7b69f88c13bc)

# Additional Context

Reported via support request

(cherry picked from commit ab6c4331df)

2025-01-06 10:46:58 +01:00

..

bundle.go

fix(middleware): init translation messages (#7778)

2024-04-16 15:46:13 +02:00

fs.go

fix(middleware): init translation messages (#7778)

2024-04-16 15:46:13 +02:00

languages.go

feat: restrict languages (#6931)

2023-12-05 11:12:01 +00:00

translator.go

fix(login): avoid disallowed languages with custom texts (#9094)

2025-01-06 10:46:58 +01:00