Austin M - a11n

We haven’t heard back from you in a while, so I’m going to mark this as resolved. Feel free to start a new thread if you have any further questions!

Hi @feijon. Thanks for the update. It’s unclear if Yoast is actually causing the problem. That’s why I recommended disabling it temporarily, just long enough to test if the product search worked with it disabled. I understand if this is not feasible, though.

I think the next step here would be conflict testing. You can use the Health Check and Troubleshooting plugin to make this easier. The “troubleshooting mode” of this plugin will allow you to simulate how your site would look and behave with plugins disabled and a default theme without actually changing the site.

These are the steps you should take:

1. Back up your site. Many hosting providers offer a way to do this, and there are plugins such as WP Database Backup that offer this functionality if backing up your database through your host is not an option.
2. Update all your plugins and your theme to their latest versions and see if the problem fixes itself.
3. Turn on Troubleshooting Mode in the Health Check plugin by going to Tools > Site Health > Troubleshooting and clicking “Enable Troubleshooting Mode.” Then, while in Troubleshooting Mode:
4. Make sure your theme is set to Twenty Twenty.
5. Make sure all plugins are deactivated, and then activate WooCommerce.
6. Repeat the action that is causing the problem.

If you’re not seeing the same problem after completing the conflict test, then you know the problem was with the plugins and/or theme you deactivated. To figure out which one is causing the problem, reactivate them one by one, testing after each, until you find the one causing conflict.

Hi @kenteush29. That may have been the wrong thing to modify. I only looked in the template files, but that HTML might be getting created somewhere else and then injected into a template somewhere. You could try searching the WooCommerce plugin for the text string h2 and trying to narrow it down that way. You can do this on GitHub if you don’t have an IDE or some other way to do it locally.

Hi @feijon! Thanks for posting your system status report and the results of your JS error testing.

I noticed that you’re on WordPress 5.5. We’ve seen a few issues related to this update, but many of them can be solved by using the Enable jQuery Migrate Helper plugin. Can you install this plugin and see if that fixes your issue?

If that doesn’t help, can you try (temporarily) disabling the Yoast SEO Premium plugin and seeing if that helps? This is just for diagnostic purposes. It looks like the JS error you found is coming from that plugin.

Great, I’m so glad to hear you were able to get things working! Cheers!

Thanks for posting your SSR @examableadmin. By the way, should this thread be marked as resolved? We can set it back to open if that was an accident.

I noticed that you’re running WordPress 5.5. We’ve seen a few issues with this update, but many of them can be solved by using the Enable jQuery Migrate Helper plugin. Can you try installing that and see if the problem is resolved?

If that doesn’t help, the next most likely cause is a code conflict with Elementor. Could you try disabling that plugin and the various add-ons for it and see if the issue is resolved? You can test this using the Health Check and Troubleshooting plugin to simulate what the site would look like with those plugins disabled without actually disabling them. To do so, go to Tools > Site Health > Troubleshooting Mode in your dashboard and then configure the plugins as needed in troubleshooting mode.

OK, sounds good! You’re very welcome! I’m going to go ahead and mark this thread as resolved. Feel free to create a new thread if you have any further questions!

Hi @arnoldjewelers. Yes, there should be a way to create the tables manually. I’m not sure where in the plugin it is, but there should be code in the WooCommerce plugin somewhere to create the tables, so you can copy that to create the tables manually and see if that helps.