| Comment | File | Size | Author |
|---|---|---|---|
| #53 | 3143958-53-subprofile-support-10.3.x.patch | 35.88 KB | kavya n n |
| #51 | 3143958-51-subprofile-support-10.2.x.patch | 57.61 KB | sivakarthik229 |
| #48 | 3143958-subprofile-support-10.1.x.patch | 58.9 KB | ramprassad |
| #47 | 3143958-47-subprofile-support-10.0.x.patch | 58.93 KB | ramprassad |
| #46 | lightning-n3143958-12-95x.patch | 2.32 KB | damienmckenna |
Issue fork lightning-3143958
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
katherinedComment #3
katherinedComment #4
phenaproximaComment #5
phenaproximaNote to self...
This is a variant of the previous patch which modifies ModuleExtensionList so that, when it scans for extensions, it includes all profiles, not just the active one and its parents.
This is needed because when a subprofile is installed, it and all of its ancestors are added to core.extension. When the "base profile" key is removed from a subprofile -- either the active one, or any of the ones in the ancestry -- suddenly some or all the ancestors cannot be found, which breaks a lot of things (like the status report page, or the update system). Because to Drupal, these are effectively installed modules which, as far as the extension system can tell, do not exist.
So this gets around that the only way that seems truly safe: by treating all profiles as modules.
Comment #6
phenaproximaHere's yet another variant of the patch, but a bit cleaner. It's similar to what I did in #5, except that it doesn't bring all profiles into the module space; just the ancestors of the current profile (if an ancestry chain is defined), or all currently installed profiles (which Drupal treats as modules anyway). This should allow subprofiles to smoothly decouple themselves from Lightning, without Drupal suddenly freaking out about missing extensions when the
base profilekey is removed.Comment #7
phenaproximaComment #8
phenaproximaHere's a patch that modifies ConfigImportSubscriber so that the profile can be changed from Lightning to something else during a config sync. This is to make it easier to uninstall Lightning.
Comment #9
phenaproximaThis should fix additional problems that cropped up in testing. It only applies on top of the sub-profile patch in #6.
Comment #10
phenaproximaSame thing as #9 but it deals with Headless Lightning too.
Comment #11
phenaproximaReroll of #6 for 8.9.x.
Comment #12
phenaproximaModified version of #10 to fix #3193991: Lightning 8.x-4.110 breaks compatibility with php < 7.3.
Comment #13
phenaproximaComment #14
phenaproximaComment #15
phenaproximaComment #16
jurriaanroelofs commentedHello @phenaproxima,
For me the lightning 5.1.7 build is failing with this error message:
I see you have created an updated version of the patch in this thread, but it's not committed to 5.1.x yet:
https://git.drupalcode.org/project/lightning/-/blob/5.1.x/composer.json#L97
Would updating this line solve the problem?
Comment #17
phenaproximaThanks for pointing that out, @JurriaanRoelofs. I had rerolled the patch in preparation for 9.1.10, but missed the actual release! I just rolled Lightning 5.1.8 to fix this.
Comment #18
jurriaanroelofs commented@phenaproxima Thanks for the quick fix!
Comment #19
abhinand gokhala k commentedThis patch #14 is not working for Drupal 9.2
Comment #20
loopy1492 commentedPatch #14 is also not working for Drupal 9.3.
I unignored docroot/core so I could get a list of what worked and what did not...
Successful:
Rejected:
Comment #21
gaurav_manerkar commented@phenaproxima Can you please roll out a patch for 9.3
Comment #22
jurriaanroelofs commented@gaurav.manerkar this project is abandoned so that won't happen.
What we've done instead is to fork Lightning and hardcode it to use Drupal 9.2.
You can make your own fork and do the same, or do something else like updating or removing faulty patches.
You can also simply use our Lightning fork which is fixed to Drupal 9.2: https://github.com/dxpr/lightning
(You can install it and update to 9.3 afterwards without problems)
Comment #23
gaurav_manerkar commentedHi,
We are not using lightning anymore. Lightning uninstall command had applied the patch to composer.json file. The patch is not getting applied to 9.3
Comment #24
rajab natshahA Re-roll for phenaproxima's patch to work with Drupal 9.3.x
Posted to #1356276: Allow profiles to define a base/parent profile
https://www.drupal.org/project/drupal/issues/1356276#comment-14374995
Comment #25
sunlixI spend some time to get the 9.2 patch compatible with 9.3 incl. the deprecation warnings by the test suite.
I hope this is useful for all who are on the migrating path to drop lightning with the current Drupal core version.
Comment #26
gaurav_manerkar commentedHi,
What is the purpose of this patch?
Comment #27
chop commentedComment #28
chop commentedThis patch causes the following error in Drupal 9.3.6
The patch adds a duplicate
Drupal\Core\Config\ConfigInstaller::$profileListproperty.Is this patch even needed anymore? Should it be re-rolled or is it not needed?
Comment #29
chop commentedAmending my statement above. I just found out that we've applied two patches that add
Drupal\Core\Config\ConfigInstaller::$profileList. They may even be from this same issue. Apologies. Clearly we have some problems of our own here.Comment #30
chop commentedAfter running
drush pm:uninstall lightningas instructed in Uninstalling Lightning the acquia/lightning patches were clashing with the same patches included in our root project. This caused the following error in Drupal when we ran things likedrush updatedbordrush config:import.Adding the following lines to the composer.json extras section fixed a problem. It was caused by double-patching of the ConfigInstaller.php
Hopefully this helps anyone else who runs into a similar problem. After we get this build to Production we'll be removing the
acquia/lightningpackage altogether. Until then the patches-ignore is needed.Comment #31
Raghav kumar commentedHi Team,
Looking for patch for Drupal 9.4.0 and above:
"9.3[subprofile support] 1356276 - Allow profiles to define a base/parent profile and load them in the correct order / 2914389 - Allow profiles to exclude dependencies of their parent": "https://www.drupal.org/files/issues/2022-01-17/3143958-25-subprofile-support-9.3.x.patch"Comment #32
lecabori commentedHi guys,
I need some help here. I was trying to upgrade to Drupal 9.4.1 (from v9.3.12) but the update produced this error:
Cannot apply patch #3143958: get the 9.2 patch compatible with 9.3 incl. the deprecation warnings by the test suite (https://www.drupal.org/files/issues/2022-01-17/3143958-25-subprofile-sup...)!
I then tried to remove the patch and this new error was issued:
Cannot apply patch REMOVE: Allow installation profile to be changed from Lightning during config sync (https://www.drupal.org/files/issues/2021-01-21/3143958-12-change-profile...)!
If I remove the above then this:
Cannot apply patch [subprofile support] 1356276 - Allow profiles to define a base/parent profile and load them in the correct order / 2914389 - Allow profiles to exclude dependencies of their parent (https://www.drupal.org/files/issues/2021
-05-20/3143958-14-subprofile-support-9.2.x.patch)!
Comment #33
s_leu commentedHere's a re-roll applying on 9.4.x and 9.5.x (so far)
Comment #34
kssundar commented9.5.x patch gets applied correctly on 9.4.5. But when installing the profile (drush si -vvv), I get the below error:
Undefined variable $parser install.inc:1138Error: Call to a member function parse() on null in install_profile_info() (line 1138 of /var/www/html/local.drupals.com/docroot/core/includes/install.inc)Full stacktrace below:
Comment #35
debasish147 commented@s_leu, I think below two services needs to be add in patch before using $parser and $profile_path in
install_profile_info()method, so that it won't give undefined variable error and code will work correctly during profile installation.Comment #36
Raghav kumar commentedI applied the 9.5.x patch with Drupal Core:9.4.8: https://www.drupal.org/files/issues/2022-07-13/3143958-33-subprofile-sup...
After patched applied I am still getting the below error
Comment #37
mei2020 commentedre-rolled 9.5 patch with https://www.drupal.org/project/lightning/issues/3143958#comment-14655703, if it is helpful for anyone.
Comment #38
mrP commentedIs there a patch working for Drupal 9.5.1? Thanks!
Comment #39
niels de ruijter commentedRe-rolled to patch for 9.5.x.
Comment #40
niels de ruijter commentedRemoved unnecessary comment change in patch that was preventing the patch from applying to 9.5.1 & 9.5.2.
Still applies on 9.5.x.
Comment #41
niels de ruijter commentedComment #42
uberengineer commentedUnfortunately doesn't apply to drupal/core 9.5.4
Comment #43
manikandank03 commentedI am also facing the same issue in drupal/core 9.5.4, patch #40 not applying
Comment #44
manikandank03 commentedRe-rolled patch to support the latest Drupal core 9.5.5
Comment #45
hande-itconsulting commentedIsso ainda é necessário no 9.5.9? Continuo recebendo erro nessa versão, ao executar composer update.
Comment #46
damienmckennaThis is #12 rerolled on top of #3266057-110: Allow profiles to define a base/parent profile [continue of #1356276].
Comment #47
ramprassad commentedRe-rolled the #44 patch to support the latest Drupal core 10.x
Comment #48
ramprassad commentedRe-rolled the #44 patch to support the latest Drupal core 10.1.x
Comment #50
sivakarthik229 commentedRe-rolled the #48 patch to support the latest Drupal core 10.2.x
Comment #51
sivakarthik229 commentedFixes drush command error for the patch present in #50
Comment #52
manikandank03 commentedThanks sivakarthik229,
The patch #51 works fine with latest Drupal 10.2.2 with PHP 8.2
Comment #53
kavya n n commentedRe-rolling the patch for 10.3.x