No currencies are currently enabled

@enochdavid Not sure exactly why you got this particular JS error, but I’ve made the code around that area more resilient in version 4.3.2. At the very least you should stop seeing this particular error, but please let me know if you can now see coins in your frontend.

@dashedslug OK I wait for the upcoming patch and hopefully this fixes my issue

@enochdavid The patch is 4.3.2 as explained above. Did you see any changes? i.e.:

1. Do you still see any errors in your JavaScript console?
2. Do you see coins in the frontend?

thanks

Yes, It still dosent save and here are the errors on browser console:

“knockout-latest.js:73 Uncaught TypeError: Unable to process binding “style: function(){return {‘background-image’:’url(‘+ cryptoCoins()[ selectedCryptoCoin()].icon_url +’)’} }”
Message: Cannot read property ‘icon_url’ of undefined
at style (eval at parseBindingsString (knockout-latest.js:69), <anonymous>:3:420)
at update (knockout-latest.js:99)
at N.K.l (knockout-latest.js:73)
at Function.$c (knockout-latest.js:52)
at Function.ad (knockout-latest.js:52)
at Function.da (knockout-latest.js:51)
at Object.N.u.N.K (knockout-latest.js:49)
at knockout-latest.js:73
at Object.D (knockout-latest.js:11)
at s (knockout-latest.js:72)”

@enochdavid Oops, I tried to fix this problem without first understanding why it happens, and this is the result.

Is it possible for me to login to your site as a user with has_wallets? I have not been able to reproduce the problem on my end.

@dashedslug It is possible, how do I get the details across to you

@enochdavid My email is available at https://www.dashed-slug.net/contact/

I have sent you the details requested

@enochdavid I logged in to your site and had a look at the following page:

/deposit/
/transfer/
/withdraw
/history/

I see the following problem in the withdrawal page:

TypeError: cryptoCoins(…)[selectedCryptoCoin(…)] is undefined

The issue is caused due to the non-standard theme you’re using. I’m guessing that some JavaScript events occur on a different sequence than what is usual.

I believe I can fix this on the next patch of the plugin. I will make the code safer around this and the plugin should be able to accommodate for this theme.

I will notify you here when the patch is out.

with regards
Alex

Thank you so much Alex

When do I look forward to this patch?

with regards
David

This particular fix affects only the theme you are using. I will have to collect a few more bug fixes/features to justify a new release, as trivial releases are being frowned upon. It should not be more than a couple of days. I will notify you again here soon.

with regards

Thank you so much.
I wait then

@enochdavid Hello David, the fix we discussed is out now with version 4.3.3. Please let me know if it solves the issue with your theme.

with regards

Well, so far so good, I still do but do I then have to change theme now?

• This reply was modified 5 years, 5 months ago by David Okoli.

@enochdavid Normally you should not have to change the theme.

Do you still encounter the original issue or is it resolved? If the issue is resolved, then we should close this thread and open a new one if you encounter any more issues.

If you are still encountering the same issue, let me know.

with regards