Fernando a11n

@tingtw I’m not familiar with any plugins that would add that sort of conditional logic. You may want to start looking into it from the tool you are using to determine your delivery date – is that a special plugin you have installed?

You may reach out to the developers to see if that sort of functionality can be integrated. My guess is this would have to be custom-coded for your site, but it doesn’t hurt to ask and explore options.

@mashour06 One way I’m thinking you can achieve this is by creating one product category for each type of product. You will then manually add products to either category, and this will automatically create a category page for each one of those categories.

Another way of doing that would be to use the hand-picked products block, and manually insert products in blocks on a new page. Depending on the number of products you have, that might involve a lot of clicks though.

Hopefully this helps!

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

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

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

@deanoj You can indeed download a previous version from the link shared above.

Having said, we don’t recommend continuing to run your store on an outdated version of WooCommerce. I’d suggest a more proactive approach: Testing the update on a staging version of your site, to make sure no conflicts arise. Once you have confirmed the update has gone smoothly, or after you have addressed issues there, you can be confident in updating the live site.

A staging site is a clone of your live website that you can modify without risking any changes or damages to your actual site. You can create a new staging environment using a plugin like WP Staging – this will let you deploy a copy of your website with minimal work.

@f3lixglez Issues like this, specially when they appear after plugin updates, are often caused by conflicts. It’s possible that either your theme or another plugin installed on the site is not compatible with the recent updates you made.

To verify if that’s the case, you’ll want to temporarily switch your theme to Storefront. Then, disable all plugins on the site except for WooCommerce, and test for the issue.

If the issue is gone, you’ll then have to re-enable features one by one, while testing for the issue; until you find out which one is causing this behavior.

We recommend that these steps are taken on a staging site, which is a clone of your live site that you can modify without risking making any permanent damage to your live site. You can create it using a plugin like WP-Staging.

@test4madness Looking at that page my guess is this is being added by your theme as part of that page’s template. The reason I say this is because out of the box WooCommerce does not behave like this.

You can verify if this is indeed coming from your theme by temporarily enabling the default WooCommerce theme, Storefront. If the issue is gone when enabling that theme, then you know it’s coming from your own theme and I’d suggest contacting the developer for assistance.

This seems similar to what is reported on this thread so I’ll share the same advice:

WordPress 5.5 removed a javascript file called jquery-migrate that some plugins which haven’t been udpated might still be relying on. Until they update, the workaround is to use the plugin Enable jQuery Migrate Helper to include the javascript files.

I’m not entirely sure this is the cause of the issue but since jQuery errors are referenced in the browser console screenshot your shared, it might be worth trying out.

If installing the plugin above does not solve the issue, I’d recommend trying a conflict test next:

You’ll want to temporarily switch your theme to Storefront. Then, disable all plugins on the site except for WooCommerce, and test for the issue.

If the issue is gone, you’ll then have to re-enable features one by one, while testing for the issue; until you find out which one is causing this behavior.

We recommend that these steps are taken on a staging site, which is a clone of your live site that you can modify without risking making any permanent damage to your live site. You can create it using a plugin like WP-Staging: https://www.ads-software.com/plugins/wp-staging/

cc @invokeeer, @robots71, @bobmorain

@rahimvaziri WordPress 5.5 removed a javascript file called jquery-migrate that some plugins which haven’t been udpated might still be relying on. Until they update, the workaround is to use the plugin Enable jQuery Migrate Helper to include the javascript files.

I’m not entirely sure this is the cause of the issue but since jQuery errors are referenced in the browser console screenshot your shared, it might be worth trying out.

If installing the plugin above does not solve the issue, I’d recommend trying a conflict test next:

You’ll want to temporarily switch your theme to Storefront. Then, disable all plugins on the site except for WooCommerce, and test for the issue.

If the issue is gone, you’ll then have to re-enable features one by one, while testing for the issue; until you find out which one is causing this behavior.

We recommend that these steps are taken on a staging site, which is a clone of your live site that you can modify without risking making any permanent damage to your live site. You can create it using a plugin like WP-Staging: https://www.ads-software.com/plugins/wp-staging/

@volkerforster Hi! The error you shared seems consistent with a known conflict between the latest version of WooCommerce and WP Rocket, or other plugins using PHP League’s Dependency Injection container. You can read more about the issue on this open GH thread.

If you are using WP Rocket indeed, their team have released a new version that fixes the compatibility issue. Updating to the latest version would fix it.

We strongly encourage users to always test updates on a staging site first, to avoid this kind of issues. If you don’t have one yet, I’d recommend reaching out to your host to see if they offer any staging options. If they don’t, you may want to look into using a plugin like WP Staging.

@reiddg If it’s not part of the menu items then it might be added directly by the theme. Have you tried asking the theme developers for some pointers on where to update the URLs?

A good way to verify if this is added by the theme itself would be temporarily enabling a default theme like Storefront. If the options disappear under a different theme, then it is most likely that they are theme-specific.

@tdenen7 Out of the box the WooCommerce plugin doesn’t add a catalog or catalog ID the way you describe, so I’m not sure what exactly you are referring to. Could this be a feature added by a third-party plugin you are using? Again, without a link to look at the page itself, it’s hard to pin-point what needs to be changed or where that might be coming from.

I’d recommend reviewing where is that catalog being added and if there might be a plugin installed on your site that is responsible for that feature.

@fabricioreck Thank you for the screenshot. This support doc might help clarify things.

From there:

You should receive an email with information about the issue causing your account to be restricted from WooCommerce team or Stripe. Please respond to this email to address the issue.

Since this is the support forum for the core WooCommerce plugin and not the WooCommerce Payments plugin, I’m going to proceed to close this thread. If you continue to have issues or are unable to find the email, please post on the WooCommerce Payments support forum or contact the WooCommerce.com support team as instructed in the doc above.

I’m going to close this thread for now but if you have any further questions please feel free to start a new thread.