See https://www.drupal.org/project/drupal/issues/2313309
The patch in #44 there fixes the admin language for the core toolbar menu. Since this module extends the core functionality, there should also be the case when this module is enabled.
Right now, if I apply that patch and enable the admin_toolbar module, I don't see the selected admin language code (English) on a Spanish node for instance.
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | admin_toolbar_translate_admin_language-3004575-12.patch | 3.44 KB | mihaic |
Issue fork admin_toolbar-3004575
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
nitebreedComment #3
adriancidI think we need to wait until the patch arrives in the core.
Comment #4
chris matthews commentedPostponed on #2313309: Admin toolbar and contextual links should always be rendered in the admin language (if set)
Comment #5
chris matthews commentedComment #6
kiseleva.t commentedProvided patch adds usage of admin language for extra links.
Comment #7
urashima82 commentedUpdate patch for 3.1.0 version.
Comment #8
bbu23Add the AdminLanguageRender service for the static calls on LanguageManager from patch no.7.
Comment #9
mihaic commentedHere is updated patch to work with version 3.2 of this module.
Comment #10
mihaic commentedUpdate the patch for version 3.5 of the module
Comment #11
dydave commentedThe patch from #8 is for Drupal 11, see Change record:
New language.admin_language_render service
There seems to be some activity around this in related core issue.
The patches still seem to apply.
The issue summary would need to be updated.
Comment #12
mihaic commentedUpdated patch for the latest version of the module 3.6.0
Comment #14
dydave commentedCreated initial merge request MR !156 above at #13 based on latest patch at #12.
Since the Tests seem to be failing ❌, the MR was set in Draft for now, since more work would be needed to integrate with the patch required for Drupal Core.
The MR in related core issue would also require some help updating and testing.
Could we requalify this issue as Feature request?
As it shouldn't register as an existing "bug" in the module since the feature is not completely integrated with Drupal Core yet.
Any feedback, comments or suggestions would be greatly appreciated.
Thanks in advance!