RRULE with UNTIL or EXDATE not interpreted custom

Open on Drupal.org →

Created on 10 September 2019, about 5 years ago

Updated 13 February 2023, almost 2 years ago

If the rule is custom and has an until date set or some dates are excluded it will be saved properly.

When however editing the hosting entity

the interpretation of the rule doesn't show it was custom
it would be saved without these custom settings resulting in unwanted occurrences

🐛 Bug report

Status

Fixed

Version

3.1

Component

Code

Created by

🇩🇪Germany tasc Berlin

Live updates comments and jobs are added and updated live.

date_recur_modular_sierra

Incomplete comments

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 almost 2 years ago →
🇦🇺Australia dpi Perth, Australia
Unfortunately the resolution for 🐛 Date exclude save wiping out dates and exclusions when saving Fixed has slight overlap with this issue, good to see reached the same result for getExcluded

Reworked UNTIL detection slightly.

Added COUNT detection.
Comment almost 2 years ago →
🇦🇺Australia dpi Perth, Australia
@dpi opened merge request.
Comment almost 2 years ago →
🇦🇺Australia dpi Perth, Australia

Comment almost 2 years ago →

dpi → committed be00f356 on 3.x

Issue #3080488 by tasc, dpi, fenstrat: RRULE with UNTIL or EXDATE not...

Issue was unassigned.
Status changed to Fixed almost 2 years ago7:10am 13 February 2023
Comment almost 2 years ago →
🇦🇺Australia dpi Perth, Australia
Comment over 1 year ago →
System Message
Automatically closed - issue fixed for 2 weeks with no activity.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024