In fe_nodequeue_features_export(), the code looks for any roles assigned to the queue, and will always export that role as part of the same feature as the nodequeue - even if the role has been exported elsewhere. This can cause features to conflict.

CommentFileSizeAuthor
#6 features_extra-do-not-always-export-role-2608700-6.patch1.32 KBherved
#2 features_extra-do-not-always-export-role-2608700-2-7.patch1.27 KBalexdmccabe

Comments

alexdmccabe created an issue. See original summary.

alexdmccabe’s picture

alexdmccabe
he/him
Primary language English
Location Orlando, FL, US / Seminole lands
commented
StatusFileSize
new features_extra-do-not-always-export-role-2608700-2-7.patch1.27 KB

Uploading a patch that fixes this for me.

alexdmccabe’s picture

alexdmccabe
he/him
Primary language English
Location Orlando, FL, US / Seminole lands
commented
Status: Active » Needs review

And setting to needs review.

Status: Needs review » Needs work

The last submitted patch, 2: features_extra-do-not-always-export-role-2608700-2-7.patch, failed testing.

leendertdb’s picture

leendertdb commented
Status: Needs work » Reviewed & tested by the community

Thanks for this! This has been bugging us for a while, forcing us to manually remove the automatically added role every time we rebuilded features.

It finally got on my nerves today, but luckily after some searching I came across this issue. Glad we're not the only one.

Applied the patch and works perfectly. Updating status to RTBC.

herved’s picture

herved commented
StatusFileSize
new features_extra-do-not-always-export-role-2608700-6.patch1.32 KB

Thanks for this.
This bug is still present in 7.x-1.x branch and this patch fixes the issue.
Here's a reroll that applies to the top level (for drush make) and for the current 7.x-1.x branch.