[alexg]

In the latest version 0.8.2-beta of the Exchange extension, it is now possible to display a static table of all markets with [wallets_exchange_market template="static"]. Additionally, the admin can pick a “default main page” for each market. These pages appear as links in this new shortcode.

(The dynamic counterpart of the markets table, [wallets_exchange_market], does not use these new page links, because clicking on a row dynamically switches the loaded views to the clicked market.)

[alexg]

In the latest version 2.1.0 of the WooCommerce Cryptocurrency Payment Gateway it is now possible for an admin to select which coins can be accepted as payment. This also affects WC Marketplace payments.

[alexg]

In the latest version 2.1.0 of the WooCommerce Cryptocurrency Payment Gateway it is now possible for an admin to select which coins can be accepted as payment. This also affects WC Marketplace payments.

[alexg]

In the latest version 2.1.0 of the WooCommerce Cryptocurrency Payment Gateway it is now possible for an admin to select which coins can be accepted as payment. This also affects WC Marketplace payments. I have not yet added the possibility for vendors to further filter down the list of accepted coins.

[alexg]

Haha, those are inspiring words! Thanks for sharing this info. We’ll see…

[alexg]

Hello,

That’s an excellent question. I got the same email yesterday.

They clearly say that API access requires KYC and the coin adapter uses the API, so yes, this affects users of the coin adapter.

What I find surprising is that it took them so long to do this, not that they are doing it. All wallets/exchanges/etc are required by law to do this. It’s not like they want to inconvenience their users, but it’s not up to them. My guess is that since they only require KYC for commercial activity, this is probably a requirement from governments for tax purposes.

What’s more, even if you use only the full node adapters on your own servers, you are probably affected by the same laws they are, and you should implement KYC yourself, but that’s another matter. Of course, not every legal jurisdiction has the same laws, but if your users are international, it’s something to keep in mind and discuss with a lawyer.

Personally I will have to go through their KYC process so that I can continue to test and support the coin adapter. For any more details it’s best to contact the CoinPayments support about this.

with regards

[alexg]

Unfortunately I do not think anyone has built any apps to integrate with the exchange extension yet.

If you are interested in hiring developers to create one, the API details are in the manual and I am happy to provide any additional technical details. The API can be accessed with bearer tokens.

with regards

[alexg]

Hello,

Thank you for providing access. I was able to login and navigate to the “crypto wallets” page, by did not see the error you encountered. I used both Firefox and Google Chrome.

However, I did see another JavaScript error, coming from some SEO/Google Analytics plugin. It looks like a common syntax error. In the following code:

links_out.forEach(function (link, key, listObj){
	if (!link.href.match(/.*\.(zip|mp3*|mpe*g|pdf|docx*|pptx*|xlsx*|rar*)(\?.*)?$/) {
		if (link.href.indexOf('mysite.example') == -1) {
			link.addEventListener('click', function (e){ ga('send', 'event', 'outbound', 'click', e.target.href, {'nonInteraction': 1}); }); }); } }});

There is a missing closing bracket after the condition of the first if statement. Ideally you should contact the developers of this plugin to let them know.

For now, first try to disable your SEO or analytics plugin, and see if this makes a difference.

I am still not sure why you saw that other error regarding JSON responses. I did not see that error. But before we look into this any further, first disable the SEO plugin and let me know please if it makes any difference.

with regards

[alexg]

Hi, this forum is public so it’s best not to post any passwords here. I have deleted your post for this reason.

Please change the password, then send me the new credentials via email.

If you don’t, people can login to your site and install backdoors.

let me know

[alexg]

Hello davej,

Unfortuantely the current API is not compatible with TabTrader. The Exchange’s JSON API is described in the extension’s manual.

with regards

(p.s. I have moved your post into a new thread as it was not related to the other thread)

[alexg]

You don’t need to look for anything. I simply need to review existing email queue plugins to see which ones can be compatible. It should not matter what the capabilities of the server are, the email queues can be configured on how fast to send emails.

I will keep you posted.

[alexg]

Great, I’ll let you know here once it’s ready.

with regards

[alexg]

Hello,

Yes that is correct. In WordPress, individual user capabilities override user role capabilities. The Wallets -> Capabilities page is there for convenience but you can use any plugin that edits capabilities to assign the correct ones.

Glad you sorted this out. Thanks for sharing this issue with the forum.

with regards

[alexg]

Hello,

This looks interesting. First of all, I have to ask, have you by any chance enabled WP_DEBUG_DISPLAY in your wp-config.php? If you did, try turning it off again. When it’s on, any PHP errors from any plugin can be written out to the JSON output.

If you still see the error after turning this off:

The error indicates that one of the responses of the JSON API endpoints is malformed for some reason. Without looking at the output I cannot tell which one.

If you like, you can email me some user credentials and I can log in to your site and see what’s wrong. Administrator access is not required, simply a user with the has_wallets and related capabilities.

Another thing you can try is to disable some of the other plugins and see if it makes any difference.

Email me if you wish for me to have a closer look.

with regards

[alexg]

Hello,

It is possible, but the emails would have to first go into a queue, because there would be a lot of outgoing emails in a very short period of time, unlike the notification emails that are related to individual transactions.

I will have to review existing email queue plugin for WordPress first.

with regards

[Author]

Posts