[#6792] CB Subs problems with the eWay plug-in

Hi,
We have added an eWay gateway to CBSubs and have been testing it with a live account and small value transactions. It appears to be setup correctly, it works fully, but the wait times are excessive (up to 8 minutes). We worked with the eWay help desk on the issue and a Live Chat transcript of the dialog is attached. eWay believed the problem to be with the website code or the host. We referred this chat to the website developer (I am the user project manager) and they have said it is a problem within the CBSubs code. The website is hosted on AWS with a Ubuntu server. Could you assist on where to go next? (A separate PayPal gateway is working well).

Regards, Robert

The request taking a long time is an HTTP request to eWays server to generate the payment URL to redirect the user to. It's an outbound call to their below API endpoint.

au.ewaygateway.com/Request/

There's nothing we can really do about this. It's either a slow down with your server making the HTTPS call, processing the XML, or a slow down with eWay handling the request.

Hi Kyle,

Further work by our developer found a "bug" in the CB Subs code.
The developer's description is as follows: "It was a CB paid subscriptions bug. We have checked the code of this plugin (see the file: components/com_profiler/plugins/user/plug_cbpaidsubscriptions/libraries/cbpaidWeservices.php), and have added a change in the 116 line (please see the snap in the attachment: we have added "/" after $urlParts[0]). The problem was, that the plugin has incorrectly generated the URL to eWay. It seems, that CB-subs works correctly for PayPal (i.e. generates the right URL to PayPal). However, for eWay an adjustment in the plugin code was necessary."

Regards,
Robert

That's not fixing anything. In fact it's completely breaking the HTTP request. That usage is for fsockopen call. The $posturl is the Hostname sent to fsockopen. If it has a trailing slash it will never make the HTTP request and thus appear fast, but it will never work. Did you try your developers change? Results in a white page. I've added a bug ticket to investigate eWay gateway after I'm done with PayPal Pro fixes to see why the HTTP request is so slow; probably just need to make an API usage adjustment.

#6792

Hi,
Yes, we have tried the Developer's change, eWay now works perfectly with real money, no delays what-so-ever. Of course, we can't be positive that thls change is the only change made.
Regards, Robert

My guess is your developer has made other changes and your install likely isn't using fsockopen but is falling back to our legacy Snoopy library, which uses cURL. We have yet to replace that function in CBSubs with Guzzle usage. As that change specifically would break fsockopen. At any rate have added a bug ticket already to investigate and fix.