Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

Fluent Forms Conditional Logic Not Working: Causes and How to Fix It

Fluent Forms Conditional Logic Not Working: Causes and How to Fix It

Short answer

Fluent Forms conditional logic usually fails because the rule compares a label instead of the stored option value, uses equal on checkboxes instead of contains, uses All when it needs Any, or a caching plugin delays Fluent Forms scripts. Check the rule first, then caches and conflicts.

Key takeaways

  • Conditions compare stored option values, not visible labels.
  • Use contains for checkboxes and multi-select fields.
  • Use Any when the conditions are alternatives.
  • Chained rules break when a parent field is hidden.
  • Script delay and combine options can stop rules reacting.
  • Conditional emails need exact value matches too.

Why is Fluent Forms conditional logic not working?

Fluent Forms conditional logic usually fails because a rule compares a label instead of a value, uses the wrong operator or match type, depends on a hidden field, or script optimisation blocks Fluent Forms JavaScript.

Conditional logic decides whether a field, container, step, email or confirmation is used, based on answers in other fields. When it breaks, fields either never appear or never hide.

Most problems are settings mistakes rather than bugs. Check the rule itself before you look at caching or conflicts.

Fluent Forms explains how rules are built in its conditional logic documentation. If you are new to the plugin, start with our guide on how to use Fluent Forms.

How is conditional logic set up in Fluent Forms?

Open a field's settings, go to Advanced Options, enable Conditional Logic, choose whether all or any conditions must match, then add rows that pick a field, an operator and a value.

The match type matters. All means every row must be true. Any means one true row is enough.

Each row has three parts: the field to check, an operator such as equal or contains, and the value to compare against.

The same rule system appears in email notifications, confirmations and some integrations. A problem in one place does not always mean a problem everywhere.

Are you comparing against the option value or the label?

For dropdowns, radio buttons and checkboxes, conditions compare against the stored option value, so a rule fails if you type the visible label and the value is different.

Fluent Forms lets you show separate labels and values for choice fields. For example, the label might read Yes, please call me while the value is yes.

Open the choice field and turn on the option to show values. Copy the exact value into your condition, including capital letters and spaces.

This is the single most common reason conditional logic seems to do nothing.

Are you using the right operator?

Use equal for single-choice fields, contains for checkboxes and multi-select fields, and greater or less than only for numeric fields; the wrong operator makes a rule silently fail.

Field typeBest operatorCommon mistake
Radio, single dropdownEqual / Not equalTyping the label instead of the value
Checkboxes, multi-selectContains / Not containsUsing equal, which fails with several ticks
NumberGreater than / Less thanComparing text or formatted numbers
Text, emailEqual, contains, starts withExtra spaces or case differences
Hidden fieldEqualValue set late by another script

Checkbox fields hold a list of selected values. An equal rule only matches when exactly one box is ticked, so contains is usually the right choice.

Number comparisons fail if the field includes currency symbols or thousand separators. Compare against plain numbers.

Text comparisons can also fail on small differences. A trailing space, a capital letter or a typing variation such as e-mail versus email is enough to stop a match. MDN's notes on string comparison show why browsers treat these as different values.

When you can, replace free text with a dropdown or radio field. Fixed choices give fixed values, which makes rules far more reliable.

Is the rule using All when it should use Any?

If you set the match type to All but only one condition can be true at a time, the field will never show; switch to Any when the conditions are alternatives.

For example, showing a field when the country is UK or Ireland needs Any. With All, the country would have to be both at once.

Mixed logic, where you need some rules combined with and and others with or, may need condition groups or a different form structure. Check your Fluent Forms version for group support.

Does the rule depend on a hidden field?

When a condition depends on a field that is itself hidden by another rule, the chain can break, because a hidden field may be treated as empty.

Example: field C shows when field B equals yes, and field B only shows when field A equals yes. If field A is no, field B is hidden and field C should stay hidden too.

Problems start when a previous answer is left in a field that is now hidden. Test each step of the chain on its own, from the first field down.

Placing related fields inside a container and putting the rule on the container is often simpler than chaining many rules.

Is a caching or optimisation plugin blocking scripts?

Conditional logic runs in the browser with JavaScript, so delaying, deferring or combining Fluent Forms scripts can stop rules from reacting to answers.

  1. Clear all caches, including server and CDN caches.
  2. Turn off JavaScript delay, combine and defer one at a time.
  3. Test the form while logged out.
  4. Exclude Fluent Forms scripts, usually paths containing fluentform, from the setting that caused the issue.

Our guide to WP Rocket delay JavaScript exclusions shows the idea, and the same approach works for other optimisation plugins.

Open the browser console while testing. Chrome's Console documentation explains how to read red errors, which often name the script at fault.

Could another plugin or the theme cause a conflict?

Yes, a JavaScript error from any plugin or theme can stop Fluent Forms scripts from running, which looks exactly like broken conditional logic.

Test with a default theme and only Fluent Forms active. If the rules work, reactivate plugins one by one to find the cause.

Our guide to fixing plugin conflicts explains how to test safely on a staging site.

Also update Fluent Forms and WordPress. The Fluent Forms changelog on WordPress.org lists fixes in each release.

Why do conditional emails not send?

Conditional email notifications only send when their rules match the submitted values exactly, so the same value-versus-label and operator mistakes can stop an email from sending.

Open Settings > Email Notifications, edit the notification and check its conditions. Use stored values, not labels.

Make sure at least one notification has no conditions, or you may get no email at all for some submissions.

If notifications fail even without conditions, the problem is delivery. See our guide to Fluent Forms email notifications not working.

How do you test conditional logic properly?

Preview the form, change each controlling answer in turn, and check that the right fields appear and disappear, then submit test entries and review the stored data.

Write a short checklist of every rule and its expected result. Work through it after each change.

Check the entry in the dashboard after submitting. Hidden fields should not hold old answers that confuse your records.

Test on mobile as well. Some themes style hidden and shown elements differently on small screens.

What should you send to Fluent Forms support?

If rules still fail after these checks, contact support with the form export, a description of each rule, the page URL, and any console errors.

Exporting the form lets support load the exact same setup. Mention your caching and optimisation plugins, because they are a frequent cause.

Free users can post on the Fluent Forms support forum, while paid users can use the vendor's own support channels.

Frequently asked questions

Is conditional logic free in Fluent Forms?

Fluent Forms includes conditional logic for fields in its free version, which is one reason it is popular. Some advanced conditional features and integrations may need the Pro version, so check the plugin page for your exact needs.

Why does my Fluent Forms field never show?

The most common reasons are a condition that uses the option label instead of its value, the All match type when only one condition can be true, or a controlling field that is itself hidden. Check each part of the rule exactly.

Should I use equal or contains for checkboxes?

Use contains. A checkbox field stores a list of selected values, so an equal rule only matches when exactly one matching box is ticked. Contains matches whenever the chosen value is among the selected options.

Can caching break Fluent Forms conditional logic?

Yes. Conditional logic runs in the browser, so plugins that delay, defer or combine JavaScript can stop it working. Clear caches, test with those features off, and exclude Fluent Forms scripts from the setting that caused the problem.

Why is my conditional email notification not sending?

The notification's conditions must match the submitted values exactly. Check that rules use stored values and suitable operators. Also confirm email delivery works by testing a notification with no conditions, since delivery problems look similar.

Sources

  1. Conditional logic WP Manage Ninja
  2. Fluent Forms WordPress.org Plugin Directory
  3. Fluent Forms support forum WordPress.org
  4. Console overview Chrome for Developers

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.