We have a web project where we use Views in page mode to build fixed landing pages. Since the views module does not come with any meta tag support, and the general Views-Options of the Meta Tags module can not deal with individual displays, but only whole views, we wanted to use the context module and define meta tags for specific paths.

When this did not work as intended, I tried to first reset and then deactivate the global settings for views meta tags in Meta Tags. Only when I completely deactivated them was the context module able to take precedence and set the meta tags correctly. Else, the views still showed what set in the views / global meta tag settings.

We do not rely on global view meta tags for our project, thus having to deactivate this part is not a problem. But if we were, we would be pretty much screwed at this point :)

Comments

DamienMcKenna’s picture

Version: 7.x-1.0-beta9 » 7.x-1.x-dev

It sounds like this is a symptom of the fact there isn't a clear hierarchy between the submodules - one can overwrite the values of another.

marcelovani’s picture

I was wondering if this issue is the same as https://www.drupal.org/node/2361343#comment-10619428