I have a repeating weekly event that was set up with 30 repeats, the last one is next week. I need to extend the repetition - it's going to be weekly for the foreseeable.

On the Configure event » Repeat screen, I can't choose a value >30, but I can set an end date far in the future.

However, doing that and pressing Save gives a confirm screen saying:

⚠️ There are participants registered for repeating events being removed from the set. Those with participants will be converted to standalone events, and those without registration will be deleted.

A repeating set will be created with the following dates.

➊ (table listing existing, past events!)

➋ (table listing events with future start dates)

I'm a bit confused by the ⚠️ warning because there shouldn't be any removed from the set, yet it states that there are; yet I can't see which events those would be?

The first table, ➊ is confusing coming under the "will be created" intro text; these are already created. The second ➋ looks right - these are the dates for future events that I would expect to be listed.

Is it just the wording that's wrong? Perhaps that warning that seems to state it's removing events is not logic-based and doesn't matter? Or is there a way to see the events being removed? Perhaps that's what ➊ is supposed to be?

Clarifications gratefully received!

EDIT: it gets quirkier! The above was observed by editing the last event in the series of repeating events. If I configure the first event of the repeating series, put a future date in, then it's weirder still: it seems to list a lot of past-dates in table ➋ and a sub-set of events in table ➊??? Also, one of the events listed to be removed is the original event itself. And it also lists certain dates in both the to-remove and the to-add tables. 🤷


The first table is listing the events that are to be removed.

It's mis-positioned under the title about adding events because of a missing </table> tag. (I've done a merge request to fix that)

1 Answer 1


Having spent an hour looking through the code and doing a couple of tests, here's what I think the answer is, but v. grateful to others who can say with more conviction.

  1. The confusing title-table mismatch is a simple HTML bug. I've done a merge request to fix that. The first table is indeed a list of events that will be:

  2. At least on Civi 5.58.1 there's a bug that causes submitting this form to crash. I've reported this but can't fix it as I don't know what that code was ever trying to do. On my single test (may not work for you!) commenting Line 408 seems to get it to work...

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.