Forum Replies Created
February 28, 2018 at 8:48 am in reply to: Can you add the Source text of a language file in the next update? #2509
Yes I have added translation strings for transaction categories and transaction status. This will be in the next patch release which should be out later today.
As for the other strings you mentioned, they will not be translated on the main plugin. I will provide translations on the faucet extension soon.
Thank you for reporting. Your input is very helpful for improving the quality of the plugin.
Addresses can be labelled but the accounting system of Bitcoin is deprecated as you know. I could maybe add code so that the RPC command assigns emails to addresses but it will require a change in the API, so I am scheduling this for version 3.0.0 where there will be a new v2 of the PHP API. I am also not certain at this time if all the wallets that have an RPC API will accept a second argument to the
getnewaddresscommand, so I will have to do some research on this, before deciding whether to add this at the
Dashed_Slug_Wallets_Coin_Adapter_Bitcoinlevel in the class hierarchy.
Labels can also be assigned on the database, but this is somewhat redundant if it is to be used for storing usernames, since the database already holds a mapping of usernames to addresses.
I am adding all of this to the backlog. Thanks for the suggestion.
P.S. In the future please open a new thread for each distinct request, this helps keep the forums clean for people who look for similar info in the future. Thanks.
I will do something about it as time permits. Adding it to the list 🙂
As always, thanks for reporting!
Great to hear that you resolved the issue. Answering to your next questions:
If you have only one coin adapter installed and enabled then that will be the only one displayed. Additionally, the front-end drop-downs that let you choose coin, will not be displayed if there is only one coin.
The UIs display all amounts in the cryptocurrency amount AND in one fiat currency. This currency is set site-wide with the Wallets -> Rates -> Default fiat currency setting and at the user level via the WordPress user profile pages.
For this to work, you need to select in Wallets -> Rates -> Rates provider an exchange rate source that includes the BTC-USD exchange rate. Rates for other fiat currencies such as EUR are pulled from fixer.io and are calculated on the fly.
If you are using the JSON API to display currencies in a custom way, then use the
ratefield from the
get_coins_infocall to calculate the amounts in the selected fiat currency.
P.S. Please try to open a new thread for each additional issue or question that you require help with. This way the forum gets more organized for people who later look for answers to similar problems. Thank you.
I do not believe so.
Additionally, there is no “wallet creation” per se. There is one wallet per coin and the plugin does not perform additional tasks when a new user joins.
1. Do you experience the slowdown on the server or client side? It sounds like it is on the server side.
2. I believe you mentioned earlier that you have a large number of users on your site. This could cause the timeout message. Try to disable the
send_funds_to_usercapability so the plugin does not attempt to send the list of usernames to the client. This will be resolved much later in version 3.0.0 as discussed, because it is an architectural change to the API.
Can you please be more clear?
1. What do you mean by “settings in functions file”? The
functions.phpfile in a theme is where you put extra code into a theme. What code did you add?
2. Which coin adapter are you using?
3. If you are using an RPC wallet, is it encrypted with a passphrase?
4. In the plugin’s Cron job settings, under Time to retain withdrawal secrets have you entered
0or some other value?
5. In the coin adapter settings, did you enter your passphrase?
Let me know so I can help you diagnose this.
I do not know what the problem might be with so little information.
If this is a freely available theme, simply point me to it and I will test it.
There should be an XHR request from the frontend to your server doing a
get_user_infocall on the JSON API. Can you see this request in your browser’s network console?
No, this is not possible.
Additionally, I do not have plans to implement fiat transactions as part of this plugin and its extensions. This is explained in the FAQ.
This has nothing to do with which coin adapter you use.
Users do not need to create wallets, they automatically have wallets for all connected adapters that are in a “Responding” state.
You, as an admin, need to make sure that the role or roles your users have have the necessary capabilities, including
has_wallets. Visit the Wallets -> Capabilities admin screen to learn more and to make the changes. Usually the users have the Subscriber role which does not have the
has_walletscapability by default.
Can you please email me a screenshot at firstname.lastname@example.org?
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/pluginsdirectory and delete either
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.
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.
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_infoJSON 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.
Thanks, I will add this in a future release.
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/