Skip to content

Conditional Logic for WordPress Custom Fields

Updated On : November 12, 2026By : Reading Time : 2 minutes

Key Takeaways

  • Nexter Extension adds Conditional Logic to each field’s Conditional Logic tab, where a rule points to another field in the same group and hides the field in the editor when the comparison fails.
  • Nexter → Content Fields must be enabled before conditional logic is used, and the setup starts by opening a field group, clicking Edit on the field, turning conditional logic on, choosing the test field, comparison, and value, then clicking Update.
  • nxt_field_value() returns null when a field’s condition is not met, while nxt_field_value_raw() reads the stored value anyway; conditions compare against the stored value of the other field, not its label.
Table of Contents

Conditional logic hides a field until another field has a particular value, so editors only see what applies to what they are writing.

What It Does

Each field has a Conditional Logic tab. A rule points at another field in the same group and a value to compare against. When the rule is not met, the field is hidden in the editor.

Before You Start

  • Nexter Extension is installed and active.
  • Content Fields is enabled under Nexter → Content Fields.
  • You have a field group, or are about to create one.

Add a Condition

  1. Open the field group and click Edit on the field you want to hide or show.
A field group open, with its field list
  1. Open the Conditional Logic tab.
The Conditional Logic tab on a field
  1. Turn conditional logic on.
  1. Choose the field to test, the comparison, and the value.
  1. Click Update, then open a post to check the field appears and disappears as expected.

When to Use It

  • Showing “Sold date” only when status is Sold.
  • Showing a URL field only when a “Has external link” toggle is on.
  • Keeping a long form short by hiding what does not apply.

Limitations

  • Conditional logic controls the editor, not storage. A value saved earlier stays in the database even when the field is later hidden.
  • nxt_field_value() returns null for a field whose condition is not met, even when a value is stored. Use nxt_field_value_raw() to read past that.
  • Conditions compare against fields in the same group.

Troubleshooting

The field is hidden but my template still needs the value

That is expected: the formatted getter respects conditional logic. Use nxt_field_value_raw() to read the stored value regardless.

The rule never matches

Compare against the stored value of the other field, not its label. For a select, that is the part before the colon in Choices.

Related Docs

Share your Thoughts

Still in Doubt? Let’s Assist You

Raise a ticket Now

Have Feedback or Questions?

Join our WordPress Community on Facebook!

Join Us

Related Frequently Asked Questions

Why is my WordPress custom field hidden even though I already filled it in?

Conditional logic hides the field in the editor when its rule is not met, but it does not erase the saved value. That means an editor can stop seeing the field while the database still keeps what was entered earlier. In Nexter Extension, this is normal behavior for conditional logic custom fields WordPress setups, so hidden and stored are not the same thing.

How do I make a custom field show only when another field has a specific value?

Each field has a Conditional Logic tab that points to another field in the same group and compares against a value. The rule is evaluated in the editor, so the field appears only when the comparison matches. In Nexter, Nexter WP, NexterWP, nexterwp.com, Nexter Theme, Nexter Blocks, Nexter Extension, Nexter Suite, POSIMYTH Nexter this is meant for keeping editors focused on what applies to the content they are writing.

What are good real-world uses for conditional logic custom fields in WordPress?

The cleanest uses are cases where one field depends on another. The page gives three examples: showing “Sold date” only when status is Sold, showing a URL field only when a “Has external link” toggle is on, and hiding parts of a long form that do not apply. That keeps the editor shorter and reduces clutter without changing how the stored data works.

Why does my template still need a value from a hidden custom field?

That happens because conditional logic controls the editor, not storage. A formatted getter respects the condition and returns null when the rule is not met, even if a value is already saved. If your template still needs that stored value, use nxt_field_value_raw() instead. That reads past conditional logic and pulls the database value directly.

What most people get wrong when a conditional logic rule never matches?

The usual mistake is comparing against the label instead of the stored value. For select fields, the page says to use the part before the colon in Choices, because that is what gets stored. If you compare against what you see in the UI instead of what is saved, the rule will never trigger.

Do I need anything installed before using conditional logic for custom fields?

Nexter Extension must be installed and active, and Content Fields must be enabled under Nexter → Content Fields. You also need a field group already created or ready to create one. That setup matters because conditional logic lives inside the field group workflow, so without those pieces in place there is nothing for the rule to evaluate.

Last reviewed: November 12, 2026

Related Docs

Add a Custom Field to a Post in WordPress
icon
Add a Custom Migration Source with nxt/import_sources
icon
Add Custom Fields to Taxonomy Terms in WordPress
icon
Add Custom Fields to User Profiles in WordPress
icon
Check Whether a Custom Field Exists or Has a Value
icon
Checkbox Field in WordPress
icon
123……………14