• 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

    1. 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
    2. 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?!
    3. 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.
    4. We aren’t able to set scheduled subcription to be unlimitted – we can only set cycles from 1 to 100
    5. 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:

    1. Accept PayPal Payments using Contact Form 7 Pro
    2. Conditional Fields for Contact Form 7
    3. 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.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter domioku

    (@domioku)

    So it looks like that

    $agreement = new \PayPal\Api\Agreement();
    $agreement->execute($token, $apiContext);

    is not working properly because you are triggering there deprecated endpoint

    https://developer.paypal.com/docs/api/payments.billing-agreements/v1/

    Plugin Author ZealousWeb

    (@zealopensource)

    Hello @domioku,

    Thank you so much for reaching out and for reporting this issue. We are currently updating the plugin and will release the latest version soon.

    Could you please create a ticket for this issue using this link ?

    If you have any questions, please don’t hesitate to ask. I’m here to assist you.

    Thank you,
    ZealousWeb

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.