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.Follow-up to #1489480: drush:features-export Ambiguous component
I still get these messages, for example for Metatags:
drush fe -y feature_article 'metatag:node:article'
Ambiguous component "node", matches node:article, node:page, node:migrate_extras_media_example, node:news
and for Panelizer:
drush fe feature_article 'panelizer_defaults:node:article:default'
Ambiguous component "node", matches node:article:default, node:news:default, node:lexicon:default
I get the components by calling drush fc.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | features-drush_fe_ambiguous_component-2490794-5.patch | 2.11 KB | gabriel.achille |
Comments
Comment #1
osopolarComment #2
osopolarIts working for the gui based export, but not for the drush command, so I guess its a features bug, not metatag or panelizers fault.
Comment #3
muriqui CreditAttribution: muriqui commentedGetting the same thing when exporting menu links:
Comment #4
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedthis is caused by https://www.drupal.org/node/1867910
Comment #5
gabriel.achille CreditAttribution: gabriel.achille at Demonz Media commentedI noticed the same thing: every time the components name as ":" in it, the drush features-export will fail with this error message.
For the record/testing purpose I've attached the revert patch of 1867910, but this is not a real solution...
Comment #6
aken.niels@gmail.comI think it's not the semicolon (:) but the dashes (-) that cause this error? Goes without saying; we are experiencing this same problem, unable to export anything with a dash in the component name, ultimately breaking multiple component exports.
Edit: for completeness-sake, here is my PoC:
Does not work
drush fe feature_name 'menu_links:main-menu:user'
Does work (note the same buildup, same amount of semicolons)
drush fe feature_name 'menu_links:navigation:filter/tips'
Edit 2: I think this issue should have higher priority, this issue has the potential to break a lot of component export systems, which is Features core business.
Edit 3: For the record; above 'revert' patch fixes our issue as well.
Comment #7
osopolarWorkaround: Use the GUI to export these components and do a drush fu feature_name after that.
Comment #8
Rob C CreditAttribution: Rob C commented"Its working for the gui based export, but not for the drush command, so I guess its a features bug, not metatag or panelizers fault."
If i try to export node: page, it will not even export it via the UI.
Tried drush, also does not work, so i can not export individual metatag:node_type's. The workaround does not work in features 2.7. What version did you guys use to test this?
Comment #9
Rob C CreditAttribution: Rob C commentedThis all isnt exported for me, via the UI/drush, same result.
node:article
node:page
file
file:image
file:video
file:audio
file:document
taxonomy_term:tags
And these work:
global
global:frontpage
global:403
global:404
node
taxonomy_term
So the global/main items work, but type-specific and files are broken?
Comment #10
mpotter CreditAttribution: mpotter commentedMarking as fixed because of patch in #1867910: Undefined index: dependencies features.drush.inc:252. Re-open if this is still an issue after using that patch (or using v2.10 or later).