[alexg]

Hello,

If you are trying to modify the UIs, please see the 5.0.0 release notes on how to override the templates.

I did not understand:

1. Where did you get a 403? This HTTP error is usually associated with not being logged in or lacking the appropriate permissions.

2. What do you mean by “execute shortcode”? What are you trying to do?

Please clarify so I can help.

thank you

with regards

[alexg]

Hello,

To deposit to the hot wallet, simply use any address generated from that wallet that is NOT assigned to a user.

One way to ensure that you get an address that is not already a user deposit address, go to Wallets → Cold Storage in your admin screens. Choose your coin and hit the deposit button.

If you want to know more about the cold storage section, you can visit the Cold Storage chapter in the documentation. It’s just an easy way to deposit/withdraw to and from the hot wallet without affecting user balances. The view also lets you see what the sum of user balances is, so that you know what percentage of the balances is covered by the funds you have online.

Please let me know if you have any other questions.

with regards

P.S. I have moved your question to the general discussion because the answer is not specific to CoinPayments.

[alexg]

Hello Megan,

Oh no, hope you are well now!

The address is still valid. Email me with the TXID when you decide to pay.

with regards

[alexg]

Hello,

Not directly. The market stats are available to the user via the [wallets_exchange_market] UI and are embedded into the table.

However, the “high” and “low” values are only relevant with respect to a particular time interval. If you need access to the price data for the current market, you can find it in the JavaScript object wp.wallets.viewModels.walletsExchange.marketHistory().

To get the prices sorted in an array, first do:

let prices = wp.wallets.viewModels.walletsExchange.marketHistory().map( function( p) { return parseFloat(p.rate); } ).sort();

Then, the lowest price within the loaded timerange is the first element in the array:

let low = prices[0];

And the highest price in the loaded timerange, is, conversely, the last element in the array:

let high = prices[ prices.length – 1 ];

Hope this helps. Please let me know if you have any more questions.

with regards,
Alex

[alexg]

Hello LeinAd,

First of all, I hope you know that the BTC_USDT.ERC20 market has Bitcoin as the base currency and Tether as the quote currency. If this is not what you want, you should swap the currencies around. The format that the plugin uses for markets is BASE_QUOTE, not QUOTE_BASE.

It is not possible to change the currency symbol. The .ERC20 part is there to distinguish this token from the USDT token on the Omni layer.

(You can however modify the name and icon using the appropriate WordPress filters. The filter for the Tether icon URL is wallets_coin_icon_url_USDT.ERC20.)

In any case, this issue arises due to CoinPayments having a USDT.png icon file, while the token symbol is USDT.ERC20. I have updated the coin adapter to remove the .* part from symbols, when it looks for icon files.

Thank you for spotting this issue. Please install the latest version 1.1.4 of the adapter to resolve the issue.

with regards

P.S. I have moved this thread to the CoinPayments forum because it turns out that it has to do with the coin adapter.

[alexg]

I’m sorry I think I misunderstood your issue earlier.

Can you confirm that the airdrop runs with the user’s primary role? Is the issue only with secondary roles? If so I can investigate this.

Let me know. thank you

[alexg]

This works as intended. Since airdrops are not something that you can see in the frontend, I thought it would be more appropriate to have them marked as private.

[alexg]

Hello,

1. Check to see if the cron jobs are running. In the admin dashboard, under the debug tab, you will find the information next to: “Cron jobs last ran on”. What do you see?

2. If you still can’t figure out why cron jobs are not running, please show me the details of your airdrop.

3. Finally. Does the airdrop run if you apply it to a more standard role, such as subscriber?

Let me know about these three points.

with regards

[alexg]

Glad you sorted it out.

The wallet notifies the plugin multiple times about each transaction, so even if communication fails once, a transaction will eventually go through. By visiting manually the notification URL, you can force a transaction to go through to the plugin. If a transaction is not reported to the plugin, then this means that your curl command has an error, or the WordPress host is not reachable from your wallet host. If this is the case, you should fix the command in your .conf file, and restart the wallet, or the next transaction will also fail to reach the plugin. See step #6 in the troubleshooting article on how to generate debug logs of the curl commands that your wallet runs.

with regards

[alexg]

Hello,

It’s likely that the notification mechanism did not work.

Please check the relevant article here: https://www.dashed-slug.net/howto-debug-an-incoming-deposit-full-node-wallet/

Normally, with Bitcoin core-like wallets (like the Litecoin core wallet), you can specify a command that runs every time a transaction is observed on the network. This command can be a curl command. This is why the plugin recommends that you have in your .conf file something like:

walletnotify=curl -k https://www.example.com/?__wallets_apiversion=3&__wallets_action=notify&__wallets_symbol=LTC&__wallets_notify_type=wallet&__wallets_notify_message=%s

The %s string is replaced with the TXID, so that the plugin can then request info on that transaction.

Check to see that the curl command succeeds. Usual culprits are your .htaccess file, firewalls, errors on the wallet server (such as curl not installed), etc.

Hope this helps. If it doesn’t let me know.

with regards

[alexg]

Yeah, sorry but I haven’t spent time on this.

This issue is due to bad design in the API’s access control. This will be resolved with 6.0.0, the next major version of wallets, which replaces the JSON-API with new restful APIs. Because the new restful APIs will have finer access control, there will be a public API that reports currency information to users who are not logged in.

In the meantime, you could use [wallets_exchange_market template="static"]. Because the template is static, no information is passed through the API, so there is no issue with coin icons.

Hope this helps.

with regards

[alexg]

Hello,

Yes, you can place the shortcodes on your page or pages. You can use columns or tables in the Gutenberg editor or another builder, to place the UIs next to each other. You can also place the UIs in your theme’s widget areas. You can then customize the look and feel of the UIs in the WordPress Customizer.

Alternatively, if you want to design the entire UI from scratch, you can communicate with the plugin using the JSON-API.

Hope this helps. Let me know if you have any more questions.

with regards

P.S. I have moved your question to a new thread since it is not related to the previous one.

[alexg]

Hi, glad you resolved the issue!

Users who have the has_wallets capability automatically have wallets, there is nothing to create.

Just make sure to assign the capability to your user roles. You can do this at Wallets -> Capabilities.

Please let me know in a new thread if you have any more questions.

with regards

[alexg]

Hello,

Please see this relevant article: https://www.dashed-slug.net/howto-debug-shortcodes-no-currencies-are-currently-enabled/

Check each step and if the article didn’t help, please tell me what you found on each step.

with regards

[alexg]

Hello,

Not sure why this happened.

First, try deactivating and reactivating the plugin. This should fix the capabilities.

If not:

Recurring airdrops are implemented as custom post types. The type slug is wallets_airdrop.

You can use any capability-editing plugin to assign the following caps to your user. A good plugin is User Role Editor.

publish_airdrops
edit_airdrops
delete_airdrops
edit_airdrop
delete_airdrop
read_airdrop

Your admin user should also have the manage_wallets capability. If you see the Wallets menu then you already have it.

Hope this helps. Please let me know if it doesn’t.

[Author]

Posts