This is a quick update to let you know the latest Stripe version (9.7.0) which includes a fix for this case we’ve been working on has been released already. It should be available for update now.
Reporting here as well for the community to know that the latest Stripe version (9.7.0), which includes a fix for this case we’ve been working on, has been released already. It should be available for update now.
Thank you for your patience and collaboration in testing this.
I wanted to chime in to let you know we’ve received other similar reports, and our developers are working on a solution which is expected to be released soon.
We’ll keep you posted once that update is released.
Thank you for your patience and collaboration while we worked on this internally.
Leaving a quick note for the community as well: our developers have been able to replicate this scenario, and a PR is already in the works. It should be released in an upcoming update.
Thank you for reaching out about this case. This is certainly an unusual one, and we’ll do our best to help you.
As we discussed in our recent conversation, we’ll continue to investigate this internally and follow up with you via email shortly.
We’ll leave this thread open while we work on a resolution. At which time, we’ll be happy to also share it here so it can help other merchants facing the same scenario.
Thank you so much for chiming in with valuable feedback and sharing your experience here, as we can see this was useful for you, and you’re in turn helping other merchants with the same issue.
We value your contributions and foster community members helping each other; that’s the beauty of the forums!
You could consider using multiple URLs to properly define which trigger/payload is for each, however, if the triggers you’re looking to work with and differentiate are Post updated and Post deleted, while the payload is basically the same, the post status could help you learn which one is which, as deleting the posts would change their status accordingly! 🙂
Thank you for your reply. Similarly, you can create more Webhook URLs for Make to use in every case, however you should be fine with just one, too, as you pass the action as a parameter in the URL. You can decide to work in either way, it’ll work fine for you! =)
At this point, using this plugin, I have successfully retrieved email, name, and what appears to be an encrypted password from newly registered users. I’m wondering if there’s any way to retrieve an unencrypted password from a newly created user. I believe WordPress uses one-way encryption though, so this might just be a pipe dream? Any ideas would be very appreciated, thanks!
With the Pro version of our plugin, the User Created Trigger has an option to send the raw password that could work for you:
As you can see, this payment method isn’t available for Subscriptions, which is in accordance with our documentation. Just to be safe, I tried this with both the new checkout and legacy checkout experiences.
I suggested opening a ticket with our Happiness Engineers for the WooCommerce Subscription premium support since the issue pertains mostly to subscription products (the payment method only fails to appear for those!). However, our docs are the guidance for it, so I think it’s just not available for this additional payment gateway.
I was able to solve the problem. It was probably because I had linked two company profiles on Pinterest. I have now been able to unlink them. I updated the plugin to the latest version and then connected it to Pinterest. It connected to the correct profile and the catalog transfer works again! Yeaaahh!!! :DThank you so much, I’m glad it’s working again. 🙂
Thank you so much for sharing the good news and the workaround so that other merchants facing the same issue can learn how to handle it!
I have created a variable product which includes an option ‘0’ (its variations are digits 0-9). Everything is set up properly, I can see all variations in backend, they are in stock with prices, but in the frontend ZERO is missing. I can see only options 1-9 in the dropdown.
Thank you for reaching WooCommerce support. This is an interesting case! I’ve tried this on one of my test sites to learn more, but I’m afraid I’m unable to replicate this issue, as you can see my variation 0 shows up:
Can you please share a link to your variable product and screenshots of how this particular variation is implemented in the back end? Did you make sure the variation 0 has a price and stock available?
Additionally, I’d like to understand your site properly. Please share with us the necessary information below for us to investigate the issue further:
Which WordPress, WooCommerce, WooCommerce database, and PHP versions are you running?
Which theme do you use, and it’s also up to date?
Do you use any other third-payment plugins for WooCommerce?
Do you set up your variable products with global or custom attributes? (attributes defined on the attributes section on WooCommerce, or only locally defined for this product).
Do you manage your products through any third-party methods besides the default WooCommerce product editor? Maybe an API, an import, a third-party plugin, etc.
Additionally, do you find any errors in your WooCommerce Logs? If so, please share them with us.
Once we have more information, we’ll be able to assist you further.
My question was whether that lower Payment section was a default WC email thing or not.
Thank you for the additional details. This email template isn’t default for WooCommerce, no. You can learn more about our email templates in our documentation here.
I will wait to hear back from QuanticaLab about it.
Sounds like the way to go for this one! 🙂
Cheers! -OP
Viewing 15 replies - 1 through 15 (of 2,100 total)
