[alexg]

Hello,

Actually, the codes shown as “deposit address”, which can be scanned via QR, are not meaningless. They are exactly the code that you can use as an admin in the deposit tool. The code uniquely identifies the combination of user and currency. It is meant to be used for any other type of deposit, as long as you can verify manually that the deposit occurred. Therefore they are shown as intended.

What you suggest could be added as an option: if it is checked, then the deposit address for custom coins can be hidden from the JSON API, and therefore will not be shown. And it is possible to change the deposit dropdown to not show any coins without a deposit address. This would require changes both in the parent plugin and the coin adapter.

I will plan to roll out the necessary changes with the next releases for these two components.

with regards

[alexg]

Version 0.1.2-beta uploaded with the fix. Thank you for testing the component!

with regards

[alexg]

Hello,

Thank you for your contribution.

You can always copy the file under your theme or child theme and edit it. For example, if you place the file into wp-content/themes/YOURTHEME/templates/wallets-exchange/chart.php, then you can edit it all you want and it will override the plugin’s template. For more details on this, see the documentation or the release notes for 5.0.0.

However, you make a valid point. I can change the template so it outputs “auto” if no dimension is explicitly specified. This will go into the next release of the exchange.

with regards

[alexg]

Hello,

This could happen due to any number of problems. It looks like JavaScript has crashed with an error.

1. Please check your browser’s console for errors and let me know what you found. If some other component is producing a JavaScript error, you must fix or eliminate that component.

2. Visit the JSON API endpoint get_coins_info. Use your browser to go to https://example.com/?__wallets_apiversion=3&__wallets_action=get_coins_info (substitute example.com with your own domain). What do you get back? If you don’t get back a proper JSON response, this could mean that there is an issue with caching plugins, the web server configuration, or even something else.

Show me what you found in 1 and 2 and I will advise.

with regards

[alexg]

Oops, yes I see it now. Thank you! I hurried to release the fix on Friday evening without noticing this bug. I will release a fix today. with regards

[alexg]

Hello,

I have uploaded a new patch release, 0.1.1-beta of the adapter, where the issue with network-active installations that you discovered is addressed.

Additionally, the adapter is now shown with a withdrawals lock (padlock) while the node is not yet synced. This will prevent any withdrawal failures while the node is syncing.

Thank you for reporting this issue.

with regards

[alexg]

Hello,

OK, I have now tested on multisite and I see that the secrets are not saved when the plugin is network-activated.

I will release a fix for this and a few other minor issues over the coming days.

Thank you very much for reporting this issue. I will notify you again here.

with regards

[alexg]

Thank you for testing! Well, the adapter works on my machine 🙂

So:

1. Check your value of the setting: “Cron job” -> “Withdrawal locks” -> “Time to retain withdrawal secrets”. By default this is 0 which means retain passwords indefinitely in the DB.

2. The passwords are stored as transients. Check your WordPress installation and any caching/optimization plugins to see if they are deleting your non-expired transients. If necessary you can disable such plugins and try again.

Please let me know if this made a difference.

[alexg]

Hello,

You simply need to enter a secret password in your coin adapter settings, under “Wallet settings” -> “Password”. The plugin will then create a new wallet for your site, and will ask the wallet-api to encrypt the wallet file with this password.

with regards

[alexg]

Hello,

TurtleCoin adapter is now released: https://www.dashed-slug.net/turtlecoin-on-wordpress/

with regards

[alexg]

The issue you discovered is now fixed in version 0.5.2-beta of the adapter. Again, thank you for your help.

with regards

[alexg]

Hello,

Yes, thank you, I will make a note of it. It should be straightforward to implement.

with regards

[alexg]

OK thank you for the clarification.

I investigated and this is my mistake. A bug was introduced in version 0.5.0-beta of the fiat coin adapter.

You can continue using 0.4.5-beta for now, and I will release a patch as soon as possible. Once this is out, I will let you know here so you can upgrade, and there will be a facebook/twitter announcement as usual.

with regards

[alexg]

Continuing from my last reply:

If you are referring to the public shortcodes of the exchange, then yes, the icons are not available to those UIs for the reason described above. This is something that I will have to address soon. I am making a note of it.

Thank you.
with regards

[alexg]

Hello,

This is expected. The coin information is retrieved from the get_coins_info API endpoint, which is not available if you are not logged in.

The issue here is, why are you even seeing the UI? The UI should not be visible if you are not logged in. Which UI are you seeing while logged out? This could be a caching issue.

with regards

[Author]

Posts