If You create a view that pulls dates through ex. Field collection the UID is not unique in case of multiple dates.
This:
UID:calendar.381.field_date.0@www.website.com
UID:calendar.381.field_date.0@www.website.com
Should probably be:
UID:calendar.381.relationsship_name.0.field_date.0@www.website.com
UID:calendar.381.relationsship_name.1.field_date.0@www.website.com
I guess this goes for relationships in general - but in my specific case this is caused by a Field Collection relation.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | date_ical-gives-relationships-unique-IDs.2644520.3.patch | 2.4 KB | coredumperror |
Comments
Comment #2
coredumperror commentedThank you for bringing this issue to my attention. I know the exact line of code this problems stems from, but I'll need to do some research to figure out how to overcome it.
Comment #3
coredumperror commentedOK, here's a patch I whipped up. It works for the method by which I added a Field Collection-based relationship to my test view, but I'm not sure I really did it in the "normal" way, since I created it through trial and error. Please give it a shot, and let me know if it works for you.
Comment #4
IT Munger commentedI can confirm this patch addresses my issue. As described in the summary, my UIDs were not unique. We use CiviCRM Multiday Event (civicrm_multiday_event) to generate events for the calendar, the sessions are stored as mentioned above.
Thanks for the patch!
Comment #5
coredumperror commentedOh good! I've been waiting to commit this patch for months. I'll go ahead and do that now.
Comment #7
coredumperror commented