Get started with POM Events
This chapter takes a site from an installed plugin to a published event with a working registration form. It separates the steps deliberately: understanding the product, checking prerequisites, installing, licensing, creating content, and approving the result.
Choose the right article
| If you need to… | Read |
|---|---|
| Understand what the plugin does before changing the site | What POM Events does |
| Check WordPress, theme, PHP and WooCommerce prerequisites | Requirements and compatibility |
| Install the plugin and confirm it is running | Install and activate POM Events |
| Connect the site to its POM subscription | Activate your POM Events license |
| Learn what every screen and panel is for | Tour the POM Events interface |
| Publish one real event end to end | Create your first event |
| Prove that registration works before visitors use it | Test your first registration |
| Approve a site for launch | Recommended launch checklist |
| Update the plugin or prepare a support request | Updates, support, and safe maintenance |
Recommended order for a new installation
- Confirm the deployment meets the requirements, starting with the POM theme.
- Install and activate the plugin.
- Save and validate the license under Settings → POM Events.
- Decide, once, whether the site will use the built-in attendee registration at all.
- Create one test event with real dates, a place and an image.
- Publish it and check the public page while signed out.
- Register once yourself, from a private browser window.
- Review the attendee in the event editor and export the list.
- Add the search form or the calendar to the page where visitors will look for events.
- Work through the launch checklist before announcing anything.
The three layers you will configure
The event itself — dates, place, description, image, taxonomy terms, and the event-specific panel that carries everything the public page shows.
The site-wide settings — one screen at Settings → POM Events with General, Archive, Single event and License sections. These decide how every event behaves.
The pages that list events — the search form shortcode and the calendar shortcode, placed on whichever page visitors use to find events.
A change in the wrong layer is the usual cause of "it did not work". Site-wide behavior is not fixed on a single event, and a single event's dates are not fixed in the settings.
The publishing rule
An administration screen that reports a saved change is not the end of a task. Open the public event page while signed out and confirm what a visitor actually sees — including the empty state, the full state and the finished state, which look very different from each other.
Two decisions worth making early
Do you need the built-in registration? If the site only announces events and sells nothing, turn attendee functionality off in the General settings. Everything about capacity, waiting lists and attendee lists then disappears from the interface.
Do you sell access? If yes, WooCommerce becomes part of the flow and registration happens after purchase rather than through the on-page form. See WooCommerce.
Start with What POM Events does.