These are not valid iCalendar events. Currently the server ignores recurrence.count when recurrence_end is present. Better would be not to allow such data to enter the store.
This will require an update to sample_events.json.
This doesn't strictly require, but should probably be done in conjunction with, cleaning the dev and production databases. A query of production db.getCollection('event').find({recurrence_end: {$exists: true}, "recurrence.count": {$exists: true}}, {title:1, start:1, recurrence_end:1, recurrence:1}) shows six events in production that contain both fields, as of 2018-04-29. Visual inspection shows that the count and end date of each of these events are consistent, so it doesn't matter which is removed. db.getCollection('event').update({recurrence_end: {$exists: true}, "recurrence.count": {$exists: true}}, {$unset: {"recurrence.count: false}}) (untested) ought to remove the recurrence end from these events.
These are not valid iCalendar events. Currently the server ignores
recurrence.countwhenrecurrence_endis present. Better would be not to allow such data to enter the store.This will require an update to
sample_events.json.This doesn't strictly require, but should probably be done in conjunction with, cleaning the dev and production databases. A query of production
db.getCollection('event').find({recurrence_end: {$exists: true}, "recurrence.count": {$exists: true}}, {title:1, start:1, recurrence_end:1, recurrence:1})shows six events in production that contain both fields, as of 2018-04-29. Visual inspection shows that the count and end date of each of these events are consistent, so it doesn't matter which is removed.db.getCollection('event').update({recurrence_end: {$exists: true}, "recurrence.count": {$exists: true}}, {$unset: {"recurrence.count: false}})(untested) ought to remove the recurrence end from these events.