Releases: LJPc-solutions/freescout-calendar-module
Releases · LJPc-solutions/freescout-calendar-module
2.6.4
2.6.3
2.6.2
2.6.1
In this patch release, we've fixed several critical issues with the performance optimizations:
- Fixed JavaScript event lookup priority. The calendar now correctly uses the fast API endpoint first when opening event URLs, instead of waiting for the full calendar to load. Event popups now appear instantly when accessing permalinks.
- Fixed API endpoint URL generation. Corrected the route generation that was causing 404 errors when trying to load individual events via the optimized endpoint.
- Fixed SQL query for normal calendars. Removed the non-existent uid column reference that was causing 500 errors when searching for events in normal (non-external) calendars.
We also cleaned up the configuration by removing unimplemented feature flags to avoid confusion.
2.6.0
In this release, we've added major performance optimizations and fixed a critical bug:
- Database event indexing for instant event lookups. When enabled, calendar events are indexed in the database, reducing lookup times from 10+ seconds to ~1.5 milliseconds - over 6,600x faster! This is especially beneficial for large calendars with thousands of events.
- CalDAV REPORT queries for targeted event fetching. Instead of downloading entire calendar files, the module now fetches individual events directly from CalDAV servers when supported, significantly reducing network overhead and processing time.
- Performance metrics tracking. When enabled, the module logs detailed performance metrics including lookup times and cache hit rates, allowing you to monitor the optimization effectiveness in production.
To enable these performance features, add the following to your .env file:
CALENDAR_ENABLE_EVENT_INDEX=true
CALENDAR_ENABLE_CALDAV_REPORTS=true
CALENDAR_FORCE_LEGACY_MODE=false
2.5.2
2.5.1
2.5.0
In this release we've added permalinks to events!
It is now possible to copy the permalink right from the event edit modal:

A direct link to the event is also added to the thread when the event has been created from within a conversation:

Since this release it is also possible to view the full event title:
