Jim W - a11n

Hi again @sagescrub,

Thanks for your patience!

You are correct, woocommerce payments does not call wc_empty_cart directly. But it interfaces with the woocommerce plugin through WooCommerce->initialize_session which does call wc_empty_cart. In that case my suggestion is to ensure that initialize_session is not called to early. There must be a way to check for that. Do you agree?

It appears this is correct, at least in part. I was able to confirm the error is thrown in WooCommerce, not WooCommerce Payments; it appears it is being triggered by wc_load_cart().

Our developers pointed out this planned fix that was built in December, which is now a part of WooCommerce 7.4 Beta 1 being testing as we speak.

Feel free to follow along with that pull request there for any updates, and with any luck that issue will be resolved in that future release.

Thanks!

Hi there @sagescrub,

I’m sorry to hear that error is still occurring. As my colleague had mentioned in your ticket back in September, he’d performed a check of the code related to that function then:

The wc_empty_cart appears to have also been depreciated and I am not seeing a record of WooCommerce Payments hooking into that function.

https://github.com/woocommerce/woocommerce/blob/5239cf62e74ba9284578e73d97353dc1e10c8fa4/plugins/woocommerce/includes/wc-deprecated-functions.php#L251

We haven’t seen any other reports of this so it’s safe for us to suspect the problem is likely with the combination of active plugins and the hosting environment. More specifically, we haven’t seen the issue on WP Engine sites so it could be the one active plugin that trying to optimize the environment.

I will ask our developers to take another look in the meantime, but at this point a conflict test isolating WooCommerce/WooCommerce Payments on your site is our best bet for finding more data to work with here. If you’re able to do this on a staging site within the same hosting environment, that would be ideal.

Let me know if you have any questions. Thanks!

Hi there @bedas,

Thanks for reaching out!

The behavior you describe there is how WooCommerce is intended to work. Here’s some details that I think will help explain why.

• WooCommerce will only prevent the use of a specific email address on the checkout page if it’s in use on an account and the Create an Account box is checked. This is because two customer accounts cannot have the same address.
• Guest Checkout, when enabled, is meant to allow ordering without logging in or creating an account at checkout. Guest orders are “standalone” orders and can have repeated customer data without causing any issues in WooCommerce.
• You can disable Guest Checkout if you wish to prevent this for record-keeping purposes. (WooCommerce > Settings > Accounts & Privacy)
• The Account email address and order email address are independent and not required to match (except on orders where Create an account is checked).
• For example, customers may log in using one address, and then order using a different email address, because they want the confirmation for that single order to go elsewhere, not their account address (placing an order on behalf of another party, or as a gift, etc).
• It’s always possible for an admin to reassign an order to a different customer account, using the Customer field on the Edit Order view. So if a customer with an account checks out as a guest and wishes to have it moved within their account history, you can do this manually regardless of the email used on the order.

In general I recommend communicating with your customers about this if you have concerns as it’s often intentional on their part, or based on convenience (it’s faster to checkout as a Guest if you don’t remember your password).

If you would like to require users to verify their email address ownership for anti-spam or anti-fraud purposes, you can do so using an extension such as WooCommerce Email Verification.

Please note that this will only require verification for account login, and will not prevent verified, logged-in customers from entering any email they wish on the checkout page.

I hope this helps explain the intent of those features. If you have any further questions, please let us know!

• This reply was modified 2 years, 2 months ago by Jim W - a11n.

Hi @3dtobias,

Thanks for confirming that, and for the System Status Report!

I believe this is a known result for stores using 4 decimal places, as the refund module appears to default to using 2, as noted here: https://github.com/woocommerce/woocommerce/issues/30263

It appears this has already been identified as a necessary enhancement and an update is in progress (testing phase) here: https://github.com/woocommerce/woocommerce/pull/34641

In the meantime, it appears that using 2-decimal place settings will be the only workaround.

Please feel free to follow along with those threads on GitHub and let us know if you have any questions.

Hi @jason9j,

Thanks for reaching out!

Unfortunately, there has not been a fixed released for that issue, as doing so may also impact other aspects of the plugin.

Our developers have noted that there is discussion of potential changes to the overall method the plugin uses for processing payments, which would make fixing this issue easier to do without affecting things like Apple Pay, etc.

I’m afraid we don’t have a timeline to offer for a fix at this point, but I can share that it’s unlikely to be anytime soon due to the factors I mentioned above.

Please stay tuned to the changelog here for future updates and fixes.

Thanks!

