![]() Otherwise, you can always hide the old version of the event, which will prevent it from showing up anywhere on the front end of your site. If your source calendar is changing the UID each time an event is updated, you can contact the source to let them know about this issue. Simply select the events that you’d like to group together and you’ll have a dedicated event page for all of your events in the series. To do this, head over to Events > Series and Add New. Given that recurring events will import as single events, you can use the series feature, included with Events Calendar Pro 6.0 and above, to group your recurring events together. Because the iCalendar feed doesn’t give us any information in the feed indicating that this new event is “linked” to the original one, Event Aggregator will see the two separate UIDs and create a new event for the modified instance. RRULE:FREQ=WEEKLY WKST=SU UNTIL=20190704T035959Z BYDAY=WEĮvent Aggregator will see this and create single events on your site using this information. However, if you modify one of the instances of that event, a new event entry with a separate UID will be generated in the iCalendar feed. In the iCalendar feed that Google creates for your calendar, this creates one event entry with a recurrence rule that looks something like this: Say you create a recurring event in your Google Calendar that recurs daily, weekly, monthly, or yearly. While Google Calendars do not change the UID following changes to single events, recurring events are a different story. Since the UID changes regularly, Event Aggregator is unable to reliably detect changes from this source. In this case, Event Aggregator will see the new UID and create a new event. ![]() In some cases, the source calendar provides a different UID each time the calendar is updated. There are a few cases where it can change, which looks to Event Aggregator like the event is new. However, the UID does not always remain the same. Typically, that UID will remain the same in the source calendar, and each time you run an import, Event Aggregator will see a matching ID for events that have already been imported. ![]() What causes events to be duplicated on my site? If it doesn’t see an event on your site with that UID, it will create a new one. If it finds an event on your site with the same UID, that event will be updated on your site or ignored, depending your Event Update Authority settings under Events > Settings > Imports. When you import events from an iCalendar feed or an ICS file, Event Aggregator uses an event’s UID to determine whether an event is new and needs to be created or has already been imported. Part of the information that is included for each event is a unique identifier, or UID. ICalendar feeds and ICS files contain information about events in a standardized format, which allows those events to be imported to other platforms. This article should help you determine why this might be happening and let you know what can be done. Running an import and seeing existing events duplicated on your site can be extremely frustrating. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |