Right now the boxes are automatically exported when another component is exported that uses them.
This is problematic for example when exporting a context which includes a box but the box itself shouldn't be part of the feature. so that the feature is not overridden when the box content changes.

Removing boxes_features_pipe_block_alter solves this, yet allows the boxes to be exported when one wishes to do so.

CommentFileSizeAuthor
#1 optional_export-2079447-1.patch627 bytesbircher
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

bircher’s picture

bircher
Location 🇨🇿
CreditAttribution: bircher commented
Status: Active » Needs review
FileSize
optional_export-2079447-1.patch627 bytes

And attached the patch for 7.x-1.x-dev

joachim’s picture

joachim CreditAttribution: joachim commented
Status: Needs review » Active

With Features 2.x, you can choose to not include a component that Features is trying to add automatically.

I think the UX of having boxes added automatically overrules having to unselect them if you don't want them.

bircher’s picture

bircher
Location 🇨🇿
CreditAttribution: bircher commented

That is a fair argument of course.

I just expected it to work like the other modules but I'm fine with this choice as well.

bircher’s picture

bircher
Location 🇨🇿
CreditAttribution: bircher commented
Status: Active » Closed (won't fix)