Checkout Form Dynamic Values

[neo314]

I just asked a question in the general forum kinda related to this, but in the checkout form wizard, I chose SEVER_NAME from the bindings tab and it put this code on the page. Thought it might be a bug.

if ("<?php echo((isset($_SERVER["SERVER_NAME"]))?$_SERVER["SERVER_NAME"]:"") ?>" != "") {
header("Location: ". "<?php echo((isset($_SERVER["SERVER_NAME"]))?$_SERVER["SERVER_NAME"]:"") ?>"); exit;
}

[Ray Borduin]

Not sure why you would choose server name... it isn't a bug, but it doesn't make much sense to do.

[neo314]

Because the local testing server is different from the online developments server is different from the live server.

This relates to an earlier question. I input that server value temporarily until I caould rewrite the code to be "http://".$_SERVER['SERVER_NAME']."/destination.php"

Perhaps you answer in the other forum will help with entering that value in the GUI without generating an error from WA extension interfaces. :D

[Ray Borduin]

I see. Well it appears this is a bug or missing feature and our interface doesn't allow you to have code in the redirect field.

Instead of using:
<?php echo((isset($_SERVER["SERVER_NAME"]))?$_SERVER["SERVER_NAME"]:"") ?>

try using:
" .((isset($_SERVER["SERVER_NAME"]))?$_SERVER["SERVER_NAME"]:""). "

In general, only fields with lighning bolts will support dynamic values. I will log this as a feature request to accept dynamic values in the redirect fields of the checkout wizard in the next version.