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.
Problem/Motivation
When an admin creates a bundle and then visits the package creation page, and there are detected packages that haven't been added to any bundle, they should see the packages and have the option of assigning them to the bundle.
However, currently, detected packages not assigned to a bundle are not shown.
Proposed resolution
Remaining tasks
User interface changes
API changes
Comment | File | Size | Author |
---|---|---|---|
#2 | features_package_assignment_into-2494777-2.patch | 4.68 KB | mpotter |
Comments
Comment #1
nedjoThis regression results from the refactoring that happened when profiles were pulled into bundles. Previously we tracked short names for features. Seemingly, when that was dropped, we lost the ability for features to be recognized independently of the the bundle to which they're attached.
For most use cases - and certainly for building for distribution - the best work flow will be to first create a bundle and then assign detected packages to that bundle. This is currently possible, but only through an awkward and counter-intuitive workflow:
The workflow should instead be:
Comment #2
mpotter CreditAttribution: mpotter commentedHere is a patch that should fix this.
Comment #3
mpotter CreditAttribution: mpotter commentedGoing ahead to commit this to get the current -dev updated to a good point for people to fully test.
Committed to 5ce8c86.