Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
the global title settings were not available to add to a feature, however I was able to add the data to the feature manually.
This needs to be fixed but here is my workaround:
- Generate the feature
- untar feautre
- Open feature.info file in yourr fav text editor
- add the bellow line to the file:
features[metatag_config][] = "global"
- update the feature via drush fu FEATURE_NAME
- It's there
Comments
Comment #1
sanguis CreditAttribution: sanguis commentedIt should be pointed out that there is no way to deploy these changes from the feature even though they are in it.
Comment #2
Dave ReidDid you actually modify the global meta tag configuration? By default you shouldn't be able to export it as it's already exported within the metatag module.
Comment #3
sanguis CreditAttribution: sanguis commentedI did modify it, that's why I wanted to export it
Comment #4
Dave ReidWhat I'm saying is that the global configuration is already exported if you are using the module. You don't need to re-export it if you haven't changed it.
Comment #5
jantoine CreditAttribution: jantoine commentedHi Dave,
I ran into a similar issue. I made a single change to the Front Page configuration so that the Front Page Title would match the Global Title. Features did not pick this change up and export it.
Comment #6
sanguis CreditAttribution: sanguis commentedHi dave,
What I am saying is I have changed it. so I do need the ability to export it.
Comment #7
mstef CreditAttribution: mstef commented+1
Comment #8
slashrsm CreditAttribution: slashrsm commented+1
I agree there should be the way to export changed pre-configured configurations. It is great to have some default configuration, but is nonsese to assume that nobody will change it.
Switching priority to normal, as this bug causes a lot of problems with code-driven workflows.
Comment #9
Chaulky CreditAttribution: Chaulky commentedI ran into the same thing. I did notice though that you can at least capture whether the default configurations are enabled or not in a feature using the default_metatag_config variable. This through me at first because I was looking for a variable starting with "metatag"
Comment #10
Chaulky CreditAttribution: Chaulky commentedAlso, based on http://drupal.org/node/1264340, looks like for now you could use
hook_metatag_config_default_alter()
to edit the default configurations in a Features module.Comment #11
Ivan Zugec CreditAttribution: Ivan Zugec commentedHere is how I exported changes to the node default:
Comment #12
mstef CreditAttribution: mstef commentedWhy don't we just have the module insert the global configuration into the database, rather than have it exported? That way, features can then export it.
Comment #13
lyricnz CreditAttribution: lyricnz commentedBeing able to export customised Global configuration seems like an obvious requirement - what am I missing?
Comment #14
DamienMcKennaTag.
Comment #15
DamienMcKennaI agree 100% with the sentiments of this discussion, there needs to be a way of exporting the current configuration. Right now there is not a clean way of exporting existing ctools defaults using Features, you have to get into drupal_alter() hooks and other messy things that are out of reach for many users.
I've changed this to a feature request.
Comment #16
DamienMcKennaThis is kinda important.
Comment #17
DamienMcKennaWould this work everyone:
Comment #18
DamienMcKennaComment #19
DamienMcKennaThis has been resolved thanks to work in #1818300: Transferring settings of module metatag through features.
Comment #20
jwilson3I'm having various issues with this implementation on the latest dev snapshots and have posted a follow up issue: #1880302: metatag features integration weirdness.
Comment #20.0
jwilson3made unorderd list, ordered
Comment #21
mikemccaffrey