insert the order_token into confirmation email

Hi,

You don't need the first step.
You can directly use the tag

{VAR:order.order_token}

<a href="https://www.google.com/search?q={VAR:order.order_token}">Click this link</a>

Hi,

It could indeed be that you're not editing the correct email.
Check in the Customers>Emails history menu. There, you can see all the emails generated by HikaShop (both normal ones and test ones). You can see the "type" of each email, which will tell you which email you need to edit in the System>Emails menu.

Also, it seems you want to change the "order status notification" email.
Note that when you edit this email, you have extra "per status override" buttons on the interface. This way, you can customize the email differently for different statuses.
If you have a status override for the "confirmed" status for the HTML section, the status override will take priority over the HTML section of the main area of the order status notification email.
So it could be that you previously made a customization of the HTML section for that status, and now that you're making a change in the main HTML section, you don't see the changes because of the HTML section for that status is being used.
And when you use the preview button, it's not exactly the same process used to generate the email (because the status of the order is not really being changed) so you don't see the problem there.
Note that this is just a potentiality. I'm not saying that this is the problem you have here.

Hi,

No worries.
If you want your text to be in different languages, like the rest of the email, then you need to add a translation in the override file by edit the languages under the Languages tab of the HikaShop configuration. Then, edit the email, and in the "preload" section, you'll need to add a code line like:

'XXX' => JText::_('XXX'),

'BILLING_ADDRESS' => JText::_('HIKASHOP_BILLING_ADDRESS'),

Hi,

The problem is that there is no tag {VAR:user.user_email}
The tag you want to use is {VAR:customer.user_email}

Please note that there is a button "list of available tags" just above the HTML area when you edit an email.
This will give you a list of all the tags including this one.

Hi,

The checkout can be configured in many different ways, and there are many plugins and other things which can interfere.
So it's hard for me to say what the problem is without analyzing the details.
Could you provide the following ?
- a super admin backend access in order to check your settings
- a FTP access if debug is necessary

You can do so via our contact form:
www.hikashop.com/support/contact-us.html

Hi,

Thanks for the accesses.

The problem is a complex one between the Stripe Connect plugin, the way you configured its payment method, and the fact that you're trying to use a 100% coupon code, and the fact that the payment and the coupon views are on the same step.
This leads to the Stripe Connect's javascript stopping the process to the next step to try to process the credit card fields of the payment method, even though the payment selection area, along with the credit card form has been removed from the page following the use of the coupon code. And since the credit card form is missing, the plugin's javascript can't process anything and thus it doesn't let you move forward.
It requires a full refresh of the page in such a case, so that the javascript of the Stripe Connect plugin is not included anymore and then it lets you proceed.

So, all this means that there are several ways to circumvent the problem:
- don't have the coupon and the payment view on the same step
- configure the Stripe Connect plugin to display the credit card form at the end of the checkout, not during the payment method selection
- configure the PayPal payment method to be the first one. That way the plugin won't add its javascript by default to the page

Now saying that, it's something that still needs to be fixed properly. So I've looked into it and I've made a patch to the checkout / show_block_payment view of HikaShop so that it properly checks whether the payment methods are selectable or not on the page before trying to contact the javascript of the payment plugins. That way, it will allow the checkout to proceed unimpeded in such a case.
I've deleted the view override of that view in your template and added the necessary modifications to that view with a new view override. I've also added the modifications on our end. So for anyone with the issue, updating to HikaShop 6.0.0 or newer will fix the problem.
However, the day you update your template in the future, the view override I've created for your website will likely be overwritten by your template's new version.
Thus this means that you have several things to take into account:
- ideally, you want to report the issue to the template provider so that they can update their template with the new version of the checkout / show_block_payment view file. This will also help others with a similar situation. And if they do it, you won't have to do anything in the future regarding this issue
- Otherwise, after updating the template, and supposing you've updated your HikaShop since then, you'll want to delete the view override of checkout / show_block_payment, so that it will use the default view file, which will contain the modifications.

Thanks !
If you didn't do it already, please consider leaving a review on the JED:
extensions.joomla.org/extension/hikashop/
Each good review there helps us a lot