[alexg]

Hello,

Can you please email me a screenshot at info@dashed-slug.net?

Did the problem occur when you activated the main plugin or the CoinPayments extension?

To regain control of WordPress, simply go to your wp-content/plugins directory and delete either wallets or wallets-cp, whichever plugin caused the error.

To find out why this occurred, please send me all error messages you can find, if you see any on your screen. Additionally, you can enable debugging https://codex.wordpress.org/Debugging_in_WordPress and check the logs.

If there are no hints in the logs then I will need as much info about your setup as possible, PHP version, installed PHP extension, etc.

Contact me by email and we’ll figure this out.

Thank you

[alexg]

Thanks for the suggestion.

You are correct that this would be a very cool feature.

Unfortunately this is a very big architectural change and I am currently busy with a number of user requests, including the exchange extension.

So it is unlikely that I would be able to do this any time soon.

[alexg]

In version 2.13.3 of the plugin you can now disable live polling altogether if you wish. Just go to the frontend settings and set the two polling intervals to zero.

Any remaining performance issues that you may face in the frontend are probably due to AJAX calls on the main thread as discussed above. This will be resolved in a later release.

Additionally, if you do not need the [wallets_move] UI and its related functionality, you may disable it from the “Capabilities” admin screen. This will disable the get_users_info JSON call, which normally sends a list of users to the client for the purposes of the user dropdown. This will be resolved more permanently in a later version.

kind regards

[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

[Author]

Posts