You’ve installed the plugin and a coin adapter, and the shortcodes show the message “No currencies are currently enabled”. Here’s how to debug this.
If you have installed and correctly configured a coin adapter, and the plugin’s shortcodes display the message “No currencies are currently enabled.”, then this guide is for you!
Is the adapter correctly configured?
Go to Wallets → Adapters. At least one adapter must show a status of “Responding”. If not, correct the issue until the adapter is responding.
Does the API key have all required permissions? (CoinPayments adapter only)
If you followed the video for installing the CoinPayments adapter, you may not have assigned all the required permissions. There is one permission missing from the video. Check the installation guide at step #23, and add the
get_callback_address permission to your API key if you haven’t already.
Is your server-side cache showing you stale output from before you configured the coin adapter?
Clear your server side caches and reload the page with the shortcodes. These caches can include (but are not limited to) WP Super Cache, W3 Total Cache, WP Fastest Cache, WP-Optimize, etc.
Is your HTML markup being optimized/minified/compressed?
Many cache plugins and other optimization plugins (e.g. WP-Optimize) offer an option to optimize the HTML output. If you are running any such plugin, please disable the feature that optimizes HTML.
Is the JSON API working as expected?
The frontend communicates with the backend using a custom-built JSON-API to retrieve data and perform transactions. It is possible that this API is not accessible. Navigate to
www.example.com with your site’s domain name). The result should be valid JSON, and should include details for at least one coin.
If the page is not shown, check your HTTP server’s configuration (
.htaccess files in Apache,
.conf files in Nginx). Check your security plugins to see if any such plugin is blocking access to that URL. If this is the case, you may need to whitelist URLs that contain the GET parameter “
PRO TIP: You can also use the browser console’s Network tab to inspect calls to the JSON-API. These calls will be listed under “XHR requests“. Calls should succeed (with HTTP status 200) and should return responses in JSON format.
Do you see an alert box complaining about invalid JSON?
If you see a popup box with a message such as: “Could not contact server. Status: parsererror Error: SyntaxError: Unexpected token < in JSON at position XYZ”, then the result you get from the
get_coins_info call is not valid JSON. This is usually caused by some plugin or theme causing a PHP error, which gets printed in the API output and causes it to become invalid.
You should instruct WordPress to hide any PHP errors from the front-end. Add
define( 'WP_DEBUG_DISPLAY', false ); in your
wp-config.php. Ideally you should aim to fix any PHP errors on your site, but this constant will at least hide them from the front-end, and from JSON-API responses.
Does the knockout observable contain any coin info?
wp.wallets.viewModels.wallets.coins(). This must contain the same information as that returned from the