Allow dependencies of parent profiles to be uninstalled #3525
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@balsama Thanks for your contribution, your PR was merged. This will be included in the next release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Drupal core #1356276 allows for profiles to be set as a parent profile and for child profiles to inherit from parents. This allows for more than one profile to be installed on a site.
Drupal (and Drush and Drupal Console) has always made exceptions for dependencies of Profiles in that you can actually uninstall dependencies of Profiles without uninstalling the Profile itself. This patch makes the same exception for parent profiles. Or rather, adds all profiles to a list of dependents to exclude instead of just the active/last profile.
It includes a check to see if the patch has been applied to core and works around it if not.