www.wysiwygwebbuilder.com

I am looking for some suggestions on effective ways to stop spamming.
I just implemented some forms, using the built-in PHP processor.
I am using a Honeypot field, and I have a Validation field on the form that requires an exact match.
I believe the main issue is these are more than likely humans spamming the forms, not a spambot, so getting past a validation field, or a captcha code is no obstacle.

Is there anything else I can use to help block these?

When an actual person is doing it there is nothing much which can be done about this.

But from my perspective making it difficult for bots or spammers also makes it difficult for average humens. But if you still want top security then a server sided otp verification for any emails submitting form can be an option. But that would require custom codes but possible.

Maybe this is helpful?
https://www.wysiwygwebbuilder.com/forms_antispam.html

However, if the spam is submitted by a human then it will be difficult to block it.

You can also use the likes of a .htaccess to prevent a range of ip addresses the downside of this is that you can also block legitimate users from using the form to make contact or even access the site or sites.

There is also the possibility to block spam/offensive words phrases being entered into the textarea and they won't be submitted. One method is just javascript the other is using php and having the words stored in a database and called when the form is submitted and blocked. Neither is available and would require a custom solution to work.
Here is an example from codepen.io
https://codepen.io/mcfan/pen/xVVNwy
Another example from jsfiddle test with one or all of the following words crap, ugly, brat, basterddouch
https://jsfiddle.net/raam86/QZW7K/2

wwonderfull wrote: Wed May 21, 2025 1:37 am But if you still want top security then a server sided otp verification for any emails submitting form can be an option. But that would require custom codes but possible.

Unfortunately, the hosting company that I use does not support server side verification.

BaconFries wrote: Wed May 21, 2025 9:58 am You can also use the likes of a .htaccess to prevent a range of ip addresses the downside of this is that you can also block legitimate users from using the form to make contact or even access the site or sites.

I am currently doing this. I always look up the IP Address to see where it is located. If outside the US, I block that IP (all my clients/customers are in the US and do not have an outside of US audience.

Another idea might be to use a progressive form process, such as not showing the entire form at once. Display it in steps or only after a user clicks a button and/or completes a form field correctly, then move to the next field.

mhinnc wrote: Wed Aug 20, 2025 2:23 pm Another idea might be to use a progressive form process, such as not showing the entire form at once. Display it in steps or only after a user clicks a button and/or completes a form field correctly, then move to the next field.

I would love to do that ... just got to figure it out.
The only method I was told about to do that is by using the Carousel as each page. I tried that but couldn't figure out how to make that work.

This may be helpful:
https://www.wysiwygwebbuilder.com/carouselwizard.html

You can also use the Wizard object to implement multi-step forms.

Pablo wrote: Wed Aug 20, 2025 3:41 pm
You can also use the Wizard object to implement multi-step forms.

Is there a tutorial for using the Wizard object?

There is no tutorial for the wizard, but it's basically works the same as a tab, accordion or other multi-panel container.

Pablo wrote: Thu Aug 21, 2025 4:58 pm There is no tutorial for the wizard, but it's basically works the same as a tab, accordion or other multi-panel container.

And that's why I don't use a Multi-Part form .... still don't know how to create it.
Thanks.

Step 1
Add a wizard

Step 2
Add form controls for the first page

Step 3
Click 'Next'

Step 4
Add form controls for the second page

If you need more pages then you add them via the properties.

Thank you.