[alexg]

Hello,

This is probably related to the other issue you experienced, regarding the JSON API being cached.

The user history is retrieved with the following GET request:

/?__wallets_exchange_action=get_user_history

If you make sure that this is not cached, the history will be reflected in the frontend. How you do this depends on the types of server-side cache you use. The response of this API is not being cached by the plugin and the browser is also instructed not to cache it, with Pragma: no-cache and Cache-Control: no-cache, must-revalidate.

with regards

[alexg]

Hello,

I have fixed the problem, and the patch will be in the next release of the Exchange.

The next release of the Exchange will be out, soon after version 4.0.0 of the parent plugin. Version 4.0.0 will be out today.

with regards

[alexg]

Thank you, I will test with Graphcoin and if possible will provide a fix. Will let you know.

[alexg]

The hot wallet balance is cached internally via WordPress transients for performance. Can you check with the setting:

“Frontend” -> “JSON API settings” -> “Disable transients (debug)”

Then go to the adapters list and see if the Hot Wallet Balance is correct.

If this setting makes a difference, then it means that your server-side cache is misconfigured so that transients are not expiring properly.

Please let me know once you try this.

with regards

[alexg]

Hello,

Thanks for reporting and posting your progress.

It is true that some security plugins can interfere with the JSON API. This caused a crash on the frontside JavaScript which then caused the knockout.js UIs to not get updated.

I will look at how to warn the user if “Hide My WP” hides the JSON API! There should be a setting in every security plugin to exclude certain pages or types of calls from being cached. The JSON API is based on GET parameters, so look for something that disables caching on pages with GET parameters in the query string.

with regards

[alexg]

Hello,

Thanks for reporting and posting your progress.

It is true that some security plugins can interfere with the JSON API. This caused a crash on the frontside JavaScript which then caused the knockout.js UIs to not get updated.

I will look at how to warn the user if “Hide My WP” hides the JSON API! There should be a setting in every security plugin to exclude certain pages or types of calls from being cached. The JSON API is based on GET parameters, so look for something that disables caching on pages with GET parameters in the query string.

with regards

[alexg]

Hello,

I checked with the MultiCoin Adapter connected to a Litecoin wallet and I get a correct deposit date.

Can I ask the following please?

1. Which coin adapter were you using? Was it the Full Node Multi Coin Adapter or something else?

2. Which wallet was it connected to?

thanks

with regards

[alexg]

Hello,

I have moved your post to the General discussion as it is not related to any coin adapter.

The plugin instructs you to run these commands in your SQL console. This will change the storage engine used by your DB to store the plugin’s data to an engine that is more compatible with the plugin. You must do this for security, especially since you are using the Exchange extension.

To enter commands into your SQL console, you can use phpMyAdmin. Simply follow any guide on how to do this, such as:

How to Run a Script with phpMyAdmin in SQL for HTML5and CSS3 Programming

Enter the commands exactly as you see them (copy & paste).

If you’ve done it successfully, you will not see the warning again.

Please let me know if you face any difficulties.

with regards

[alexg]

Thank you, I will check.

[alexg]

Hello Megan,

Thank you for reporting this. I am already aware of the issue.

As you say, the CoinMarketCap and CoinGecko APIs have changed. I believe the idea is that they now give the top 100 coins for free, then you need to pay for the entire feed. This can be circumvented by querying the specific coins needed.

I will need to develop a solution for this. Hopefully this will be out in one of the next updates.

with regards

[alexg]

Hello,

First of all, it looks like what you are trying to accomplish is some type of tipping feature. So, if you haven’t already, see if the Tip the Author extension can perform the function you want.

If you want to do exactly what you described, you will need to add some JavaScript to your page.

You would need to attach your code to the wallets_ready event:

$( 'html' ).on( 'wallets_ready', function( event, coins, nonces ) {
    // TODO add your code here
} );

Inside this, you can read your GET parameter.

Once you have your user name in a variable, you can add it to the wallets_move form like so:

if ( userName ) {
    wp.wallets.viewModels.wallets.moveUser( userName );
}

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

with regards

[alexg]

Thank you very much!

Version 3.9.4 is now out and includes the feature you requested.

with regards

[alexg]

Thank you for sharing these details.

Actually I have already developed this feature. I have placed it next to the existing “Renew Deposit Addresses” feature, and you will be able to use it tomorrow when version 3.9.4 will be out.

The command affects all users with the has_wallets capability. If you like, you could temporarily remove this capability from the roles that you do not want affected (see Admin -> “Wallets” -> “Capabilities” menu), then generate the deposit addresses, then finally restore the has_wallets capability to the other roles.

with regards

[alexg]

OK now I understand your question.

No, unfortunately right now it is not possible to populate deposit addresses for all users in one go. Of course everything is possible if you can create a script that inserts deposit addresses into the database directly. But this is not easy.

I might be able to include such a feature in the plugin’s next patch release.

If you don’t mind me asking, what’s your use case? Why do you need this?

thank you

[alexg]

Hello,

The product page and the checkout use the same API.

In the product page, the exchange rate between the shop’s default currency (WooCommerce -> Settings -> Currency), and each enabled cryptocurrency is used.

At checkout, the exchange rate between the order’s currency and the user’s chosen cryptocurrency (billing cryptocurrency) is used. The order currency should be the shop’s default currency.

The billing cryptocurrency is passed via a POST variable. I’m thinking that maybe some other plugin prevents POST variables from being passed unfiltered. Could you please:

1. Try an order again with all plugins disabled except the ones necessary and with caching disabled?

2. What exactly do you see on checkout? Is there an error message? Could you show me a screenshot if there is?

thank you

with regards

[Author]

Posts