Active
Project:
Ubercart SecureTrading Payment Method
Version:
6.x-1.2
Component:
Miscellaneous
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 Mar 2010 at 18:42 UTC
Updated:
14 Sep 2011 at 20:39 UTC
I've just set up securetrading checkout, using a template and callback reference of 1 (standard setup). I've uploaded callback.txt and callback-f.txt files from the config page. when testing I get an error from securetrading of
Cannot open Merchant Form //merchantfiles/xxx/xxxxxxxxxxxxxx/form1.html
It seems to be looking for form1.html not form.html which is all I should have created from what I've read. Has anyone else had this problem?
Comments
Comment #1
longwaveSo if you upload a copy of form.html as form1.html does it work as expected? From what I remember the SecureTrading documentation is not entirely clear on the use of form.html/form1.html, in both the live sites I administer that use SecureTrading I am using higher callback reference numbers for historical reasons so this issue does not affect me. If you can confirm that form1.html is the correct name when using callback reference 1 I will update the code appropriately.
Comment #2
Tony Sharpe commentedTheir documentation does indeed fall a little short in this area but having talked to them and tested things I can confirm that '1' needs to be added to the various file names even when only using a single callback reference. So it's form1.html, customeremail1.txt, merchantemail1.txt and failureemail1.txt (but no change to callback.txt and callback-f.txt).
Thanks for the great module - works great.
Comment #3
hixster commentedFirst time configuring this payment gateway. I am using the template and callback reference set 1 and have uploaded my form file called form1.html
but I still getting the missing for error.
Also, credit card info on the checkout pages show n/a?
Comment #4
hixster commentedNevermind - i just flushed my caches and the form is being picked up.
Still need info on how to show credit card logos alongside payment info.
Comment #5
longwave