After 6.4.0 installation I personnaly get a message on my administration interface of wordpress:
You’ve got a critical error. Check your email administration address, or something like that … (but I did not receive any error, nor am I able to see any error on my error files )
PS: I am on PHP 8.1
Did you get the same behaviour ?
I had to go back to 6.3.0 (6.4.0) definitely breaks my wordpress administration page.
@escael I’m not sure how that’s possible, but we’ve had trouble before with older versions of MySQL that couldn’t handle that syntax for updating the table.
I’ll note that if you’re on PHP 8.1, that might be a possible lead on the error @lemagcinema is experiencing. One of the changes in PHP 8.1 was to make MySQL errors into Exceptions–which means they could become fatal errors if WordPress is not catching them like it previously caught MySQL errors.
At any rate, if you could (both) post the site health report from Tools->Site Health, that might shed some light on a MySQL version that we haven’t accounted for yet.
Thread Starter
escael
(@escael)
Hi, sorry by not said before, but i am indeed using php version 8.1.1
WP version: 5.8.8. Latest version
Mysql: 8.0.27-0ubuntu0.20.04.1 for Linux on x86_64
Redis server v=5.0.7
I hope can help you
Thanks
Ugh, confirmed on my dev server running 8.0.27 also. I had figured that if MariaDB fixed the bug, surely MySQL 8 would have the fix also. But sadly not…
You can manually set the default value for the ‘updated’ column to CURRENT_TIMESTAMP, but I’ll add a conditional for MySQL 8.0.x to make sure the next update uses the fall-back (slower) table upgrade method.
quite same configuration for me: php 8.1 and mysql 8 … as for now, I wait for the 6.4.1 release to fix it before upgrading …
Hi folks,
I’ve pushed a fix for the MySQL 8 glitch to our GitHub repo: https://docs.ewww.io/article/73-update-from-github
Please confirm whether this resolves the MySQL issue–the plugin should be able to set the default value for the ‘updated’ column to CURRENT_TIMESTAMP.
@lemagcinema if the fix resolves your issue, please do let me know. Still don’t know 100% if the two are connected since I don’t have any sites on PHP 8.1, but it’s a definite possibility.
I prefer not to install a version directly from github but instead wait for the 6.4.1 update. I do not need the 6.4.0 features for now.
(+ I guess you are able to install quickly a mysql 8 and check by yourself !)
@lemagcinema My dev site already is running MySQL 8, so that much I could easily verify 🙂
We still don’t know whether your PHP 8.1 issue is connected to this one though, and I’ve had no other similar reports.
@escael When you had that MySQL error, did it break the wp-admin like @lemagcinema reported here: https://ww.wp.xz.cn/support/topic/fatal-error-when-upgrading-to-6-4-0/
Thread Starter
escael
(@escael)
Hi, @nosilver4u the latest version fix the problem. I have tested it in my local development and not problem.
About your mysql ask, it’s correct did broken the admin.
I wait for the finish version to upgrade in production environment.
Thank a lot
Perfect, thanks for confirming! We’ll release the fix later this week or early next.
I wanted to note that if folks are using WP 5.9, this should not be an issue anymore. They’ve worked a lot on PHP 8.0 & 8.1 compat for the 5.9 release which includes “reverting” the MySQL behavior change for SQL errors.
Thread Starter
escael
(@escael)
hi, that’s correct, the problem was fixed with the latest version of WP
Thanks
-
This reply was modified 4 years, 4 months ago by
escael.
