[current-page:title] doesn't integrate well with views

If you disable metatag module, the views title will populate the <title> tag normally.
This is because of the way metatag override the $variables['head_title'] in hook_preprocess_html().

Related to https://www.drupal.org/node/2563647

@frazac_naba: We'll update this issue when the bug is fixed.

Confirmed the bug, it affects e.g. the default front page.

Looks like I am having this issue with contextual filter title replacement. Anyone working on a patch?

@damienMcKenna - Could this be a problem in D8? I am having a very similar problem where we use a token replacement for the title {{ title }} and it gets replaced correctly on the Drupal Views Preview output. However, on the views page in the tag (browser tab) you see {{ title }} | Site name.

https://www.drupal.org/node/2101301#comment-11741180

@Deraynger: Yes, it'll be fixed eventually, how fast depends upon whether someone puts together a patch for this or if I have to do it. The other issues are not directly related to this, one is about adding the meta tag fields to the Views UI, the other is a problem with the D7 module which works quite differently to the D8 module.

I figured out a temporary work-around for this issue by implementing the hook_preprocess_html() function in the .theme file of the theme that I'm using.

When you override a View Page title via Contextual Filter, the title is stored in $variables['page']['#title']

In my case:
- I have a View Page with a path that has 4 arguments (i.e. /foo/bar/profile/%)

- The Contextual Filter I’m using is the title of a node

- I want the title of my View Page to be: "node-title" | "site-name"

- My contextual filter is the 4th argument in the path of my View Page

- The path /foo/bar/profile does not exist and will direct you to a 404 page (If I wanted this path to lead to an actual path, this process would still work but we would just need to add another conditional inside of the function)

/**
 * Implements hook_preprocess_HOOK().
 */
function THEME-NAME_preprocess_html(array &$variables) {
  $path = \Drupal::service('path.current')->getPath();
  $path_args = explode('/', $path);
  $site_name = \Drupal::config('system.site')->get('name');

  if (isset($path_args[3]) && $path_args[3] === 'profile'){
    $variables['head_title']['title'] = $variables['page']['#title'] . ' | ' . $site_name;
  }
}

If I wanted /foo/bar/profile to lead to an actual page, I would just have to add on to the conditional, like so:

if (isset($path_args[3]) && isset($path_args[4]) && $path_args[3] === 'profile'){ 
//the code 
}

Again, this should just be a temporary work-around.

There is still no working decision?

Seems to me this is still an issue. On my site, the page title is just the View Title even though the title in the page content is overridden with the value set in the "Contextual Filters" section of the View (the "Override Title" section of the filter). Thanks for your work, Damien and all!

I think this is an issue with the [current-page:title] token, from token module, not the metatag module itself.

The problem is that the token [current-page:title] doesn't respect the title overrides from the contextual filters, and also that it doesn't process the twigs (if you use twig it will simply output the twig code without processing it first).

I can confirm this is still an issue with the latest version of drupal and metatag module.

Main issue with patch that fixes this problem can be found here: https://www.drupal.org/project/drupal/issues/2716019

Confirming #19

#19 does not resolve the issue for me. Using a taxonomy term argument in the page title {{ arguments.term_node_taxonomy_name_depth }} results in the twig not being processed when page title is re-written via the [current-page:title] token in the metatag module.

Same results as @cbrody: The core patch linked in #19 does not fix the issue for me. I ended up removing the default page title pattern from Metatag configuration, letting it fallback to the default "[current-page:title] | [site:name]" set by core. With this change, I could leave Metatag installed and controlling the other metatags but not have it affect my page title overrides from Views contextual arguments.

ya patch 19 does NOT resolve the issue for me either

Patch 19 solves an issue for me. I am generating titles with tokens from contexual filters. Before they were just twigs, now they works nicely. Thanks!

The patch from #19 didn't seem to improve anything for me. Removing the global Page Title pattern did improve the title tag for me, but I am still having an issue with breadcrumbs.

I came across this problem too when using the metatag module on a views page.
I am altering a view page title in a HOOK_views_post_render with $view->setTitle();

Without the metatag module the page title and tag work as expected (both what I set with $view->setTitle()).

With metatag module on and the "title" meta set to "[current-page:title] | [site:name]", the tag does not have what I would expect for [current-page:title] , it is blank.
Weirdly, the first time I load the page after a cache clear, it seems to work ok, subsequent page loads do not (so something to do with caching?).

#19 was no help in my situation.

EDIT:
It seems line 762 of token.token.inc
$title = \Drupal::service('title_resolver')->getTitle($request, $route);
gets null on views pages, at least in my case

Turns out I could work around my situation by adding [view:title] as the title metatag on the view itself.

I ran into this problem with a view that uses a taxonomy contextual filter {{ arguments.name }} as a title. On the suggestion from @2pha, I enabled Metatag Views to override, using [view:title] | [site:name] in Meta tags: Page Title within the view.