DB Save Function creates Honeypot Check Failed Message

I have created a form on our test server and have tested with and without the DB Save in the onSubmit (with the proper table). It operates well without the DB Save function, but with the DB Save function in onSubmit every test creates a honeypot check failed error message.

How do I combat this? I would prefer to have DB Save in place.

Hi jelliott,

Do you have an Event Loop action in the DB Save On Fail box? That might explain this behaviour. What do you see if you add a Debugger action?

Bob

Hi Bob,

There are not interior boxes for success or fail within my DB Save function? It is a simple box like Display Message. DB Save is enabled and connected to the proper table. I'm assuming there should be success and fail boxes given your question.

When adding the Debugger option, the error message changes to You Have Entered the Wrong Verification Code, I have not, but I get this message. I am also taken to a blank page that I must refresh to see the message. Funny thing is, I still receive all of the email messages...

Jillian

Hi,

Please post a screenshot for your setup section!

Regards,
Max

Is this out of order somehow?

Thanks,
Jillian

Hi Jillian,

I suspect that you don't need both the HoneyPot and the Captcha as they do more or less the same thing. I'd stick with the HoneyPot as it is less obtrusive to the 'real' user.

Your DB Save won't run normally run after a ReDirect action as the user has already been redirected somewhere else The ReDirect needs to be the last action in the sequence.

Where are you redirecting to?

Bob

Ok, I will rearrange the order of actions and I have removed the Honeypot (my company prefers Captcha). Redirecting to a thank you page.

Thanks for taking a look.

Now when tested, I am directed to a blank page after submitting the form. It functions perfectly without the DB Save option.

Any suggestions?

Jillian

Completely full blank page or just a blank body ? if its the first then please go to your Joomla global config and set "Error reporting" to "Maximum" and try again, do you get an error ?