Support » Plugin: Gravity Forms Duplicate Prevention » Cryptographic hash and unique ID fields

  • Resolved Harelin


    I use Gravity Perks ( to generate a Unique ID with every form submission.

    Some relevant info about this plugin: “It’s important to note that in order to guarantee that the ID is truly unique, the field is populated only after the form has been successfully submitted. Since the field has no value prior to submission, this field is not visible on the frontend.”

    Does this negate the usefulness of your duplicate prevention mechanism, in the context of the cryptographic hash? Would this cause every submission (duplicate or not) to have a unique hash, therefore removing its ability to detect duplicates?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Steve Grunwell


    Gravity Perks shouldn’t conflict with Gravity Forms Duplicate Prevention. GFDP’s primary prevention method is simply disabling the submit button via JavaScript, so that should fire unless you disable the script (via the gform_duplicate_prevention_load_script filter) or the user has JavaScript disabled.

    The second line of duplicate prevention (and the one you seem to be concerned about) creates a hash from the raw HTTP POST data, which Gravity Perks’ ID would not be included in (as their documentation states the ID is generated after a successful form submission).

    Hopefully this answers your question, and please let me know if you do run into conflicts. Thank you for using Gravity Forms Duplicate Prevention!

    P.S. Sorry it took a few days to see this, I haven’t been keeping up on my RSS feeds as much as I should be :/


Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Cryptographic hash and unique ID fields’ is closed to new replies.