Custom button labels
The registration button changes wording according to the event's state. Three labels are configurable per event.
The three labels
| Label | Where | Default |
|---|---|---|
| Available button label | Event info tab | I want to sign up |
| Waiting list button label | Registration form tab | Join the waiting list! |
| Finished event button label | Registration form tab | Event finished |
Which one is shown
The button chooses its label from the event's state:
- The end date has passed → the finished label, and the button is disabled.
- The event has a capacity set → the waiting-list label.
- Otherwise → the available label.
The second rule matters more than it looks. An event with Available space filled in uses the waiting-list label — so word that label for a capacity-limited event in general, not only for a full one.
Practical approach for capacity events: set the waiting-list label to something that works either way, such as Request a place or Sign up, and let the remaining-places display tell visitors how full the event is.
Writing labels that work
- Say what happens next. Reserve your place is better than Continue.
- Match the event's register. A workshop and a gala do not use the same words.
- Keep them short. The button is full width but the label wraps badly on a phone at more than four or five words.
- Do not promise what does not happen. You will receive a confirmation email is wrong; POM Events sends none.
Examples
| Event | Available label | Waiting-list label | Finished label |
|---|---|---|---|
| Free talk | Save me a seat | Save me a seat | This talk has ended |
| Limited workshop | Request a place | Request a place | Registration closed |
| Members' event | Register | Join the waiting list | Event finished |
| Guided visit | Book a visit | Ask about availability | No longer available |
Consistency across a calendar
Labels are per event, which makes drift easy. Agree one set of wordings and apply it to every event, so a visitor moving between two events on the same site does not read two different vocabularies.
If you already keep a template event as a draft, put the agreed labels in it — see Duplicate and reuse events.
What is not configurable
- The modal heading, which reads Sign up for this event followed by the event title.
- The form's own submit button, which reads Sign up.
- The field placeholders: Name, Last name, Email, Telephone, Comments, Country.
- The success, waiting-list and error messages.
Those come from the plugin's own translations. On a site running in another language, they follow that translation.
Multilingual sites
The three labels are per-event text fields, so a translated event carries its own labels. Set them in each language as part of translating the event.
Verify
- Set the three labels and save.
- Open the event signed out and read the button.
- Set a capacity and confirm which label is shown.
- Set the end date to yesterday, reload, and confirm the finished label and that the button is disabled.
- Restore the real dates.