Problem/Motivation
This functionality would be really useful on the smart date module https://www.drupal.org/project/smart_date but it currently doesn't work because Smart Date uses its own custom entity. This patch makes that integration work
| Comment | File | Size | Author |
|---|---|---|---|
| 1551026-smart_date.patch | 1.31 KB | rloos289 |
Comments
Comment #2
stijndmd commentedThis patch works.
However, it doesn't catch recurring smart dates, it just adds the final date from the recurring to the calendar.
Comment #3
rloos289 commentedCorrect, my original requirement was just to get this to work for singular events. I haven't yet looked into getting recurring dates to work, but if there is interest in that functionality then that could be a good next step for this patch.
Comment #4
jdearie commentedThank you - this patch worked for us.
+1 for support for recurring dates. Until then, we have to add some language letting users know that only the first instance of the event will be added to their calendar.
Comment #5
smustgrave commentedI had a lot of luck with https://www.drupal.org/project/smart_date_calendar_kit which used fullcalendar.
Comment #6
matt_paz commentedThe patch works well enough for recurring dates with "Allow recurring date values" set for the range. It shows each instance with that setting, but it would be even better if we could find a way to render the date itself with the smart date formatter.
Comment #7
mandclu commentedFYI there is now support for recurring dates in add to calendar links in Add to Calendar Date Augmenter: https://www.drupal.org/project/addtocal_augment Any feedback would be appreciated.
Comment #8
matt_paz commented@mandclu - I haven't gotten around to testing it yet, but both it (and date_augmenter) look interesting. Thanks for sharing!
Comment #9
coaston commentedJust tested and the patch works. Thank you!
Comment #11
wxactly commentedThanks all - this will be in the next release of the module. If anyone makes more progress on supporting recurring smart dates, please open a new issue with a patch.
Comment #12
wxactly commented