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

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

nedjo’s picture

This 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:

  • Generate all detected features without a bundle.
  • Create a bundle.
  • Go back and edit each detected bundle, assigning it to the bundle.

The workflow should instead be:

  • Generate a bundle.
  • Assign selected detected features to that bundle.
mpotter’s picture

Status: Active » Needs review
FileSize
4.68 KB

Here is a patch that should fix this.

mpotter’s picture

Status: Needs review » Fixed

Going ahead to commit this to get the current -dev updated to a good point for people to fully test.

Committed to 5ce8c86.

  • mpotter committed 5ce8c86 on 8.x-3.x
    Issue #2494777 by mpotter: Package assignment into new bundle broken
    

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.