Hi,

Would it be possible to use this module to get through panels different meta tags on different domains please?

Thanks a lot in advance for your reply!
Greetings, Martijn

Comments

Miszel’s picture

I suppose so but it is difficult to say how without knowing more details about your set up. I guess, you would need to be able to trigger context on a specific domain. Here are some modules that you could look at and possibly use one of them in conjunction with context metatags:

http://drupal.org/project/context_domain
http://drupal.org/project/domaincontext

Summit’s picture

Hi My setup is the following.
I have one codebase and more than one domain running through domain_access.
What I would like is for starters to get different meta tags (title, description, keywords) on the different homepages.
The homepages are panels. The homepages for both domains are the same panels, but the content of the panels is based on views which have nodes with filter for this domain.

Is this enough setup information please? Will this module help with setting the meta tags right? Does it use tokens, so I can variabelize my information?

Thanks a lot for your quick reply!
Greetings, Martijn

Miszel’s picture

Yes, context metadata supports tokens. I reckon you will need two conditions to trigger the right context - the domain and the path () Try to use the domain context module to trigger a context on a specific domain. Then use the context matadata module to add the meta tags. I have never tried but it should work. Please let us know if it works for you.

Summit’s picture

Hi,
I am trying to build this context.
1) I made a context with domain context which says (Set this context when viewing a node depending on its domains).. I do not know which reaction to set?
2) I do not see the context meta data anywhere in the conditions list?

Can you help please? It would be great if we got this working. Until now there is no working solution to get meta tags on different domains!

Greetings, Martijn

Miszel’s picture

I haven't done it before but I think that you should set two context conditions:

1) A domain condition that you set to the domain you choose (the condition that you say you are trying)
2) A path condition set to <front>

Those two conditions will create a context that will be triggered on the front page of your chosen domain. Now you need to set up a reaction which will set your meta tags on the targetted front page. This is where you use the context metadata module. Choose "Meta Data" from the reaction dropdown.

Please note that Context Metadata does not define any conditions. It only provides a reaction that sets the meta data when context is triggered.

Miszel’s picture

BTW, please use the dev version of the Context Metadata module.

Summit’s picture

Hi,
I build a context with both conditions 1) and 2) , see underneath the export.
But I do not see the "Meta Data" in the reaction dropdown....I use the latest .dev of the module.

Export Context:

$context = new stdClass();
$context->disabled = FALSE; /* Edit this to true to make a default context disabled initially */
$context->api_version = 3;
$context->name = 'domain_ais';
$context->description = 'if domain is AIS and path is front then..';
$context->tag = '';
$context->conditions = array(
  'domain' => array(
    'values' => array(
      1 => 1,
    ),
  ),
  'path' => array(
    'values' => array(
      '<front>' => '<front>',
    ),
  ),
);
$context->reactions = array();
$context->condition_mode = 1;

// Translatables
// Included for use with string extractors like potx.
t('if domain is AIS and path is front then..');

Thanks again for your quick reaction.

greetings, Martijn

Miszel’s picture

Clear all cache. Then you should see Meta Data in the dropdown.

Now you can use 7.x-1.2 version.

Miszel’s picture

Category: feature » support
Summit’s picture

Hi, you where right about the cache, thanks!
It is working now, with tokens!

Greetings and thanks for your help with this!
Martijn

Miszel’s picture

Status: Active » Closed (fixed)

Cool, no problem. I am closing this issue.