Support for <meta http-equiv="XYZ" content="ABC">

Meta tags always are <meta name="..." content="..." /> type of stuff, not <http-equiv name="..." content="..." />.

I think the easiest way to add something like that would be to add it to your theme, as you need to include it in any page anyway.

I may consider adding support for <http-equiv .../> type of things, and why not <link ... /> someday.

Subscribe

Hi,

I'd like to help out and try to make this request.
How can I help?

Thanks in advance!

Hello Jacques,

I think it's important to allow the value noarchive for the robots metatag is important : sometimes you just don't want to allow the robots to keep all your information. How about having the options :

all=index,follow,archive
index,nofollow,archive
index,nofollow,noarchive
index,follow,noarchive
noindex,follow,archive
noindex,nofollow,archive
noindex,follow,noarchive
none=noindex,nofollow,noarchive

I created a new file canonical.inc (source was abstract.inc)

<?php
// $Id: canonical.inc,v 1.1.4.2 2008/01/22 09:14:20 robrechtj Exp $
 
/**
 * @file
 * Support file for canonical meta tag.
 */
 
function nodewords_canonical_form($type, $value, $settings) {
  return array(
    '#type' => 'textfield',
    '#title' => t('canonical'),
    '#default_value' => $value,
    '#size' => 60,
    '#maxlength' => $settings['max_size'],
    '#description' => t('Enter a short canonical for this page.'),
  );
}

and now I want to create a new entry in the HEAD
<link rel = "canonical" ..... />
but nodewords.module creates only
<meta name ="...." content ="....." />

What do I need to make changes in code?

function nodewords_init () (
   $ tags = nodewords_get ();
   foreach ($ tags as $ name => $ content) (
     if (! empty ($ content)) (
       drupal_set_html_head ( '<meta name="'. $name .'" content="'. $content .'" />');
     )
   )
)

to show in HEAD <link rel = "canonical" ..... /> For the data entered in canonical.inc, but not for all existing

My guess is that this is waiting for the rewrite of this module that's been mentioned elsewhere.

Looks like it almost supports just defining a new_metatag.inc file and loading it up, but not quite.

Hopefully soon though. Would be some great flexibility.

Branch 6.x-1.x already supports <meta http-equiv="XYZ" content="ABC />, even though it doesn't define any of those meta tags.
It supports also <link rev="XYZ" content="ABC" />, and <link rel="XYZ" content="ABC" /> (which includes the support for the canonical URL).

Facebook share specification suggests specific meta tags for specific content types (eg: music or video).

Accordingly the ability to specify meta tags and to populate them *per node* would be a great feature.

For example, If I had a page featuring music, I could specify specific preview image, description, track title, album title and MP3 file. This content appears then in facebook neatly packaged up with an MP3 player when the page is shared.

I'm doing this with a simple hand-coded HTML site: http://www.profilemusic.com.au (want to do it properly as Drupal or Wordpress CMS sometime soon) for a client.

Hit the share link and you will see the detailed level of control over what is shared on facebook (or just go here: http://www.facebook.com/pages/Profile-Music/117669132330)

Here is sample metadata for audio example above:

<link rel="image_src" href="/music/090805/hotel-costes-12.jpg" />
<link rel="audio_src" href="/music/090819/hotel-costes-12_samples.mp3" />
<meta name="audio_title" content="Hotel Costes 12 CD samples" />
<meta name="audio_artist" content="Various Artists" />
<meta name="audio_album" content="Hotel Costes 12" />

[Edited to make the meta tags visible]

The topic of this thread is to allow meta tags in the format <meta http-equiv="XYZ" content="ABC">, which is not the same as the meta tags you are shown.

Branch 6.x-2 has never been supported, and it is not anymore developed.