Test your first registration

This test proves five separate things: the form appears, it validates, it creates an attendee, the attendee reaches the right list, and the capacity rule works. Do it before any visitor sees the event.

Before you start

• Attendee functionality is enabled under Settings → POM Events → General.
• One published event with a start date and an end date in the future.
• A private browser window.
• An email address you control, and which is not already a user of this site.

1. Open the form as a visitor

1. Open the event in a private window.
2. Select the registration button.
3. The form opens in a modal, headed Sign up for this event.

You should see Name and Email as required, plus whichever optional fields you enabled — last name, telephone, comments, country.

If a privacy policy URL is configured in the settings, the form also shows a consent checkbox and the clause text below it.

2. Test the validation

Submit with the name empty. The form must refuse and report that the required fields are missing.

This is worth doing once: it confirms the form is actually wired to the plugin and not just rendered.

3. Register

1. Fill in the name and a new email address.
2. Complete the optional fields, including a comment — you will look for it in the admin.
3. Accept the privacy checkbox if it is present.
4. Submit.

You should see a success message confirming the sign-up.

4. Check what was created

In the administration:

1. Open the event.
2. Find the Event assistants panel.
3. The registration is in the Confirmed section.
4. The row shows the name, the email as a mail link, the telephone as a call link, and a comment icon that opens the comment.

Also check Users: registering with an email that was not yet a user creates a WordPress user account for that address, using the email as the login. This is how the attendee list identifies people.

That is worth knowing before a large public event: registrations grow the site's user list.

5. Test the duplicate rule

Register again from the private window with the same email.

The form refuses it and reports that the user is already signed up for this event. One email address is one registration per event.

6. Test the capacity rule

1. In the event, set Available space to the number of registrations that already exist — so the event is exactly full.
2. Update the event.
3. From the private window, register with a different new email.

The visitor is told the event has reached its available space and that they have been moved to the waiting list. In the admin, the new registration appears in the Waiting list section rather than Confirmed.

Set Available space back to its real value afterwards.

7. Test the export

In the Event assistants panel, select Export to CSV. Open the file and confirm it contains your test registrations with their status.

Then repeat with Export to XLS if your team uses spreadsheets.

8. Clean up

1. Move the test registrations to Cancelled.
2. Delete them from there — deletion is only available on cancelled rows, and it is permanent.
3. Remove the test user accounts from Users if they should not remain.

What this test does not cover

• Emails. POM Events does not send confirmation emails. Nothing arrives in the attendee's inbox unless another integration sends it. See Emails and confirmation expectations.
• Paid access. If the event has an associated WooCommerce product, the button is Get access and the flow is a purchase. Test that separately — see Automatic enrollment after purchase.

If the form does not behave

Then continue to the Recommended launch checklist.