- Issue created by @mithun-a-sridharan
- 🇩🇪Germany mithun-a-sridharan Heidelberg
Looking at the patch → provided as a fix for the issue reported here ✨ Support for multiple standard (non smartdate) date fields Active , the unique events are identified based on the event ID, start and end dates.
I suspect that the issue with extended duration I observed and reported in this bug report could touch upon another bug in the end date as referred by the $event['end'] variable.
Logically, the $event['end'] should be populated from the entry in the Event content type and something's broken in between. Is there a mapping step I missed or some documentation that I overlooked?
Thanks in advance
Mithun A. Sridharan - 🇩🇪Germany mithun-a-sridharan Heidelberg
Update:
The patch → provided for this issue ✨ Support for multiple standard (non smartdate) date fields Active also fixed the bugs I reported. Huge shout out to @vinayakmk47 → for the patch.
My approach:
- Apply the patch via composer
- Create a start and end date in the view
- Assign the dates in the event content type
- Clear the cache
I've attached the screenshots to this note:
- Two-Dates-View.jpg: Add start and end dates to the view
- Single-Day-Event.jpg: Start and end times on the same date for an event
- Multiple-Days-Event.jpg: Different start and end dates for an event
- Working-Outcome.jpg: Final, working calendarThanks a ton to all those that made this patch possible.
Mithun A. Sridharan