Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The region title from a "bootstrap panel" style set on a region does not seem to be translatable.
Here are my steps:
- Install a fresh install of the WxT distro
- I created a panel page in page manager, with any layout.
- I then added some panes to a region.
- I then set the region to be "Bootstrap Panel" and set the Region title.
The region title does not seem to be translatable.
Any help would be appreciated !
Comment | File | Size | Author |
---|---|---|---|
#7 | wetkit_theme-Translation_fix-2908075-7.patch | 824 bytes | joseph.olstad |
Comments
Comment #2
natew CreditAttribution: natew commentedIs this still an issue in the latest?
Comment #3
joel_osc CreditAttribution: joel_osc at OpenPlus commentedI checked this recently and yes it is still an issue.
Comment #4
natew CreditAttribution: natew as a volunteer commentedI looked into this while waiting for some CI tests. I was able to recreate and doing a little investigation it appears that this is part of wetkit_theme. If I wrap the region_title on line 87 of /wetkit_theme/modules/wetkit_bootstrapx/plugins/styles/bootstrap_styles.inc (theme function) and save the panel page. I then see the title in the translate interface, can add the translation, and see it on the page.
'region_title' => !empty($settings['region_title']) ? t($settings['region_title']) : '',
However, I am not sure if this is the right place for the translation.
Comment #5
joel_osc CreditAttribution: joel_osc at OpenPlus commentedInteresting... I can run with this issue a bit from there. It should really be translated using i18n_string instead of the t function. Nice work.
Comment #6
joseph.olstadstill need to patch this
Comment #7
joseph.olstadnew patch
Comment #8
joseph.olstadComment #9
joseph.olstad#2728871: BEF translations passing invalid localization keys to views translation.
Comment #10
joseph.olstadI ended up doing a hook form alter to fix this by adding code in a custom module
Comment #11
joseph.olstadOh ya the above patch still good