[alexg]

Thanks, I will add this in a future release.

kind regards

[alexg]

This is more likely due to the fact that some AJAX calls are done on the main JavaScript thread, which is not a best practice approach. I also have plans to fix this. Thank you for reporting.

[alexg]

Your query is about the main plugin so I replied to the other thread you opened at https://wordpress.org/support/topic/source-map-error/

[alexg]

I will add this option in the next patch release which will be out soon.

In the meantime, if you set the polling rate to something long, like 15 or 30 minutes, then it won’t impact your frontend performance much. Keep in mind that this will only affect frontend performance.

If you have issues with the time it takes for your server to respond, then try disabling the exchange rate provider under Wallets -> Rates, or try a different rate provider. That should tell you if the problem comes from that.

There’s also some info in the troubleshooting pages about performance.

Can you describe the performance issue you are facing?

Thanks

[alexg]

Apologies for the very late reply.

Once you have a translation ready you can enter it in the languages directory to test it yourself.

Only send it to me if you want to contribute your translation to the project.

Note that you need to rename the .pot file to a .po file for the translation to be available.

kind regards

[alexg]

Hello,

Yes, I plan to do this. This is a much requested change. For example, see here: https://wordpress.org/support/topic/bitcoin-wallet-app-transfer-issue/

I will post to all the relevant threads when the change is done.

kind regards

[alexg]

Hello,

Answering your questions in order:

I went to coinpayment prices, but could not understand it much better.
In their prices, I will be charged 0.50% while recieving payments.
If I use this plugin, will I also be charged 0.05%.

Yes, when depositing using the CoinPayments adapter, a fee of 0.50% is charged. Deposits are done to callback addresses.

In addition, if a user sends coin to another user using their username or email address, will I be charged?

No, the only fees charged when transferring to another user are the proportional fees that you specify in the coin adapter settings. The setting is at Wallets -> CoinPayments -> Fees -> Move fee (proportional).

If also, a user send coin to other user on that same site using the wallet address of the reciever, will it be a charge also?

If you attempt to withdraw to a deposit address of a user on the same site, you will find that an internal transfer will be performed instead. So the same move fees will be applied as described above.

I asked this, because I don’t know also in which transactions on the site do IPN calls are made.

IPNs are the callback mechanism that the CoinPayments service sends to the plugin to notify that a deposit has occurred.

Hope this answers your questions. Do let me know if you have any more questions.

kind regards,
Alex

P.S. I have transferred your post to the CoinPayments support forum because it is not relevant to the WooCommerce extension.

[alexg]

Hello,

Glad to hear that you resolved the 60% issue.

If you want to contribute a french translation, you are very welcome. You can email me the .po file and I will include it in the next release.

I do not yet have plans for the Lightning network.

If you want to retain the passphrase forever, go to Wallets -> Cron job and set Time to retain withdrawal secrets to 0. If you want the passphrase retained for one year exactly, set the value to 365*24*60 = 525600 minutes. Then, go to your adapter and enter the passphrase again.

If you want to become a premium member, visit the homepage and click on the Become premium dashed-slug member button.

regards

[alexg]

Yes this is in my plans and is the most requested thing.

First of all, there is already a ShapeShift extension. This is simply a frontend for the shapeshift.io service and should be OK for exchanging between the coins supported by that service.

I do intend to build a full exchange with an orderbook on WordPress. This is a huge task and I am currently at the analysis phase, so it’s not really possible for me to give an exact estimate. It will be at least a few months.

Note that this will not be an exchange that can scale to large volumes, due to the limitations of WordPress. One issue is the unavailability of websockets, which makes polling necessary. The exchange should be good enough for low volume markets though, and should provide some liquidity for small coins.

Learning from the mistakes of the past, I am currently preparing to upgrade the plugin to a better API, and the current PHP and JSON API will continue to work but will be marked deprecated. This will occur at version 3.0.0 which I am planning to release over the coming month.

This API upgrade is a prerequisite for working on the exchange. This still has epic status in my backlog, so I do not want to give an estimate. I have done this in the past for other things and I am always off.

It will not be very soon.

Hope this makes the situation a bit clearer for you.

[alexg]

There’s no way to do this.

