Today’s update is an under-the-hood enhancement to the way Online Booking deployments access calendar configurations across our load balancers. This speeds up these sites while isolating them from Firebase disruptions.

Today’s update improves the calendar’s responsiveness when fetching events and disabling calendars or navigating dates. (This update also adds the ability to assign the “Before Events Fetched” action to read-only calendars.) The responsiveness improvement allows you to turn off a calendar while it’s fetching events. This will immediately kill the fetch process, and the UI will respond right away. The one exception is in FileMaker: if a script is actively running, the web viewer cannot receive input. So, if events are being fetched, that process will most likely need to finish before the UI can respond to input.

This internal update improves error trapping to prepare for an upcoming Google change in OAuth that will mandate “granular” authentication when signing into Google. Today’s update also moves the notifications file that DayBack uses to display news items from our site to a Github repo; this should load a bit faster, though it loads after the calendar, so most folks likely won’t notice it.

When you clear a resource filter in DayBack, the calendar will no longer clear your selected resources as well. In some cases, this used to put the calendar into an unfiltered state, asking it to show events from all the possible resources. In large deployments, this could cause things to slow down; now the calendar will preserve your selected resources until you de-select them or filter them out.