major issues with paid plugin
-
We have encounteres several issues with the paid version of the plugin and we need some immediate assistance. What we wanted to achieve is to implement subscription payment into contact form – so user after going through form should be redirected into paypal and have a subscription created
- After every payment we are receiving error from Paypal that “HTTP/2 stream 1 was not closed cleanly” – I ran more detailed research on it and found that it’s triggered during
$agreement->execute($token, $apiContext);
because of that it doesn’t save properly information about the payment - What is also important, for some reason if such error is triggered it shows to the user entire response from Paypal – so it contains app key and secret! This is unacceptable as this is a very major security breach! I have no idea who though that just throwing var_dump in such place is a good idea? For what you have log files?!
- logs aren’t working properly – so none of these communicates above are saved in debug logs – I’m aware of debug mode – it’s just not working.
- We aren’t able to set scheduled subcription to be unlimitted – we can only set cycles from 1 to 100
- Another major issuer – for some reason it’s set to have a subscription started ~1h after payment and at the same time it has a setup fee configured – so it means that user has to paid twice! Did you even test it?
Also – before I wrote that I made sure that all plugins are updated. I ran tests on it on both php 7.4 and 8.1, in both cases issues appeared.
List of contact form related active plugins on our site:- Accept PayPal Payments using Contact Form 7 Pro
- Conditional Fields for Contact Form 7
- Contact Form 7
Before I started debugging it we had activated at the same time plugins “Accept PayPal Payments using Contact Form 7” and “Accept PayPal Payments using Contact Form 7 Pro”, but when I updated them to the newest version, my wordpress admin panel started crashing – I had to manually debug it and it looks like these plugins have the same function names and because of that fatal error was triggered. After I deactivated free plugin, it started working fine.
That plugin requires a lot of work before it will start normally working, how you can take money for it?
Start from fixing the issue with “HTTP/2 stream 1 was not closed cleanly” as that is the most critical of these. - After every payment we are receiving error from Paypal that “HTTP/2 stream 1 was not closed cleanly” – I ran more detailed research on it and found that it’s triggered during
- You must be logged in to reply to this topic.