When will PHP8 be supported?

I bought the theme today. I’m currently using WordPress on a Japanese VPS, and it works with PHP 7.4, but when I change to PHP 8, it doesn’t work.

Since PHP8 is required for production environment, when will it be supported?

Good evening from Japan.

I have checked and it seems that there is no problem with the theme itself. However, when I turn on the tagDiv Composer plugin, I get an error in WordPress.

I have the latest version of PHP (8.1) and WordPress is also up to date.

tagDiv Composer throws an error with PHP 8 and does not enter the Wordpess dashboard, when the plugin is disabled everything is fine.

Hello, everyone,

When I turned on the plugin in question in PHP 8.1, I got the following message in the admin panel.

The message is as follows.

「このサイトで重大なエラーが発生しました。対応手順については、サイト管理者のメール受信ボックスを確認してください。

WordPress のトラブルシューティングについてはこちらをご覧ください。」（Japanese）

Translated

「A critical error has occurred on this site. Please check your site administrator’s email inbox for instructions on how to respond.

For more information on troubleshooting WordPress, please click here.」

Note that when you view the site, you will see a blank screen.

When I open the debug mode, I don’t see anything that looks like an error, so I assume that the plugin in question is not compatible with PHP 8.

This way, I hope you can use the plugin to support it as much as possible.

Have a good day.

Hi,

When I changed to PHP 8, the site displayed fine, but I got the following error message.

Turning on tagDiv Composer causes an error in PHP 8.

ーーーーーーーーーーーーーー
Fatal error: Uncaught TypeError: ftp_fget(): Argument #1 ($ftp) must be of type resource, null given in /home/kusanagi/ichigo-an/DocumentRoot/wp-admin/includes/class-wp-filesystem-ftpext.php:146 Stack trace: #0 /home/kusanagi/ichigo-an/DocumentRoot/wp-admin/includes/class-wp-filesystem-ftpext.php(146): ftp_fget(NULL, Resource id #380, ‘/home/kusanagi/…’, 2) #1 /home/kusanagi/ichigo-an/DocumentRoot/wp-content/themes/Newspaper/includes/wp-booster/wp-admin/plugins/class-tagdiv-theme-plugins-setup.php(351): WP_Filesystem_FTPext->get_contents(‘/home/kusanagi/…’) #2 /home/kusanagi/ichigo-an/DocumentRoot/wp-content/themes/Newspaper/includes/wp-booster/wp-admin/plugins/class-tgm-plugin-activation.php(1977): tagdiv_theme_plugins_setup->theme_plugin_has_update(‘td-composer’) #3 /home/kusanagi/ichigo-an/DocumentRoot/wp-content/themes/Newspaper/includes/wp-booster/wp-admin/plugins/class-tgm-plugin-activation.php(1836): TGM_Plugin_Activation->does_plugin_have_update(‘td-composer’) #4 /home/kusanagi/ichigo-an/DocumentRoot/wp-content/themes/Newspaper/includes/wp-booster/wp-admin/plugins/class-tgm-plugin-activation.php(422): TGM_Plugin_Activation->is_tgmpa_complete() #5 /home/kusanagi/ichigo-an/DocumentRoot/wp-includes/class-wp-hook.php(303): TGM_Plugin_Activation->init(”) #6 /home/kusanagi/ichigo-an/DocumentRoot/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters(NULL, Array) #7 /home/kusanagi/ichigo-an/DocumentRoot/wp-includes/plugin.php(470): WP_Hook->do_action(Array) #8 /home/kusanagi/ichigo-an/DocumentRoot/wp-settings.php(578): do_action(‘init’) #9 /home/kusanagi/ichigo-an/DocumentRoot/wp-config.php(93): require_once(‘/home/kusanagi/…’) #10 /home/kusanagi/ichigo-an/DocumentRoot/wp-load.php(50): require_once(‘/home/kusanagi/…’) #11 /home/kusanagi/ichigo-an/DocumentRoot/wp-admin/admin.php(34): require_once(‘/home/kusanagi/…’) #12 /home/kusanagi/ichigo-an/DocumentRoot/wp-admin/index.php(10): require_once(‘/home/kusanagi/…’) #13 {main} thrown in /home/kusanagi/ichigo-an/DocumentRoot/wp-admin/includes/class-wp-filesystem-ftpext.php on line 146
ーーーーーー
Is this a problem with the plugin?

I have a WordPress site that uses a different theme and it works fine with PHP 8.

I forgot about it. This is the error above in the admin panel.

Good evening from Japan,

If you turn on only tagDiv Composer, you will get an error.

It seems that tagDiv Composer is still wrong.

We need PHP 8 in our production environment, so it would be great if you could take care of this as soon as possible.

If there is anything else, I will post it in this thread.

Thank you for your support.

Did you find any solution to this? Posted same error few months ago here https://forum.tagdiv.com/topic/activating-td-composer-causes-500-internal-server-error/ without any working solution.

One symptom for this error is when WordPress is using FTPEXT access to files and PHP is 8+, probably doesnt show up on installations where it has direct access to files. Unfortunately my host doesnt provide direct access and I am stuck with error. Even tried to include FTPEXT credentials in wp-config.php to provide WP access without having to ask user for these, still no change. Probably just using FTPEXT causes this PHP8.

It shows even on clean install of WP+Newspaper on this config (PHP8 and FTPEXT). Thought that when I give it some time (posted about this problem about 5 months ago), it will be fixed with some update. Still doesnt.

UPDATE: Problem could be temporarily solved by adding define('FS_METHOD', 'direct'); to wp-config.php
But its is just workaround as it forces WP to try only direct access to files and as soon as it tries to change something on disk, it will fail. Without asking for FTP access. So errors caused by composer are gone, but you cant update nor manipulate files. But at least it is definitive confirmation that there is something wrong in Composer module when using FTPEXT access.

And should be possible to replicate on hosting with PHP 8.0.13 using wp-config.php set to forceuse FTPEXT by adding following to wp-config.php

define(‘FS_METHOD’, ‘ftpext’);
define(‘FTP_BASE’, ‘/your/path/to/web/www’);
define(‘FTP_USER’, ‘user’);
define(‘FTP_PASS’, ‘pass’);
define(‘FTP_HOST’, ‘host’);
define(‘FTP_SSL’, false);