Recurring Events
Recurring Events#
Create events that repeat on a schedule. Set up weekly classes, monthly meetings, or annual conferences from a single event.
How recurrence works#
When you publish a recurring event, the plugin creates one event post per extra date. The original event is the parent. Each generated event is an instance linked to the parent.
- The parent keeps the first date
- Each instance copies the parent’s title, content, time, venue, organizer, type, status, capacity, categories, and featured image
- Instances are normal events. They show in calendars, lists, and the archive on their own dates
- Saving a published parent deletes all instances and creates them again. Edits made to single instances are lost
Setting up recurrence#
- Create or edit an event
- In the Event Settings box, set Repeat Event to a pattern
- Fill in the interval, days, and end condition
- Check the Summary line under the fields
- Publish the event
Repeat Event#
- Does not repeat
- Daily: every X days
- Weekly: every X weeks on the selected days
- Monthly: every X months
- Yearly: every X years
- Custom: every X days, same as Daily
Every#
The interval between occurrences, from 1 to 99. The unit follows the pattern (days, weeks, months, or years).
Weekly options#
Under Repeat on, tick the days of the week. Pick several days for an event that runs more than once a week. Leave all unticked to repeat on the start date’s weekday.
Monthly options#
- Same day of the month: for example the 15th
- Same day of the week: for example the second Tuesday
Ends#
- Never: generates dates for the next 2 years
- On date: stops at the End Date you pick
- After occurrences: stops after the number in Occurrences (1 to 365)
A series is capped at 365 dates in all cases.
Managing instances#
Viewing instances#
In Events > All Events, each instance appears as its own event with the same title and its own date. The parent’s Event Settings box shows “This event has X recurring instances.”
Editing one instance#
- Open the instance from Events > All Events
- Change the time, content, venue, or other details
- Update
The instance shows a notice that it belongs to a recurring series, with a link to the parent. Recurrence fields can only be changed on the parent. Saving the parent later replaces all instances, so edit instances last.
Editing the whole series#
- Open the parent event
- Change the details or the recurrence fields
- Update
All instances are deleted and created again from the new settings. The Regenerate Instances button in the box saves the event and does the same thing.
Removing one date#
Move the instance to Trash. It stays removed until the parent is saved again.
Removing the series#
Set Repeat Event to Does not repeat on the parent and update. All instances are deleted permanently.
Trashing the parent does not remove its instances. Remove the series first, then trash the parent.
Tickets for recurring events#
Ticket products link to one event each. Instances do not inherit the parent’s ticket products.
- To sell tickets for a single date, create a product and pick that instance as its event
- Capacity is copied to each instance, so each date has its own limit
Examples#
Weekly class#
- Repeat Event: Weekly
- Every: 1
- Repeat on: Tuesday, Thursday
- Ends: After occurrences, 24
- Result: 24 sessions over 12 weeks
Monthly meeting#
- Repeat Event: Monthly
- Type: Same day of the week
- Every: 1
- Ends: On date, December 31
- Result: same weekday each month through year end
Annual conference#
- Repeat Event: Yearly
- Every: 1
- Ends: After occurrences, 5
- Result: one event a year for 5 years
Biweekly workshop#
- Repeat Event: Weekly
- Every: 2
- Repeat on: Saturday
- Ends: After occurrences, 6
- Result: 6 workshops over 12 weeks
Recommendations#
Plan the pattern first Set the pattern before anyone registers. Regeneration replaces every instance.
Check generated dates Open Events > All Events after publishing and review the dates.
Edit instances last Make per-date changes after the parent is final. Saving the parent again undoes them.
Limitations#
- Maximum 365 dates per series, or 2 years when Ends is Never
- No excluded dates in the editor
- Instances do not keep per-date edits after the parent is saved
- Ticket products must be linked to each instance by hand