Additional Checkout Phase Required (V4)

[GraemeG]

Hi
This will test you .

I need to break out of the checkout phase immediately after the customer has chosen their payment method and clicks next/continue.

I appreciate this is going to be an orderscript.pl hack, but I would like to know how I can sense the "cash on delivery" method so I can divert the customer to an intermediary page (application form) which upon completion will divert the customer back to the order confirmation. It's a little like the OCC operation, but without leaving the server or encrypting data between 2 servers.

The reason for this, I want Actinic to ignore orders where customers do not complete the (new) form. This will also prevent the customer receiving an email about the order, should they fail to complete the form.

Not completing the form would therefore be the same as pressing cancel during the checkout process.

I appreciate that I will have to pass the form contents of order01 and 02.html to the intermediary page and resubmit the data back to the perl script (to mimick the next or continue button of the original order02 page) upon submission.

I know that I could edit the code that handles the order02.html next button (I have code to check the OCC server is live before submission) to change the form handler url, but I'd rather achieve this via the orderscript.pl file.

I'm not looking for a complete solution here, just a starting point and maybe some procedural advise (ref the perl routine)

Any help, as always, is greatly appreciated.

Tx

[Robert_Taylor]

Checked with the Actinic development team and received the following which should help...

"As a starting point, you could look at Actinic.pm. This collects all of the data supplied from the submitted forms and save them in a global hash. When the Orderscript detects the payment method has been submitted then it can display the additional form. The form will need to include hidden fields for all of the input parameters. When the new form is submitted and accepted the Orderscript can first process the new fields and if all okay then resume with the next stage of checkout as if the previous Actinic form had been submitted.

The new form should use different variable names from Actinic to avoid overwriting of the Actinic variables.

To detect the required payment method check the input variable PAYMENTMETHOD for 'Cash on Delivery'."

Regards,
Robert