reCAPTCHA v3 Implementation Update

  • Given the implementation issues, undesired design (for some users), as well as the machine ‘learning curve’ required with reCAPTCHA v3, would it be possible to consider an update which would:

    – Automatically use reCAPTCHA v2 if [recaptcha] if detected within one or more form templates (there could be a one-time scan on plugin activation and then following that, a check each time a form template is saved)

    – Otherwise, use reCAPTCHA v3

    This would be a far more user-friendly way to handle the v2 to v3 push than the current all or nothing approach.

    Any consideration for this?

    • This topic was modified 5 years, 11 months ago by wplegacymu.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter wplegacymu

    (@wplegacymu)

    Just realized what the plugin author was saying.

    The plugin update literally removes the v2 keys so your options are:

    1). Downgrade/prevent it from updating AND re-add your v2 keys

    2). Following the forced upgrade procedure and add v3 keys, removing the [recapcha] from your form templates.

    Removing data as part of a plugin update is a decision that shouldn’t be taken lightly and in this case, it was really a massive oversight.

    Thread Starter wplegacymu

    (@wplegacymu)

    Actually it does keep the old keys handy so just a downgrade and version lock will do the trick until this spam-happy business gets sorted out.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘reCAPTCHA v3 Implementation Update’ is closed to new replies.

Tags