Background
SettingsWebhooksPage already pulls its heading from i18n (features.adminForm.settings.webhooks.title), but WebhooksErrorMsg still hardcodes English. Raised on #9524 by @kevin9foong, split out as a follow-up by @LoneRifle.
Scope is WebhooksErrorMsg only: per @LoneRifle the sibling WebhooksUnsupportedMsg is now a historical artifact (webhooks are fully supported across storage mode and MRF), so it's intentionally left out.
What to do
Move the hardcoded copy in WebhooksErrorMsg.tsx to the existing webhooks i18n files, matching how the title already works:
- "Couldn't load webhook settings", the body sentence, "Try again" / "Trying again…"
Keys live in apps/frontend/src/i18n/locales/features/admin-form/settings/webhooks/ (index.ts for the type, en-sg.ts for the English values). English values only — no ms/ta/zh translation needed (these feature folders ship English only).
Done when
Follow-up to #9512 / #9524.
Background
SettingsWebhooksPagealready pulls its heading from i18n (features.adminForm.settings.webhooks.title), butWebhooksErrorMsgstill hardcodes English. Raised on #9524 by @kevin9foong, split out as a follow-up by @LoneRifle.Scope is
WebhooksErrorMsgonly: per @LoneRifle the siblingWebhooksUnsupportedMsgis now a historical artifact (webhooks are fully supported across storage mode and MRF), so it's intentionally left out.What to do
Move the hardcoded copy in
WebhooksErrorMsg.tsxto the existing webhooks i18n files, matching how the title already works:Keys live in
apps/frontend/src/i18n/locales/features/admin-form/settings/webhooks/(index.tsfor the type,en-sg.tsfor the English values). English values only — no ms/ta/zh translation needed (these feature folders ship English only).Done when
WebhooksErrorMsgusesuseTranslation; no hardcoded user-facing strings leftFollow-up to #9512 / #9524.