eCart Checkout Wizard - not saving order details to database.

Having re-ran the eCart Checkout Wizard, making sure to uncheck the "I don't want to store my order details to database" checkbox, we've run a successful test transaction to Sage Pay but the order isn't being saved to database?

Pages attached.
Thank you.
NJ

I think the code is added to the checkout_success page in the SagePay process. Can you send me a copy of that page?

Attached. Thank you.
NJ

Add the protx include file to the top of the checkout success page:
<?php
require_once("WA_eCart/checkoutScripts/Protx_VSPForm.php");
?>

make sure you have edited that file and put in your protx password in the first line.

Then change the triggers on lines 19 and 52 from:
if (isset($_POST["Payment_submit"]) || isset($_POST["Payment_submit_x"])) {

to:
if ($Protx_VSPServer_Profile['Success']) {

That has not resolved the matter. Both pages attached.
Hope you can resolve this for us.

Thank you.
NJ

Please reply to the other open thread with contact information and we can debug this in a screen sharing session.

All set here. Let me know if you're still able to do that today. Thank you Ray.

Regards
NJ

This was because you still had an older version of the protx_vspform.php file. We downloaded the latest and it should fix this issue.

In the orders table, that's automatically created by the eCart Checkout Wizard, there are the following 5 fields:

TransactionCode
TransactionID
SecurityKey
AuthorizationNumber
SignatureString

Whilst the order and order details are being stored to the relevant database tables, these fields are blank which means we've no way of cross referencing the orders in Sage Pay.

There is also an OrderComplete field which just defaults to a value of 0. Is that field simply to allow us to build in a "dispatched" notification - updating that value to a 1 for example to signify that it's been dispatched (and therefore completed)?

Thank you.
NJ

That information should be updated on the success page. Can you include a copy of it so I can see why it might not be working?