Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add to cart spining too long #2827

Open
2 tasks done
tase09 opened this issue Nov 21, 2024 · 19 comments
Open
2 tasks done

Add to cart spining too long #2827

tase09 opened this issue Nov 21, 2024 · 19 comments

Comments

@tase09
Copy link

tase09 commented Nov 21, 2024

🔎 Isolate the bug

  • I have confirmed this occurs in the most recent version of WordPress, WooCommerce, and Facebook for WooCommerce.
  • I have confirmed this occurs when only WooCommerce and Facebook for WooCommerce are active and when using a default WordPress or WooCommerce theme.

✍️ Describe the bug

Recently from today we discovered on many woocommerce websites that the plugin is making add to cart button loading too hard when adding to cart

🚶‍♀️ Steps to reproduce

Add to cart

✔️ Expected behavior

🗃 Logs

@WouterBossen
Copy link

Here for exactly this. turning off the plugin immediately fixes the problem.

@WouterBossen
Copy link

It also impacts the checkout page.

@martinstr
Copy link

Same here; also, clicking from the product listing into a single product takes forever when the Facebook for WooCommerce plugin is activated.

@gruberro
Copy link

We experienced the same issue and had to disable either the plugin or disconnect the connection. The error seems to be related to the Facebook app managed by Automattic, as the app is no longer available and requests to FB are timing out.

An example error is:

2024-11-21T08:55:53+00:00 NOTICE Response
code: 400
message: Bad Request
body: {"error":{"message":"Cannot call API for app xxx on behalf of user xxx","type":"OAuthException","code":200,"fbtrace_id":"AZq0AEzSlTFR-xxx"}}
 CONTEXT: {"_legacy":true}

@aquezada
Copy link

Here for exactly same problem!

@WouterBossen
Copy link

We experienced the same issue and had to disable either the plugin or disconnect the connection. The error seems to be related to the Facebook app managed by Automattic, as the app is no longer available and requests to FB are timing out.

An example error is:

2024-11-21T08:55:53+00:00 NOTICE Response
code: 400
message: Bad Request
body: {"error":{"message":"Cannot call API for app xxx on behalf of user xxx","type":"OAuthException","code":200,"fbtrace_id":"AZq0AEzSlTFR-xxx"}}
 CONTEXT: {"_legacy":true}

Can confirm the issue is also happening when viewing uncached single product pages.

@Aironas47
Copy link

Aironas47 commented Nov 21, 2024

our company facing same issue. We had to disconect more than 50 ecommerce stores and turn of facebook plugin. Hope this problem will be resolved soon

@wahidnory
Copy link

wahidnory commented Nov 21, 2024

Same issue here, solved directly after disabling the plugin. It affected the entire site. Caused very long load times and sometimes even time outs.

@tase09
Copy link
Author

tase09 commented Nov 21, 2024

We experienced the same issue and had to disable either the plugin or disconnect the connection. The error seems to be related to the Facebook app managed by Automattic, as the app is no longer available and requests to FB are timing out.

An example error is:

2024-11-21T08:55:53+00:00 NOTICE Response
code: 400
message: Bad Request
body: {"error":{"message":"Cannot call API for app xxx on behalf of user xxx","type":"OAuthException","code":200,"fbtrace_id":"AZq0AEzSlTFR-xxx"}}
 CONTEXT: {"_legacy":true}

so you are saying the app will be discountinued ? so we need to change also the feed of products? they will stop to sinc?

@gruberro
Copy link

We experienced the same issue and had to disable either the plugin or disconnect the connection. The error seems to be related to the Facebook app managed by Automattic, as the app is no longer available and requests to FB are timing out.
An example error is:

2024-11-21T08:55:53+00:00 NOTICE Response
code: 400
message: Bad Request
body: {"error":{"message":"Cannot call API for app xxx on behalf of user xxx","type":"OAuthException","code":200,"fbtrace_id":"AZq0AEzSlTFR-xxx"}}
 CONTEXT: {"_legacy":true}

so you are saying the app will be discountinued ? so we need to change also the feed of products? they will stop to sinc?

I don't know what happened with the FB-app that is required for the integration. No idea whether it's discontinued, or simply set in sandbox mode due to missing approval of a toc-update 🤷‍♂️. I mean the plugin is useless without this app, so I guess/hope this will be fixed soon 😄…

@WouterBossen
Copy link

our company facing same issue. We had to disconect more than 50 ecommerce stores and turn of facebook plugin. Hope this problem will be resolved soon

Without the plugin though, events will not be handled anymore which could seriously impact your marketing strategy on facebook and instagram. That's why this is HUGE! Really hope there will be a fix for this asap.

@tase09
Copy link
Author

tase09 commented Nov 21, 2024

so i found a temporary fix, u can keep enabled the plugin if u put the pixel in parallel with another plugin and it stops messing with the website, so for the moment this is a good fix, events will not duplicate

@WouterBossen
Copy link

WouterBossen commented Nov 21, 2024

so i found a temporary fix, u can keep enabled the plugin if u put the pixel in parallel with another plugin and it stops messing with the website, so for the moment this is a good fix, events will not duplicate

Could you elaborate on this? Am I correct in understanding that you mean inserting the pixel, say, through GTM and not through the plugin?

@Sebastian1005
Copy link

Sebastian1005 commented Nov 21, 2024

We have another issue which seems related.

We cannot connect to Facebook anymore when installing the plugin. It seems the Facebook-APP from the plugin with CLIENT_ID facebook-for-woocommerce/includes/Handlers/Connection.php is deactivated in facebook.

@WouterBossen
Copy link

On my end it looks like the problem has been fixed. Can anyone else confirm?

@gutobenn
Copy link

On my end it looks like the problem has been fixed. Can anyone else confirm?

Yes, it's working again

@gruberro
Copy link

On my end it looks like the problem has been fixed. Can anyone else confirm?

I can confirm as well!

@aquezada
Copy link

Me to!

@martinstr
Copy link

it works now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants