WP 6.2 kills shop page

Hi @devsaredead,

Thank you for reaching out.

I understand you’re having an issue with the latest WordPress release, wiping the shop page from its products.

I tried replicating the issue, but the shop page and products displayed just fine. Are you able to try the latest WordPress version using a default theme like Storefront on a staging site to see if the issue persists? Should the issue persist, please try disabling all plugins, leaving only WooCommerce as the active plugin.

Let us know how it goes.

thank you for your attention. For some weird reasons, the problem went away overnight (though I had it both on my staging ad live site). I can’t explain how, maybe the database just needed to… make itself comfortable with the new version. ??

Hello @devsaredead,

Glad to hear that the issue resolved itself overnight! Sometimes, mysterious solutions can be a welcome surprise.

Should you have further inquiries, kindly?create a new topic here.

If you have a few minutes, we’d love if you could leave us a review: https://www.ads-software.com/support/plugin/woocommerce/reviews/

Cheers!

hello again, sorry but now I have this error: attempt to read property “post_count” on null in wp-content/plugins/woocommerce/includes/widgets/class-wc-widget-price-filter.php on line 80

You can view the page here.

Please advice. Thank you

Hi @devsaredead

This error usually indicates that the query to fetch the products returns null.

To help you troubleshoot this, could you please temporarily deactivate all your plugins except for WooCommerce and switch to a default theme like Storefront? If the issue persists, there might be a conflict with one of your plugins or your theme.

If the problem is resolved, you can reactivate your plugins one by one to identify the one causing the conflict.

Please let us know how this goes. We’re here to help.

Hello again, I confirm this must be a corrupted database after latest WP (or Woo?) release, because you can see the issue persists with Storefront activated.

Hi @devsaredead,

I confirm this must be a corrupted database

I understand that you suspect a corrupted database following the latest WordPress or WooCommerce update.

You can try repairing your database using a plugin like WP-DBManager. Please be sure to make a backup of your site before installing or using the plugin. Also note that we do not provide support for the suggested plugin.

Let us know how this goes.

I have tried repairing it via my cpanel, to no avail. What happens if I reinstall WOO? Will I loose all my products/settings/categories/attributes?

But what do YOU suspect it is?

Hi again ,

I have tried repairing it via my cpanel, to no avail.

Did you already have the chance to try repairing via the recommended plugin?

What happens if I reinstall WOO? Will I loose all my products/settings/categories/attributes?

If you reinstall WooCommerce, it should not delete your products, settings, categories, or attributes. This is because the data is stored in your database, not the plugin itself. However, it’s always a good idea to back up your site before making any major changes as a precaution.

But what do YOU suspect it is?

It’s challenging for me to make an accurate assessment at the moment. However, I’m here to help you troubleshoot this issue further. You can create a staging site and make all troubleshooting tests there to avoid messing with your live store.

I don’t think I’m gonna test that plugin which has not been updated for over a year. I trust more to repair the database via mysql. However, neither that nor reinstalling Woo has been successfull. I’m stuck now, because the issue is both on staging and live site, and I fear it cannot be fixed. I have also downgraded WP version with a plugin but the situation is stuck. This is Woo’fault, you can see again the shop page, please advice in details.

• This reply was modified 2 months, 1 week ago by devsaredead.

Hello again, I have resolved this issue. ?? Though everything seemed to point to Woo, I have actually discovered that it was a translation plugin (Falang). By pure chance, when I deactivated the plugin my shop page was redirecting to the homepage, therefore I assumed something was taking over the shop slug. The plugin author confirmed that (and we are now seeing if it’s a bug or some settings that need to be tweaked). Thank you for your time.

Hi @devsaredead,

I’m glad to hear that you’ve managed to identify the issue with your shop. It’s interesting to find out that the Falang translation plugin was the cause.

If you have a few minutes, we’d love if you could leave us a review on the support offered. In the meantime, if you have any other questions or if anything else comes up related to WooCommerce, feel free to contact us.

We’re here to help!