nelsonleemiller

I am getting the exact same error with the latest update. If I manually change a subscription it gives the fatal error.

Is this plugin still actively supported? I have not heard a response in 2 weeks. Let me know, otherwise I can report it to WordPress for removal.

No I’m literally applying a payout to one affiliate.

It is not cache, let’s just move past that ??

I think every website has caching, whether at the site level with a plugin or CDN level. I use both a plugin and Cloudways and they have cache. However, your reply about cache does make any sense in relation to the nature of the issue. I don’t think email addresses being removed from a field and payment not sending when it says it did is anything to blame on cache ??

Okay I sent a message with the logs. We also noticed the ones that I found are all PayPal (not happening with Stripe) and have that “Subscription set to Manual Renewal because payment method was not saved at PayPal”

Awesome, that sounds great to hear you are planning some things! I set up your plugin on my site last night and really enjoyed it. The debug tricked was so helpful.

Reply from Cloudways:

We have checked our nginx configuration and it already have required timeouts:

#params for nginx proxy backends
proxy_connect_timeout 1200;
proxy_send_timeout 1200;
proxy_read_timeout 1200;
client_max_body_size 400m;
client_body_buffer_size 128k;
proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;
proxy_temp_file_write_size 256k;
proxy_redirect off;
proxy_buffering off;

If you wish for we changed any option – please let us know.

I think you read it backwards – I was asking this as a feature request – you SHOULD render the button as “Please wait…” because you currently do not and it would be a huge UX improvement.

I’m waiting to hear back from Cloudways ticket now.

Thanks for replying but there were three pending updates, not sure why WordPress takes so long to approve replies.

Regarding the button, a customer mentioned that your plugin does not do what they expected and saw other places, like a “Please wait…” in the button text. So that would be good if you could add that please, even though it is not the issue here.

latest customer said they know they only pressed it once, and waited and it made two orders

I found something else thats weird

USER A – – [02/Dec/2022:14:16:55 +0000] “POST /?wc-ajax=checkout HTTP/1.0” 200 885
USER A- – [02/Dec/2022:14:15:55 +0000] “POST /?wc-ajax=checkout HTTP/1.0” 200 810
USER B – – [02/Dec/2022:09:28:14 +0000] “POST /?wc-ajax=checkout HTTP/1.0” 200 808
USER B – – [02/Dec/2022:09:29:14 +0000] “POST /?wc-ajax=checkout HTTP/1.0” 200 1042

The duplicate request happens exactly 1 minute after the first request, like down to the second

I feel like this is to do with the Nginx setup of the server

https://serverfault.com/questions/523340/post-request-is-repeated-with-nginx-loadbalanced-server-status-499

Is this something I should contact Cloudways hosting about?

We found one thing, for the orders today that were duplicated, I am seeing something in the nginx logs.

upstream prematurely closed connection while reading response header from upstream

both of these happen on the https://127.0.0.1:8080/?wc-ajax=checkout url

So its probably related

That url is hit when the checkout button is pressed

But we don’t know what this means, so we are hoping it helps you understand.

I have one of the best programmers in the world on call (seriously), and he checked everything and cannot see the issue on our end. Importantly, there are no errors in the logs for any of the times this happened and nothing in the logs related to these user ID or orders. This happened 5 or 6 times now in the last week, 2 more today.

I think a possibility is that the server is taking a little extra time to process the first click, and the user is clicking again. Some of them mentioned that “maybe they clicked it twice” but that should absolutely not happen, and if so is a major flaw in your plugin. The checkout button should be blocked until it has finished loading the first request. Can you please confirm if your plugin has this feature, or if we need to program this ourselves (which would be a little absurd)?

@aweissinpsyde Is that an automatic response? I can’t decide if I should laugh or cry at this. You are right – it has been quite some time since YOUR last communication.

I am posting a reply here from PayPal Merchant Technical Support:

Hi Nelson,

Thank you for contacting PayPal Global Technical Support. I'm sorry to hear of the troubles. 

<strong>In this instance, you will need to work with the plugin developer/owner directly. PayPal does not directly support 3rd-party plugins. I did review our XML logs and show that the void request is coming directly from the plugin: </strong>

https://snipboard.io/IutlBP.jpg
Apologies for any inconvenience this has caused. 

Thank you!

Sincerely,

Carlos
Global Technical Support
PayPal