• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

PHP 8.0.0 Login from Plesk not working

Harm Jakob Tolsma

New Pleskian
Be aware that logging in using the newly released PHP 8.0.0 leads to HTTP 500 Server Error when loggin in through Subscription screen.
From the WordPress sites list, it shows 'WordPress administrator credentials are missing' error. This also somehow makes Plesk 'forget' the admin credentials.

Code:
Server Error
500 PleskExt\WpToolkit\Exception\WpCliExecutionException
PHP Fatal error: Uncaught TypeError: implode(): Argument #2 ($array) must be of type ?array, string given in /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/WP_CLI/DocParser.php:75 Stack trace: #0 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/WP_CLI/DocParser.php(75): implode() #1 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CompositeCommand.php(32): WP_CLI\DocParser->get_longdesc() #2 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(20): WP_CLI\Dispatcher\CompositeCommand->__construct() #3 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(93): WP_CLI\Dispatcher\Subcommand->__construct() #4 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(40): WP_CLI\Dispatcher\CommandFactory::create_subcommand() #5 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/class-wp-cli.php(480): WP_CLI\Dispatcher\CommandFactory::create() #6 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/commands/help.php(192): WP_CLI::add_command() #7 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/RegisterFrameworkCommands.php(32): include_once('...') #8 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/bootstrap.php(75): WP_CLI\Bootstrap\RegisterFrameworkCommands->process() #9 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/wp-cli.php(23): WP_CLI\bootstrap() #10 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/boot-fs.php(24): include_once('...') #11 {main} thrown in /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/WP_CLI/DocParser.php on line 75 Fatal error: Uncaught TypeError: implode(): Argument #2 ($array) must be of type ?array, string given in /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/WP_CLI/DocParser.php:75 Stack trace: #0 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/WP_CLI/DocParser.php(75): implode() #1 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CompositeCommand.php(32): WP_CLI\DocParser->get_longdesc() #2 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(20): WP_CLI\Dispatcher\CompositeCommand->__construct() #3 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(93): WP_CLI\Dispatcher\Subcommand->__construct() #4 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(40): WP_CLI\Dispatcher\CommandFactory::create_subcommand() #5 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/class-wp-cli.php(480): WP_CLI\Dispatcher\CommandFactory::create() #6 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/commands/help.php(192): WP_CLI::add_command() #7 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/RegisterFrameworkCommands.php(32): include_once('...') #8 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/bootstrap.php(75): WP_CLI\Bootstrap\RegisterFrameworkCommands->process() #9 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/wp-cli.php(23): WP_CLI\bootstrap() #10 /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/boot-fs.php(24): include_once('...') #11 {main} thrown in /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/WP_CLI/DocParser.php on line 75
 
Last edited:
Thank you for your report! We are acknowledging several issues with PHP 8.0 support, that will be addressed in one of the nearest releases of WordPress Toolkit.
 
Hey guys,
I have a problem after upgrading one of my websites (in development) to PHP 8.
I can confirm the same error @Harm Jakob Tolsma has and another one which is probably up to WP Toolkit. The website is working fine but Toolkit says that it's broken. An error log and screenshot is in the attachment. I hope it will help you to improve. If you need more info feel free to ping me.
 

Attachments

  • error-log.zip
    672 bytes · Views: 3
  • wp-broken.png
    wp-broken.png
    64.2 KB · Views: 12
Back
Top