• Resolved Anthony Eden

    (@anthonyeden)


    Hello,

    The function mo_oauth_login_validate() is hooked into ‘init’, so it runs all the time.

    However, it does a check for the URL Parameter ‘code’, and returns ‘No request found for this application.’ if a set of other parameters aren’t found.

    This breaks Wordfence’s 2FA setup process, but it also breaks anything else that uses the URL Parameters ‘code’ – anywhere in WordPress!

    I’d suggest adding some extra checks to ensure this function actually needs to run, instead of just assuming it always should.

    This is sloppy. Please fix 🙂

    Thanks,
    Anthony.

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

    (@cyberlord92)

    Hi @anthonyeden,

    Thanks for reaching out to us and sorry for the inconvenience caused to you.

    We will take care of this issue with the next update of our plugin which will be released soon so that you won’t face any such issue due to conflicts between the plugins.

    Also, can you please drop an email to [email protected] if you have any other questions or need any help regarding our plugin, so we can assign an engineer for your query to guide you better?

    Thanks,
    Team miniOrange

    Thread Starter Anthony Eden

    (@anthonyeden)

    Thank you – I will keep an eye out for the update!

    Plugin Author miniOrange

    (@cyberlord92)

    Hi Anthony,

    We have resolved the conflict with the WordFence 2FA plugin in our latest plugin release (6.20.3).

    Let us know if you need any help regarding the plugin. You can also drop an email to [email protected] if you have any other questions.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘‘code’ URL parameter conflict with Wordfence 2FA’ is closed to new replies.