Remember that in WooCommerce you add some products on a basket and then pay for the entire basket in one currency.

The basket can potentially contain different products. The customer then pays for the entire basket.

I don’t know exactly what you are trying to do, but perhaps one solution would be to have a multisite install, and have several shops on the same domain. Each shop could have its own coin adapters with coins disabled or enabled as needed.

From the screenshot it looks like you are trying to create an exchange. You will not be able to do this easily via WooCommerce and you’d be better off starting from scratch to do your own plugin, in my opinion. WooCommerce is for e-shops, and not a good fit for selling currencies.

kind regards
Alex

[alexg]

Great news that you found it!

If you have identified that a particular plugin is incompatible with Bitcoin and Altcoin Wallets, do let me know so I can look at it. I may be able to resolve the incompatibility.

kind regards

[alexg]

Hello,

Thanks for your kind words.

1) The plugin does not directly interface with an Ethereum wallet, but if you use the CoinPayments cloud wallet adapter then Ethereum is available as an option. I had previously indicated that I would support ERC20 tokens with a coin adapter, but it turns out that there is no straightforward way to do this. The reason is that the plugin works best with coins that follow Bitcoin’s UTXO model, rather than Ethereum’s account model. So the answer is no, ether based coins are not supported.

2) Thanks but unfortunately I do not undertake custom projects, as detailed in the FAQ.

3) If you wish to use the plugin without installing any full nodes, this is what the cloud wallet adapters are for. The downside is that you rely on a third party service. But this solution is considerably easier from a technical perspective to install and maintain, and also requires a lot less hardware resources. Currently the cloud wallets available are the block.io adapter and the CoinPayments adapter, both freely available to subscribers of this site.

kind regards

[alexg]

Hi,

Thanks for reporting this issue.

I have now tested again the WooCommerce payment gateway extension with the latest version of WooCommerce, 3.3.0. I cannot reproduce the defect that you are describing. This could mean one of two things:

1. The problem occurs due to bad interaction with some other plugin. As a test, disable all other plugins except WooCommerce, Bitcoin and Altcoin Wallets, and the payment gateway, and try again. If you are now able to perform a checkout, then you should enable your plugins again one-by-one until you find out which plugin is causing this. (Usual suspects are security plugins that sometimes block AJAX requests.) Then report your findings to me. If you cannot do a checkout even with all but the essential plugins disabled, then try changing the theme to something standard like Twenty Seventeen.

2. Since you mentioned the error (DOM Exception 23): The operation timed out. it is possible that some JavaScript code takes too long to execute, perhaps due to network issues or because of something else slowing down your server. As you know, both WooCommerce and Bitcoin and Altcoin Wallets rely heavily on JavaScript and XHR requests. I would open up the network tab in the browser console and observe how long the various XHR requests take. Can you find one that takes too long to respond?

3. Since your error could be caused by anything really, if you can’t find anything with 1 or 2, I would enable logging (https://codex.wordpress.org/Debugging_in_WordPress) and check the WordPress logs at wp-content/debug.log. It could be that there is some error on the server side that slows down your checkout. Unlikely, but it’s worth a shot.

Most likely it is some incompatibility with another one of your plugins, so go through 1 first. If you do identify a plugin that’s causing this then let me know so I can see what I can do about this.

let me know what you find

kind regards,
Alex

[alexg]

Thank you for reporting this. I am posting here for the benefit of anyone else reading this.

You describe that the get_user_info JSON call divulges user names. This is not a bug, but works as intended and is documented behavior.

I do intend to replace this API in the future with something that does not divulge user names, but it will be done when I rework the API because it’s an architectural change and is tied to a lot of other things that also need to change.

For the time being you can disable the “send funds to user” capability from any user roles that you do not wish to be able to see user names. These users will not be able to initiate internal transfers or use the [wallets_move] shortcode, but the deposit/withdrawal functionality will still be there.

Again thanks for reporting.

[alexg]

Hello,

Thank you for finding this and for reporting it to me.

You can find my contact email at https://www.dashed-slug.net/contact/

I will look at it today and if it is indeed a problem I will release a fix ASAP.

thanks again

kind regards,
Alex

[Author]

Posts