[alexg]

After doing some more investigation:

You coin’s symbol is SCOOBY. This is 6 characters long and the current DB schema for this plugin allows up to 5 character symbols.

https://github.com/dashed-slug/wallets/blob/master/includes/wallets-core.php#L284
https://github.com/dashed-slug/wallets/blob/master/includes/wallets-core.php#L308

Can you try with SCOOB? It should work.

I might increase this limit in the next schema upgrade.

kind regards

[alexg]

Thank you for the additional info. I signed up to your site and had a look at the test page.

As you said, there are no JavaScript errors.

The JSON API does not report a deposit address. This is why it is not shown. When logged in, you can see the response yourself. There is a missing field,deposit_address: https://scoobycoin.com/test/?__wallets_apiversion=2&__wallets_action=get_coins_info

The JSON API code uses the wallets_api_deposit_address filter to get the user’s deposit address: https://wallets-phpdoc.dashed-slug.net/classes/Dashed_Slug_Wallets_PHP_API.html#method_api_deposit_address_filter

If an address is not already assigned to the user, a new address is generated by the wallet via the getnewaddress RPC command. Then, the address is attached to the JSON API response, like so:

https://github.com/dashed-slug/wallets/blob/3.5.4/includes/json-api.php#L612-L618

1. Is it possible that your wallet does not respond to the getnewaddress RPC command? Can you call the command from the CLI to check yourself? For Bitcoin, you would do a bitcoin-cli getnewaddress and it would respond with a string that is a new address. You should replace bitcoin-cli with the name of your wallet’s binary.

2. If the RPC command works as expected, it might be worth looking at your PHP logs. You can enable WordPress logging and then look at wp-contend/debug.log. Then, check to see if any errors appear while the plugin requests a new address.

Please let me know.

kind regards

[alexg]

This is not exactly possible at the moment.

There will be shortcodes in the future to display coin rates.

At the moment you can do the following in JavaScript on the frontend:

• The coin that exchange rates are given against is indicated by walletsUserData.fiatSymbol. This is normally the selection under Wallets > Exchange rates > Default fiat currency but can be overridden in a user’s profile.
• The exchange rate for e.g. Litecoin is accessible as wp.wallets.viewModels.wallets.coins()['LTC'].rate.

Hope this helps. Once the shortcodes are ready I will report it and there will also be a blog announcement.

kind regards

 

 

[alexg]

Hello,

I previously indicated that I would like to implement something with CoinHive but I have not yet found the time to do so.

The plugin you indicate has a slug of bitcoin-faucet and is not developed by me. You need to contact the developer(s) of that plugin for any issues you have.

The wallets-faucet plugin that I have developed does have some basic adblock detection capabilities, and it uses mockingbird for this: https://github.com/retargetly/mockingbird

kind regards

[alexg]

Coingecko is added as an exchange rates provider in 3.5.4.

[alexg]

Hello,

Yes I will add CoinGecko. Thank you for the suggestion.

Additionally, you should know that I recently added cryptocompare in version 3.5.2 (released a few minutes ago).

kind regards

 

[alexg]

This has now been rolled out in 3.5.2.

 

[alexg]

Hello,

There are two issues here:

1. You can safely disable exchange rates if you uncheck all the checkboxes under Wallets → Exchange rates → Exchange rates providers. The only drawback is that fiat amounts will not be displayed on the frontend, and payment gateways such as the WooCommerce payment gateway extension and Events Manager payment gateway extension will not work. Disabling exchange rates will not affect operation of the ShapeShift extension. But again, fiat amounts will not be shown in the ShapeShift extension’s UI.

2. The free plan for fixer.io gives you 1000 API calls per month. The plugin pulls data from fixer once per hour. For a 30 day month this comes out to be 30×24, or 720 calls per month. The plugin will do these calls whether the site is being used or not, as long as it is online. So you see that you should not exceed the limit, if you are using the plugin only on one site. You can always check your fixer account to see how much of the limit you have been using. Simply login to the service and go to your dashboard to check: https://fixer.io/dashboard

If you are using the same API key with multiple sites then you might have to consider upgrading to another plan. If not, then there should be no problem.

Hope this is clear. Let me know if you have more questions.

[alexg]

OK you have now presumably installed correctly, and activated, the multiadapter extension. Can you please tell me the following:

1. You previously reported an error about the qrcode library not being loaded. Do you still get that error?

2. What do you get when you type the following in your console? typeof jQuery.fn.qrcode

3. Do you see any errors now in your JavaScript console?

4. Could it be that you have done the same installation mistake with the main plugin? The main plugin should be installed either by uploading the zip file via the “upload plugin” button or directly from wordpress.org via the admin interface. (You could unzip the plugin manually, but in that case you need to make sure that the directory is named “wallets” and that the file permissions and user ownership match those needed by your web server.)

Let me know.

[alexg]

Hello San,

Yes I am currently working on the exchange and it will be out soon.

Sorry but I cannot be any more specific.

There will be an announcement on the blog as with all news and releases.

kind regards

 

[alexg]

Yes this is possible.

I will do the necessary modifications so that a user can override the site-wide default.

I will let you know here when it is done.

Thank you for the suggestion

kind regards

[alexg]

Hello,

It seems you have not installed the plugin extension correctly. You have extracted the zip file into the plugins directory, retaining the filename as a directory name.

Delete the plugin directory, then go to Plugins -> Add new -> Upload plugin and select the plugin’s zip file for upload.

After this, activate the extension and it should be ready for configuration.

kind regards

 

[alexg]

The link http://scoobycoin.com/wp-content/plugins/wallets-multiadapter/assets/scripts/wallets-multiadapter-validator.min.js?ver=1.0.4 returns 404 which normally means that the script is not on your server. Could it be that the file is missing from your server directory?

 

[alexg]

Thanks for yuor reply.

From the errors you reported it is clear that some of the frontend scripts are not loaded.

The frontend script for the address validator is not loaded, and the JQuery qrcode script seems to be missing too. This would explain your issues. Some thoughts that come to mind:

Could it be some problem with a CDN you use?

Or a misconfiguration of your web server? Try to determine why the assets would not load.

Is this a new installation? Did you change something on your server recently? Does the plugin work when you disable other plugins?

 

[alexg]

Hello,

No, unfortunately this is not possible with this plugin.

The plugin and its extensions are built around the idea that the user deposits crypto and then uses their balance to do stuff, such as pay for a cart.

There are other plugins out there that do what you ask.

kind regards

 

[Author]

Posts