What POM Events does

POM Events adds a complete event manager to a POM WordPress site: an event content type with dates and details, a public event page, a searchable list and a calendar, an optional registration form with capacity and a waiting list, an attendee list you can export, and an optional WooCommerce path for paid access.

The event content type

Events are their own content type, separate from posts and pages, with:

• a title, an editor, an excerpt, a featured image and an author;
• Event types and Categories, both hierarchical;
• Tags, shared with the site's normal post tags;
• its own archive and its own single-event template.

Everything specific to an event — dates, place, organizer, contact number, registration options, capacity — lives in an Events settings panel above the editor.

Dates that are usable, not just displayed

An event carries a start date and time and an end date and time, with the time optional. From those, POM Events derives sortable date values that the search form, the calendar, the archive ordering and the "upcoming events" logic all use.

You also control how dates are shown per event: the site's default date, date and time, or a reduced format such as month and year, month only, year only or day only. An event can hide its dates completely, and an event can be marked as lasting all day.

The public event page

The single-event template renders, in a fixed and predictable order:

• a subheader with the event title and its categories, over the featured image or a custom image;
• previous and next event navigation, ordered by start date;
• a start/end date block;
• a details sidebar with date, category, place, organizer, telephone, an Add to my calendar link and any additional link buttons you defined;
• the remaining capacity, when you choose to show it;
• the registration or purchase button;
• the introduction, the featured image and the content;
• a related-content block.

Almost every one of those elements can be turned off site-wide from the settings.

Registration, capacity and the waiting list

When attendee functionality is enabled, each event can offer a registration form in a modal: name and email are required, and last name, telephone, comments and country are optional fields you switch on per event.

Behind it:

• Available space sets the capacity. Left empty, the event has no limit.
• When the capacity is reached, further registrations are placed on the waiting list automatically and the visitor is told so.
• The button label changes by state: the normal label, a waiting-list label, and a finished-event label once the end date has passed.
• Display remaining space shows visitors how many places are left, or that the event is full.
• Disable signup button removes the button without touching anything else.

The attendee list

Every event has an Event assistants panel with three sections — Confirmed, Waiting list and Cancelled — each showing the person's name, email, telephone and comments.

From there you can move a registration between the three lists, permanently delete a cancelled registration, and export the whole list to CSV or XLS for a door list or a mailing.

The events list screen adds an Event start date column, sortable, and an Assistants column counting confirmed registrations.

Finding events

Two shortcodes put events in front of visitors:

• [web_event_search_form] — a filterable list with a date picker, type and category filters, AJAX results and a Load more events button. By default it shows events that have not yet finished.
• [pom_events_fullcalendar] — a month calendar of every published event, with each entry linking to its page.

Paid access through WooCommerce

When WooCommerce is active, an event can be linked to one or more products. The registration button becomes Get access, which puts the product in the cart and sends the visitor to checkout. After the order is placed, the buyer is enrolled in the event automatically, respecting the same capacity and waiting-list rules.

What it does not do

• It does not send confirmation or reminder emails on its own.
• It does not manage recurring events.
• It does not issue tickets, seat numbers or QR passes.
• It does not require the POM theme for its settings and updates — but the event runtime, the templates and the shortcodes need it.

Continue with Requirements and compatibility.