[alexg]

The main file in any child theme is a style.css file.

Make sure that you have created this file correctly and that the child theme is activated.

Then you can add to this file any CSS rules you like.

All the faucet UIs have classes in the markup. These include the class “wallets-faucet” plus some other classes to differentiate between the different UIs.

For instance, to change the color of the background in the “Faucet earnings” table, you would add something like:

.wallets-faucet.referrals-list table { background-color: lightblue; }

Hope this helps.

[alexg]

Hello, thanks for your kind words.

The get_market_summaries API call provides the information you mention. Please see the accompanying documentation for details.

kind regards

[alexg]

Hello,

You can already control whether withdrawals are enabled or disabled for a group of users (Role), using the capabilities menu.

As for your other requirement, there is no need to use a blockchain address. Simply do an internal transfer (move). You could override the [wallets_move] UI to provide a UI that always sends to the admin account, using a hidden input field rather than a visible user field. Please see the documentation on how to override the knockout UIs. If you create your view in wp-content/plugins/wallets/includes/views/move/toadmin.php, then you can use a shortcode such as [wallets_move template="toadmin"].

kind regards

[alexg]

Thanks Alex, that was quick!

[alexg]

You are of course correct. Apologies for the delay.

I am currently working on a fix which will be out today or tomorrow.

[alexg]

The strings you mentioned, plus a few more, are now translatable in version 0-3.0-beta.

[alexg]

In version 0.3.0-beta of the plugin extension the markets are sorted alphabetically and are searchable/filterable.

[alexg]

In version 0.3.0-beta of the plugin extension the markets are sorted alphabetically and are searchable/filterable.

Icons will be added in a later release.

[alexg]

The max available balance is now updated after order placement in version 0.3.0-beta of the plugin extension.

[alexg]

Orders are now listed in descending order in version 0.3.0-beta of the plugin extension.

[alexg]

With version 1.4.1 you can now use the provided CSS classes to style your UIs.

Either provide a child theme to your theme, or use one of the many plugins for adding custom CSS rules to your page.

kind regards

[alexg]

Thank you.

You are correct, the faucet UIs do not currently have classes to allow for easy styling with CSS.

I will add some classes and will release a patch soon.

I will let you know here once this is done.

with regards

[alexg]

Hello,

Glad that this fixed it. I will have to see if somehow this fix can be incorporated in a future patch.

1. I cannot see how this fix would negatively affect anything else.

2. The plugin maintains for each user and coin one “current” address that is displayed, and a number of “old” addresses that are retained so that if a user attempts to send funds to an old address, the funds can still get credited to that user. If you have no need for these addresses then you can delete them. Clicking on “Renew deposit addresses” under a coin in the adapters list marks all deposit addresses for that coin as “old”, and the plugin will next produce new “current” addresses. This is a way to make sure that the displayed deposit addresses are renewed.

3. I would recommend that you do not do any more changes.

4. No. See #2 above.

[alexg]

Hello,

Normally addresses are not refreshed on every reload, but stored in the DB and reused (table: wp_wallets_adds). You can then manually ask to refresh addresses. So you could check the table to see if addresses are being saved in it. This table normally holds an association of user_ids and coins to deposit addresses.

If addresses refresh on every reload, this could indicate that they are not saved on that table, due to some DB problem. The table requires some non-standard features (latin1 encoding). This could be damaged, for example, if you have exported the table from another machine and imported the SQL manually into your current installation. (see also the discussion here).

Could you please show me the result of DESCRIBE wp_wallets_adds on your MySQL console (replacing wp_ with your default DB prefix if needed)?

Additionally, there could be some related error in your mysql error.log file. This would indicate that addresses are not inserted. If you could spot such an error it would be very helpful for determining the root cause of the problem.

with regards

[alexg]

Hello,

I had another look. The deposit fee is handled correctly. This is also illustrated by the screenshots you posted above (see Capture-CP-Transaction-test-1.0.7.png).

amount = 0.995
amount+fee = 1.000

This is the expected behavior.

with regards

[Author]

Posts