Duplicate and reuse events

Events repeat — a monthly talk, an annual open day, a course that runs three times a year. POM Events has no recurrence and no duplicate action, so this page covers the supported ways to reuse an event's setup.

What is not available

• No recurring events. Each occurrence is its own event record.
• No duplicate button. The plugin does not add one.

That is a deliberate scope decision, and it has one advantage worth naming: each occurrence has its own dates, capacity, attendee list, page and URL, so an edition that changes venue or price is not fighting a recurrence rule.

Method 1 — a template event kept as a draft

The most practical approach for a repeating series.

1. Create one event with everything that stays the same: content, image, place, organizer, telephone, button labels, form fields, capacity, taxonomy terms, additional links.
2. Name it clearly — TEMPLATE — Monthly talk.
3. Leave it as a draft, permanently.
4. For each occurrence, open it and use the browser to copy the parts you need into a new event.

The draft never appears publicly, and it records the decisions you would otherwise have to remember.

Method 2 — copy from the previous occurrence

Open the previous edition and the new event side by side, and copy across:

• the content;
• the introduction;
• the place, organizer and telephone;
• the button labels;
• the form field selection;
• the capacity;
• the additional links.

Then set the new dates and the featured image.

Always work from the most recent occurrence, so improvements accumulate instead of being rediscovered.

Method 3 — a plugin-independent duplicate

If your site already has a general-purpose post duplication tool, it will copy an event like any other content type, including its meta and terms.

If you use one, always check afterwards:

• the dates — a duplicate carries the original's dates, which are the one thing that must change;
• the attendee list — never publish a duplicate that carried the previous edition's registrations;
• the status — the copy should start as a draft;
• Available space, if capacity differs.

What must change on every new occurrence

A short checklist worth pinning:

• [ ] Start date and time
• [ ] End date and time
• [ ] Title, if it carries an edition or a season
• [ ] Featured image, if it is edition-specific
• [ ] Capacity, if it differs
• [ ] Content details that reference the previous edition
• [ ] Additional links pointing at a previous programme
• [ ] Related content
• [ ] An empty attendee list

Series that share a page

For a series where visitors should reach one page rather than twelve, the alternative is one event with a wide date range and the schedule in the content. It gives one URL and one attendee list — appropriate for an exhibition, wrong for a course where each session has its own capacity.

See A recurring format without recurring data.

Verify a duplicated event

1. Both dates are the new ones.
2. The attendee list is empty.
3. The capacity is right for this occurrence.
4. Taxonomy terms are assigned.
5. The public page reads correctly signed out, with no text left over from the previous edition.