The report applies not only to 2.3 but to the dev builds available for past 3 days as well.
Path-based metas apparently do not get rendered into the final code, on a bilingual D7.12 site.
Ticked: copyright, description, keywords.
Default fields (meta_keywords, etc...) + custom one "field_author" (named as instructed, but this one does not appear as checkbox for ticking, why?), all not hidden, tested with various formatters.
The paths follow the pattern en/* to enable global metas per language. Paths suggested to admin by clicking the secondary tab do not work as well.
Tried to enter * alone as a path (without leading lang code), but this is not allowed (why?).
Auto settings: Global keywords do not render as well, no edit field to enter default keywords.
Isn't it a total mess-up and disaster on that little setup? :)

Comments

moniuch’s picture

moniuch commented
Category: bug » support

Changed into a support request
I managed to get the metas into the code of a particular node, however, my goal is to have global metas per language. Therefore it'd be useful to have a path expression like / or /*
Please consider for future release or advise how to handle this case.

valthebald’s picture

valthebald
Location Sofia
commented
Version: 7.x-2.3 » 7.x-2.x-dev
Category: support » feature

Bumpin version

valthebald’s picture

valthebald
Location Sofia
commented
Issue summary: View changes

text touchup

astonvictor’s picture

astonvictor commented
Issue summary: View changes
Status: Active » Closed (outdated)

D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.