swicks
Forum Replies Created
-
Forum: Plugins
In reply to: [WooCommerce SagePay Direct Payment Gateway] Vendor Name IssuesHi
I’m not aware of a solution sorry, Sage brought Protx in Europe and rebranded them SagePay. I assume Sage brought out another gateway payment company in the US.
regards
Steve
Forum: Plugins
In reply to: [WooCommerce SagePay Direct Payment Gateway] Vendor TX CodeThat be the problem then 🙂
It uses an ‘order number’ custom field to retain the sequential number – nice code/plugin.
I’ll take a look at implementing it into the vendor tx code.
Forum: Plugins
In reply to: [WooCommerce SagePay Direct Payment Gateway] Vendor Name IssuesSagePay should have provided you with a valid VendorName. However if you are trying to connect to Sage (US) then this gateway will not work for you.
regards
Steve
Forum: Plugins
In reply to: [WooCommerce SagePay Direct Payment Gateway] Vendor TX CodeAre you using another plugin to generate the order number or are you using woocommerce’s order numbers (post numbers)?
Steve
Forum: Plugins
In reply to: [WooCommerce SagePay Direct Payment Gateway] Vendor TX CodeIt worked for me.
What errors are you getting, it will only work on new orders?
Forum: Plugins
In reply to: [WooCommerce SagePay Direct Payment Gateway] Deferred is spelt wrongHi
Apologies for that, I will push out an update in the next few days to correct this. In the meantime you can access the updated version in development (0.1.7.1)regards
Steve
Forum: Plugins
In reply to: [WooCommerce SagePay Direct Payment Gateway] Vendor TX CodeHi
Within the file ds-sagepay-direct.php (version 0.1.7.0)
line 592:
$this->add_param('VendorTxCode', $this->create_vendor_tx_code());
change to:
$this->add_param('VendorTxCode', $this->create_vendor_tx_code( $order_id ));line 1094:
private function create_vendor_tx_code() { $time_stamp = date("ymdHis"); $rand_num = rand(0,32000) * rand(0,32000); return $this->vendor_name . "-" . $time_stamp . "-" . $rand_num; } // end create_vendor_tx_codechange to:
private function create_vendor_tx_code( $order_id ) { $time_stamp = date("ymdHis"); return $this->vendor_name . "-" . $time_stamp . "-" . $order_id; } // end create_vendor_tx_codeForum: Plugins
In reply to: [WooCommerce SagePay Direct Payment Gateway] Simulator or TestThat’s correct, however the only file that has changed is ds-sagepay-direct.php, so you could just overwrite that.
Regards
Forum: Plugins
In reply to: [WooCommerce SagePay Direct Payment Gateway] Simulator or TestHi Jeremy
I’ve updated the dev version with support for virtual products and the sagepay simulator.
Regards,
Steve
Forum: Plugins
In reply to: [WooCommerce SagePay Direct Payment Gateway] Simulator or TestCan you confirm that everything works with a standard product and I will take a look at the virtual.
Regards
Forum: Plugins
In reply to: [WooCommerce SagePay Direct Payment Gateway] Simulator or TestHi
SagePay needs shipping details, this is taken directly by the plugin from the woocommerce order object. Would there be any reason why in this particular order doesn’t require delivery details or is this happening on all orders?Versions are all upto date, which I have already tested.
For simulator and test you should only use test cards. You can’t test the postcode in woocommerce because of it’s own validation and it’s not a problem it’s failing, it’s just a warning letting you know that an invalid postcode was used.
also, the first line of the address only needs to begin with 88 to validate – you can enter ’88 High Street’ for example
The message makes sense based on your request – this information is mandatory and it will fail.
Is this a collection or a download, should it have a delivery address.
regards
Steve
Forum: Plugins
In reply to: [WooCommerce SagePay Direct Payment Gateway] Simulator or TestYou should of also received a Request email with all the sent details to sagepay.
do you get the same statusdetail message everytime?
what versions of WP, WC & SagePay Direct are you running sa I can try and emulate?
Forum: Plugins
In reply to: [WooCommerce SagePay Direct Payment Gateway] 3D Secure – No OptionThe description doesn’t display in checkout, this is because this particular gateway ‘has_fields’. This means instead of woocommerce calling for the description it calls for the form and the form doesn’t show the description.
To add the description you could modify the code in file:ds-sagepay-direct.php after line 412 (just after the tbody tag)
<tr><td colspan="2"><?php echo $this->description ?></td></tr>Forum: Plugins
In reply to: [WooCommerce SagePay Direct Payment Gateway] Simulator or TestThis is on SagePay’s simulator.
Forum: Plugins
In reply to: [WooCommerce SagePay Direct Payment Gateway] Simulator or TestHi
What opton did you select on the SagePay simulator? The response back from the simulator is controlled by yourself?If you select OK/REGISTERED do you still get the same error?