composer 2.3.5 breaks composer/installers

[aaronredwood]

I use composer/installers as part of our roots/bedrock based WordPress multisite codebase. As part of a recent system update, we upgraded composer to version 2.3.5. After running normal deployment process, site was broken. Determined cause to be that WordPress theme and plugins had not been installed to custom locations, just installed into vendor folder. Downgrading to composer 2.1.3 fixed problem. We were running 2.1.3 locally, so that's why we tried that version; did not spend any time trying to identify specific version where defect occurs. Version of composer/installers in production is 1.12.

[Seldaek]

Can you check if composer/installers 2.1.1 works? And if not, it'd be nice if you could try variuos composer versions to see which broke. Try composer self-update 2.2.12 vs composer self-update --stable for example to see if 2.3.0 broke it or if 2.2.x was already broken?

[fredpotvin-platformsh]

@aaronredwood upgrade to 2.3.6. The allow plugin directive is enforced now but 2.3.6 will simply continue without executing your plugins, so, composer/installers won't run. It was fixed by composer/composer#10920 which is included in 2.3.6

[Seldaek]

@fredpotvin-platformsh this issue predates the enforcing by default of allow-plugins so I don't think this is related.. That said I also don't know what was going on here as there was no feedback provided.