← Back to modules

nexya custom fields

Fields of your own, kept in their own tables — and read in a single query per page.

  • Your fields, not a plugin’s A group is made here, placed on a post, a term, an account or an options page, and read in the theme with nexya_get_field().
  • Read in one query Values live in their own tables rather than in postmeta: a whole page, repeaters included, costs a single query.
  • Come from ACF, leave when you like The groups and values of an ACF site import, clones included. A group goes back to ACF whenever you decide.
0:17

Free

Every field type — repeaters, flexible content, group, clone, accordion, relationships, icon —, conditional logic, options pages, ACF import and export, and fields in the block editor, Elementor and Bricks.

Pro

ACF’s function names — get_field(), have_rows()… — so that a theme written for ACF runs unchanged.

Get started

nexya custom fields in three steps

  1. Switch on nexya custom fields In the nexya hub. If ACF is installed, the import takes its groups over in one click.
  2. Create a field group In the NCF menu: the fields, then where they show — a content type, a page template, an options page.
  3. Read them in the theme With nexya_get_field('field_name'). With Pro and without ACF, get_field() and ACF’s other functions answer too.

nexya custom fields is in the free extension, on as many sites as you want.

Download the free version View pricing

FAQ

Everything about nexya custom fields

In the NCF menu, create a group, add your fields (text, image, repeater, relationship…) and choose where it shows. The field appears in the editor of the matching content.

With nexya_get_field('field_name'), and nexya_have_rows() and nexya_get_sub_field() for repeaters. With Pro, when ACF is not installed, ACF’s names — get_field(), have_rows()… — answer too: a theme written for ACF runs unchanged.

On a PHP theme that reads its fields with get_field() and have_rows(), yes: repeaters, flexible content, gallery, group, clone, accordion, relationships and options pages are free, ACF’s groups and values import, and Pro adds ACF’s functions. ACF’s conditional logic is carried over. Elementor or Bricks settings wired to ACF are redone with the nexya widgets and tags; ACF blocks, WPGraphQL for ACF and ACF Extended are not supported.

Values live in their own tables instead of piling up in postmeta: a whole page, repeaters included, is read in a single query. And a group can go back to ACF whenever you decide.

The values stay in their tables, nothing is erased. And since a group exports in ACF’s format, you are never locked in.

Yes: a field’s Display tab sets when it shows — when another field of the same list equals a value, differs from it, contains it, is filled in or is empty. Rules combine, and the conditional logic of an imported ACF group is carried over.

In Elementor, the “nexya” category offers three widgets — a field, a repeater’s rows, a field’s terms — and, with Elementor Pro, dynamic tags. In the block editor, a paragraph, heading, button or image binds to a field. In Bricks, {nexya:…} dynamic data goes anywhere.

The suite

Other modules

nexya translate

The site in several languages: every content with its versions, an address per language, and the site’s texts translated in one place.

nexya popup

Popups composed section by section, opening at the right moment — and able to close the shop and the forms while they are live.

nexya aris

Audience figures, measured by the site itself — no Google, no Matomo, no IP address kept.

nexya mailya

Newsletters written on the WordPress site, with your posts in them — sent in the background, at the pace your server can hold.

nexya media

Folders to sort the media library, and thumbnail regeneration in the background, in batches, carrying on when you close the tab — and telling you when it is finished

nexya hub

The panel that gathers every nexya plugin. A module you switch on, a module you switch off — and nothing running on the WordPress site while it is off

nexya dashboard

The WordPress admin as the client sees it: menus cut down to what is useful, a tidy admin bar, and the dashboard in your own colours right through to the login page

nexya shortcuts

Duplicate, reorder, add — three gestures placed on the WordPress content lists, so you stop doing them by hand

nexya roles

WordPress capabilities filed under the plugin that creates them, readable at last. And the menu cut down to what the person in front of it actually has to do

nexya activities

Who changed what on the WordPress site, and when. Down to the ACF fields, with the value before and the value after — and the button to put it back

nexya cookie

Cookie consent, and the blocking that goes with it. Nothing runs before the visitor agrees — not the scripts, not the embedded videos, not the remote fonts

nexya seo

What the WordPress site says about itself to search engines — and what it shows when someone pastes its address somewhere. Written once, applied everywhere, checked before publishing

nexya mail

The WordPress site’s emails actually go out — and you know which ones did not, with the exact reason given by the SMTP server

nexya redirects

The 404 errors picked up as visits happen, and the 301 redirect suggested before anyone goes looking for it. With the number of hits, so you know which ones count

nexya security

The HTTP security headers set without breaking the site, the watch on vulnerabilities in the WordPress plugins installed, and the eye on what moves in the files

nexya maintenance

The operations you carry out on the WordPress site rather than in it: closing it for an intervention, slimming its database down, taking a copy

nexya cache

Each page kept as a file and handed to the next visitor before WordPress loads — then thrown away as soon as something changes it.