Skip to content
Front User Submit
Menu

WordPress event submission form: how to build the whole site

By Aleksan Aharonyan ·

To take event submissions on WordPress, you need three things working together: an event post type that stores the date and place, a front-end form organizers can fill in without opening wp-admin, and a review step so nothing reaches the calendar until you have looked at it. Building the form is the easy part. The planning goes into who may submit, what you check before publishing, and how an organizer fixes a wrong date afterwards.

Key takeaways

  • Create the event post type before you build the form, so dates, venues and categories have somewhere to live that a blog post does not give them.
  • Send every new submission to the Pending post status and publish from the review queue, rather than handing out wp-admin accounts.
  • Decide whether organizers must register, because guest submissions are lower friction but leave no author account to email and no dashboard to edit from.
  • Layer the spam control: a login requirement or manual review works on any plan, while a captcha field or AI moderation needs Pro.

What an event submission site needs before you build anything

Four decisions come before any form building: where events are stored, who is allowed to submit, what you check before publishing, and how a submitter corrects a mistake. Make them at the start, because changing them later means rebuilding the form and re-teaching your submitters.

Where events are stored. A community calendar, a venue listing page and a club diary all need an event post type with its own permalink, archive and fields. A regular post can hold an event description, but the date and venue end up as body text that no calendar view can read.

Who may submit. There are three options: anyone including logged-out visitors (guest posting), registered users only, or a short list of accounts you create yourself. Guest posting brings in the most submissions and the least accountability. Registered users can come back and edit their own events.

What you check. Either you review every event before it goes live, or you trust the form. For a public calendar, review is the safer default, and it has to be fast: one screen, one decision per event.

How mistakes get fixed. Someone will enter the wrong date. Decide now whether the organizer edits it in a front-end dashboard or emails you. Email works for a handful of events a week and falls apart after that.

One more decision worth making early: one date per submission, or a recurring series? A submission form collects a single event well. Recurring series are usually better handled by the events tool that displays your calendar, with a line in the form asking organizers to describe the pattern in the description.

Step 1: Create the event post type and the fields visitors fill in

An event post type gives each submission its own permalink, archive and fields for date, venue and cost, which is the difference between a calendar and a blog category. You can get one from an events calendar plugin, from a plugin whose job is registering custom post types, or by registering it yourself in a small site-specific plugin; WordPress documents registering custom post types if you prefer code.

Keep the submitted field list short. Every required field costs you submissions, and whatever is missing can be added during review.

Field What it collects Tier
Post Title The event name Free
Content editor The description, as blocks, Markdown, TinyMCE or plain text Free
Featured Image One image, through a simple uploader Free
Taxonomies A category or tag, such as Music or Markets Free
Date Event date and time, with optional limits Pro
Google Map Venue address, picked with address search Pro
Text Ticket link, price or contact email Pro
File upload A flyer, with type and size limits Pro

The Pro rows are custom fields, and they are what turn a description into a structured event. Check that the submission plugin you choose can write into a custom post type before you commit; if it cannot, you are limited to the default Posts, and the date sits in a custom field rather than in your calendar view.

Step 2: Build the front-end event submission form

A front-end event submission form is a page on your site whose form writes straight into the event post type, so the person submitting never opens wp-admin. Build it once, place it on a page, and link that page from your navigation and from every “submit an event” mention on the site.

Front User Submit, a free plugin for frontend post submission and guest posting forms, is one option: you drag fields into place in the form builder and place the finished form on a page with [fe_form id="123"] or the Front Editor block, and the form builder basics cover field order and per-form settings. Sending submissions into a custom event post type is a Pro feature there, and the plans start at $9.99 per month for one site.

Order the fields the way an event reads: name, date, venue, description, image, then the optional extras. Mark only the essentials as required, and ask for a full street address rather than a venue name, because the address is what the map and the listing need. Put your rules in a short block at the top of the form, saying what gets rejected and what a good title looks like. If two kinds of event need different fields, build two forms instead of one long form full of optional sections.

Step 3: Choose what happens after submit

The post status attached to a form is the most consequential setting on it: Pending holds every event for review, Publish puts it on the calendar immediately, and Draft saves it without going live at all. For a public calendar, Pending is the setting to start with, because it keeps the calendar clean at the cost of one click per event.

In Front User Submit you set the form’s Post Status to Pending, and submitters can also press Save Draft to keep an unfinished event; the post submit settings control the success message, the redirect and comment status as well. Two habits help. Send Pending submitters to a thank-you page rather than to the event, since the event is not public yet. Turn on the admin notification so each submission arrives in your inbox with the post title and a link.

