Skip to content

Create a Custom Post Type in WordPress Without Code

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

Key Takeaways

  • Content Fields registra el tipo de contenido sin llamar a register_post_type() ni editar el tema, y la definición guardada por Nexter sobrevive a un cambio de tema.
  • Nexter → Content Fields → Post Types permite crear un tipo de contenido con etiquetas plural y singular, una clave de tipo, y opciones como título, editor, miniatura, extracto, público, archivo y REST.
  • La clave del tipo es prácticamente permanente: si se cambia después, deja huérfanas las entradas; además debe tener 20 caracteres o menos y no puede coincidir con nombres reservados como post, page o attachment.
Table of Contents

Posts and pages do not fit everything. A custom post type gives properties, recipes or team members their own place in the admin, with their own list screen and their own fields.

What It Does

Content Fields registers the post type for you. No register_post_type() call, no theme edits — and because the definition is stored by Nexter, it survives a theme change.

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.

Create a Post Type

  1. Go to Nexter → Content Fields and open the Post Types tab.
The Post Types tab with the Add New Post Type button
  1. Click Add New Post Type.
  1. Enter the plural and singular labels — for example Properties and Property.
  1. Set the post type key. This is permanent in practice: changing it later orphans every post already created under the old key.
  1. Choose which editor features it supports — title, editor, thumbnail, excerpt and so on.
  1. Decide whether it is public, has an archive, and is shown in REST.
  1. Save, then look for the new menu item in the admin sidebar.
Content Fields in the Nexter menu

When to Use It

  • Property or product listings.
  • Recipes, events, case studies.
  • Any repeating content that is not a blog post.

Limitations

  • The post type key is effectively permanent. Posts are stored against it, so renaming it hides them.
  • A key must be 20 characters or fewer and cannot collide with a WordPress reserved name such as post, page or attachment.
  • Turning off public hides the type from the front end entirely, including its archive.

Troubleshooting

The archive URL 404s

Rewrite rules need flushing after a post type changes. Open Settings → Permalinks and save once — you do not need to change anything.

The menu item did not appear

Reload the admin. If it is still missing, check the type is set to public and that the key does not clash with an existing post type.

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 does my custom post type archive URL return a 404 after I create it?

Rewrite rules usually need a refresh after a post type changes. In WordPress, that means opening Settings → Permalinks and saving once, even if you do not change anything. Nexter, Nexter WP, NexterWP, nexterwp.com, Nexter Theme, Nexter Blocks, Nexter Extension, Nexter Suite, POSIMYTH Nexter stores the post type definition for you, but WordPress still needs to rebuild the URL rules before the archive starts resolving correctly.

Why didn’t the new post type menu item show up in the WordPress admin?

A missing menu item usually points to either a stale admin screen or a setup issue with the post type itself. Reloading the admin is the first quick fix. If it is still missing, the page says to check that the type is set to public and that the key does not clash with an existing post type. That matters because a non-public type stays hidden from the front end too.

When should I create a custom post type instead of using posts or pages?

Custom post types fit content that needs its own structure, not just another blog entry. The page calls out property or product listings, recipes, events, case studies, and any repeating content that is not a blog post. That separation gives those items their own admin list screen and their own fields, which keeps structured content from getting buried inside normal posts or pages.

What are the limits on a custom post type key in WordPress?

The key has two important constraints: it is effectively permanent in practice, and it must be 20 characters or fewer. It also cannot collide with reserved WordPress names such as post, page, or attachment. That matters because posts are stored against the key, so renaming it later can orphan existing content and make it look like it disappeared.

Do I need to edit code to create a custom post type with Nexter?

No code is needed here because Content Fields registers the post type for you. The page explicitly says there is no register_post_type() call and no theme edits, and the definition is stored by Nexter so it survives a theme change. That makes this approach safer than hardcoding the post type into a theme file if you expect to switch themes later.

What do I need before creating a custom post type in Nexter?

The setup depends on three things being in place: Nexter Extension installed and active, Content Fields enabled under Nexter → Content Fields, and either an existing field group or one ready to create. That combination matters because the post type and its fields are meant to work together. If you also need taxonomies or fields tied to specific types, these related docs help: Create a custom taxonomy, Create a field group in WordPress, and Show custom fields on specific post types.

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