I reply to all queries on the forums and via email, once per day, Monday to Friday (not weekends).

If you are new here, please see some information on how to ask for support. Thank you!

kses after update of

dashed-slug.net › Forums › General discussion › kses after update of

Tagged: ,

  • This topic has 4 replies, 2 voices, and was last updated 6 years ago by Anonymous.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • June 5, 2019 at 1:13 pm #6437
    Anonymous
    Inactive

    I checked and the other plug-in that is due for update shows its version details OK. I will leave it not updated. “view details” on all the other plug-ins seems ok too.

    June 6, 2019 at 8:29 am #6443
    alexg
    Keymaster

    Hello,

    Thank you very much for reporting this and for providing detailed information on the problem.

    I can confirm that this error occurs, and I am able to reproduce it on my machine.

    This issue will not prevent you from updating to the latest version of the CoinPayments adapter, it only prevents you from seeing the changelog before updating. The changelog is also found in the plugin’s zip file, in CHANGELOG.html. I am posting here the latest entry in case you wish to review it:

    1.1.0

    • Add: It is now possible to edit fee settings per individual coin.
    • Add: It is now possible to edit the minimum withdrawal amount for each individual coin.
    • Add: The minimum withdrawal amount is initialized to the amount enforced by the platform.
    • Add: The fixed withdrawal fees for each coin are initialized to the fees incurred by the platform.
    • Add: If the admin enters a withdrawal fee or minimum withdrawal amount less than that allowed by the platform, the value from the platform is used instead.
    • Fix: Do not show admin warnings to users who do not have manage_wallets.

    I will investigate further this issue on my end and will report here any findings.

    with regards

    June 6, 2019 at 9:47 am #6446
    alexg
    Keymaster

    I was able to resolve this issue, it was a minor defect on the update mechanism.

    You might continue to see this error for up to a few hours, because the update info is cached. Eventually the data will be refreshed and you will not be seeing this error any more.

    Thanks again for your help in identifying it.

    June 6, 2019 at 10:05 am #6447
    Anonymous
    Inactive

    Excellent, thanks!

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.