Upgrade to protocol 2.23 - Simulator won't work with older versions
vivianspencer - March 5, 2009 - 16:24
| Project: | SagePay (former Protx) Direct Payment Gateway for Ubercart |
| Version: | 5.x-1.3 |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | hanoii |
| Status: | closed |
Jump to:
Description
I'm currently setting up an ecommerce site and I get the following error in my logs when putting a purchase through using the VSP Simulator
"Payment failed: Incorrect VPSProtocol version. The value should be 2.23, not 2.22"
According to Protx they've updated all of their services to use the 2.23 protocol, but every service apart from the VSP Simulator is backwards compatible whereas the VSP Simulator only supports 2.23.
You can read more about it here: https://support.protx.com/forum/Topic7730-22-1.aspx.
I've had a look at the new protocol and the changes look straightforward; I'll be making a patch for this as I need the functionality
#1
Thanks for letting me know, and for setting out to patch it. :-)
#2
This sounds exactly what I am looking for! Would be very much appreciated if you could provide the patch once finished! Thanks alot. :)
#3
#4
#5
Has any progress been made with this one?
#6
bump....
has this patch been completed at all???
#7
Any progress here?
It would also be great to have a protx compatible module for 6.x.
#8
The upgrade to protocol version 2.23 has been implemented, tested with the simulator, and committed to CVS.
#9
Automatically closed -- issue fixed for 2 weeks with no activity.
#10
Has this been fixed?
#11
Closed issues are generally fixed, or has been closed for a reason. It's a good practice to read the whole issue thread to get an idea of what happened before. As commented in #8, this issue has been fixed.
#12
I did read the whole thread, but I wanted to confirm it 100%. I'm making a quote to a client, and this gateway is one of the major components of the gateway. If it turned out there were still problems, then I'd be offering something I couldn't provide.
No need to be rude about it. Like me ma always said - if you don't have anything good to say, don't say anything at all. Was it really that big of a deal to take eight seconds to type out that post?
But, all berating aside, thank you for confirming it has been fixed. That's what I needed to hear. Feel free to leave out the extraneous attitude next time.
#13
I am sorry if it sounded rude or with an attitude, not really what I meant. It's sunday and recently woke up, and over the years, I got a lot of issues re-opened with no reason and re-asking questions that were answered in the same issue queue, so I just tried to give an advice that just in case you were new to drupal. I should have checked your profile and notice you are not.
Anyway, sorry for that.
#14
Thank you very much. Either way, I appreciate the speed of your response. Have a nice Sunday.