onHikashopBeforeDisplayView in checkout address

Hi,

The trigger onHikashopBeforeDisplayView has a variable &$view
To get the current controller, you can use $view->ctrl
To get the current task, you can use $view->getLayout()
To get the current step, you can use $view->step
To get the current position, you can use $view->module_position
To get the options of the current view, you can use $view->options
So basically, you can have such code so that you skip your code if you're not in the checkout:
if($view->ctrl != 'checkout' || $view->getLayout() != 'show') return;

Supposing that you add your input fields in the address view form, you can use the onAfterAddressCreate and the onAfterAddressUpdate triggers to check the data in $_POST.

We use something similar with the recaptcha plugin which adds the catpcha in the registration form of the "login" view with the onHikashopBeforeDisplayView trigger and then checks the captcha in the onUserBeforeSave trigger called before the new user is being created.
www.hikashop.com/support/documentation/7...-with-recaptcha.html

Hi,

Well, I still don't know what goal you have in doing that. So I can't say for sure what would be the best.
Alternatively, if you don't want to attach your input field to any pre existing form of the checkout, you can use the checkout API of HikaShop to create your own view that you can add to the checkout workflow.
www.hikashop.com/support/documentation/6...tation.html#checkout
You can use the plugins/hikashop/user_points/ plugin as an example as it implements that API to add its own user points view to the checkout. Thanks to that API, you'll be able to display whatever you want, and you'll also be called by the checkout system when the block or the page where the block is are submitted so that you'll be able to find your input data in $_POST.

Hi,

When the view is submitted in ajax it is called once so that it can get the data from the view.
When the whole step is submitted, it is called once so that it can get the data from the view. Also, if all the views of the step tell the checkout that it's ok and it can move to the next step, the checkout will call again that trigger on the views of all the steps prior to the new current step so that they can check that they have the correct data.
So the user_points plugin should also be called twice when you click on the "next" or "finish" button on a step where this plugin displays its view.
So there is no problem. It's just the normal way it works.