Error Message Orders - Forum | JoomShaper
Solved EasyStore

Error Message Orders

Asked by Alex Barendregt 1 year ago Last activity 1 year ago

Hi team,
i had in version 1.5 for a client an error message in the orders overview.
An error has occurred.
0 bcmul(): Argument #1 ($num1) is not well-formed
I updated now all to the latest versions. Joomla 3.5.2 / Pagebuilder and EasyStore 1.6 etc.
Same Problem

Frontend seems to be ok. all other pages as well. Please advice. thank you

Accepted answer

Marked as the solution
Toufiq Senior Staff

Please check now and let me know. Thanks

1 more reply

Toufiq Senior Staff

Hi there,

Thank you for reaching out, and I apologize for any inconvenience caused by this oversight. To better address the issue, could you kindly provide Joomla administrator access? This will enable me to thoroughly investigate the matter and provide you with a prompt resolution.

I appreciate your cooperation and will ensure to get back to you as soon as possible.

Best regards,

Toufiqur Rahman (Team Lead, Support)

Alex Barendregt Asked this

thank you for your answer, access in hidden content

Alex Barendregt Asked this

oh and also none of the orders in july seems to have gotten in. the clients were a success message but the emails never got in to them or to the shop admin.

Alex Barendregt Asked this

looks good thank you for the gast support.
can you tell me in short what the problen was ?

Toufiq Senior Staff

We have installed a patch on your site. We will fix it next release. Thanks

Alex Barendregt Asked this

sorry i found another issue on the settings page.
i get the following error:

Unhandled Runtime Error

TypeError: can't access property "call", n[e] is undefined

Please open the browser console for more information!
Call Stack
d

store/js/app/admin.settings.js (1:93594)
69413

store/js/app/9413.js (1:1651)
d

store/js/app/admin.settings.js (1:93599)
22450

store/js/app/2450.js (1:7083)
d

store/js/app/admin.settings.js (1:93599)

Toufiq Senior Staff

I have checked on my end and no problem found. Please check the screenshot.

Log in to reply.