Skip to content

Nexter Fields FAQ

Updated On : November 12, 2026By : Reading Time : 1 minute

Key Takeaways

  • Nexter Extension includes Content Fields, and it is not a separate plugin to install.
  • Nexter Blocks lets values bind as dynamic content without code, while displaying values in a classic theme template needs a little PHP.
  • Nexter Extension 4.9.0 supports migration from ACF, Secure Custom Fields, Meta Box and Pods, but JetEngine is not currently supported.
Table of Contents

Short answers to the questions that come up most often.

What It Does

If your question is not here, the troubleshooting docs cover the specific failure modes in more depth.

Before You Start

  • Nexter Extension installed.

Common Questions

  1. Is Content Fields part of Nexter Extension? Yes. It is not a separate plugin to install.
Content Fields in the Nexter menu
  1. Do I need to write code? Not to create fields or fill them in. Displaying values in a classic theme template needs a little PHP; in Nexter Blocks you can bind values as dynamic content without code.
  1. Can editors create field groups? No. Field group management requires the manage_options capability, so it is administrator-only. Editors can fill in values.
  1. Can I migrate from ACF? Yes, along with Secure Custom Fields, Meta Box and Pods. JetEngine is not currently supported.
  1. Will my ACF template code keep working? No. Nexter does not provide identically named functions. Template calls have to be rewritten.
  1. Does it work with Elementor? Not in 4.9.0. There is no Elementor dynamic-tag integration. Nexter Blocks is supported.
  1. Are values available over the REST API? Scalar values yes, structured ones such as repeaters not by default.
  1. Does it work on multisite? Yes. Field groups are per-site, and user field keys are scoped per site so two sites do not collide.

Limitations

  • Answers here describe Nexter Extension 4.9.0. Behaviour may change in later versions.

Troubleshooting

My question is not answered here

Check the troubleshooting docs, which cover missing field groups, values not saving, cache staleness and REST errors in detail.

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 custom field empty in Nexter Fields?

Empty fields usually come down to one of the failure modes covered in the troubleshooting docs, especially missing field groups, values not saving, cache staleness, or REST errors. In Nexter Extension 4.9.0, scalar values are available over the REST API, but structured values like repeaters are not by default, so that can also look like a blank field in some setups. The most relevant deep dive is Why is my custom field empty?.

Does Nexter Fields work with Elementor?

Nexter Fields does not have Elementor dynamic-tag integration in 4.9.0, so it is not the path for Elementor-based dynamic content. Nexter Blocks is supported, which matters if your workflow depends on binding field values inside the Nexter ecosystem instead of a separate builder integration. That distinction is important because the limitation is about dynamic tags, not about whether fields exist at all.

Can I migrate custom fields from ACF to Nexter Fields?

Migration from ACF is supported, and the same applies to Secure Custom Fields, Meta Box, and Pods. JetEngine is not currently supported. The practical gotcha is that your old ACF template code will not keep working as-is because Nexter does not provide identically named functions, so template calls need to be rewritten. The migration path is covered in Migration overview.

Do editors have permission to create field groups in Nexter Fields?

Field group management is administrator-only because it requires the manage_options capability. Editors can still fill in values, which keeps content entry separate from schema control. That split matters on larger sites because it prevents editors from changing the structure of fields while still letting them work with the data day to day.

What are the main limitations of Nexter Fields 4.9.0?

The big limitations called out for Nexter Extension 4.9.0 are straightforward: there is no Elementor dynamic-tag integration, JetEngine migration is not supported, and structured REST output such as repeaters is not available by default. Another practical limitation is that ACF template code will not carry over unchanged because Nexter uses different function names. Those constraints matter most when you are planning a migration or a builder-heavy workflow.

Does Nexter Fields work on multisite?

Multisite support is built in for Nexter Extension 4.9.0. Field groups are per-site, and user field keys are scoped per site so two sites do not collide. That separation matters if you run multiple sites under one network because it keeps each site’s field setup isolated instead of sharing keys across the whole install.

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