ArcanePOS API’s blocked by Wordfence

  • Resolved aetherscythe

    (@aetherscythe)


    3 years, 4 months ago

    In the following file:

    Filename: wp-content/plugins/terminal-for-stripe-and-woocommerce/terminal-for-stripe-and-woocommerce.php

    Please add a filter to avoid Wordfence blockage of ArcanePOS API calls.
    Or better yet, put an option in the plugin settings to toggle this setting.

    Line ~218:
    add_filter( ‘wordfence_ls_require_captcha’, ‘__return_false’ );

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author arcanedevops

    (@arcanedevops)

    Thanks. We’ll be sure to pass this to the dev team for the next sprint. There’s a release scheduled for today or tomorrow, so this will have to be handled in the following sprint but that should be a fairly quick one.

    Plugin Author arcanedevops

    (@arcanedevops)

    This is slated for the next release. We had to postpone this due to the patch required for the Stripe Gateway 5.8 regression error. The next release will be 2.2.0.

    Plugin Author arcanedevops

    (@arcanedevops)

    Hi there,

    Your requested filter has been added to the plugin’s init function. Unfortunately we were unable to reproduce any interference with the plugin’s functionality on web or mobile, so we are unable to test the results of this update. Hopefully it resolves your needs. If not, please do let us know how you are able to achieve your needs.

    Version 2.2.0 has been released today.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘ArcanePOS API’s blocked by Wordfence’ is closed to new replies.