Protx VSP Direct v2.0.0

[marcps]

My zen admin says this....

Warning:
You do NOT have PEAR:Crypt_Blowfish installed on your server!
Encryption will not be used for the Credit/Debit Card Details being stored in the Session.

but when i try to install my command line says this

[root@www logs]# pear install Crypt_Blowfish
Package 'Crypt_Blowfish' already installed, skipping

Any help???

[conor]

Hi,

Any help???

This means that your PHP installation can't access the PEAR folder... either your include path is wrong or you have open_basedfir restrictions in effect.

Switch on Debug Mode in the Protx Direct module and put through a test order... it will tell you what your include path and open_basedir settings are. You can then update the include path for your server (php.ini) to also include the path to your PEAR installation (or adjust your open_basedir settings).

Once you've done that then the warning will more than likely go away.

Hope that helps!

All the best...

Conor
ceon

[powersellersuk]

Hi, just wondering if it was an oversight but it seems basket contents do not get sent through the same way as they do via Protx form, What i mean is, they do get sent but via the (Description=) I looked at the way it is sent using Protx form and it looks like it wants number of lines blah blah blah ..


Just wondering if this will be or can be added to this mod??

[webfooted]

I am getting the "Couldn't create a transaction (VRTXInvalidIPAddress)" error message and can't seem to get past it even though I'm following the advice in the protx_direct faqs. I've contacted the web host to check which IP address I should use and they insist I'm using the right one. Is there any other reason why I might be getting that particular error?

Many thanks for any help!

[conor]

Hi,

I've contacted the web host to check which IP address I should use and they insist I'm using the right one. Is there any other reason why I might be getting that particular error?!

No. Your web host's staff are unreliable!

Unfortunately there are few hosts that just don't seem to understand that their clients might want to use software on their server which makes use of web services (e.g. payment systems!!).

The IP address your server is using is different from the IP address your site is hosted at.

Please upload the following script to your server and call it from your browser:
-------
<?php

$url = 'http://ceon.net/WHATISTHISSERVERSIP';

$contents = @file_get_contents($url);

print "Contact me now to let me know that you've carried out this test and I'll get the IP address from my logs!";

exit;

?>
------
As the message says, please let me know when you've done this and I can see what IP address your server contacted mine from.

All the best...

Conor
ceon

[webfooted]

Just wanted to say a public thank you to Conor. I ran the script he posted and he sent me the correct IP address to use. No more error message :-)

Now to send the web hosts a piece of my mind...

[limbo90]

I found this script most helpful when trying to ascertain the IP my host uses (as opposed to the IP my domain is situated at.

For less techy readers, you can use this script by replacing the ceon.net domain with one of your own. You can then locate your raw log files (usually called access.log), open it up in a text editor and check the last few entries for the string WHATISTHISSERVERSIP. Or if you have a command line access then use the 'tail' command to find the last few entries like so:

tail access.log

cheers

limbo90

Hi,

The IP address your server is using is different from the IP address your site is hosted at.

Please upload the following script to your server and call it from your browser:
-------
<?php

$url = 'http://ceon.net/WHATISTHISSERVERSIP';

$contents = @file_get_contents($url);

print "Contact me now to let me know that you've carried out this test and I'll get the IP address from my logs!";

exit;

?>
------
As the message says, please let me know when you've done this and I can see what IP address your server contacted mine from.

All the best...

Conor
ceon

[Pixxi]

Just an FYI ...

We've had a couple of transactions now where the customer has received the error message 'Technical problem contacting the Protx gateway' and no order has appeared in the shop, but Protx has actually authorised the transaction and taken the funds from the customer's card.

On one of these occasions the customer tried (and 'failed') twice with Protx before emailing us. We checked in the Protx admin and no transactions were being shown as received/authorised for the customer, so we suggested he used Paypal instead - and the transaction went through fine.

(We also checked the Protx admin the next day - no transactions for the customer were showing then either).

The customer has just emailed us on getting his card statement and it seems his card was debited twice by Protx. We've just checked the Protx admin again today (3 weeks since the transaction) and it now shows the two authorisations.

Obviously, the transactions apparently not showing in the Protx admin is a Protx problem, and nothing to do with the mod - but it's something to be aware of if anyone has any customers who get the 'Technical error contacting payment gateway' error.

With respect to the 'Technical problem contacting the payment gateway' error, there's a post on the (new) Protx forum here:

https://support.protx.com/forum/Topic277-22-1.aspx

that suggests that the default cURL timeout might be set too low for times when Protx and/or the banks are busy - the default in the Protx integration kit is 30 seconds, same as in the Protx module.

We've upped the timeout to 120 seconds to see if that helps to avoid the problem, although, obviously, customers are likely to give up anyway if they have to wait that long ...

includes/modules/payment/protx_direct.php, line 950:

        curl_setopt($ch, CURLOPT_TIMEOUT, 120); 

[conor]

Hi,

Just wondering if this will be or can be added to this mod??

There are no plans to add it at this time as the Protx Direct module doesn't tend to fail in the same way as Protx Form sometimes can (if there is a problem with Protx Returning to the server so that the order can be created). Protx Direct carries out all the transactions via a cURL call then creates the order... it can only fail if there are server issues and the cURL call never returns (or the PHP script gets interrupted between that point and creating the order... only takes milliseconds so is unlikely!).

If you still want this feature please feel free to request a quote from us.

All the best...

Conor
ceon