Club Fixture List in WordPress: Cancel One Date, Keep the Season

A club calendar has two kinds of entries. Training happens every Tuesday and Thursday whether anyone remembers it or not. Fixtures are different every week: a new opponent, a new venue, a new kick-off time. Most event plugins treat both as the same thing, and that is where club secretaries start fighting their own website.

This guide shows how Eventonomy handles both, with one feature in the middle that sports clubs tend to need more than anyone else: cancelling a single rained-off date without touching the rest of the season. I’ll cover what the Free plugin does, where Pro takes over, and a few limits worth knowing before you promise anything to your members.

Training is a series, fixtures are not

The split that makes a club calendar easy is simple. Anything that repeats on a fixed rhythm is one recurring event. Anything that is different each time is its own one-off event.

Training sessions, the junior squad’s Saturday morning practice and the monthly committee meeting are all recurring events. You create them once and Eventonomy writes a real entry for every date, so each one shows up on the calendar, in the browse views and on its own date.

Fixtures are one-offs. The opponent changes, the venue changes and sometimes the time does too. The docs say the same thing about a date that needs to differ from the rest of a series: if one date genuinely needs to be different, create a separate one-off event for it. For a club, that means every fixture gets its own event, and nobody has to bend a recurring rule into a shape it was never meant to hold.

Setting up the training series

Open the event editor and find the Recurrence panel. The Free plugin gives you two controls there:

• Repeats: None, Daily, Weekly, Monthly or Yearly (Yearly only works with Pro).
• Every: the interval. 1 means every time, 2 means every other.

So a weekly session is Repeats set to Weekly and Every set to 1. A fortnightly committee meeting is Weekly with Every set to 2. Eventonomy expands the rule into real dates up to a horizon, which is 12 months ahead by default and can be set anywhere from 1 to 60 months. A daily background job keeps extending that horizon as time passes, so a long-running series never quietly runs out.

Recurring events are on by default. If you don’t see the panel, check Eventonomy, Settings, Appearance, Recurring events.

One limit to plan around. The Free editor shows only those two controls, so a session that runs on a specific pair of weekdays, such as Tuesday and Thursday in the same event, isn’t a Free rule. The simplest Free setup is one weekly event per training night.

Cancel one date, keep the season

This is the part clubs ask about first. A pitch is waterlogged on a Saturday and the session is off. You don’t want to delete the series or edit the whole schedule.

In the event editor, open the Date and Time section and find Upcoming dates. Every date in the series is listed there with a Cancel this date action. Press it and that single date is cancelled. The rest of the season stays exactly as it was.

A cancelled date leaves the calendar, the browse views and the public event page. If it was a mistake, or the weather clears, the same list lets you restore it.

Under the hood, the cancellation is a soft one. Eventonomy keeps the date’s row and marks it cancelled and as an exception, instead of deleting it. That detail matters because a deleted date would simply be regenerated the next time the schedule is recomputed. A cancelled one is remembered. Even if you later change the schedule of the series, dates you cancelled individually stay cancelled.

Developers get the same thing through the REST API: DELETE on an occurrence cancels it, and PATCH with a status of active restores it. The editor panel calls those same routes, so there’s no separate path to keep in sync.

Who can do it

Cancelling is not open to everyone logged in. The route checks that the person can edit the event the date belongs to, and returns a forbidden error if they can’t. In practice, whoever you trust to edit the training event can cancel one of its dates, and nobody else can.

That’s useful for a club. The coach or secretary who looks after the junior session can call off a wet Saturday, while an ordinary member can’t touch it. Developers also have a filter that runs before an occurrence change is written, which can reject it, and an action that fires afterwards. Either one is a clean place to log who cancelled what.

What it will not do

Setting honest expectations saves you an awkward email later, so here are the limits.

You can’t move a single date. The occurrence route only cancels or restores. If Tuesday’s session moves to Wednesday this one week, the clean way is to cancel Tuesday and add a one-off event for Wednesday.

There’s no “this and following” edit. Editing a recurring event edits the whole series. Change the schedule and the occurrences are recomputed from the new rule, though cancelled dates stay cancelled.

