Skip to content

[T3410] other fixes after the second failing test - #396

Merged
Danielgergely merged 3 commits into
18.0from
T3410-footer-i18n-followup
Sep 23, 2026
Merged

Danielgergely merged 3 commits into
18.0from
T3410-footer-i18n-followup

Conversation

@danpa32

@danpa32 danpa32 commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

The footer and the settings page were not being translated on mobile phones. Now on mobile phones:

  • The buttons text are translated
  • The settings button text are translated
  • The "change language" button in the settings is now fixed and open the languages selctor

my_compassion_native had no i18n/ directory at all despite shipping
several donor-facing strings, so they always rendered in English
regardless of the viewer's language: the mobile bottom-nav tab labels,
the profile page's buttons and subtitle, the two "new letter" push
notification strings, and the three payment-status banners shown during
the native-app payment flow.

Translated into fr_CH, de and it (the three languages MyCompassion CH
actually serves), reusing this brand's already-established wording from
my_compassion's own translations wherever an equivalent string already
existed there. Left the ~37 backend-only admin strings (field labels,
wizard forms, help text) untranslated - internal Compassion staff use the
backend in English regardless, and they were not part of what was
reported.
Used Bootstrap 4 toggle syntax (data-toggle/data-target) while the rest
of this codebase is on Bootstrap 5 (data-bs-toggle/data-bs-target), which
doesn't recognize the unprefixed attributes at all - so clicking never
wired up the collapse panel.
@greptile-apps

greptile-apps Bot commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerConfidence Score: 5/5

Safe to merge; there are no outstanding blocking issues.

Reviews (2) · Last reviewed commit: "[T3410] Register my_compassion_native fo..."

Odoo only delivers a module's JS (_t()) translations to the browser if
the module explicitly registers itself in
_get_translation_frontend_modules_name() (defaults to ['web'] only, per
core's own http_routing/models/ir_http.py). my_compassion and
theme_compassion_2025 both already do this for themselves;
my_compassion_native had no ir_http.py at all, so its 3
payment_resume.js strings would stay in English everywhere - not a
local/dev quirk, a permanent gap regardless of environment - despite
having correct .po entries.

Verified via code_translations.get_web_translations('my_compassion_native',
'fr_CH'): all 3 translated strings are now retrieved correctly through the
actual delivery mechanism.
@Danielgergely
Danielgergely merged commit 3bf01c4 into 18.0 Sep 23, 2026
2 checks passed
@Danielgergely
Danielgergely deleted the T3410-footer-i18n-followup branch September 23, 2026 09:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants