[alexg]

After a lot of searching I determined the source of the problem and provided a fix in 0.4.2-beta. The Exchange extension should not cause new negative balances any more when matching trades. The bug was partly due to differences in the application of maker and taker fees to the base currency while buying the quote currency. If you wish to continue testing the plugin, I would suggest that you first wipe all trades and orders from the database, with delete from wp_wallets_txs where category='trade';delete from wp_wallets_orders;

I will keep the extension in beta for a short while longer and if no more bugs are detected, it will be bumped to 1.0.0 (i.e. production-ready).

[alexg]

In the latest Exchange version 0.4.2-beta the selected market remains the same after market data is reloaded.

[alexg]

Hello,

Please see the troubleshooting section of the coin adapter for the error “too many errors in the last two minutes”. Essentially you need to re-check your codes, deactivate the plugin for two minutes, then enable it again and the problem should go away.

If you get an error in the CoinPayments platform when enabling a coin, this is not related to the plugin. I am not sure why you would get this error. You should ask CoinPayments support about it.

The plugin requires the cron job to be running. There is no URL to trigger the cron job externally at the moment, although this is in my future plans.

with regards

P.S. Could you please open a new thread per individual topic in the future? This makes things clearer for everyone reading this. Thank you!

[alexg]

Please see my reply in your other post: https://www.dashed-slug.net/forums/topic/moved-deposits-do-not-register-in-plugin/

[alexg]

Hello,

I have moved your request to a new thread.

1. Are you using the block.io adapter?

2. Did you use a user deposit address (i.e. an address shown in the [wallets_deposit] shortcode?

Let me know please.

Thanks

[alexg]

This is the screenshot

Attachments:

You must be logged in to view attached files.

[alexg]

Hello,

No, unfortunately I do not have any update on this.

It is in my future plans.

with regards

[alexg]

Hello,

Thank you. I am aware of the problem and am looking for a solution.

Once this is fixed, the Exchange will be taken out of beta.

with regards

[alexg]

The Monero coin adapter for full nodes is now released. See the blog announcement and adapter homepage for details.

[alexg]

The Monero coin adapter for full nodes is now released. See the blog announcement and adapter homepage for details.

[alexg]

Thank you for your feedback. When IPN messages are not received it is always due to some firewall or other security measure.

[alexg]

Thanks,Yes you are correct as far as Local hosting goes!The Plugin is running Live on the web in my case BitNija is being used.
This was Responsible for the block!

[alexg]

Thanks for your feedback.

I was curious what you did, because it might be something that could be added in the troubleshooting instructions, in the plugin’s manual. However I am not sure how the SMTP (SendMail Transfer Protocol) settings are relevant to IPNs.

If you are running the plugin in your local network, instead of a public-facing server, then you can indeed configure your modem/router to forward incoming IPNs to your local machine. However, the settings section of your router that would be relevant would be the NAT (Network Address Translation) settings, or port forwarding settings. These can go by other names; for example in Thomson routers, look under “Games and Applications Sharing”.

with regards

[alexg]

Hello,

I checked and all of the strings you mentioned are already in languages/wallets-front.pot: https://github.com/dashed-slug/wallets/blob/3.7.4/languages/wallets-front.pot

Did you encounter a problem while providing a translation? Have you followed the translation guide in the manual?

[alexg]

When I developed this I could not find a way to do it any different.

I will look again in case there is something new in WooCommerce.

with regards

[Author]

Posts