[alexg]

The fix is now out in version 5.0.1 of the plugin. Thank you.

[alexg]

Hello,

I’m very well, hope you are well too.

Thank you for spotting this regression. I have been able to reproduce the issue and find a fix.

The previous fix in version 4.3.1 was to only load the plugin’s qr code library if it was needed on the current page. This way, assuming you are not using the shortcodes [wallets_deposit] and [twofactor_user_settings] in the same page, the issue would not arise.

Some performance enhancements were added in 5.0.0, including lazy-loading the QR code library. The library is now registered always but only enqueued if needed. This causes the current issue, because the wallets plugin always registers (and therefore overrides) the library used by the 2FA plugin.

I have already accumulated some minor fixes on version 5.0.0 on several issues. I plan to release a patch to the plugin very soon, possibly today or tomorrow, where this issue is fixed. I will post again here when this is out. Until then, you can either revert to version 4.4.8 of wallets, or disable QR codes from the frontend settings.

I will notify you again here when this is out, and there will be an announcement on facebook and twitter as with all releases.

with regards

[alexg]

Hello, I have replied about this issue to the original post at https://wordpress.org/support/topic/html-comments-error/

[alexg]

@alecmtetwa Hello, I have replied about this issue to your original post at https://wordpress.org/support/topic/html-comments-error/

[alexg]

A QR Code scanner has been added in version 5.0.0. Full release notes here: https://www.dashed-slug.net/wallets-5-0-0/

[alexg]

This is now permanently fixed in version 5.0.0 of the plugin. Full release notes here: https://www.dashed-slug.net/wallets-5-0-0/

[alexg]

Well, this didn’t take long.

Sadly the answer is no, you can’t use this service with the plugin as it is. These are the RPC commands allowed: https://support.blockdaemon.com/hc/en-us/articles/360032625252

You are not allowed to issue some commands that are used by the plugin, most importantly getnewaddress, sendtoaddress and getbalance.

In any case, if you are still interested in setting up a full node, you can email me, or post here about the difficulties you encountered, and I can try to help.

[alexg]

Hello Andy,

Interesting. I haven’t tested this service, but I think it can work. The reason I say this is that at the “PRICING & CAPABILITIES” section they mention “JSON-RPC with TLS”.

The plugin wants to communicate directly to the wallet over the JSON-RPC port (8332 by default). Since this connection is plaintext, normally you wouldn’t do that over the internet without some extra technology that adds encryption.

In the past, Bitcoin supported SSL via a bitcoin.conf option, rpcssl, which the plugin is compatible to. I have kept the option in the plugin because some other wallets might still be using it. The plugin uses easybitcoin’s ssl feature.

The real question here, is what do they mean by TLS. Do they mean SSL? Do you have to set up your own tuneling? Do you need to set up a certificate?

I will test the service today and find out if it works with the plugin.

I am currently busy finalizing the upcoming release 5.0.0 of the plugin. If the plugin can use this service with some minor modifications, these modifications will go into the release.

Give me some time to check, and I will get back to you soon with more details.

with regards

[alexg]

Hello,

Actually the error message you found is very helpful. It means that the plugin cannot contact your wallet.

Reasons for this can be:

1. the rpcallowip= line in your conf. You probably have something like rpcallowip=5.146.4.167/24 in your conf. But if you’ve set up NAT then connections should be coming from your modem/router. Try adding something like rpcallowip=192.168.0.1/8, assuming this is the IP of your router. Whatever you do make sure to use CIDR notation (i.e. include a netmask as shown above)

2. NAT configuration. Double check the port forwarding rules in your router. You want port 8332 to be forwarded to your local network address.

Hope this helps.

with regards

[alexg]

Hello,

I have now built and tested the plugin with Bitcoin 0.19.1. I have not spotted any issues with generating new addresses.

You mentioned that you tested 0.19.9 which is not out yet, I’m guessing you meant 0.19.1.

