Closed (won't fix)
Project:
Sage Pay Go Direct Payment Gateway for Ubercart
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
22 Jul 2010 at 10:34 UTC
Updated:
28 May 2012 at 13:40 UTC
The Drupal 5 module puts up this message on the settings page:
Credit card number validation is broken in Ubercart 1.0.
which I assume relates to issues discussed at http://drupal.org/node/270778. If this is still a valid message, what is required to port D6/UC 2 changes to UC1, is it just whats covered by that issue?
Comments
Comment #1
hanoiiI don't think you have placed this issue in the correct project issue queue, is it at all related to the sagepay module?
I am moving it to Ubercart right now as I think it belongs there although I must warn you that drupal 5.x version of the modules are are slowly moving to be unsupported (or very lightly supported).
Comment #2
tr commentedThat string is printed by the Drupal 5 version of uc_protx_vsp_direct.module, so yes, the support request was in the correct issue queue.
Comment #3
Tony Sharpe commentedComparing the code, the changes in http://drupal.org/node/270778 are implemented exactly the same in UC1 and UC2 so is this warning that uc_protx_vsp_direct.module(5.x-1.8) puts out still valid?
Comment #4
hanoiiRight, sorry about that. I have inherit this module after some development, and that was a string that was present from day 1 from the previous development so I didn't have it present in my mind.
IIRC, there was some kind of warning or issue with CC validation in Ubercart (maybe TR can throw some light into this?) but to be honest I am not surei f that warning is still valid, I think you can ignore it and eventually, if the CC ubercart validation fails for you in any case, you can disable it. I generally don't use CC validation, I just let sagepay does its thing and in case of a cc number error, it will complain.
But you are right in that such a warning might be confusing, maybe I'll just remove it.
a.=
Comment #5
tr commentedI don't know what the module author had in mind when he added that "broken" message. Ubercart does only minimal validation of a number before sending it off to the gateway where the detailed validation is performed. Ubercart checks to see if the number is all digits, then computes the checksum according to the Luhn algorithm to ensure the number passes, then checks the first digit of the card number against the enabled card types. It's that last check which might cause a problem for a UK based payment gateway like Sage Pay. #270788: Double big bug : impossible to create an alias for user/register mentions that this first digit check is ambiguous in the case of International Maestro cards (and other cases not mentioned in that thread), so the first digit check really should be re-written. Unfortunately, to check it properly you need to look at the first four or five digits and compare them against a big table of card issuers.
Comment #6
Tony Sharpe commentedI would suggest that after double checking the issue in #3 that the warning is removed as I think the original issue that prompted the message inclusion is fixed.
Comment #7
longwaveDrupal 5 is no longer supported.