Subscribed calendar apps may not drop the date. Eventonomy’s calendar feed is free, and people can subscribe to it from their phone. For a recurring event, the feed describes the series as a single entry with a repeat rule, and it doesn’t list skipped dates. So don’t tell members that their phone calendar will remove a cancelled session by itself. Tell them directly, and treat your website as the place that’s always right.

Telling people the date is off

Cancelling the date fixes the website. It doesn’t reach the parent who already put Saturday in their diary, so you need a message as well.

The event’s attendee management screen has an email compose panel that sends a message to everyone who registered for the event, either just those who are going or those going plus the waitlist. The background sends run in batches. Eventonomy skips people who have opted out of messages, so you won’t be emailing someone who asked not to hear from you.

There are limits by design. An event can send 5 of these messages per hour, which keeps a stuck keyboard or a panicked secretary from sending the same note twenty times. The subject can be up to 200 characters and the message up to 5,000. A site owner can change the hourly limit with a filter.

Reminder emails are separate and still work per date: an attendee gets the one-day and one-hour reminder for each upcoming date, naming that date. The documentation doesn’t say what happens to a reminder for a date you cancel after it was queued, so on a real season, cancel a test date early and see what your own members would receive before you rely on it.

What Pro adds for a full season

Free keeps recurrence simple on purpose. If your club needs more precise rules, Pro’s recurrence engine takes over for any event that uses them, and plain interval events carry on with the Free engine unchanged. Pro adds:

• Specific weekdays on a weekly or monthly rule, so one event can run every Tuesday and Thursday
• The nth or last weekday of the month, such as the last Friday
• A fixed day of the month
• End after a number of sessions, or end on a date
• Skip dates, a comma-separated list of dates removed from the series

The last two suit a season well. You can stop a series on the date your league finishes, and you can list the school holiday weeks up front so they never appear. Skip dates is for planned breaks, and Cancel this date is for the ones nobody saw coming. If you rely on advanced rules and later drop back to Free, the dates already generated stay, but the series stops extending, so keep Pro active on a site that depends on them.

Fixtures and the venues catalog

Each fixture is a one-off event, and the reusable venue catalog saves typing. Start typing a venue name in the editor and a list of matching entries drops down. Pick the clubhouse pitch or the council ground once and its name and address fill in. Eventonomy matches venues on a normalized name and city, so you don’t end up with five spellings of the same ground.

Organizers work the same way, which suits a club with a different coach for each age group. Pro lets an event list more than one organizer or venue, handy for a joint fixture or a tournament on two pitches.

A worked season

Here’s a made-up club, so you can see how the pieces fit. Nothing in this section is a real club or real data.

Northfield Rovers has a Tuesday training night, a Thursday training night and a home fixture most Saturdays.

1. The secretary creates two recurring events, Tuesday Training and Thursday Training, each set to Weekly with an interval of 1.
2. Each Saturday fixture is its own one-off event, with the opponent in the title and the home pitch picked from the venue catalog.
3. On the Thursday before a storm, the coach opens Thursday Training, goes to Upcoming dates and presses Cancel this date on that week only.
4. The coach uses the email panel on that date’s event to tell registered players, because their phone calendars may still show the session.
5. The following week the training is back on, with nothing to repair.

Two events cover the whole training year, plus one event per fixture. That’s far less to maintain than a hundred hand-made copies of the same session.

Test it before the season starts

A short rehearsal catches problems while nothing depends on them.

1. Create a weekly test event a few weeks out and confirm the dates appear on the calendar.
2. Cancel one date and check it has gone from the calendar and the event page while the others remain.
3. Restore it and confirm it comes back.
4. Edit the schedule and confirm the cancelled date doesn’t return.
5. Log in as a user who can’t edit the event and confirm they can’t cancel anything.
6. Subscribe a phone to the calendar feed and look at what a cancelled date does there, so you know what to tell members.

Once that works, copy the setup for your other squads.

Where to go next

If you want the reasoning behind how a series should behave, why recurring events are where plugins break goes through the traps. The event calendar feature page shows the views members will see, and the RSVP page covers registration and waitlists. For exactly what needs Pro, see Free vs Pro.