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);
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.
Wrong post…deleted.
-
This reply was modified 4 years by
fonetechcz.
-
This reply was modified 4 years by
fonetechcz.
-
This reply was modified 4 years by
fonetechcz.
Email with info sent directly…
It is not possible to downgrade php for me, its fixed by hosting and I can select from 8.x only 8.0.13 or 8.1. But there shouldn’t be many changes in between 8.0.13 and 8.0.9. Also you announce compatibility with PHP 7+ so I thought that it should be fine.
Culprit of this problem seems to be ftpext access to filesystem, but I even tried to put FTP login info to wp-config.php to avoid WP asking every time when it has to work with files. Unfortunately it didn’t help.
Access to website is now pointless, because I had to move it back to older PHP and original theme – I need it working. Will wait a bit with migration and upgrade before you test newer versions of PHP.
-
This reply was modified 4 years by
fonetechcz.
-
This reply was modified 4 years by
fonetechcz.
Same here, updated to 11.2 from 10.something and WP crashes when activating TD_composer. And there is no Update/Time machine tab in theme page. So its kinda hard for me to come back to previous version.
Seems that more and more pages are now with ads. So probably my theory about indexing pages and adding ads to them seems legit. You could close this thread…