Protx VSP Direct 2.4.0

[conor]

Hi,

Is there a known reason and fix for this?

To get payment modules written for 1.3.0-1.3.8 working with Zen Cart 1.3.9 you need to modify includes/application_top.php as the Zen Cart developers added a "security patch" to 1.3.9 which breaks their old payment module format:

Change the code:

[FONT=Courier New]$paramsToCheck = array('main_page', 'cPath', 'products_id', 'language', 'currency', 'action', 'manufacturers_id', 'pID', 'pid', 'reviews_id', 'filter_id', 'zenid', 'sort', 'number_of_uploads', 'notify', 'page_holder', 'chapter', 'alpha_filter_id', 'typefilter', 'disp_order', 'id', 'key', 'music_genre_id', 'record_company_id', 'set_session_login', 'faq_item', 'edit', 'delete', 'search_in_description', 'dfrom', 'pfrom', 'dto', 'pto', 'inc_subcat', 'payment_error', 'order', 'gv_no', 'pos', 'addr', 'error', 'count', 'error_message', 'info_message', 'cID', 'page', 'credit_class_error_code');[/FONT]

to

[FONT=Courier New]$paramsToCheck = array('main_page', 'cPath', 'products_id', 'language', 'currency', 'action', 'manufacturers_id', 'pID', 'pid', 'reviews_id', 'filter_id', 'zenid', 'sort', 'number_of_uploads', 'notify', 'page_holder', 'chapter', 'alpha_filter_id', 'typefilter', 'disp_order', 'id', 'key', 'music_genre_id', 'record_company_id', 'set_session_login', 'faq_item', 'edit', 'delete', 'search_in_description', 'dfrom', 'pfrom', 'dto', 'pto', 'inc_subcat', 'payment_error', 'order', 'gv_no', 'pos', 'addr','count', 'info_message', 'cID', 'page', 'credit_class_error_code');[/FONT][FONT=Courier New]

[FONT=Verdana]Hope that helps!

All the best...

Conor
ceon
[/FONT]
[/FONT]

[Rigel]

Just wanted to say a huge thank you to Conor for help above and beyond.....

The mod is a breeze to install (though admittedly I haven't yet linked it up to payment etc.).

I have now managed to port it all from the development server to the live one Conor - and all seems ok so far, fingers knotted.

Thanks again.

Rigel

[plymgary1]

Hi Conor,

Hope you're well.

I received a message from Sagepay that reads:

We’ve noticed you’re still using the old Protx URLs to send transaction information details to Sage Pay. As part of our system upgrade we now need you to make a minor change to your system by starting to use the Sage Pay URLs as soon as possible.

What do I need to do to make sure everything works okay?

Thanks,

Gary

[Rigel]

Newbie,

All you need to do is to amend your config files to point to the secure pages. I can't remember where on the faqs this is, but that's it - both configure.php files.

Am about to do this with my site so if anything different, will let you know.

Rigel

Sorry - couldn't find your post

"Yes Conor is a great help and thanks to Ceon too.

I'm stuck with one thing though..

How do I force the payment page to be https rather than http?

There's no instructions and this is first time I've ever used SSL certs.

Thanks
***************
"

[conor]

Hi,

Hope you're well.

Thanks for the nice sentiments. I'm actually very unwell at the minute but I should start to get better in a month or two.

I received a message from Sagepay that reads:

What do I need to do to make sure everything works okay?

You have until September 30th to do something about this. You can either upgrade to a Sage Pay module now or wait for a new Sage Pay replacement for the free Protx Direct module. I'll get something sorted before September 30th but can't say when before then (for the reason above ;) ), it could even end up being late September. The current version of the module will work fine until then so if you want to continue using it that's fine, just ignore any messages from Sage Pay as they'll more than likely send a few more until that date saying the same old thing, basically reminding you about the Sep 30th deadline! :)

All the best...

Conor
ceon

[plymgary1]

Hi,



Thanks for the nice sentiments. I'm actually very unwell at the minute but I should start to get better in a month or two.


ceon

Thanks Conor. Oh no, I hope you're feeling better soon.

[plymgary1]

Hi Conor,

Hope you're feeling better. I updated to the sage pay URL's, thanks.

I had a customer call me today trying to pay with a maestro card. She got to part 2 (3D secure verification) and tells me she was presented with a dropdown box that only went as far as 1995!

Is there something I need to change in my php files or sql database?

Many thanks,

Gary

[conor]

Hi,

Hope you're feeling better. I updated to the sage pay URL's, thanks.

Thanks, not yet but hopefully soon.

I had a customer call me today trying to pay with a maestro card. She got to part 2 (3D secure verification) and tells me she was presented with a dropdown box that only went as far as 1995!

I've never come across such a problem before. Please contact me via this address as I'll need to know more.

All the best..

Conor
ceon

[amdowney]

Hi I'm using 2.6.2 and have just realised there is no option for Maestro?? How do I add this?

[conor]

Hi,

Hi I'm using 2.6.2 and have just realised there is no option for Maestro?? How do I add this?

That option is only available in the commercial distribution as 3D-Secure is required for Maestro.

All the best..

Conor
ceon