Limit Checkboxes 1.3.23 – for Gravity Forms

When a form has a “Pick up to 3 options” checkbox list, Gravity Forms doesn’t enforce that by default. Users can tick everything, submit, and you end up cleaning the data later. I’ve seen this most on pricing calculators, event add-ons, and “choose your bundle” screens.

Limit Checkboxes – for Gravity Forms solves that one job: cap how many checkboxes can be selected in a single Checkbox field. No theme hacks. No fragile “HTML5 required” tricks.

How it works (and where it actually lives)

I treat it as a Gravity Forms add-on that hooks into the form rendering + validation pipeline.

What I see in practice:

• You set a per-field limit in the Gravity Forms Form Editor (Checkbox field settings). That setting becomes part of the form meta Gravity Forms stores in the DB (the same form JSON you’ll find in the wp_rg_form_meta table).
• On the frontend, it usually adds a small JS behavior to prevent/selectively undo extra checks.
• The important part: it also needs server-side validation so bypassing JS (or breaking JS) doesn’t let invalid submissions through. In Gravity Forms terms, this is typically done via validation hooks (the “gform_*_validation” family).

Editable vs hardcoded:

• Editable: limit value per field (inside the Form Editor UI).
• Hardcoded/extendable: if you need conditional limits or custom messages, you still do that in PHP with Gravity Forms hooks (theme functions.php or a small mu-plugin). I do that when the “max” depends on another field.

Assets/caching reality:

• Gravity Forms scripts are enqueued on pages where the form shortcode/block renders. If your optimizer delays/defer/minifies the wrong file, you don’t get the client-side guardrail, and the form feels “broken” even if server validation still blocks submission.

Where it usually breaks (and the fastest fixes)

I’ve seen three repeat offenders:

1. JS optimization breaks the click-limit behavior
   Root cause: cache/minify plugins delay jquery-core or Gravity Forms’ own runtime, so the limit script runs before window.gform is ready (or runs on a cached HTML variant that doesn’t match the form).

Fix (fast):

• In your optimization plugin (Autoptimize / WP Rocket / LiteSpeed Cache / Perfmatters), exclude from delay/defer:
  • jquery-core
  • Gravity Forms frontend scripts (search in DevTools → Network for files containing gravityforms / gform)
  • the plugin’s own script (usually contains limit or the plugin name in the filename)
• DevTools check: open Console and look for gform is not defined, $ is not a function, or missing script 404s in Network.

2. Multi-page / AJAX forms behave inconsistently
   Root cause: the checkbox inputs are re-rendered on page transitions or AJAX confirmations, so event handlers bound “once on load” don’t reattach.

Fix (fast):

• Enable the plugin’s server-side validation (if it has a toggle).
• If the issue is only UX, rebind on Gravity Forms render events (the practical signal: it works on first page load, fails after “Next”).

3. Conditional Logic hides options, but the limit still counts them
   Root cause: some implementations count checked boxes regardless of visibility state.

Fix (fast):

• Confirm what’s being counted: visible checked vs all checked.
• If needed, enforce counting rules server-side (I prefer “count checked inputs that are actually submitted”, not what the DOM used to contain).

Licensing / activation / updates (what you actually get)

In my install this plugin behaves like a straightforward utility add-on: no license key screen, no activation gate. It runs as soon as it’s activated, and the limit logic works immediately (I tested it live).

Updates are the normal WordPress story:

• If it’s connected to the WP updater, update from Plugins → Installed Plugins.
• If you’re on a packaged build, update by uploading a new ZIP (or via FTP). As always: don’t edit plugin files directly, because updates overwrite them—put custom validation in a snippet plugin or mu-plugin instead.

You can find detailed instructions on how to update a theme or plugin on this page.

FAQs (the real pain points)