wbrubaker.a11n

Hi, there is some documentation that you should review here: https://docs.woocommerce.com/document/facebook-for-woocommerce/#how-can-i-get-facebook-to-display-prices-including-tax

You may want to contact the theme author to see if they have some suggestions for the CSS or you may wish to consider using a different theme if yours is incompatible with the messenger and you need that functionality.

I’ve found a thread here that reported a similar problem https://www.ads-software.com/support/topic/sale-price-not-syncing-in-facebook/#post-14442913

In that thread, it was a conflicting plugin that was causing the issue. We suggest conflict troubleshooting to eliminate the possibility of a plugin conflict causing this. There’s some instructions on that here: https://docs.woocommerce.com/document/how-to-test-for-conflicts/

Hi there,

It looks to me like this is being addressed in a ticket at WooCommerce with ticket id 4122401. Do I have that right?

I’ve been in contact with Stripe and they say that Woocommerce generates all of the Stripe webhook requests

That’s not exactly accurate. The webhooks that Stripe sends to your site are, indeed, a result of various payment requests that are sent from your site to Stripe. You can configure which events webhooks will be sent for on your Stripe dashboard. We have a bit of documentation on that here: https://docs.woocommerce.com/document/stripe/#webhooks

Might a possible fix for the backlog of requests be to delete the webhook endpoint and recreate this?

No.

@konjx what does this mean:

+1 for This

Are you saying that the steps you listed fixes the issue for you?

@choppex86 have you tried the above?

https://docs.woocommerce.com/document/paypal-standard/#paypal-ipn-url

I have noticed that payments are being completed successfully

Without the IPN enabled, it is possible that payments are being completed via the PDT. That said, this method is unreliable because it relies on human interaction with your site. If that human completes the payment at PayPal and then closes their browser, the Payment Data Token is not transported back to your site via their browser.

The IPN does not rely on the customer to return back to the site and as such is more reliable.

It is not advisable to have both the IPN and PDT methods enabled simulatanesouly. You can disable the PDT by blanking out the value in the PayPal identity token field.

What settings have you got that enable this:

to authorise the payment via an OTP

If the payment request buttons weren’t showing on the single product page or the cart page then you might have mentioned that earlier. There’s likely something else to account for that.

I’m not able to find anything that I recognize as a WooCommerce single product page on your site. I guess that cartflows is taking over or something like that. That might be behind this. I’d suggest you do a conflict test: https://docs.woocommerce.com/document/how-to-test-for-conflicts/ you can do that on a staging site if you don’t want to turn off features on your live site. Maybe see https://www.ads-software.com/plugins/wp-staging/

I’ve tried to replicate this on a test site here: https://wctesting.tk/shop/ and everything releated to the Stripe payment request buttons works as expected there.

You can also enable debug mode and then view the logs. That might provide you some clues about what is behind this. See Log Debug Messages here: https://docs.woocommerce.com/document/stripe/#setup-and-configuration

Also, while I was looking around, I found that you have a caching problem. If not logged in, a user might encounter an infinite spinner at checkout. This is caused by a nonce being cached on the checkout page which results in a 403 response code to an AJAX call as well as a respnose body to that same call of -1

You’ll want to exclude the checkout page from caching. We’ve got some documentation on that here: https://docs.woocommerce.com/document/configuring-caching-plugins/

There is no way to sync each product individually. If this is something you would like to see in a future version, please do open a feature request on our ideas board here: https://ideas.woocommerce.com/ Ideas there are reviewed by our developers and product managers and prioritized according to demand.

Have you reached out to Facebook support for assistance with the error message that is happening on the Facebook interface? What insight have they been able to provide?

You may want to take that error message to the support team for Webpay transbak in this case.

We are tracking a similar issue here as well: https://github.com/woocommerce/google-listings-and-ads/issues/845

but in that case, the error cleary does call out the Google listings & Ads plugin whereas your error message is coming from the payment gateway.

@psstar1 You did see that the issue was reopened, correct?

Hi there. We have seen one other report with that specific error message. It was resolved in this comment if you want to give that a go: https://www.ads-software.com/support/topic/woocommerce-plugin-fatal-error-while-trying-to-activate-plugin/#post-14473996

Howdy ??

Sorry to learn about the troubles you are having with this. This is not reproducible on a test site of mine here: https://wctesting.tk/

I think that the linebreak in the JavaScript code is a result of the warning message that is being output. I’m not sure exactly the source of that warning but I do expect that suppressing error output would help with this and you will want to do that anyhow. See: https://aristath.github.io/blog/wp-hide-php-errors

If you are able to reproduce this under the following conditions:

1. An unmodified, default WordPress theme such as Twenty Twenty or Storefront active.
2. No other plugins except for WooCommerce and Braintree active.

Please do let us know and we can take a closer look.