Néstor Soriano Vilchez

Hi @magneticdud, you can prevent the plugin from being automatically installed by adding the following code snippet to your site, for example with the Code Snippets plugin:

add_filter( 'woocommerce_skip_legacy_rest_api_plugin_auto_install', '__return_true' );

We mentioned this in the plugin autoinstall announcement post, apologies if that wasn’t clear enough.

• This reply was modified 10 months, 2 weeks ago by Néstor Soriano Vilchez.
• This reply was modified 10 months, 2 weeks ago by Néstor Soriano Vilchez.

Great, thanks for letting me know. I’ll mark this thread as resolved then.

Hi @jowo, I’m still unable to reproduce the issue. However, may I suggest you to register your endpoint like this instead:

register_rest_route('wc/v3', 'products/dec', array(...

If this still doesn’t work, could you please create an issue in the WooCommerce repository in GitHub? As Shameem pointed out that’s the better place to continue the discussion.

• This reply was modified 10 months, 3 weeks ago by Néstor Soriano Vilchez.

Hi @jowo, I’m unable to reproduce the issue with your snippet. Could you please provide some more information?

1. What’s the exact WooCommerce version you’re using?
2. What’s the response that you get when you try to reach the endpoint?
3. Do you have the Legacy REST API plugin installed?

Hi, I’m Néstor Soriano, the developer who implemented the WooCommerce product attributes lookup table feature. Please take a look at the comment I wrote in the GitHub issue: https://github.com/woocommerce/woocommerce/issues/46699#issuecomment-2066101259

Hi, that’s really weird because the error message seems to suggest that indeed the site is running in PHP 7.3, which is not the case.

We don’t know yet what’s going on, but for now we have removed that type hint (and a similar one in a related class) for 8.7 since it’s not necessary for the code to work: https://github.com/woocommerce/woocommerce/pull/44829

Thanks for the system report by the way, we’ll take a look at it.

• This reply was modified 1 year ago by Néstor Soriano Vilchez.

Hi, WooCommerce doesn’t have this functionality built-in, but looks like you can accomplish it using the Conditional Shipping and Payments extension.

I suggest you to give it a try (we don’t offer trials but we have a 30 day refund policy). If this extension turns out to not be what you were looking for, please contact us again so we can think of a different alternative.

I hope that helps! Regards.

• This reply was modified 1 year, 8 months ago by Néstor Soriano Vilchez.

Hi, please see this answer for details about that message, including a workaround to disable it.

Hi, please see this answer for details about that message, including a workaround to disable it.

Hi, WooCommerce developer here. To start with: on behalf of my team, apologies for the trouble and for the lack of communication from our side.

The email verification step for guest orders was introduced in WooCommerce 7.8.1 as a means to improve the security of the checkout process, but it’s certainly causing more trouble than we had anticipated. We are discussing how to improve the process and will share an announcement in the WooCommerce developer blog soon.

Meanwhile, you can indeed disable the verification step by using a code snippet that causes the woocommerce_order_email_verification_required hook to return false; and contrary to what @catalinbaciu says, it works when introduced via a snippets plugin (like e.g. Code Snippets), there’s no need to put it in functions.php or in a child theme.

If the snippet hasn’t worked for some of you that’s probably because you copied it directly from one of the comments that mentions it, and when you pasted it you got typographic quotes (‘’) instead of standard single quotes (''). Try copying the snippet from here instead:

add_filter( 'woocommerce_order_email_verification_required', '__return_false' );

And that’s all for now, please stay tuned and sorry for the incoveniences.

I have tested your snippet as-is in a test site and it works as expected, showing something like $10.00 $5.00 in the cart page.

If either the regular price or the sale price passed to wc_format_sale_price aren’t valid numbers they won’t be displayed, but I can’t figure out what could cause $cart_item['data']->get_regular_price() to return a wrong number. Do you have any other snippet hooking on woocommerce_format_sale_price by chance?

Edit: for the line that shows only the strike-through’ed price, what is returning a wrong number is either $cart_item['data']->get_sale_price() or $cart_item['custom_price'], depending on the result of the if. Where does that 'custom_price' key come from? Are you sure that it always has a valid value?

• This reply was modified 1 year, 8 months ago by Néstor Soriano Vilchez.

Hi, usually strikethrough on a price means that that’s the regular price, but the product has a sale price applied. However that should appear together with the actual sale price and only in the product page, not in the cart.

Also since you say that you deactivated all the plugins in your site I assume that you don’t have any custom code snippet in place either, is that correct?

Could you please open an bug report in GitHub? Please provide details about how your store is configured and to the extent possible, detailed reproduction steps (which would likely include creating products configured as the ones in your store). You can then answer here with a link to the created issue. Thank you!

Hi @hammadks. When you list the shipping methods for a particular shipping zone in the admin area you’ll see that there’s an icon representing three horizontal bars next to the method title. You can click on these and drag the shipping methods up and down in the list. The one in the top of the list is the default shipping method that appears at checkout.

Hello. While there’s no straightforward way to edit that file, other than opening it directly in a text editor in your server, note that the wc_cart_totals_shipping_html is a small wrapper around the cart shipping template (cart/cart-shipping.php). You can edit that template directly from the admin area of your site if you use the Edit WooCommerce Templates plugin.

Anyway, may I ask what are your specific needs? If you could provide some context on why you want to edit wc_cart_totals_shipping_html perhaps we’ll be able to provide a better answer to you.

Hi puregraphx. I’ve been able to reproduce the issue in your site, and have also found that your snippet is working when using the alternative WordPress search route based on ?s=, try for example: https://www.decoratiehuren.be/?s=lat+met+palmbladeren

By looking at the WooCommerce code I have been able to locate the relevant part, but I don’t see any immediate way to fix the issue. So I have created a bug report in the WooCommerce repository: https://github.com/woocommerce/woocommerce/issues/36043 – feel free to add a comment there if you think you could provide additional information.