-
-
Notifications
You must be signed in to change notification settings - Fork 413
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
composer 2.3.5 breaks composer/installers #508
Comments
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 |
@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, |
@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. |
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.
The text was updated successfully, but these errors were encountered: