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.
This has been fixed in the latest dev. Just wanted to document it.
Comment | File | Size | Author |
---|---|---|---|
#3 | eck-features-revert-bundles-1733312-3.patch | 520 bytes | joelstein |
#1 | duplicate_bundles-1733312-1.patch | 703 bytes | derhasi |
Comments
Comment #1
derhasi CreditAttribution: derhasi commented@fmuzzel, great you worked on this.
For referencing a patch file for other users: it lays here.
But there's still a little work to do. The problem is, when you want to overwrite the existing bundle with the settings from the feature, this currently is not possible, as the ->save() currently denies to write the object. So for the features part, we first have to load the existing Bundle, and then populate the properties.
This should be fixed with the attached additional patch for 7.x-2.x-dev.
Comment #2
fmizzell CreditAttribution: fmizzell commentedComment #3
joelstein CreditAttribution: joelstein commentedThis needs to be re-opened, because it's currently impossible to revert a bundle in Features.
To see this in action, do the following:
I did a lot of troubleshooting, and for the life of me I don't understand what is causing this. All I know is that during the feature rebuild, when it looks up the bundle by machine name, it doesn't see the bundle's ID. I did lots of troubleshooting, and for some reason the cached bundle ID gets lost before we get to this function, thus telling ECK that it's a "new" bundle, which wrecks havoc during the save (aka, it won't save).
This simple patch does the trick by resetting the cached bundles before reverting.
Comment #4
joelstein CreditAttribution: joelstein commentedSorry for re-opening a really old issue. I created a new one at #2500341: Cannot revert bundle in Features.