I have a feature that is capturing global metatag information. I have disabled global:403, global:404, global:front page, taxonomy term and user. Node specific metatags are captured with features dealing with specific node types.

When I move the feature to production disabled metatags are not disabling and the feature is listed as overriden. Other changes are propagating into production these four strings are those that don't.

A portion of the diff is:

Legend:
Code: drush features-revert will remove the overrides.
Overrides: drush features-update will update the exported feature with the displayed overrides

Component type: metatag
),
),
< 'disabled' => TRUE,
'instance' => 'global:403',
),
),
),
< 'disabled' => TRUE,
'instance' => 'global:404',
),
),
),
< 'disabled' => TRUE,
'instance' => 'global:frontpage',
),
),
),
< 'disabled' => TRUE,
'instance' => 'taxonomy_term',
),
),
),
< 'disabled' => TRUE,
'instance' => 'user',
),
)

Thank you

CommentFileSizeAuthor
#7 metatag-features_revert_disabled-2276855-7.patch606 bytesben.kyriakou
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

letrotteur’s picture

letrotteur CreditAttribution: letrotteur commented

Can't seem to be able to disable global:frontpage tru features either. Is this suppose to be possible?

pianomansam’s picture

pianomansam CreditAttribution: pianomansam commented

Deleted

pianomansam’s picture

pianomansam CreditAttribution: pianomansam commented
Version: 7.x-1.0-beta9 » 7.x-1.4

On further inspection, this does not appear to be working for me, even in 7.x-1.4. In my instance, I attempted to disable the Global Front Page metatag setting and export it to features.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna commented
Version: 7.x-1.4 » 7.x-1.x-dev
Component: Integration with other module » Features integration
DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna commented
Related issues: +#2462117: Add option to disable default configurations

I've just committed #2462117: Add option to disable default configurations which allows the included default configuration to be disabled. The intended workflow is that you'd customize all of the default configurations, disable the included default configurations, and then it'd only use the values you'd created, which should work just fine with Features. Please give it a try and let me know if it resolves these problems. Thanks.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna commented
Status: Active » Postponed

Marking this as 'postponed' until someone can get back to me as to whether the desired workflow is currently possible.

ben.kyriakou’s picture

ben.kyriakou CreditAttribution: ben.kyriakou at Cogapp commented
FileSize
metatag-features_revert_disabled-2276855-7.patch606 bytes

The above patch didn't solve this issue for me - it appears that the way Features reverts the config will never touch the state of the config, as this is set via ctools (into the default_metatag_config variable) rather than in the metatag_config table. I had success with the attached patch, which simply does what the enable/disable buttons do on the metatag page.

ben.kyriakou’s picture

ben.kyriakou CreditAttribution: ben.kyriakou at Cogapp commented
Status: Postponed » Needs review

Moving to 'Needs Review' to kick off testing.

solenity’s picture

solenity CreditAttribution: solenity commented

The patch in #7 works for me. It fixes the issue with features metatag configurations not applying the enabled/disabled state.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented
Status: Needs review » Fixed
Parent issue: » #2699045: Plan for Metatag 7.x-1.15 release

Committed. Thanks.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.