Closed (fixed)
Project:
Metatag
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
21 Sep 2011 at 12:23 UTC
Updated:
16 Sep 2014 at 20:10 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dave reidHrm, interesting. I guess it makes sense that if there is no valid configuration for that entity (aside from global) that you should not be able to edit any metatags for that item as well. I wonder if there is a use case to enable meta tags for specific content but not have any default meta tags for content?
Moving to feature request.
Comment #2
dave reidComment #3
damienmckennaA better way of making this a generic feature would be to provide a way of disabling meta tags for a given entity/bundle/object. Marking this as "postponed" as it won't be a 1.0 feature, unless someone provides a patch.
Comment #4
damienmckennaComment #5
damienmckennaThere was some code in #1371968: Show/Hide Meta tags fieldset per content type that might contribute towards this goal, will look at it after 1.0 is released.
Comment #6
JvE commentedThis is the workaround module I used which should work again now that #1718594: Disabling metatags for bundles no longer works. is solved:
I'm a bit busy with project work atm but in a week or so I'd be willing to work on this if it becomes clear what approach to take.
Comment #7
JvE commentedCan this be closed in favor of #1846080: Only enable Metatag on entities that request it ?
Comment #8
damienmckenna@JvE: They're two separate issues, one is a fix of the default interaction with entities, the other is a UI feature.
Comment #9
damienmckennaClosed a duplicate: #1958992: Administrators cannot disable meta tags with the beta5 release.
That issue was gong by the assumption that if a configuration was not available for a given entity type that the fields should not be displayed. I don't know Dave's intentions, but that is not what I expect to happen, instead functionality from this issue would control it.
Comment #9.0
damienmckennaClarified the goals for this issue.
Comment #10
damienmckennaTemporary solution:
Comment #11
damienmckennaI've not tested this, but theoretically it should work. Check the README.txt for instructions.
Comment #12
damienmckennaRerolled, with a slight tweak on the note in README.txt.
Comment #13
damienmckennaCommitted, after I did some testing and verified it worked correctly.
Comment #15
user654 commented.
Comment #16
damienmckenna@pinkonomy: Go to the new settings page under admin/content/search/metatags.
Comment #17
user654 commented.
Comment #18
damienmckennaUncheck the content type you want to exclude?
That shows how to exclude the Basic Page content type and User entity entirely.
Comment #19
user654 commented.
Comment #20
damienmckennaThe settings page was added in 7.x-1.0-rc2.
Comment #21
mrpauldriver commentedGood work everyone