Enabling Captcha in JotX Comment Forms

Captcha in JotX was often enough to cut comment spam dramatically on older Evolution CMS projects.

The original note was short, but the configuration itself is worth keeping because it solved a real problem fast: comment spam on JotX-powered pages.

Example

[!JotX?
  &moderated=`1`
  &pagination=`5`
  &subscribe=`1`
  &sortby=`createdon:d`
  &notifyEmails=`mail@pochta.ru`
  &captcha=`1`
!]

Why this mattered

On older Evo sites, comment spam often arrived before teams had the time to build more advanced moderation workflows. Enabling captcha, keeping moderation on, and limiting public exposure of raw form endpoints was usually enough to make the comment system manageable again.

Recommendation

If a legacy project still runs JotX or a comparable comment stack, treat captcha and moderation as the baseline, not as optional hardening.

Newer post

Embedding eForm Instances Inside DocLister Items Safely

How to place an eForm inside a DocLister loop without collisions by giving each form instance a unique identifier.

Older post

Handling Multiple Image Size Options in Shopkeeper Product Variants

How to model multiple size or format options in a Shopkeeper-based product when each option changes the visual or commercial presentation.