Closed pbiron closed 3 months ago
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 myclabs/deep-copy/src/DeepCopy/deep_copy.php
Warning: require(/app/web/app/plugins/query-monitor/vendor/composer/../myclabs/deep-copy/src/DeepCopy/deep_copy.php): Failed to open stream: No such file or directory in /app/web/app/plugins/query-monitor/vendor/composer/autoload_real.php on line 42
Fatal error: Uncaught Error: Failed opening required '/app/web/app/plugins/query-monitor/vendor/composer/../myclabs/deep-copy/src/DeepCopy/deep_copy.php' (include_path='.:/usr/share/php') in /app/web/app/plugins/query-monitor/vendor/composer/autoload_real.php:42 Stack trace: #0 /app/web/app/plugins/query-monitor/vendor/composer/autoload_real.php(46): {closure}() #1 /app/web/app/plugins/query-monitor/vendor/autoload.php(25): ComposerAutoloaderInitad25d53a23099da4b0886b4f6754360e::getLoader() #2 /app/web/app/plugins/query-monitor/query-monitor.php(56): require_once('...') #3 /app/web/wp/wp-settings.php(517): include_once('...') #4 /app/web/wp-config.php(10): require_once('...') #5 /app/web/wp/wp-load.php(55): require_once('...') #6 /app/web/wp/wp-blog-header.php(13): require_once('...') #7 /app/web/index.php(5): require('...') #8 {main} thrown in /app/web/app/plugins/query-monitor/vendor/composer/autoload_real.php on line 42
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
Fatal error: Uncaught Error: Class "QM_Activation" not found in path-to-site/plugins/query-monitor/query-monitor.php:58
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 composer dump-autoload
from the command-line. And that seems to produce a usable auto-loader. The vendor dir resulting from that CLI (which has the working auto-loader) is attached here.
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:
PHP Fatal error: Cannot declare class ComposerAutoloaderInitad25d53a23099da4b0886b4f6754360e, because
the name is already in use in /var/www/html/example.com/wp-content/plugins/query-monitor/vendor/com
poser/autoload_real.php on line 5
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 wp-content/db.php
file? Then deactivate and reactivate QM.
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