Hi there @mbhebsgaard,

Thanks. I investigated this a bit as well. Did not find a solution. I ended up creating a new catalog. Removed to old and updated my ads. The problem were in the interaction with Woocommerce and Meta.

I’m glad to hear you were able to find a workaround, but I agree it’s definitely not the ideal solution for this issue.

Reading back through the previous conversation, I’m not seeing that we ever confirmed if you were using the Facebook Price field or if you left that blank in your product settings.

Can you confirm if you have a value set there that may have been overriding the WooCommerce price settings?

Thanks.

Hi there @headfuel,

I’m sorry to hear that automated Tax calculation with WooCommerce Shipping & Tax is still not operating as expected for you. In order to help you troubleshoot this further, we will need to take a closer look at your site.

P{ease go ahead and submit a ticket here:

https://woocommerce.com/my-account/create-a-ticket/

You may need to log into your WooCommerce.com account before you can access that page.

Also, don’t forget to include your System Status and a link to this forum thread in the ticket, so that we can keep track of what’s already been done. The information included will help our support team narrow down the issue much more quickly.

Thanks!

Hi there @s2925534,

Thanks for reaching out!

In order to edit the Refund amount you must select the quantity of products to be refunded, or manually enter the shipping cost refund amount. Those changes made on each line item on the order will then reflect in the total field below.

Here’s a screencast of what that will look like: https://d.pr/i/sAjNO2

• This reply was modified 2 years, 6 months ago by Jim W - a11n.

Hi there @contactpoint01,

Thanks for reaching out!

Since the WordPress update to 6.0.2 and Woocommerce update to 6.8.1+, the thumbnails are not getting displayed properly. We use the following code to display the thumbnail:

get_the_post_thumbnail(null, ‘shop_catalog’);

It sounds like you may be using a custom snippet or modifying your theme in some way. Could you please share a copy of your site’s System Status? You can find it via WooCommerce > Status. Select “Get system report” and then “Copy for support”.? Once you’ve done that, paste it here in your response.

Are you using a child theme to make those customizations?

Hi there @elmersw,

We’d be happy to help you with your site. Although you may have a similar issue to the one were working on here, we’ll be able to help you more effectively if we work in a new thread for your site.

Please create a new support topic here to get started with troubleshooting.

Thanks!

Hi there @savvae,

Thanks for reaching out!

I believe that you can add some custom code to your theme’s functions.php file using this Code Snippets plugin to achieve this.

Please take a look at this post for specifics and some example PHP code to try.

If that doesn’t work for you, could you please share a copy of your site’s System Status? You can find it via WooCommerce > Status. Select “Get system report” and then “Copy for support”.? Once you’ve done that, paste it here in your response.

Thanks!

Hi there @elcohaul,

Thanks for reaching out!

With the release of WooCommerce 6.8.1, there was a bug reported that sounds very much like what you’ve experienced with the default Shipping Zone/Method. I’m sorry to hear this affected your site’s incoming revenue, and understand this is definitely not desireable.

WooCommerce is free and open-source, and we rely on and encourage users to be active in the reporting of any issues encountered. You can read the bug report and find information on the related fix here.

While we make every effort to test for and eliminate issues from each release, we’re unable to cover all eventualities when it comes to compatibility and existing site configurations. We always recommend testing any updates to WooCommerce or any other plugin in a staging or development environment before launching the update on a live site.

If you don’t have (or your host doesn’t provide) a staging site already, this free WP Staging plugin is an easy way to create and maintain one for such purposes.

I hope this is helpful for the future! Let us know if you have any other questions. ??

Hi @saraeee,

Thanks for sharing those screenshots and elaborating on how you were able to solve the issue with the import.

I’ll mark this thread as resolved for now. Feel free to reply and reopen it if you need any further assistance.

Thanks!

Hi @contremaitre,

Thanks for sharing that System Status Report!

You mentioned previously:

The user tried on a different device/browser with the same issue. But he also tried a regular order (not subscription) and it worked. Only the subscription fails every time.

However, I’m not seeing any subscription plugins installed or active on your site. Can you clarify what kind of products these are, since you say payment with Stripe works with all others?

Thanks!

Hi again @triptikon,

that appears to be correct, but it doesn’t work. And the tests doesn’t show incompatibility

Can you confirm which alternate theme you tested with? We recommend testing with a default option such as Storefront or Twenty Twenty-two.

When you did so, did you also test with all plugins aside from WooCommerce and WP Job Manager disabled?