Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By damienmckenna on
Change record status:
Draft (View all draft change records)
Project:
Introduced in branch:
7.x-1.x
Issue links:
Description:
Prior to version [..], any Metatag string that was translated through the Internationalization module had a verbose "context" value assigned. This resulted in meta tags needing to be translated individually for every page they were visible, so e.g. a default page description would have to be translated for every page it was displayed, even if the source string was identical.
Starting with version [..], Metatag has been changed so that each translation string now has a shorter context - "metatag:METATAGNAME", e.g. "metatag:title", "metatag:og:title", "metatag:twitter:image", etc.
| Old context | New context |
|---|---|
| metatag:global:front_page:title | metatag:title |
| metatag:global:front_page:description | metatag:description |
| metatag:global:front_page:og:title | metatag:og:title |
| metatag:global:front_page:og:description | metatag:og:description |
| metatag:node:4:title | metatag:title |
| metatag:node:4:description | metatag:description |
| metatag:node:4:og:title | metatag:og:title |
| metatag:node:4:og:description | metatag:og:description |
As a result of this change, all translation meta tags will need to be re-translated.
Note: this does not affect the translated strings themselves, only how they are selected for use on each page.
Impacts:
Site builders, administrators, editors
