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
With the changes in drupal 8.6.x the dependencies of subprofiles do not seem to be resolved correctly anymore. Configurations are imported with dependencies that are not yet installed. This especially concerns the time when the block configuration of themes is installed.
See Issue #1356276 Comment #475 ff.
Proposed resolution
Effectively, there can only be a solution if the dependency graph is built correctly, i.e. Issue #1356276 is solved.
Remaining tasks
Accurate analysis of why dependency resolutions do not work in the case of Vardoc (or other Varbase subprofiles). Possibly restructuring the features or benefits of Issue #2952888 and Issue #2914389.
Comments
Comment #2
metalboteA possible - provisional - workaround is:
to use a core.extension.yml in a profile config/install folder and set the install order static,
core.extension.yml example file:
module:
mymodulefirst: 1
mymodulesecond: 2
mymodulethird: 3
...
address: 0
core modules
...
theme:
stable: 0
classy: 0
seven: 0
mybasetheme: 0
mysitetheme: 1
profile: myprofilename
Comment #3
rajab natshahThank you Jörg for reporting and the suggested workaround,
I'm closing this issue as we committed your work on the other issues
#2994045: Fix subprofile syntax changes on Drupal 8.6
Thank you again for testing sub profile of Varbase with us.
Comment #4
rajab natshahComment #5
rajab natshahComment #6
rajab natshah