Title works only for Front Page and Global

I have another problem with title.
I have ampersand (&) in my site title which is displaying as & on all pages except front page.

@Vlad See #1284684: Special characters double encoded in page titles.

same issue. sub.

Mmm I have the opposite. I have my front page set to a specific node, so it just looks at the node settings rather than the front page settings. This is ok, but I think the UI should make it clear that the front page settings are not being used because the front page is a node.

I had forgotten that I'm doing the same thing. My content settings are not affecting the basic page that I have set as my front page. Good point.

same problem, i have tried to disable global, but that don't have effect (then just dissapear all meta tags)

when global is turned on, then same settings from global is on all pages (nodes, taxonomy)

The same problem.. i have only Front Page title and meta tags. Even when add default meta tags for Content types...

I've found a similar problem on meta description. In my case the meta description loads the value from a field using a token. The field contains an apostrophe '.

The HTML code is:
'

And the meta description printed by meta tag module is:
'

Example:

• meta description field value: I'm a meta description.
• rendered meta description: I'm a meta description.
• expected meta description: I'm a meta description.

Moreover I've a question: if the meta description value contains an "&" or another special HTML char, what should be printed on the meta description?

Subscribe

Please use separate issues to talk about special characters.

To recenter on titles, I have the same issue on alpha3 and dev versions.
I tried to dig but this module is a bit complicated to understand :/

This issue seems to come from two points (did not find the real one) :
- global configuration is always loaded at page build
- specific configuration is never rendered and when I try to force it, page rendering comes after so global configuration overrides specific one

Please, can somebody try to fix this ? It made my brain liquefy :/

Please don't mark this as critical. Likely if your node, user, or term pages are not rendering it means your template is not actually calling render($page['content']) or render($node['content']) like it should be.

Our graphic designers enjoy exploding the render process in their templates so my page tpl was good but the custom node tpl was not !
I took a day trying to understand where was the bug and one more time, it was human...

Sorry :/

Same situation version 7.x-1.0-alpha4.

Subscribe

I had this issue.
I found out that it was because I was using the DS(display suit) module.

You can fix this by copying the relative template file form path/to/ds/layouts to your theme folder and adding render($content['metatags']); to the top of the template file.

This needs to be fixed for the initial stable release.

I think that metatag module should expose the metatag field in the display settings page. That way it will be more compatible with other modules. e.g. DS

Thanks for the tips, With render($content['metatags']) in the node--[node-type].tpl, the meta appears

See #1284852: Make Metatag work OOTB with Display Suite

Well, can you explain why it is a duplicate?

I don't use Display Suite and I experience the exact same behavior.

If there's a solution, can you put it in the documentation maybe?

metatags_page_build() seems to be overriding the specific meta tags with the global ones. Surely that wasn't intended. Specifically, I'm having problems with the title tag.

A simple fix of giving the global tags a #weight of -1 seems to fix it.

Duplicate of #1732538: Page title pattern ignored.

Patched

@Island Usurper Are you saying there's a configuration setting somewhere to set the weight or are you saying this needs to be done as a patch to form elements or something? If a patch, could you please supply it? If simple re-prioritization of weights works, this seems like an overall more flexible and robust solution than the array_unshift solution proposed by iwhitcomb in #23. But without more info, I'm applying #23 for now.

[Edit: patch failed against recommended release. Downloaded 7.x-1.x-dev and appears to be working without the patch now. Considered fixed?]