Closed (won't fix)
Project:
Meta tags quick
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
13 Sep 2011 at 15:41 UTC
Updated:
1 May 2012 at 02:23 UTC
Jump to comment: Most recent file
Comments
Comment #1
valthebaldCan be easily achieved with http://drupal.org/project/field_group
Comment #2
davemybes commentedSure, but that requires manual creation of the fieldset and manual moving of the fields into it. I was thinking that when you add the fields to the various content types, it would automatically stick them into a Metatags fieldset.
Comment #3
valthebaldMaybe the right solution is to create a feature (as in http://drupal.org/project/features) that will incorporate pre-made fieldset with meta tag fields? Thus we can avoid duplicating code.
Comment #4
davemybes commentedNot sure how that would work...so I'm looking at just doing a form_alter in a custom module. But thanks for the suggestions.
Comment #5
valthebaldI have attached example feature created with features module. It contains Basic page content type with meta fields placed in vertical tab in the node edit form.
Feature can be installed just like any other module, yet is much easier to maintain/upgrade.
Comment #6
valthebaldPrevious comment contains wrong archive
Comment #7
davemybes commentedThanks, Val. I appreciate your time on this. That works fine.
Comment #9
kpv commentedHere is a module that puts keywords and description fields into a fieldset. You can easily add other fields. Just add their ids to
$field_idsarray insidemetatags_fieldset_form_alterfunction.Comment #10
valthebald#9: This will work, however, features+field group will give you more flexibility with zero coding.
Comment #11
kpv commented#10: That's right. This one is just enough for me. By the way, found a nonsignificant bug. Uploading new version )
Comment #12
doublejosh commentedThis will do it to all of them.
Comment #13
doublejosh commentedSure would be lovely as a setting in the module.
Might be nice to place them within a programatic fieldset on the content type editing form too, if the options was ticked.