Protx VSP Direct 3.x

Hi John,

zilla:

is there something i'm missing in the configuration?

Have you added a 3D-Secure rule in the admin? If so, have you made sure that you **have **ticked allow MPI errors?

If you have done both of those then the answer is simply that your bank isn't requesting 3D-Secure authentication for the cards you are using.. Protx/Sage Pay has no control over this so changing settings won't affect the outcome. Unfortunately 3D-Secure is a bit like black magic.. sometimes I get asked with my own card, sometimes I don't, it's very strange!

If you need any more help with this please don't reply here but contact me privately at this address.

All the best..

Conor

Hi Conor
Thanks for that... I'd already added a rule but hadn't allowed the mpi errors... I've changed it now so I guess I'll just have to wait and see (i've just tested it and it didn't ask for it), but like you say it may come up or it may not!
great mod though, thanks for your help... and also for your help via jsweb regarding my super tracker issue... turned out i just needed to upgrade it to the current version!
Cheers
john

Hi Connor

First of all I originally posted this in the wrong thread so apologies for that. It is meant to be here in the full commmercial version thread.

I have your protex (now sage pay) module on my site and I have just migrated to a new server. I have, of course made sure that I have updated my sagepay account with the new IP addresses and all seems to be working ok with cc's being transacted fine. However I have one small (?) problem in that if a customer makes a mistake, or their card is declined, or anything other than a perfect transaction I get a white screen. In the address bar of the browser I see a long winded url with the basis of what's wrong wit hthe transaction (eg, issuing bank declined coz the buyer is skint) but nothing actually on the page.

Do you have any ideas why this may be?

Incidentally this was the case with the site when migrated with the 'old' protex module and in tha last few days I have downloaded the update - sagepay module and get the same error. Could it be a pemissions issue as my new host will not allow 777 permissions?

Cheers

Rob

I have sorted this out following several steps previously posted in this thread.

Thanks

Rob

ajlisowski:

Im having an issue similar to what a user a few posts ago had. We originally had the free version of this module installed and it worked great, but we needed support for Meastro so we upgraded to the 3.61 version.

Now in test mode, successful transactions are fine, but ones that fail bring the user to a blank page with error in the get variables of

|lt%3B|p+class%3D"ErrorInfo"|gt%3B|The+card+number+entered+is+invalid.+Please+check+the+number+and+try+again%2C+try+another+card+or+|lt%3B|a+href%3D"index.php%3Fmain_page%3Dcontact_us"|gt%3B|contact+us|lt%3B|%2Fa|gt%3B|+for+further+assistance.|lt%3B|%2Fp|gt%3B|

Any help?

Hello, did you manage to get this sorted out? I understand it was supposed to be Mod-Security causing the error, but even when the host said they switched it off for me the blank page issue is still occuring on a failed transaction?

Thanks
Sam

In your /includes/modules/payment/ folder are the various payment modules available in your store.

Find the one related to the module that's giving you the problems, and open it in your favorite text editor.

Search the file for this:```
payment_error=

Paste that line plus the 10 lines above and 10 lines below it ... into a reply here.

Hi,

Sam has got this fixed now. I'm going to release a new version of the software later in the month which fixes the problem he had.. an incompatibility with the new security ciode being added in 1.9.x and 2.0.0. The error_message paramater was "too long" for this code so the new vedrsion of the module will pass all messages using the session and the messagestack.

All the best...

Conor

Was just about to post about this, Thanks for the advise Dr Byte and also to Conor for your support on the module, :smile:

Hi,

I have had the protx direct module installed and working for some time now and working fine but today i got this..

PROTX DIRECT: You have “Store entered details temporarily in session” and “Use Blowfish Encryption” enabled but your PHP installation does NOT have access to PEAR:Crypt_Blowfish on your server!

Either consult the documentation (especially the FAQs) to see how to get Blowfish encryption working on your server, change “Store entered details temporarily in session” to “No”, or disable Blowfish encryption.

It is not recommended to disable Blowfish encryption if there's a chance someone can see the contents of the “sessions” folder on your server (which may be possible if you are on a shared server) - this is left up to your own descretion.

The current values for the various settings on your server follow. These are, without a doubt, the values currently set for these settings, available to PHP on the shop's side, no matter what the admin, your control panel, the Server/Version Info or phpinfo() etc. may say!

Info to help enable Blowfish support...

It would appear that the PEAR:Crypt_Blowfish package is not on your include path or is being blocked by open_basedir restrictions. Please check that Crypt_Blowfish is installed in your PEAR library and that the path to the PEAR:Crypt_Blowfish package is also in your PHP installation's open_basedir configuration setting.

Alternatively, your server may have more than one PEAR installation and the PEAR:Crypt_Blowfish package may not have been installed in the “correct” PEAR library folder - please check that you are using the correct PEAR library if you have more than one on your server.

Current Include Path: .:/usr/lib/php:/usr/local/lib/php

Safe mode in use?: no

open_basedir restricted directories: /home/jaso3019:/usr/lib/php:/usr/php4/lib/php:/usr/local/lib/php:/usr/local/php4/lib/php:/tmp

I have no idea whats going on... or what to do? HELP!!!