January 26, 2019 at 7:57 am #5602AnonymousInactive
In the withdraw, deposit and transfer pages it says on top: No currencies are currently enabled.
Currencies are enabled and their status is “Responding” under adapters.
Also, in Deposit, the QR appears but no addresses are shown in the address field.
What can be the issue?
January 26, 2019 at 1:03 pm #5604AnonymousInactive
I just found this..
I am checking the options now..
RegardsJanuary 26, 2019 at 3:23 pm #5606AnonymousInactive
I added notes to the original post about this issue in the above mentioned link…January 28, 2019 at 11:21 am #5618
Thanks for reporting and posting your progress.
I will look at how to warn the user if “Hide My WP” hides the JSON API! There should be a setting in every security plugin to exclude certain pages or types of calls from being cached. The JSON API is based on GET parameters, so look for something that disables caching on pages with GET parameters in the query string.
with regardsJanuary 28, 2019 at 11:23 am #5620AnonymousInactive
Thanks Alex, for the reply..
In fact, Hide My WP works fine with the plugin. However Wordfence does not.
I advise to use Hide My WP along with the exchange..January 28, 2019 at 11:38 am #5627
Thanks. Wordfence works fine with the plugin, as do all server side security or cache plugins. But it might need a little tweaking in your case.
It is possible that the issue is related to IP geolocation or some other setting. The main thing to check is that the JSON API returns correct and recent data via your browser. All plugins can be configured to exclude requests with GET parameters from caching and/or blocking.
with regardsJanuary 28, 2019 at 11:40 am #5628AnonymousInactive
Good to know…
Thanks for the details, and I am sure it was something I did with the settings.
The fresh installation works great.January 28, 2019 at 11:50 am #5629AnonymousInactive
So, can Cloudflade’s caching be a problem?January 29, 2019 at 9:10 am #5659
Yes, anything can cause problems if it blocks or caches the plugin’s JSON API. So, caching plugins and security plugins are the usual culprits. Requests with the
__wallets_actionGET parameter must be allowed to run unmodified. You should be able to configure any such plugin to exclude these requests.
- You must be logged in to reply to this topic.