swicks

Hi
I just looked through the previous versions of woocommerce on Github to try to reproduce this issue. It turns out that version 1.4 and above only support WC_Payment_Gateway class it was renamed from woocommerce_payment_gateway on your version.

Apologies it will not work with your version of Woocommerce.

Regards

Steve

In all release updates of this plugin there has been no security patches, they have been feature enhancements and modifications to the procedure calls to WooCommerce as it evolves.

I’m not aware of any security issues with any of the releases.

best regards

Steve

@monzu02 what is safe ? Please explain yourself, little more explanation please? Thank you.

is what safe?

Hi,
WC_Payment_Gateway is a WooCommerce class that 3rd party payment gateways extend. Check that WooCommerce is activated.

I would recommend you upgrade to Version 2 on WooCommerce or if that is not possible try using an earlier version of this plugin 0.1.5 or 0.1.4 which would have worked with your version 1.3.2.1.

regards

Steve

Hi

Sorry, no plans to support the subscriptions plugin.

regards

Steve

Unable to reproduce the error – plugin worked as expected.

ok, so the issue we have is this one transaction appearing to be successful, but wasn’t.

In the admin panel for this order under Custom Fields you should see one or more transactions depending on your payment type. Can you please email [support(at)devicesoftware.com] those transactions so I can assertain what the issue is?

regards

I will update the topic once and the plugin once this has been resolved.

If you receive a notification that an order has been placed, you shouldn’t need to check the status of the payment as the payment should have been successful.

Have you had issues where this hasn’t been the case?

thanks

The fix was setting the content-type header application/x-www-form-urlencoded to all lowercase.

Up until now this wasn’t necessary.

I’ve applied an update to the plugin – version 1.6.2 or higher.

Thanks

please send it to: support(at)devicesoftware.com

regards

Steve

In Test mode can you switch debug on and email me the results before and after and I will atake a look at the responces (make sure you only use test card numbers, the first line of the address starts with the number 88 AND THE cV2 CODE IS 123.

thanks for the heads up – I’ve removed active_cards variable as it’s was planned for a later release.

pushed a new update out…

Steve

Hi, Are you seeing this issue in ‘Test’ and ‘Live’?

‘Test’ you can run without SSL, I wouldn’t run ‘Live’ without SSL.

PCI complience is obviously required, but has no effect on the workings of the plugin.

Test & Live are managed by Sagepay separately, if Test is working and Live isn’t could be a configuration problem with Sagepay.

regards
Steve

Hi

Does everything work in test mode?

I would expect once the payment was taken the order status would show ‘processing’ and when you have sent out the goods you would set the status to ‘complete’.

In the custom fields on the admin order page should show the status of your transactions with SagePay and also in the SagePAy Direct table.

regards

Steve