Sitekey as general setting

  • Resolved koen Huybrechts

    (@koenhuybrechts)


    5 years, 8 months ago

    Thanks for this plugin!
    It’s a nice addition to the existing GF addons.

    Why do I have to add the sitekey everytime I use the hCaptcha field?
    Isn’t it more efficient to add it as a setting in the hCaptcha setting?

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

    (@webandappeasy)

    5 years, 8 months ago

    Thank you for your reaction!

    I made that decision, because that way you can have multiple hCaptchas on a page which you can track separate on your hCaptcha dashboard. For example when you have a contact form in the body and a newsletter opt-in in the footer.

    Thread Starter koen Huybrechts

    (@koenhuybrechts)

    5 years, 8 months ago

    Thanks for your reply!
    Of course it’s a total legit motivation.

    Is it an option to add the Sitekey both as a setting on GF level and as an option on field level? If there is a Sitekey on the field level, this one is taken. Otherwise, the one on GF level is taken?
    This makes it more user-friendly when less technical users create forms, since they don’t _have_ to find and enter a Sitekey.

    What are your thoughts?

    Plugin Author Kevin Landsbergen

    (@webandappeasy)

    5 years, 8 months ago

    I will integrate a “Global Sitekey overwrite option” for the next update.
    Think it’s a good suggestion for the less technical users as you’re saying.

    Thank you for your input!

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

The topic ‘Sitekey as general setting’ is closed to new replies.