WordPress 5.5 has broken tabs in WooCommerce products

[jbrookechao]

URL: ​https://www.grilledcheesemania.com
WordPress 5.5
Browser: Safari and Chrome

My site automatically updated to WordPress 5.5, and several weird things happened:

1. Some substitutions were made from media library (photos that had been attached to content changed...I'm the only editor)
2. (and this is the biggest issue), I cannot click on tabs or areas underneath my product/page/post content. They won't open. This means I cannot edit my attributes or variations on any of my WooCommerce products! Same with the panels for for Yoast SEO....you can't even edit the SEO fields or even see them because the tabs and accordion box for that content won't work.

Y'all did not test this well.

Those features are not specific to those plugins...it seems to be a general problem with any type of plugin content that uses tabs or accordion expand/close (which would be almost any plugin that allows manipulation of content within a post, item, or page).

[TimothyBlynJacobs]

Welcome to trac @jbrookechao!

This is most likely an issue caused by a plugin that is using old jQuery functionality that will no longer work in WordPress 5.5 due to jQuery Migrate being removed.

A summary about that can be found in the "jQuery Migrate is Disabled by Default" section of the 5.5 upgrade guide: ​https://wordpress.org/support/topic/read-this-first-wordpress-5-5-master-list/#post-13238244

For more info about that see #37110 and ​https://make.wordpress.org/core/2020/06/29/updating-jquery-version-shipped-with-wordpress/

If you open your web browser's developer console, you should be able to see which JavaScript file is causing the error: ​https://wordpress.org/support/article/using-your-browser-to-diagnose-javascript-errors/

You can also try deactivating all plugins and then reactivating them one by one to pinpoint the issue.

[jbrookechao]

Your link to the upgrade guide is a broken link

Replying to TimothyBlynJacobs:

Welcome to trac @jbrookechao!

This is most likely an issue caused by a plugin that is using old jQuery functionality that will no longer work in WordPress 5.5 due to jQuery Migrate being removed.

A summary about that can be found in the "jQuery Migrate is Disabled by Default" section of the 5.5 upgrade guide: ​https://wordpress.org/support/topic/read-this-first-wordpress-5-5-master-list/#post-13238244

For more info about that see #37110 and ​https://make.wordpress.org/core/2020/06/29/updating-jquery-version-shipped-with-wordpress/

If you open your web browser's developer console, you should be able to see which JavaScript file is causing the error: ​https://wordpress.org/support/article/using-your-browser-to-diagnose-javascript-errors/

You can also try deactivating all plugins and then reactivating them one by one to pinpoint the issue.

[jbrookechao]

Please, do not mark this as "resolved" until I confirm it actually is. That's incredibly rude.

[johnbillion]

@jbrookechao In the hours and days after a new version of WordPress is released the team of volunteers has to deal with a very high number of support requests and bug reports. Timothy didn't intend to be rude by closing your ticket, rather it's just our process for helping manage the high number of open tickets.

The upgrade guide for jQuery is in the link provided, you just need to scroll down a little way as it's included with various other information about the release. Hopefully there's helpful information for you there.

I'll close this off again, conversation can continue here if necessary while the ticket is closed. If there does turn out to be a bug in WordPress core then we can reopen this for further investigation.

[jbrookechao]

No, I just told him that his link is broken. I tried to follow it and it says that page doesn't exist.

[johnbillion]

Sometimes links in email notifications get truncated. Can you try clicking the link above (on https://core.trac.wordpress.org/ticket/50952 ) rather than directly in your email notification? Sorry about that.

[jbrookechao]

Read ticket 37110, and it seemed less like helpful information and more like developers arguing about the JQuery update. So not at all helpful

Finally got his link to work, and honestly, it looks like your'e asking WordPress users to hunt down and diagnose development issues caused by rolling out a version of WordPress for which many well known plugins were not adequately prepared. One of the ones throwing an error is the Product of the Day plugin for WooCommerce. I don't have a way to replace that, and I am not a developer so I won't be playing with their plugins code.

Also, there is an error that does not appear to be tied to a specific plugin:

{{{TypeError: undefined is not an object (evaluating 's.hasClass')
anonymous function (load-scripts.php:629:482)
Dispatch (jsquery.js:3:112375)
anonymous function (jsquery.js:3:9094)
trigger (jsquery.js:3:11494)
anonymous function (jsquery.js:3:18873)
}}}

I guess I'll just have to roll my sites back to 5.4 and turn off automatic updating until y'all get it together. This is nuts.

[jbrookechao]

That last error seems to have to do with WordPress own load Scripts/load-scripts.php file.

[layotte]

@jbrookechao The update to jQuery was announced several months ago and it is on the developers to make sure that they tested the new version and ensure that their plugins (or themes) continue to work with this update. The fine volunteers working on WordPress even provided a handy plugin to assist us developers in ensuring that our plugins (or themes) are working properly. It does sound like you have at least one plugin that wasn't updated to ensure that it would remain compatible with the latest WordPress updates. If you can determine which plugins are not working properly for you, it would make sense to contact the developer(s) of those plugins to alert them of the issue, so they can fix it in their code. A common way to determine the root cause of an issue is by disabling all plugins, and slowly reactivate them a few at a time until the problem appears again. I hope this helps you troubleshoot your site.

[SergeyBiryukov]

My site automatically updated to WordPress 5.5, and several weird things happened

Just wanted to note that WordPress does not automatically upgrade itself for major releases (which 5.5 was).

It's possible your webhost did this for you, and if you had not enabled auto-updates and don't have any plugins that may have done that, I recommend you reach out to your host directly for help.