Conversation
supportThe last autoupdate took down site with: PHP Fatal error: Uncaught TypeError: Return value of Composer\\ Autoload\\ClassLoader::initializeIncludeClosure() must be an instance of Composer\\Autoload\\void, none returned in …/wp-con tent/plugins/wordpress-beta-tester/vendor/composer/ClassLoader.php:580\nStack trace:\n#0 …/wp-content/plugins/wordpress-beta -tester/vendor/composer/ClassLoader.php(112): Composer\\Autoload\\ClassLoader::initializeIncludeClosure()\n#1 …/wp-content/p lugins/wordpress-beta-tester/vendor/composer/autoload_real.php(28): Composer\\Autoload\\ClassLoader->__construct(‘……’)\n#2 …/wp-content/plugins/wordpress-beta-tester/vendor/autoload.php(25): ComposerAutoloaderInit248763277659ec81f8c4ff690d89804d::getLoad er()\n#3 …/wp-content/plugins/wordpress-beta-tester/wp-beta-tester.php(33): require_once(‘……’)\n#4 …/wp-settings.php(447): include_once(‘…..’)\n#5 …/wp-config.php(76) in …/w p-content/plugins/wordpress-beta-tester/vendor/composer/ClassLoader.php on line 580 Not immediately obvious to me why. Moving the WordPress-beta=-tester plugin out the way got the site back, but no time to troubleshoot today. php 7.0.33
I’m sorry Simon. I’ll take a look today.
Can you re-download the plugin? I can’t replicate this and it seems to be from Composer.
Okay I have version 3.2.5, it matches the development version in all files. Quick Google of error took me to: https://github.com/composer/composer/issues/11245 Which suggests it is PHP version and returning void (I am overdue upgrading this box, so not especially surprised I eventually hit PHP support issue, but the plugin is reporting 5.6 and up, when I assume it is at least 7.1 and up now). My PHP foo is feeling dated, both on server and in my head.
Only requires PHP 5.6 or higher. https://github.com/afragen/wordpress-beta-tester/blob/554250518a7f517c87020ac913b3e50f9f5f5fdb/composer.json#L41
Not quite sure what you are saying there, the composer ClassLoader.php in the plugin was updated with 7.1 only “void” return type in 3.2.5 from 3.2.4 just like the example from Composer 2.5 I linked in the bug report, the composer.json file wasn’t updated at the same time. initializeIncludeClosure() replaced includeFile()
What I’m saying is the requirement is the same as for WordPress, PHP 5.6+
I’ve reinstalled Composer 2.5.0, which doesn’t suffer from this bug. Should be fixed in next version of Composer. Update to this plugin available soon.
I’m sorry Simon. I’ll take a look today.
Can you re-download the plugin? I can’t replicate this and it seems to be from Composer.
Okay I have version 3.2.5, it matches the development version in all files. Quick Google of error took me to: https://github.com/composer/composer/issues/11245 Which suggests it is PHP version and returning void (I am overdue upgrading this box, so not especially surprised I eventually hit PHP support issue, but the plugin is reporting 5.6 and up, when I assume it is at least 7.1 and up now). My PHP foo is feeling dated, both on server and in my head.
Only requires PHP 5.6 or higher. https://github.com/afragen/wordpress-beta-tester/blob/554250518a7f517c87020ac913b3e50f9f5f5fdb/composer.json#L41
Not quite sure what you are saying there, the composer ClassLoader.php in the plugin was updated with 7.1 only “void” return type in 3.2.5 from 3.2.4 just like the example from Composer 2.5 I linked in the bug report, the composer.json file wasn’t updated at the same time. initializeIncludeClosure() replaced includeFile()
What I’m saying is the requirement is the same as for WordPress, PHP 5.6+
I’ve reinstalled Composer 2.5.0, which doesn’t suffer from this bug. Should be fixed in next version of Composer. Update to this plugin available soon.