Show/Hide Meta tags fieldset per content type

admin/config/search/metatags/config/add

I agree, I also think the ability to customize the default tokens for the meta description & tags by content type would be helpful. For example I have a specific "news" content type that has a separate field for the node summary, and I'm not utilizing the default Body summary field. So I'd like to switch the token *only that content type* from [node:summary] to [node:field_front_page_teaser].
It would make sense to have these settings under Structure > Content Type > Name-of-Content-Type > Manage Fields > Meta Tags /Edit
Thank you for your work!!

subscribe

I'm using the Entity Registrations module for event signup. Registrations are fieldable entities and meta tags are undesired visible in form. So it is necessary to hide those.

This might be a duplicate of http://drupal.org/node/1429100

like in #7, I am using an entity and do not want the meta tag field set to show up.
this will also help reduce the page weight.
I am using the feedback module.

I went to admin/config/search/metatags
I disabled all of them.
the metatag field still showed up in the feedback box.

Why is that?

The settings at admin/config/search/metatags allow you to set custom settings for the meta tags on different entities, but disabling the configuration simply disables the custom settings; it doesn't disable meta tags on those entities.

so there is no "global disable"?

I haven't looked at the code to confirm, but I do not believe it can be completely disabled for any particular entity/bundle type.

See here for a fix to the feedback problem, and a start at an explanation fo rhow entities can choose not to have metatags at all.
http://drupal.org/node/1543900#comment-6130492

However, it is a fair request that metatag should allow this option to be flagged from the metatag UI.

Yes. There are content types or entities that need no meta data associated to them. I would like to disable them on a bundle basis too.

Subscribe

Having same issue.

How about modifying metatag_entity_supports_metatags() to check if any configuration is actually enabled for the current bundle.

For example, if you have an Article node bundle you could check if there are settings for that specific bundle, if not for Node (that are enabled) and if not you check if Global is enabled. Does that sound like a valid approach and would that function the place to do it?

A first version.

If there is no enabled config for the current entity:bundle just return false. Obviously this still needs some work to integrate cleanly but this works for node bundles.

An alternative would be to just add a metatag on/of checkbox on each bundle's settings form.

Added a little break to stop the foreach when it's no longer needed.

Sorry for the spam, but yet another alternative would be that if a specific configuration for a entity/bundle combination is added but disabled that the form is not shown. That would leave the possibility to leave the node configuration enabled and just disable the metatag form for one content type.

#1718594: Disabling metatags for bundles no longer works. marked as dupe of this one.

Marking this as a duplicate of #1281770: Disable metatags by default on all entitity types, enable it only on needed and popular types - nodes, terms

Reopening.

@JvE: that issue is for controlling the meta tags per entity type, this is to control it per node entity bundle, which is not the same thing.

Anyway, this seems to be fixed in the latest alpha. When you disable Global and Node and only leave per bundle settings the metatag fields only show up for those bundles.

Yes, this issue was solved by #1281770: Disable metatags by default on all entitity types, enable it only on needed and popular types - nodes, terms which was about more than just types but included bundles as well.

Lets continue the discussion of disabling the output of specific meta tags in #1286270: Option to disable meta tags per entity/bundle/object.

Updated issue summary.

An alternate approach may be to use the form #after_build property.

$form['#after_build'][] = '_custom_afterbuild_callback';
function _custom_afterbuild_callback($form, &$form_state) {
  $form['metatags']['#access'] = FALSE;
}