[alexg]

Hello,

Glad you resolved the issue, but this has probably nothing to do with versions.

You should have the latest versions installed. Latest wallets version is currently 5.0.4, and latest fiat adapter version is 0.5.1-beta.

Whether you see the fiat currencies listed depends on whether the Exchange Rates subsystem has had a chance to retrieve the latest data from fixer.io.

So, my recommendation is that you check to see that you have the latest versions installed in all components, then go to “Wallets” -> “Exchange Rates” and hit the button “Clear/refresh data now”. This will force the plugin to pull the data immediately.

with regards

[alexg]

Hello,

All of the above can be adjusted with CSS. I do not normally give advice on this because

A. it’s the job of you or your web developer, and most importantly
B. it depends on how your theme works

In any case, I will attempt to give you CSS rules, hoping that they will match your theme’s styling rules.

1. .dashed-slug-wallets-exchange.market-order select { background-size: 2em; }

2. .dashed-slug-wallets-exchange.market-order table { margin-bottom: 0; } .dashed-slug-wallets-exchange.market-order input[type=submit] { margin-top: 0; }

3. .dashed-slug-wallets-exchange.market-order input[type=submit] { display: block; margin: 0 auto; }

4. There are actually four columns in the table, with widths set to 20% 35% 35% 10%. Here’s how you would set them to 10% 40% 40% 10%:

.dashed-slug-wallets-exchange.market-order thead th.label-col { width: 10%; }
.dashed-slug-wallets-exchange.market-order thead th.amount-col { width: 40%; }
.dashed-slug-wallets-exchange.market-order thead th.coin-col { width: 40%; }
.dashed-slug-wallets-exchange.market-order thead th.swap-col { width: 10%; }

with regards

[alexg]

OK, I am still not sure I understand.

How does the exchange mix with users receiving payments?

Users can already receive payments to their deposit addresses, and then they are free to use these amounts on the exchange if they wish.

Perhaps you can give me an example use case of what you mean?

thank you

[alexg]

Hello,

I am sorry I did not understand if this was a question or a suggestion?

Can you please rephrase? Thank you.

with regards

[alexg]

Hello,

Thanks for the heads up. It seems the styling can vary across themes. You can add the following CSS to your site to make it look better.

.dashed-slug-wallets-exchange.market-order select {
	width: 100%;
	height: 2.6em;
	background-position: right 8px center;
	background-repeat: no-repeat;
}

I will add this to the next release of the plugin.

with regards

[alexg]

Hello,

Thank you for the additional details. But what I asked, is what series of steps did you take to see this error? What did you do in WCMp? How did you request for commissions to be paid?

Only report this issue to the gray parrots if you can reproduce the problem with their own payment gateways. If you can only reproduce the problem with the Crypto payment gateway, then please describe how you arrived at the problem. Once I can reproduce it, I will dig into the code myself.

thanks

with regards

[alexg]

Hello,

Just keeping you updated, I have been developing a solution for turtlecoin and clones. Dev is about 60% done and I hope to finish the remaining dev and testing over the next week if no issues crop up during the weekend.

with regards

[alexg]

Hello,

Thank you for reporting. It is unlikely that this is an issue with WCMp. It is far more likely that this is an issue related to the gateway.

Please help me reproduce the issue step-by-step. Then I can look at why this happened.

You have traced the exact line where the error is thrown, but this might be not the root cause. Once I can reproduce the problem on my machine, I will be able to fix it, or at least tell you what went wrong.

with regards
Alex

[alexg]

Hello Duane,

The issue you discovered is now fixed in version 5.0.4 of the plugin.

Thanks again for reporting it.

with regards

[alexg]

Ooops! This is my mistake. Thank you for letting me know.

I will correct it in the next patch release, which will be out soon.

I will notify you again here.

with regards

[alexg]

Thank you.

I will think about it. The idea of asking the user to login is something that could perhaps be added to all the UIs, not just the tipping UI. It is possible that this requires a more general solution.

with regards

[alexg]

Hello,

For a currency to appear in the checkout page, all of the following must be true:

1. The adapter status for this currency must be shown as “responding”. This is found in Wallets -> Adapters.

2. The currency must be selected in WooCommerce -> Settings -> Payments -> “Bitcoin and Altcoin Wallets” -> “Accepted coins” (or, alternatively, no coins in the list must be selected).

3. The exchange rate between the shop’s currency and the coin must be available:

The shop’s currency is in WooCommerce -> Settings -> General -> “Currency options” -> Currency. In your case this is EUR. So, go to Wallets -> Exchange Rates -> “Exchange rates debug views” -> “Exchange Rates” and check to see if the EUR_USD or USD_EUR exchange rate is found there.

4. The user must have enough balance in that currency to pay for the current cart contents. If the user does not have enough balance in this currency, the option for this currency is not shown.

Please check all of the above and let me know if you still can’t figure it out.

with regards

[alexg]

Hello,

CMC integration is now working again in version 5.0.3 of the plugin.

You are now required to enter an API key, which can be obtained for free from CMC. Previously, the API key was optional.

If you have enabled any fiat currencies using the Fiat Coin Adapter Extension, then you should also enable the fixer.io service via an API key. This helps the plugin know which currencies are considered fiat, so that it does not attempt to query the CMC server about them.

Thanks again for letting me know about this issue.

with regards

[alexg]

Then you need to have the EUR_USD or USD_EUR exchange rate. Have you set up fixer?

[alexg]

Hello again,

Turns out the reason for error 400 is that v1 of the API, which the plugin currently uses, has been discontinued: https://pro.coinmarketcap.com/migrate/

I will develop a new solution based on the latest API and will publish an update to the plugin soon.

Thank you for bringing this to my attention.

with regards

[Author]

Posts