-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to create recurring event in v2* #368
Comments
+1 to implement this missing functionality in v2 |
Hi all, We really need this feature for a project we are working on, and we used this feature in 0.16. |
It perfectly works on 0.16 :) |
I am the maintainer of the Drupal module "Views iCal" which uses this library to render iCalendar pages. This issue is a blocker for me to upgrade to 2.0. https://www.drupal.org/project/views_ical/issues/3209012 Edit: I think we can go one of two routes, 1, simply treating recur rules as strings, and be agnostic of the meanings those rules have. Or two, we add a new "Domain\ValueObject" class for this, and in that depend on rlanvin/php-rrule for generating our recurrence rules instead of trying to set up our own system of parsing/generating these. The 0.x version of the library took the latter approach, and you would build a class and feed it individual rrule properties I'm going to checkout the rlanvin/php-rrule library to see if this can be leveraged. |
In the meantime, it might be possible to generate RRULE fields in calendars using custom properties. See example 2 https://github.com/markuspoerschke/iCal/blob/2.x/examples/example2.php#L45 |
Well there is also an PR #560 |
Hello everyone.
I can not understand how to create a recurring event with version 2.*
I see that there is RecurrenceRule class in https://github.com/markuspoerschke/iCal/blob/0.11.x/src/Eluceo/iCal/Property/Event/RecurrenceRule.php
But I do not see anything similar in v2.*
Could anyone guide me on how to create a recurring event for 'Every Monday at 9.00 during January' ?
Thanks in advance
The text was updated successfully, but these errors were encountered: