Hello I have a very urgent issue

After Akira 2.3.5 to 2.3.6 upgrade, we received no order on our website.

After checking, we notice that the order button appears disabled even if the customer choose the payment method and and accepts conditions.

The button is in fact active, but appears disabled. 

Edit: I found a contingency procedure, by removing {if !$selected_payment_option} disabled{/if} on /root/themes/akira/templates/checkout/_partials/steps/payment.tpl line 126

But it's not optimal

Thank you

Yes because all modules are not compliant with 1.7.8.0. so we prefer to maintain 1.7.7.8 until all acceptance tests are ok

I disagree with your answer. The template is reputed to be compliant with 1.7.x, without to be forced to migrate to the very last version of PS. So that means your customers have to live with that issue that didn't exist on the previous version of Akira?

Is there a way to downgrade version?

You should warn your customer before they confidently upgrade that if they are not in 1.7.8.0 they would meet issues....

Hello

After upgrading to PS 1.7.8.0 and Akira 2.3.7, the bug still remains, I am forced to apply the contingency procedure indicated in my first post

Hello.

Can you have a look on that issue?

Thank you

Hi, I had the same problem.

It's just enough to change themes/akira/templates/checkout/_partials/steps/payment.tpl  line 126 from

<button type="submit" class="btn btn-primary center-block{if !$selected_payment_option} disabled{/if}">

to:

<button type="submit" class="btn btn-primary center-block" {if !$selected_payment_option} disabled="disabled"{/if}>

This solves.

Stefano / coderz.cz