Closed whitehawkJulie closed 8 months ago
Hello @whitehawkJulie
You have reached out to open GitHub forum with a support request. We utilize GitHub mainly for development activities, so I would like to ask you to reach out to the support team directly for more guidance.
This looks a lot like this issue: https://github.com/woocommerce/woocommerce-paypal-payments/issues/1816 We have got a thread open for this, but since it does not have a direct impact (failing orders or critical site failure), the priority is lower for such cases. I have added this report to the bug and asked the team if this can be investigated. It might be good to open a private support thread with us, so we can more easily request for additional details on your site and the issue (logs), instead of communicating via this public forum. I would advise to at least follow the related GH issue, since we use that one as the main GH thread for development if the dev team needs to make any update to the plugin for this issue. I would advise you to see if onboarding your account with the connect wizard might help resolve the issue, and possibly to reach out to PayPal Merchant Technical Support to have them have a look at the backend to see why these requests are being sent. They have access to verify the backend; we don't.
I'll mark this thread as resolved, but leave the first GH thread open for further dev activities in case required.
Kind regards, Joost
Thanks so much for your reply. We've moved to a different plugin, so won't pursue further help. But thanks!
On Tue, 13 Feb 2024 at 18:58, Joost van de Vijver @.***> wrote:
Hello @whitehawkJulie https://github.com/whitehawkJulie
You have reached out to open GitHub forum with a support request. We utilize GitHub mainly for development activities, so I would like to ask you to reach out to the support team https://woocommerce.com/document/woocommerce-paypal-payments/#get-help directly for more guidance.
This looks a lot like this issue: #1816 https://github.com/woocommerce/woocommerce-paypal-payments/issues/1816 We have got a thread open for this, but since it does not have a direct impact (failing orders or critical site failure), the priority is lower for such cases. I have added this report to the bug and asked the team if this can be investigated. It might be good to open a private support thread with us, so we can more easily request for additional details on your site and the issue (logs), instead of communicating via this public forum. I would advise to at least follow the related GH issue, since we use that one as the main GH thread for development if the dev team needs to make any update to the plugin for this issue. I would advise you to see if onboarding your account with the connect wizard might help resolve the issue, and possibly to reach out to PayPal Merchant Technical Support https://www.paypal-techsupport.com/s/contactsupport to have them have a look at the backend to see why these requests are being sent. They have access to verify the backend; we don't.
I'll mark this thread as resolved, but leave the first GH thread open for further dev activities in case required.
Kind regards, Joost
— Reply to this email directly, view it on GitHub https://github.com/woocommerce/woocommerce-paypal-payments/issues/2024#issuecomment-1940809680, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACOB3WVIUB5KVZP6LFDKFU3YTMTJZAVCNFSM6AAAAABDCUFVC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBQHAYDSNRYGA . You are receiving this because you were mentioned.Message ID: @.*** com>
Describe the Bug
When I activate the plugin, my website slows down horrifically (and/or 504's my site), and I get a bunch of errors as shown in the image. It can take minutes to load a single back end page. If it doesn't 504, Query Monitor shows me these:
Here's the full stack trace of one of the failing calls, if that helps:
It even happens when I first activate the plugin - it's not even set up with WooCommerce yet, so shouldn't even be being called yet, surely??
To Reproduce
Environment
I have no caching plugins, and turned off all server level caching, and that didn't make a difference (as per this which seemed similar to my issue)