Contrib.social

Date augment, remove occurrence

Open on Drupal.org →
Created on 27 November 2021, over 3 years ago
Updated 25 January 2025, 2 months ago

Problem/Motivation

If you remove an occurrence from a recurring date before one with date content augmentation the deltas change so later augmented dates have their out by one.

Steps to reproduce

Create a recurring event field, with the augmented content enabled.
Create an entity with a recurring date, say daily.
Add augmented content to a date, somewhere in the list, not the end.
Edit the entity and remove an earlier instance of the recurrence.
The augmented content will retain the old delta so display itself with the date with the new delta, one later.

Proposed resolution

My first thought was if it could be attached something 'unique' like the (combined) timestamps of the date rather than the delta. Then it's only going to break if you change the date of the occurrence. This might make sense as well if someone changes the rrule, what other logic could there be that one occurrence becomes another, certainly not its position in the sequence.

[update] The iCal spec actually has a rule for this https://www.kanzaki.com/docs/ical/recurrenceId.html https://icalevents.com/4437-correct-handling-of-uid-recurrence-id-sequence/ which also makes sense if you're thinking about someone subscribing to an individual event - they want to know if it's moved time, as well as other changes.

With some feedback from the field itself, rather than the display, knowing about augmentation this could even be fixed I'd guess.

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Version

1.0

Component

Code

Created by

🇳🇱Netherlands ekes

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment 2 months ago →
    🇳🇱Netherlands ekes

    So in my digging into how these things can be done. I've logged what happens with the ical feeds of a Google calendar. Overriding, changing, and removing. Figure I'll log it here too as it might be useful.

    https://gitlab.com/ekes/2025-date/-/blob/notes/ical-rrule-override-seque...

    Referencing the RECURRENCE-ID works here, as it references the time in the sequence it would have happened, no matter other individual alterations, including removal. Google does not try and reconcile overrides if you change the underlying sequence. Although interestingly it seems they might remain orphaned with no data, as if the underlying sequence returns to the same start times, the empty overrides reappear in the feed.

  • Comment 2 months ago →
    🇳🇱Netherlands ekes
contrib.social Blog FAQ Discussions
Production build 0.71.5 2024