Please let me know if you spot any issues in your logs while attempting to generate new addresses.

Also, it would be helpful to look into the database. Can you execute the following query?

select status,count(*) from wp_wallets_adds where symbol='BTC' and account=1 group by status;

This would show you how many BTC deposit addresses for the admin user are marked “current” and how many “old”. After hitting “Wallets” -> “Adapters” -> “Renew deposit addresses” all the addresses should be marked “old”, meaning that calling get_coins_info would then create new addresses. Again, if there is a problem this would probably show in the WordPress debug log (wp-content/debug.log) or bitcoin log (~/.bitcoin/debug.log).

Please let me know if you find anything of interest. I will continue to look for a situation where this issue could arise.

with regards

[alexg]

Hello,

I have now pushed version 1.3.0 of the Tip the Author extension, where it is now possible for guests to see the tip list. Additionally, the admin can choose how the past tips are sorted before display.

with regards

[alexg]

Thanks for the feedback.

I will release very soon a new version, where the tips list for an article will be displayed whether the user is logged in or not. There will be an option on how to sort tips.

In general this extension needs to be reworked. I am currently busy with the upcoming major version 5.0.0 of wallets. The most important change in 5.0.0 is that the output of all shortcodes will be theme-able. This will gradually affect all the extensions as well, including Tip the Author. One of the things I want to do after 5.0.0, is to revisit this extension and improve on the way tips are displayed, especially when there are many tips.

Since the markup will be theme-able, it will be easier to modify what is displayed and what not, either at the theme or child-theme level. There will be blog posts about these changes.

with regards

[alexg]

Hello,

1. I am not sure why only IPv6 worked. In any case running your wallets on a home machine is tricky. If it works now, then that means that you’ve set up NAT forwarding correctly. Don’t forget to put your machine and modem on a UPS for maximum uptime. Also, you’ll need a static IP for this to work. If your residential modem restarts or reconnects and you have a dynamic IP, it will be different each time.

2. The “Renew deposit addresses” feature simply marks all deposit addresses as “old”. Next time the user logs in to the frontend they will be assigned a new deposit address. I am not sure why this happens but I will test with the latest Bitcoin core and will report back. In the meantime you can check your wallet’s log file, or enable WordPress logging and check the debug log for any problems. If there is an issue it will show up when you call the get_coins_info endpoint: (https://www.example.com/?__wallets_apiversion=3&__wallets_action=get_coins_info)

There shouldn’t be any problem with bech32 addresses as far as the plugin is concerned. If you want to force your wallet to generate another type of address, you can set addresstype in your conf file. Consult bitcoin-cli help getnewaddress for details.

I will test with 0.19.1 and get back to you.

with regards

[alexg]

Hello,

To define the dimensions of the chart in pixels, use the width and height attributes. For example, to display a 200×200 chart:

[wallets_exchange_chart width="200" height="200"]

See the documentation under “Frontend” for details on exchange shortcodes.

with regards

[alexg]

Hello,

First of all, as @scorza420 mentioned, it’s a good idea to place the wallet shortcodes in a page that is only viewable by your members.

However, even if you don’t do this, it should not be possible to see user-specific data such as balances or deposit addresses when you are logged out. If you are seeing this info when logged out, it indicates a problem with your server cache.

Try this: logout, then go to https://www.example.com/?__wallets_apiversion=3&__wallets_action=get_coins_info (replacing example.com with your domain name) and see what you get. You should normally see a JSON response like the following: {"result":"error","code":-106,"message":"Must be logged in or specify a valid API key"}

If you instead see actual coin information, you should whitelist the plugin’s JSON-API in your server-side cache plugin(s). This could be “W3 Total Cache”, “WP Super Cache”, “WP-Optimize”, or some other plugin. You can exclude all URLs that have the _wallets_action GET parameter.

Please let me know if you continue to face this issue.

with regards

[Author]

Posts