Order total issue

We our just about to release our 1.2.0 update. When that is done we will begin on our 1.2.1 list, and I am adding this to that list. We’ll have a developer try to reproduce the problem and get it resolved asap.

There is a another issue in paypal plus. When user fill up all details on checkout page, place order button should become enable for further process but button remains disable though user fill up all details and select a payment method. If i remove disable attribute from button then validation is not working on checkout page. It skips validation and redirect to paypal payment page.
My website is live right now so i need solution as soon as possible anyhow so please help me out from this bug.
Thanks

We are a team of two (with really just one primary developer) so we’ll get to this as quickly as we can, but I am not exactly sure when we’ll be done with it. We have other things that are a higher priority right now due to more users requesting it.

If you would like to make this a priority you could submit an order for premium support, and then we can bump this up on the priority list. You’ll need to submit the order for two hours if you choose that option.

Otherwise, we’ll still get it done as quickly as we can in our normal routine.

Thanks for the response.

I am facing another issue with the paypal plus for cart total or order total on checkout page.
When user chooses his country or change his country, order total is updated as per tax calculation for that country but this total is not updated for paypal plus as it is taking old price. There was a same issue with applying voucher code but i solved it manually through code by rendering paypal plus again though it is not a good solution. For country’s tax calculation i need to change so much things which is not possible for me right now.
How can you irresponsible like this? you should test all criteria and scenario for this as it is used for payment gateway.
If you have any solution for this then let me know because it might be helpful for me.
Thanks.

I got your other message about this, which I’ve added to our GitHub repo. We’ll get it worked out ASAP. It’s scheduled for the 1.2.1 update.