Paid submissions are a different route to the same place. If you charge venues a listing fee, the Pro version links a form to a WooCommerce product: the event is saved as a draft, the organizer pays at checkout, and the event takes the form’s status once the order is Processing or Completed. Guest submissions have no author account, so the author emails never go out for them; the admin notification is the one that matters.

Step 4: Give organizers a front-end dashboard to edit their own events

Organizers need to fix a typo, add a cancelation notice or correct a date without emailing you, and a front-end dashboard does that without a wp-admin account. The plugin creates a dashboard page on activation: the [fe_fs_user_admin] shortcode renders Publish, Pending and Draft tabs with edit and delete icons on each post.

Deletion follows the user’s WordPress role. Subscribers cannot delete posts by default, Contributors can delete their own unpublished posts, and Authors can delete their own posts, so the dashboard never gives a stranger more power than the role you assign. Editing opens the same form the event was submitted with, and an optional time lock stops edits a set number of hours after the post was created, which suits a calendar where late changes go through you.

Registration is where this falls down if you skip a step. New users from the registration form get the site’s default role and an email with a link to set their password (since version 5.2.5), so test that this email arrives and mention the WordPress “Lost your password?” page in your confirmation text as a fallback. If you accept guest submissions instead, there is no account, no dashboard and no author notification; any contact address a guest types in is yours to follow up manually.

Step 5: Keep spam and duplicate events out of the queue

Spam and duplicates are different problems: spam is automated junk you can block at the form, while duplicates are real people submitting the same market twice, which you catch in review. Treat them separately or you will spend your time deleting the wrong thing.

For spam, the free defences come first. Requiring login removes most automated submissions, and Pending review is the backstop that catches whatever gets through. A captcha field (reCAPTCHA v2 or hCaptcha, both Pro) adds a challenge for logged-out visitors, and Pro AI moderation checks posts that would otherwise publish straight away, saving flagged ones as Pending or Draft; if the AI provider is unreachable, the post saves as usual. Review is cheap when the queue is short and expensive when it is long, which is the real reason to block spam at the form rather than after it.

For duplicates, there is no automatic check, so build a habit and a convention. Search the event name and date before you publish anything. Ask for titles in one format, such as “Makers Market, May 4, Town Hall”, so two copies of the same event sit next to each other in the queue. Tell organizers in the form intro that a recurring event should be submitted once, with the pattern described. When one venue sends twenty events, give it its own form and a hidden field (Pro) that tags every submission from that source.

Step 6: Show dates, locations and maps on the published event

How an event looks on the page comes from your theme and the events tool that renders the calendar; the submission form’s job ends when the post is saved. Plan the display side while you plan the form, so every field you collect is a field you can show.

Check the date path first. Your calendar view has to read the same field the form writes, whether that is the events plugin’s own date field or a custom field on the event post. If the two do not match, you will re-enter every date by hand, which is the failure that kills community calendars.

For the venue, the Google Map field (Pro) lets an organizer search for the address during submission and shows the location on a map in the published event through a shortcode; it needs a Google Maps API key in the plugin’s global settings, and the Google Map field docs cover the key and the field limits. Other custom field values go into the post template with a shortcode such as [fus_custom_field_content meta_name="X"], so a ticket price or contact email is not buried in the description.

Finally, check the structured data. If you want search engines to read event dates, your events tool needs to output Event structured data on the single event page; Google’s event structured data guidance lists the required fields. Run one published event through Google’s Rich Results Test rather than assuming your theme handles it.

FAQ

Can visitors submit events without creating an account?

Yes, if the submission plugin supports guest posting, which in Front User Submit is a Pro feature. The trade-off is that a guest submission has no author account behind it: no dashboard to edit from and no author notification when the event is published. Offer both routes, a guest form for one-off community events and a logged-in form for venues that submit regularly.

Do I need a custom post type to collect events?

Not strictly. You can submit events into the default Posts, file them under an Events category and store the date in a custom field. A dedicated event post type pays off once you want a calendar archive, a single event template and clean URLs, and it is usually the point where a free submission setup turns into a paid one.

What WordPress role should event organizers have?

Contributor is the usual choice for people you do not fully trust: Contributors can create posts and edit their own unpublished work but cannot publish. Subscribers can do very little, and Author or Editor is too much for a stranger. Pair the role with the Pending post status so nothing reaches the calendar without your click.