Hi, A user discovered that events from May 2 and beyond are not loading on our main calendar (or any calendar).
We also see this in our console when we try to replicate the error:
Uncaught TypeError: Cannot read properties of undefined (reading ‘getUTCMonth’)
at j.lib.LWCDate.getMonth (calendar.rev.1742713255.js:7:8187)
at j.lwCalendar.DayView.getMultiDayEventTimeRange (calendar.rev.1742713255.js:7:27661)
at j.lwCalendar.DayView.getEventTimeRange (calendar.rev.1742713255.js:7:28170)
at j.lwCalendar.DayView.formatEventObject (calendar.rev.1742713255.js:7:36267)
at j.lwCalendar.DayView.render (calendar.rev.1742713255.js:7:48993)
at HTMLBodyElement. (calendar.rev.1742713255.js:7:73216)
at HTMLBodyElement.dispatch (frontend.min.rev.1695539491.js:7:67864)
at g.handle (frontend.min.rev.1695539491.js:7:65859)
at Object.trigger (frontend.min.rev.1695539491.js:7:96311)
at HTMLBodyElement. (frontend.min.rev.1695539491.js:7:96937)
Is anyone else having the same problem? Does anyone have a solution? Thanks!
Sorry to hear this is giving you trouble. I see what you mean – it looks like the front-end calendar date logic is getting thrown off by an annually repeating event in the results (looks to be id:65709, “UConn ECE Spring and Full-year course evaluation period”).
We’ll work on reproducing this on our servers so we can file it for a core bug fix. In the meantime, if you want to try hiding that event, or re-creating it as a single (non-repeating) event, I bet that might do the trick as a stopgap. Hope this helps!
Let us know if we can help further with this, and thanks for bringing this to our attention.
We’ve bundled a fix for the underlying issue here with our next release, LiveWhale 2.20.0 – this means that after your calendar’s next upgrade, you should be all set to resume using multi-day repeating events in this way. Thanks for bringing this to our attention.
