Custom fields, post types and taxonomies (DJIA fields, ACF, Meta Box, Pods)

What this does

DJIA Builder has one field model for four sources: its own DJIA fields, ACF (and Secure Custom Fields), Meta Box and Pods. When a post or term is saved, its field values are copied into the builder's tables, where the runtime reads them for dynamic tags, the Field element, Query Loops, sorting, facets and display conditions. Each DJIA field is an ordinary meta key, so the REST API and other plugins read it too.

Content types registered here are real WordPress post types and taxonomies, registered on every request. Routes, archives, sitemap entries and Query Loop sources follow them without extra steps; deleting one keeps its posts or terms in the database.

Steps

1. Add a post type.

   Open DJIA Builder → Content types and click Add post type. Fill Plural name and Singular name; the Post type name is filled from the singular (lowercase letters, digits, - and _) and is locked once saved, because WordPress stores content under it. Set the URL slug (posts live at /slug/post-name/), Public, Archive page, Hierarchical, Hide from search, REST API and block editor and Edit with DJIA Builder, tick the boxes under Supports, then Save post type. Permalinks are refreshed once; routes and sitemaps update in the background.

2. Add a taxonomy.

   Click Add taxonomy, choose its Post types, switch Hierarchical on for categories-like terms or off for tags-like terms, and Save taxonomy. Term archives live at /slug/term/.

3. Add a field group.

   Click Add fields in the post type's row (or DJIA Builder → Fields → Add field group). Enter the Field group title, click Add field and give each field a Label; the Name (meta key) follows it. Choose one of 26 types, from Text, Number, Date and Color to Image, Gallery, Relationship, Terms, Address and map, Group, Repeater and Flexible content. A field can be Required, have a Default value and Conditional logic.

4. Set the location and save.

   Under Location ("Show this field group if") choose Post type, Page template, Post term, Post ID, Taxonomy term form or User role. Rules in a row must all match; any row is enough. Group settings add the Position, Order and Show in REST API (off: only users who can edit the post read the values over the REST API). Click Save field group.

5. Switch on Sort & filter where you need it.

   In a field's settings, Sort & filter copies its value into an indexed table, so Query Loops can sort and filter by it and facets can count it.

6. Create the templates.

   Back on Content types, the type's row offers Create single template and, with an archive page, Create archive template. Both are drafts with their conditions set (Post type, Post type archive) at priority 20: the single one with the title, featured image, content and a Field element per field; the archive one with and a three-column grid of cards on the main query, 12 per page. Open, adjust and publish them.

7. Show a field anywhere.

   Use the Field element (Date format, Decimals, Before / After the number, Labels or Values, Image size, When empty) or a tag such as . On the Fields screen each field shows its Dynamic tag.

ACF, Meta Box and Pods

Tab ACF, Meta Box, Pods of DJIA Builder → Fields lists each plugin with its state ("Read through its API", "Unsupported version: raw meta" or "Not active") and its field groups with Field, Dynamic tag, Type and a Sort & filter switch per field.

To leave ACF or Meta Box, use Preview first ("Import preview (nothing was changed)"), then Import all into DJIA fields. Field groups become DJIA groups under the same meta keys; with Convert values stored in another format on, repeater rows, links and maps are rewritten in the DJIA format. One run converts up to 2,000 objects ("run the import again to continue"), and "Fields that were not imported" lists the rest. Pods has no import.

What you should see

• Edit screenthe field group below the content or in the sidebar of each post the location rules match
• Editorthe fields in the Dynamic data menu of templates for that content, and "Page fields" with the DJIA field values of the open page, saved right away
• Live sitea changed value on the next page view, without a publish
• Tab Import and exportExport JSON: every field group and content type in one file, to move to another site or keep in Git

Limits

• Group, repeater and flexible content fields nest up to four levels. Fields inside them are not indexed for the whole site; loop over the rows (Query Loop Type Field) to filter and sort them.
• Sort & filter works for text, email, URL, phone, color, select, radio, checkboxes, number, true / false, date, date and time, time, terms and user fields.
• Field groups attach to posts and term forms; the User role rule narrows who sees a group, it does not add fields to user profiles.
• JetEngine, Toolset and Carbon Fields are not field sources.
• After an import into DJIA fields, tags that name the acf or metabox source still read that plugin. Change them to djb before you deactivate it.

If it doesn't work

• A field tag stays empty. The source is wrong, the group's location does not cover that content type, or the value is still being copied: check the Dashboard's sync queue.
• Sorting by a field changes nothing. Sort & filter is off, or its index is still being built.
• The post type row says "Name taken by another plugin". Another plugin registers the same name first; choose another name.
• New posts open WordPress's template. The single template is still a draft, or it is staged under Go live → Templates.
• A warning says ACF or Meta Box is "newer than this version of DJIA Builder supports". Values are read as plain meta until DJIA Builder is updated.

Last verified 2026-10-20 · tested with DJIA Builder 1.0.20.15
To confirm Verified against the plugin code; run the steps on a test site before launch