X-Cart forums

[photo]

Originally Posted by Steve-C

Photo, where do these appear? Are they in Protx Direct?

Yes that code appears in payment\cc_protxdir.php

[Steve-C]

Ene,

My cc_protx.php won't patch with the patch you have posted. I am on V4.1.8 but I think I may be using cc_protx.php V4.1.10.

I have tried to do it manually but it looks quite different.

Does the patch you posted cover all versions?

[Ene]

1. The list of patches is updated: http://forum.x-cart.com/showpost.php?p=258486&postcount=17

2.

Does the patch you posted cover all versions?

This change adjusts the payment URLs only, so the patch should work for all versions.

Please perform the following steps:

1. Create a new support ticket with the 'Protx Patch - for Eugene Kaznacheev' subject.
2. Attach your 'cc_protx.php' file.

After that I will look into the issue.

[photo]

Originally Posted by Ene

1. The list of patches is updated: http://forum.x-cart.com/showpost.php?p=258486&postcount=17

Thank you Eugene

[TanyaG]

Originally Posted by Ene

1. The list of patches is updated: http://forum.x-cart.com/showpost.php?p=258486&postcount=17

2.

This change adjusts the payment URLs only, so the patch should work for all versions.

Please perform the following steps:

1. Create a new support ticket with the 'Protx Patch - for Eugene Kaznacheev' subject.
2. Attach your 'cc_protx.php' file.

After that I will look into the issue.

Hi Eugene,

Thanks a lot for patches. Is it any reason why all URLs for Protx Direct has on them: sagepay.com:443/. I was checking Sage site and its no URLs with "443" on it.

Many thanks,

Tanya

[Ene]

Thanks a lot for patches. Is it any reason why all URLs for Protx Direct has on them: sagepay.com:443/. I was checking Sage site and its no URLs with "443" on it.

'443' is just a default port for HTTPS, so it is OK to have it there.

[promart418]

Hi all, I have been meaning to update thr Protx URLs to Sagepay URLs on my site for a long time. I have 1 day left to do it now!

Is it as easy as simply changing /payments/cc-protxdir.php, so that all URLs pointing at the old protx domain change to the relevant sagepay URLs?

Or... are there any other files that need updating?

p.s. I tried to apply the patch, but it failed and I don't really understand what it does, so I would prefer to do it manually.

[Isleman]

Originally Posted by promart418

Hi all, I have been meaning to update thr Protx URLs to Sagepay URLs on my site for a long time. I have 1 day left to do it now!

Is it as easy as simply changing /payments/cc-protxdir.php, so that all URLs pointing at the old protx domain change to the relevant sagepay URLs?

Or... are there any other files that need updating?

p.s. I tried to apply the patch, but it failed and I don't really understand what it does, so I would prefer to do it manually.

I am having the same problem with the patch not working . I need to do it manually as I can't process the payments .
Can somebody help with this ?
I will try to change the url's manually to see if it makes a difference.

[seyfin]

The patch provided in the forum (http://forum.x-cart.com/showthread.php?p=258486#post258486) needs to be corrected, as changing the protocol version from 2.22 to 2.23 would cause errors like "Status: 3107 : The BillingSurname field is required".

Actually, the main (necessary) changes are updating the Protx URLs to Sagepay URLs, and you can still keep the protocol version as 2.22. So, you should ignore the following lines when applying the patches provided in this thread:

protx-direct.txt

- $post[] = "VPSProtocol=2.22";
+ $post[] = "VPSProtocol=2.23";

protx-form.txt:

- "VPSProtocol" => "2.22",
+ "VPSProtocol" => "2.23",

However, if you want to upgrade the Sage Pay (Protx) integration in your X-Cart store to use the new protocol version 2.23, you should apply the corresponding patch provided here:

http://help.qtmsoft.com/index.php?title=X-Cart:Protx/Sage_Pay_API_update