Skip to content
Front User Submit
Menu

Submit a Custom Post Type From the WordPress Frontend

By Aleksan Aharonyan ·

You can submit a custom post type from the WordPress frontend, but only with a form that is told which post type to write to. A form built for ordinary posts creates a post entry no matter what the site collects; a form built for recipes, events, listings or reviews has to name the custom post type in its settings and show the fields that post type actually stores.

Key takeaways

  • A frontend submission form writes to a custom post type only when that post type is registered on the site and the form’s post type setting points at it.
  • The form’s fields have to match where the data lives: title and content in the post fields, categories and custom taxonomies in taxonomy fields, everything else in post meta.
  • Keep new submissions on Pending until a few real entries have passed review and appear correctly on the front end.
  • Choose a custom post type when the entries need their own archive and template; choose a category on regular posts when they are blog posts that only need a label.

What a custom post type changes about frontend submission

A custom post type changes three things about frontend submission: which post_type the entry is saved as, which fields are meaningful for it, and which template displays it. WordPress keeps posts, pages and every custom post type in the same wp_posts table, separated by the post_type column, and the submission form fills that column in.

That means the post type has to exist before the form can target it. Something on the site registers it, usually a plugin (many listing, event and recipe plugins register their own) or a small register_post_type() call in a site-specific plugin. If nothing registers it, there is nothing for the form to submit to.

Registration also decides how the entry behaves once saved: whether it has an archive page, whether it is hierarchical like pages, which user role can edit it, and whether it is public at all. A post type registered as not public can hold data but will not show a permalink or an archive, which surprises people after their first test submission.

What the submission form needs: post type, fields and taxonomies

The form needs three things: a post type setting, a field for each value the post type requires, and taxonomy fields for the terms attached to that post type. Miss any of the three and the entry saves with missing data or lands in the wrong place.

The post type setting is the one people forget. A form that offers no choice writes an ordinary post, so a submitted event appears in the blog feed instead of the events list. Front User Submit, a free plugin for frontend post submission and guest posting forms, lets you set the form’s post type, and pointing a form at a custom post type is a Pro feature; the form builder documentation covers that setting and the field list.

The fields come next. Most custom post types need a title and some content, which map to the post title and the post content, and that part works the same as any blog submission. A featured image is also a post field, not post meta. Everything beyond that is either a taxonomy or a custom field, and those two behave differently enough to decide deliberately.

Custom fields and taxonomies: what the person submitting actually fills in

The person submitting fills in what the form shows, so the form should show only the data the post type needs: a taxonomy field for anything used to filter and browse entries, a custom field for each additional piece of data the template prints. Getting that split wrong is the most common reason a submitted entry looks right in the dashboard and wrong on the page.

Taxonomy fields are the browsing layer. Categories, tags and any custom taxonomy registered for the post type get their own term pages and query parameters, so if visitors will filter events by type or recipes by cuisine, that belongs in a taxonomy field. A term only appears in the form if the taxonomy is registered for the post type the form targets. If the field comes up empty, the usual causes are terms excluded in the field settings or terms that have no posts yet, which stay hidden until you turn on Show empty, both covered in the taxonomy field documentation.

Custom fields are everything else: an address, a price, a date, a number of guests, a link. These save as post meta and stay invisible on the front end until the theme or a shortcode prints them. They also need a field type that fits the value, which is why the field reference is worth reading before you build the form: it lists each field, what it saves and which ones require Pro. In Front User Submit, custom fields beyond the basic post fields are Pro, and Professional is $9.99 per month for one site if you buy monthly, with the other options on the plans page.

What happens after submit: status, review, editing and the user dashboard

After submit, the entry goes to the status the form is set to: Publish for immediate appearance, Pending when someone has to review it first, or Draft when the user saves without submitting. Status is a form setting rather than a property of the post type, so you can run two forms against the same post type with different levels of trust.

Pending is the setting to start with when submissions come from people you do not know. WordPress does the separation for you: a Pending entry is saved, visible to editors in the admin, and not visible on the front end until someone with the right role publishes it. That is also why you do not need to give contributors a role that can publish. A Contributor can submit and edit their own unpublished posts and nothing more, and the review step handles the rest.

Editing matters as much as submitting for listings and events, because the person who submitted will need to correct a date or a price. Front-end edit settings let a user reopen their own entry in the same form, and an optional time lock stops edits a set number of hours after the post was created. A front-end dashboard, such as the plugin’s [fe_fs_user_admin] shortcode, shows each user their own Publish, Pending and Draft entries with edit and delete icons.

Email notifications are the other half of review: an admin notification per submission and an author notification when a post is submitted, published or trashed. They go out through the normal WordPress mail function, so if mail on the site is unreliable, notifications are the part that fails first.

Custom post type or a category on regular posts

A custom post type is the right choice when the entries need their own archive, their own template and their own data, and a category is the right choice when they are ordinary blog posts that need grouping. The decision is about structure, not about how the content looks on the day you build it.

What the entries need Custom post type Category on posts
Their own archive and template Yes, by design Shares the blog template
Different fields from blog posts Stored per post type Stored per post, mixed in
A separate admin list Own list Filtered post list
Setup work Registration plus templates None

The registration cost is real: a post type needs a register_post_type() call somewhere that stays active, a template or block setup for the single entry and the archive, and often a re-save of permalinks before the new URLs work. A category costs nothing and inherits everything from the theme. The trade is that categories mix entry types in the same admin list and the same feed, and any query that wants only the listings has to exclude everything else by term.

A middle path exists: use a custom post type for the data and a taxonomy on it for grouping, or register the post type with an archive so entries sit under one URL. Pick based on what the visitor does with the entry, not on how the entry gets written.

Common things that break and how to check them

Most failures come from a mismatch between the post type registration and the form, and each one is checkable in a minute. Run a single test submission before you announce the form.

  • The entry lands in the blog. The form’s post type setting is still the default. Check the entry’s type in the admin list, change the form setting and submit again.
  • The entry saves but the page is a 404. The post type’s permalinks were registered after the site’s permalink structure was last saved. Re-save permalinks, then open the single entry URL.
  • The entry exists but is not in the archive. The post type may have no archive, or the entry is still Pending. Check the status first, then the registration arguments.
  • The taxonomy field is empty or terms do not save. The taxonomy is not attached to this post type, or the field excludes the terms you want. Open the taxonomy field settings and review the term list.
  • Custom field values are missing on the front end. They saved as post meta and nothing prints them. Check the entry’s meta in the admin, then add the output to the template.
  • The featured image is missing. The image saved but the single template does not call it for this post type, or the upload failed on file type.
  • A Contributor cannot publish. That is the role working as intended, with the submission held in review. Do not widen the role to fix it.

The check that covers all of these: submit one entry as a real user would, find it in the admin under the right post type, open the single page, open the archive, open a taxonomy term page, then delete the test entry.

FAQ

Can visitors submit to a custom post type without an account?

Yes, if the submission plugin supports guest posting; in Front User Submit that is a Pro feature. A guest submission has no author account behind it, so there is no dashboard entry for the guest and no author email when the post is published. Review status matters more here, not less: keep guest submissions on Pending.

Why does my submitted entry show up as a normal blog post?

The form is writing to the default post type. A submission form has to be told which post type to create, and until that setting points at the registered custom post type, every entry saves as a post and appears with the blog. Check the form’s post type setting first, then the entry’s type in the admin list.

How do I show submitted custom field values in the post?

The values are saved as post meta, so something has to print them. Add the meta keys to the single template for that post type, or use whatever custom field output your theme or submission plugin provides. Confirm the meta key name on the entry’s admin screen before you write the template code.