use closure to properly defer l10n initialization

[butonic]

Description

fixes translation of web ui for ldap users. backport to 9.1 requested

Related Issue

Motivation and Context

Mixed language in the UI.

How Has This Been Tested?

locally, with ldap and german, english, spanish language mix.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[mention-bot]

@butonic, thanks for your PR! By analyzing the history of the files in this pull request, we identified @PVince81, @DeepDiver1975, @Gadzy and @Xenopathic to be potential reviewers.

[butonic]

waiting for CI will then backport.

also, I don't know if I catched all occurrences of this. I certainly did not catch the ones in other apps ... how do we enforce them to defer initialization ... The problem is that $l is initialized in app.php ... way before the user preferences have been loaded.

I guess we need to log a warning when anything but a closure is used?

[DeepDiver1975]

👍

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.