You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Class DrupalProject\composer\ScriptHandler is not autoloadable, can not call post-install-cmd script
To get the site upgraded in a 2-hour timespan, I kinda cut a few corners tossing out some old composer.json cruft, and I seem to have broken some of the stuff that the drupal-project/composer-template had originally injected into the Composer config (like the ScriptHandler... might not even be needed anymore?).
The text was updated successfully, but these errors were encountered:
Actually load.environment.php gave me an error but I just got rid of it.
I did get another warning about the CONFIG_SYNC_DIRECTORY constant in ScriptHandler.php needing quotation marks too.
[ErrorException]
Use of undefined constant CONFIG_SYNC_DIRECTORY - assumed 'CONFIG_SYNC_DIRECTORY' (this will throw an Error in a future version of PHP)
That being said I don't think you need the ScriptHandler anymore because it creates a settings.php file but then it is immediately overwritten in the Dockerfile
After the Drupal 9 upgrade (see video: https://www.youtube.com/watch?v=nLoJ2L0AzDY), I noticed that when running
composer install
I'm getting the following:To get the site upgraded in a 2-hour timespan, I kinda cut a few corners tossing out some old
composer.json
cruft, and I seem to have broken some of the stuff that the drupal-project/composer-template had originally injected into the Composer config (like the ScriptHandler... might not even be needed anymore?).The text was updated successfully, but these errors were encountered: