Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
Drupal 9.4.0 stable was released on 15 Jun 2022 by: xjm
https://www.drupal.org/project/drupal/releases/9.4.0
Drupal 9.4.1 stable was released on 21 Jun by: xjm
https://www.drupal.org/project/drupal/releases/9.4.1
Drupal 9.4.2 stable was released on 7 Jul 2022 by: xjm
https://www.drupal.org/project/drupal/releases/9.4.2
Thank you, Jess , and the Drupal core team.
Proposed resolution
Update the patch #1356276: Allow profiles to define a base/parent profile to work with Drupal 9.4.1
#3291387: Unable to add additional comment or changes to issue number 1356276 (5xx - Server Error)
#3266057: Allow profiles to define a base/parent profile [continue of #1356276]
Remaining tasks
- ✅ File an issue about this project
- ✅ Addition/Change/Update/Fix to this project
- ✅ Testing to ensure no regression
- ✅ Automated unit/functional testing coverage
- ➖ Developer Documentation support on feature change/addition
- ➖ User Guide Documentation support on feature change/addition
- ➖ Accessibility and Readability
- ✅ Code review from 1 Vardoc core team member
- ✅ Full testing and approval
- ✅ Credit contributors
- ✅ Review with the product owner
- ✅ Update Release Notes and Update Helper on new feature change/addition
- ✅ Release vardoc-4.0.5, vardoc-5.0.0-alpha5
Vardoc update type
- ✅ No Update
- ➖ Optional Update
- ➖ Forced Update
- ➖ Forced Update if Unchanged
User interface changes
- N/A
API changes
- N/A
Data model changes
- N/A
Release notes snippet
- Issue #3290900: Updated the Allow profiles to define a base/parent profile patch to work with Drupal 9.4.*
Comments
Comment #8
rajab natshahComment #9
rajab natshahComment #10
rajab natshahComment #11
rajab natshahComment #12
rajab natshah❌ Automated unit/functional testing coverage
Comment #13
prabhu.j commentedProposed resolution
Modify the module load system to take into account base install profiles.
Modify the install profile system to run parent installer(s) in the correct order.
One proposed solution was to simply use modules instead of profile inheritance. This was discussed at length and the prevailing attitude was that the functionality for profile inheritance has valuable use cases that cannot be solved by modules alone.
An early resolution was to include a tag to exclude dependencies and themes. In an effort to clearly define focus for this patch, this functionality was removed from this patch. The use case for excluded_dependencies and excluded_themes is still very much valid, so this feature request has been given its own issue.
Comment #14
rajab natshah#1356276: Allow profiles to define a base/parent profile
#3291387: Unable to add additional comment or changes to issue number 1356276 (5xx - Server Error)
#3266057: Allow profiles to define a base/parent profile [continue of #1356276]
Needs work and more testing
Comment #15
rajab natshahPlanning to depart all needed classes, and functions from the base profile to be used in the sub-profiles without the need for the patch.
like:
Comment #16
rajab natshahComment #17
rajab natshahComment #18
rajab natshahComment #19
rajab natshah#3291387: Unable to add additional comment or changes to issue number 1356276 (5xx - Server Error)
#3266057: Allow profiles to define a base/parent profile [continue of #1356276]
Comment #20
rajab natshahComment #21
rajab natshahComment #22
rajab natshahComment #23
rajab natshahComment #24
rajab natshahComment #25
rajab natshahComment #26
rajab natshah✅ Released vardoc-4.0.5
Comment #27
rajab natshah✅ Released vardoc-5.0.0-alpha5
Comment #28
rajab natshah