Appearance
Recurring Events — Multiple Instances
By default a recurring event appears once in an archive no matter how many upcoming dates it has. This makes it appear once per upcoming occurrence, each card showing its own specific date — so a weekly class shows up as every upcoming session rather than a single entry.
How it works
- Events with multiple upcoming dates appear multiple times in post feeds
- Each card displays only that occurrence's date
- Cards are sorted by occurrence date, soonest first
- The Posts per page setting on your Post Feed widget is respected
- The results count reflects the total number of occurrences shown
Requirements
- The post type must have a Recurring Date field
- Events must have future occurrences — past dates aren't expanded
Card template setup
This is the step that's easy to miss. For each card to show its own date rather than the event's first date, the card template must use the occurrence tags:
| Tag | Displays |
|---|---|
@post(recurring-date.upcoming.start) | Start date/time of the occurrence |
@post(recurring-date.upcoming.end) | End date/time of the occurrence |
Use your actual field key
Replace recurring-date with your recurring date field's real key if it differs. A mismatched key outputs nothing, which looks like the feature is broken.
Without these tags the cards duplicate correctly but every one shows the same date, which is more confusing than not enabling the feature at all.
Related dynamic tag
The function also provides @post(feed_position), the position of a post within the feed — useful for numbering occurrences or styling the next one differently.
Troubleshooting
Events still appear once
- Confirm the post type has a Recurring Date field
- Confirm the event has more than one future occurrence
- Confirm the archive uses a Post Feed widget
Every card shows the same date
The card template isn't using the occurrence tags. Swap the date field for @post(recurring-date.upcoming.start), using your actual field key.
Dates output nothing
The field key in the tag doesn't match. Check the recurring date field's key on the post type and use that exact value.
Pagination looks wrong
The count reflects occurrences, not posts — 10 events with 3 dates each reads as 30 results. That's intended; each occurrence is separately browsable.