To reproduce this behavior, create a custom bundle where Views are required configuration (not optional), unlike the default bundle.
Then export a view into a feature via the UI (making sure to select your custom bundle). Notice that the view is (correctly) placed into the config/install directory. Now do the same thing, but check "allow conflicts" before exporting the feature. Notice that the view is incorrectly placed into the config/optional directory.
It seems that the problem isn't necessarily whether the checkbox is checked or not, but the act of clicking on it. I found that if the checkbox was already checked and I left it that way when exporting it, the view was exported correctly. But if I then unchecked it without reloading the page, the view was exported incorrectly.
It seems like the act of checking/unchecking that box causes Features to forget about any custom bundle settings.
Comment | File | Size | Author |
---|---|---|---|
#3 | features_bundle_lost-2790221-3.patch | 1.27 KB | mpotter |
|
Comments
Comment #2
Dane Powell CreditAttribution: Dane Powell at Acquia commentedComment #3
mpotter CreditAttribution: mpotter at Phase2 commentedReproduced this issue. Here is a patch that I think fixes this.
Comment #5
mpotter CreditAttribution: mpotter at Phase2 commentedCommitted this to e82609b so I can work on some additional issues with the Bundle setting on the Edit form.