It runs too late. It allows credit card information to be processed, then stops only the entry from being created in the database and notification emails.

2024-07-25 11:24:18.812467 – DEBUG –> GFAuthorizeNet::get_payment_transaction(): Initializing new AuthorizeNetAIM object based on feed #197

…

2024-07-25 11:24:20.171147 – DEBUG –> GF_No_Duplicates::validate_token(): POST request from [form url] using GND Token 20240725103733-a4bb1597a253f5ac105ec977bb89cd4e818708d9 Existing entries using this token: 1 2024-07-25 11:24:20.171220 – DEBUG –> GF_No_Duplicates::validate_token(): GND Token 20240725103733-a4bb1597a253f5ac105ec977bb89cd4e818708d9 was saved to a previous entry!

Hello,

I have the Gravity forms No duplicates installed on our website and I noticed that with form submission there is a considerable delay between clicking on Submit and the actual submission taking place.

Is this something the No duplicates plugin could be causing and if so is there a way around it?

Thanks.

Hello Samuel, could you please help modify or point me in the direction on how to make the plugin prevent same request within 5 minutes or any customisable timeframe.

Currently, the plugin prevents creating any entry that has almost the same values from an already existing entry.

Please help

Hi. Thank you for making this much needed plugin.

Are there any settings?

And how do you know if it’s working or was triggered?

Thank you for making this plugin!

I have two questions that weren’t covered in the readme:

1. Is there any risk that this plugin could accidentally block a valid entry?

2. Will you be maintaining this plugin to be compatible with future versions of WordPress and Gravity Forms? And is there a GH where other developers could contribute?