This is fallout from T300183: Reconsider skin-specific menu label item behaviour; the wrong message is picked. T301203: Update skin-specific menu labels to be more predictable, intuitive with better default values mentions that new messages will be defined with (I presume) the right text.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | BUG REPORT | None | T302672 Mirage edit button messages are wrong | ||
| Resolved | Jdlrobson | T301203 Update skin-specific menu labels to be more predictable, intuitive with better default values | |||
| Resolved | PRODUCTION ERROR | Jdlrobson | T302051 MWException: Non-string key given | ||
| Resolved | BUG REPORT | Jdlrobson | T303012 [subtask] Permissions based errors should not reuse messags intended for skin labels |
Event Timeline
Comment Actions
rMW40d041e0642d: Introduces skin- prefixed message key for nav items fixes the issue without requiring any changes to Mirage. It would appear that mirage-action-add-section is now no longer necessary, but I can't determine if the fallback it would use that was added by T303012: [subtask] Permissions based errors should not reuse messags intended for skin labels will remain.