Expand hreflang support, auto-add fields for each locale

Deja vu. I just started looking for something to provide the hreflang tag today and was hoping metatag did before I threw the code into an existing custom module on my site.

What could cause this to not work? Something obviouse I am hoping.

I been testing this yesterday and this morning and I am not getting the metatags in the HEAD of the document of nodes.

I turn dupes on as well.

This is my settings for my node. Since I do not have translations I only set the default to the source.

So I installed on a default Drupal 7 and it works. Therefore it is something in my code base not allowing it to work. If you can throw me any ideas that would be much appreciated. Once I figure out they conflict we can document it if it is something someone else may run into.

That is rather interesting. You are right that I have the "Content Translation" module shut off. Why did it not throw an error that the tocketn [node:source:url] was not available?

So the problem was the token being empty.

Is this worth documenting? I've also just found that even with the content translation module enabled that the token [node:source-url] is still empty. So for those of us just trying to get the default hreflang tag and have no other translations, you just need to use the node/page URL.

Yeah.... We got more issues. I would suggest that the default values be empty. After installing the module on my production site I found I could not publish any nodes. All threw errors saying that [node:url-en] did not exist. And what I found was the default value got put into every configuration causing everything to have a token that doesn't exist. I've had to go through all of my metatag settings and overrides and remove the language-specific value.

Installing this module on a site without localization will "freeze" all publishing of the site till you correct the default values.

So I would recommend this get removed or changed so that it tests for the existence of the language specific token first:

// Add all of the other hreflang values.
        $languages = language_list('enabled');
        if (!empty($languages[1])) {
          foreach (array_keys($languages[1]) as $langcode) {
            $config->config += array(
              'hreflang_' . $langcode => array('value' => '[node:url-' . $langcode . ']'),
            );
          }
        }

Oddly enough, even though I had not overrode the Node metatag configuration it had the wrong token in it after setting global configuration to what I need. Maybe just a fluke.

The [node:url-LANG]?

When testing this I found that it's not picking up the translated nodes within metatag_hreflang_tokens as the $node->translations wasn't displaying the translations found in the node translate tab.

I found that getting the translations using translation_node_get_translations($node->nid) returned my correct translations.

The below is what worked for my translations.

/**
 * Implements hook_tokens().
 */
function metatag_hreflang_tokens($type, $tokens, array $data = array(), array $options = array()) {
  $replacements = array();

  $sanitize = !empty($options['sanitize']);

  // Node tokens.
  if ($type == 'node' && !empty($data['node'])) {
    // Shortcuts.
    $node = $data['node'];
    $translations = translation_node_get_translations($node->nid);
    // Only generate tokens if there are multiple translations.
    if (isset($translations) && !empty($translations)) {
      $languages = language_list('enabled');
      if (!empty($languages[1]) && is_array($languages[1]) && count($languages[1]) > 1) {
        foreach ($tokens as $name => $original) {
          foreach ($translations as $langcode => $translation) {
            if ($name == 'url-' . $langcode) {
              $url_options = $options;
              $url_options['language'] = $languages[1][$langcode];
              $url_options['absolute'] = TRUE;
              $replacements[$original] = url('node/' . $translation->nid, $url_options);
            }
          }
        }
      }
    }
  }

  return $replacements;
}

I didn't originally set this website up and it has both of the modules enabled but I believe the node was translated with 'Content Translation'

Within the publishing options Multilingual support the option: 'Enabled, with translation' is selected.