WordPress 5.5 probably breaks sites with page builders

[lichttraeumer]

Hi,

updating three of my WordPress sites to 5.5 was very sobering: two pages falling apart because "something" triggered an 302 redirect, after sending the login form via wp-login.php, to the to the respective start page and the design (Divi and Enfold) was broken. So login in the WordPress backend was not longer possible.
After rolling back via wp-cli to 5.4.2 both sides worked well.

The update to 5.5 on a WordPress page without page builder, rather than Gutenberg plugin worked well.

Best,
Martin

[lichttraeumer]

Some more information about the 302 redirect after logging in:

update-core.php / themes.php / nav-menus.php / wp-admin.php /customize.php triggers an 302 to ​https://<my-domain.de>/wp-admin/upgrade.php?_wp_http_referer=%2Fwp-admin%2Fupdate-core.php

The response code for the redirected target url is 404 every time.
Deactivating all plugins, including mu-plugins, does not help!

Plugin List:
wp plugin list
+---------------------------+----------+--------+---------+
| name | status | update | version |
+---------------------------+----------+--------+---------+
| antispam-bee | active | none | 2.9.2 |
| autoptimize | inactive | none | 2.7.6 |
| breeze | active | none | 1.1.7 |
| cache-enabler | inactive | none | 1.3.5 |
| classic-editor | active | none | 1.6 |
| erecht-share | active | none | 1.0.2 |
| eu-cookie-law | active | none | 3.1.4 |
| imagify | active | none | 1.9.10 |
| iwp-client | active | none | 1.9.4.6 |
| justified-image-grid | active | none | 3.9.7 |
| ninjafirewall | active | none | 4.2.3 |
| optimus | active | none | 1.6.0 |
| wp-mail-bank | active | none | 4.0.11 |
| wp-redis | active | none | 1.1.0 |
| wordpress-seo | active | none | 14.7 |
| 0-ninjafirewall | must-use | none | 1.0 |
| SupportCenterMUAutoloader | must-use | none | |
| mu-iwp-client | must-use | none | |
| advanced-cache.php | dropin | none | |
+---------------------------+----------+--------+---------+

Theme list:
wp theme list
+--------------+----------+-----------+-------------------------------+
| name | status | update | version |
+--------------+----------+-----------+-------------------------------+
| Divi-Child | active | none | 1 License: GNU General Public |
| Divi | parent | none | 4.5.6 |
| twentytwenty | inactive | available | 1.4 |
+--------------+----------+-----------+-------------------------------+

After consulting my team we found out that the problem could be the missing database update.
So I did

wp core update-db
Success: WordPress database upgraded successfully from db version 47018 to 48748.

After that the WordPress backend, with Divi and all plugins activated, works again!

This "hack" doesn't work for Enfold! For Enfold I had, after rolling back to 5.4.2, also trigger the manual wp core update-db to get the db fitting to 5.4.2.
Flushing the opcache also does not help.

Best,
Martin

[lichttraeumer]

Ups ... deleted answer to myself :)

[johnbillion]

Thanks for the report @lichttraeumer . Do you know if the Divi and Enfold developers are aware of the issue?

[lichttraeumer]

Replying to johnbillion:

Thanks for the report @lichttraeumer . Do you know if the Divi and Enfold developers are aware of the issue?

See the Ticket on kriesi.at; ​https://kriesi.at/support/topic/update-to-wordpress-5-5-broke-website/

[desrosj]

@lichttraeumer I am going to close this one out. It doesn't seem that there is an issue within WordPress Core that can currently be identified, and the problem seems to be specific to these two themes. If it turns out there is a bug in Core, feel free to reopen this ticket with more details to reproduce on a fresh install with a default theme active and no plugins).

In the future, please use the WordPress.org support forums for issues like this. Thanks!