Despite the beauty of the very flexible Checkout Pages / Panes system, the Off-site redirect Pane needs some love.

* It's a shame to have a single Page to show a simple button.
* Despite being a Pane, it currently needs it's own page since it doesn't play well with others
- If you put the pane on another page, you get the off-site redirect button PLUS the "back" and "continue" buttons (labels might be wrong there, working from memory)
- If you put, let's say, "Review" pane on the redirect page, it works pretty nicely, but you lose the "back" button.

I think a consistent solution is to:
* Add a "back" button to the Off-site redirect page
* Dunno how to handle the "Proceed to Payment" button, seeing as how the functionality will be different than "Proceed" to next Checkout page
If this last can be handled dynamically, then the placement / order of the Off-site pane / page becomes transparent....

Comments

rszrama’s picture

rszrama commented

Ahh, this is a tad incomplete, in that the page is meant to automatically redirect on pageload via a JS form submission. The button should only be present if JS is disabled... and yeah, we do need a way to lock that page down. I've been taking the approach that it's always defined (and therefore visible in checkout configuration) but bypassed if a non-redirected payment method is selected in checkout. I wonder if instead we should conditionally add the page based on the current checkout process... not sure.

oz_an’s picture

oz_an commented

I really couldn't understand what this page does. Why do we need a client to push another button after a review page. I'm using a redirected service and I don't want the user see all the form hidden fields that I send to the server including the total amount of the order.
(I thought if I set the 'offsite_autoredirect'=> true, redirect form would be automatically submitted but it didn't. Maybe I couldn't grasp the parameter).
Is there a way to auto-submit of the redirect form other than js?. I see no need to render and expose the form.

rszrama’s picture

rszrama commented

You have to render and expose the form (and have something like JS automatically submit the form on pageload) because there's no way to POST data to a third party service and redirect the customer there at the same time any other way. You can POST stuff using cURL, but that doesn't incorporate the necessary redirect.

rszrama’s picture

rszrama commented
Issue summary: View changes
Status: Active » Closed (fixed)

Just closing this out as completed a long time ago. : )