-
-
Notifications
You must be signed in to change notification settings - Fork 201
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
Problem w/ the auto-loader in 3.16.0 #861
Comments
This Composer configuration has been nothing but a nightmare. I need to find a way to make it determinate and testable. |
I've shipped a fix for this directly to wordpress.org as 3.16.1 because evidently there is an issue with the Composer configuration in the build action here on GitHub. |
Sorry but I get the same problem but for another file
edit 3.16.1 was not available on wpackagist when I tested. Same problem as @pbiron now. Thanks for looking into it so quickly @johnbillion :) edit 2 Downgrade to 3.15 works |
unfortunately, 3.16.1 fatals as well, with a slightly different error message
|
I think I need to get rid of the dependency on the Composer autoloader and ship my own. It's just a simple class mapping, so the rest of the Composer autoloading functionality isn't needed. |
I just cloned the repo to my local machine and did a |
Shipped 3.16.2 with that class map back in place. Bleugh. |
success: 3.16.2 works! Thanx for jumping on this so quickly! |
Not sure if it's worth making a new issue, but
I am able to install/activate the plugin (via wp-cli) with no problem, but the site then throws a critical error:
I'm happy to split this out into a separate issue if that's better. |
@jakeparis Yeah that's a separate issue, probably not related to this one. Can you try deleting the More info here: https://wordpress.org/support/topic/fatal-error-cannot-declare-class-composerautoloader/ |
Yes, fixed it. Thank you for that reference. |
I just updated to the newly released v3.16.0 and the site crashed w/ a WSOD. Appears there's a problem in the composer auto-loader in the new version
The text was updated successfully, but these errors were encountered: