Currently features_get_component_map includes hidden modules. This is the function used by features_get_conflicts to check component conflicts. Hidden modules will show up as a conflict for non-hidden modules which can be a bit confusing.

Incoming patch which ignores hidden modules - and to prevent issues with the test module, it'll alter system info to make it unhidden when enabled for testing.

CommentFileSizeAuthor
#1 ignore_hidden_modules-2479803-1.patch1.23 KBmglaman
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mglaman’s picture

mglaman
Primary language English
Location WI, USA
CreditAttribution: mglaman at Bluehorn Digital commented
Assigned: mglaman » Unassigned
Status: Active » Needs review
FileSize
ignore_hidden_modules-2479803-1.patch1.23 KB

Patch attached.

mpotter’s picture

mpotter CreditAttribution: mpotter commented
Status: Needs review » Needs work

But I think this is wrong. If you have a hidden module that contains the same config as some other Feature, then it *should* show as a conflict. What matters is if the module is enabled or not. If the module is enabled it needs to flag a conflict regardless of if it's hidden.