The bug fixes that were in beta last week have been released to production. This includes a fix for an issue that was preventing the After Events Rendered action from firing on the calendar’s first load. It also fixes a bug where whole calendars sometimes wouldn’t load when navigating back to the calendar from admin settings, or where events might appear offset from their proper positions.

There are a couple bug fixes in beta that you may want to check out by closing and reopening the calendar in beta mode a few times. This includes a fix for an issue that was preventing the After Events Rendered action from firing on first load. This also includes a fix for an issue where some calendar events wouldn’t load when navigating back to the calendar from admin settings.  We will be publishing this to production on Monday morning, August 26th.

In resource schedule view there was a bug preventing the ability to target the calendar grid cells based on date or resource name due to a formatting issue. This has now been resolved.

Today’s update adds a new app action helper function dbk.updateEditEvent(). It also resolves an issue that could lead to the loading image remaining if there was a Before Calendar Rendered action set to Prevent Default and action.callbacks.cancel() was used.

Today’s update resolves an issue where events could render in incorrect positions in some rare circumstances when loading with the sidebar closed. It also resolves and issue where changing the calendar selection state in an “On Calendars Fetched” app action would update the selection state in the sidebar but the calendar would not retrieve events for that calendar.