Sol J. a11n

Hi @gnetconsulting

Let’s skip running the step to “reinstall” Pinterest for now and we’ll use it as the last resort.

As indicated by my colleague, very likely the affected products don’t match. In the log, it says the problem is with the variation while we don’t see the product itself a variable product with variations: https://mariakillam.com/product/white-is-complicated/

Link to image: https://d.pr/i/H33XnW

My question is that, was this product a variable product before but at a point it was change to a simple type of product?

If it’s a variable product, it’s look like this: https://d.pr/i/7Akata

But if it’s a simple product, it’d look like: https://d.pr/i/3uIqw1

Let’s say you intend to use it a simple product now. Let’s try the following steps:

• Duplicate the affected product: https://mariakillam.com/product/white-is-complicated/
• Rename that duplicated product so you know it’s the duplicated product
• Adjust the detail: https://d.pr/i/4SSh0Y
• Then click update

Typically, the feed file is updated every 10 mins in WooCommerce and pulled by Pinterest every 24 hours to update the catalog on Pinterest. Let’s wait and see if the product is synced well to Pinterest.

If it’s synced, you can hide the old product, and keep this new duplicated product, feel free to swap the title if required

Hi there I see we’re already communicating via a ticket there. I am closing this for now.

Hi @ecomsight

Do you have exact full steps to replicate the problem?

What I understand, it would be:

• A guest is placing an order, they complete the checkout form.
• They submit an order clicking the button.
• They’re redirected to thank you page, but they’re asked to supply an email.

Is that correct?

Also, please take a screenshot of your Accounts & Privacy setting at WooCommerce > Settings > Accounts & Privacy.

We recommend https://snipboard.io for sharing screenshots – please follow the instructions on the page, then paste the URL in your reply.

Please contact us at WooCommerce.com > My Account > Support. Because we need to verify your information, like asking for the detail of your website and business registration, which can be not suitable in public.

You may need to create an account before you can access that page.

Please include a link to this forum thread, so that we can keep track of what’s already been done.

We will be able to help you further there.

Hi @dkdgarrett

To avoid any conflict possibility, have you tried to clone the site, and then on the cloned site, just keep WooCommerce core plugin only, and see if the problem is still reproducible?

Hi @staxwp @staxwp

Are you folks using WooCommerce Subscriptions with Braintree for WooCommerce?

Subscription plugin is a premium plugin you can get the support by creating a ticket directly on WooCommerce.com.

Please contact us at WooCommerce.com > My Account > Support. You may need to create an account before you can access that page.

Please include a link to this forum thread, so that we can keep track of what’s already been done.

We will be able to help you further there.

Hi @jtowell

They keep adding odd comments like “5962802-zen” on GitHub but I have no idea what this means or if it is getting any closer to being dealt with. 

This means that we receive the same reports from other WooCommerce users.

Hi @krelle

I am not a GitHub user so don’t know if there is a correspondence there. I notice that WooCommerce has just released a new version, but today I encounter the exact same problem again. I try to update a customer field on a WP user, and get the fatal error in WC.

That’s not good, thanks for sharing your experience with us.

@qlstudio

Ticket is not resolved just because the responsibility has been moved elsewhere and as it’s very clear that the bug is not fixed and that the actual users of this plugin are not getting the information needed to understand the process or when this issue will be correctly addressed.

I can confirm that the bug hasn’t been resolved.

You all can see here the progress: https://github.com/woocommerce/woocommerce/issues/35752

Our developers are working on resolving this bug.

Given that we have no extra information, I recommend that you subscribe to that thread on Github to follow the discussion. That’ll allow you to be the first to get any updates from the devs and find out when this is closed and solved. You can subscribe by clicking this button on the GitHub repo (this will only be visible if you have a GitHub account, which can be done for free):

If the image does not load, please click this link: https://d.pr/i/2EmX9K

For now, I will place this ticket on Resolved status as I’d suggest that you can follow the Github thread directly.

Thanks for the patience while our developers are looking into resolving this bug.