Blog Sections Open
Using antispam and Captcha with JotX
If antispam seems to “do nothing”, verify what fields it actually injects and whether your template or theme is hiding them.
JotX antispam can appear broken when the expected hidden fields are not visible in the rendered form, but the real issue is often in the template layer rather than the feature itself.
What to verify
- whether the antispam option is enabled in the snippet call
- whether the generated hidden field is being styled away or removed
- whether Captcha is configured separately from the antispam helper
Key point
Antispam and Captcha are related but not identical protections. One may add honeypot-like behavior, while the other requires explicit visual verification setup.
Recommendation
Inspect the rendered HTML first. If the field is present but the form still fails, move on to validation and submission logs. If it is missing entirely, the issue is in the rendering path.
Creating Resources from eForm Data with docBuilder
Turning a form submission into a new resource becomes much easier when the field-to-document mapping is declared in one readable array.
Counting Only Visible Children with ChildCounter
If a menu counter should ignore hidden resources, include the hidemenu condition in the document query instead of counting every child indiscriminately.