Composer 2.7.* breaks composer install?

Hello,

After two days of trying to figure out why one of my old Bedrock WP sites went down and a fresh up-to-date Bedrock site also had the same issues, I determined that at least for my use case, composer 2.7 breaks the installation on the deployed servers. Composer 2.6 works fine. Something changed :slight_smile:

For me, it’s a code deployed AWS elastic beanstalk server, but shouldn’t matter other than because EBS is a managed service, they upgrade the composer. So I just had to work around that by forcing 2.6.* in the composer install command.

Here’s a sample of the issue in 2.7:

Installing dependencies from lock file
Verifying lock file contents can be installed on current platform.
Package operations: 91 installs, 0 updates, 0 removals
  - Installing roots/wordpress-core-installer (1.100.0): Extracting archive
The "roots/wordpress-core-installer" plugin was not loaded as plugins are disabled.
  - Installing composer/installers (v2.2.0): Extracting archive
The "composer/installers" plugin was not loaded as plugins are disabled.
  - Installing brick/math (0.11.0): Extracting archive

Something to do with changes composer 2.7 implemented in terms of allowed-plugins?

Hope this post helps anyone that gets this problem in the future!

See Composer 2.7.0 usage with root user leads to plugins not being loaded · Issue #11839 · composer/composer · GitHub

1 Like