Tiki 27.0 LTS will be released in February 2024.
It is a Long Term Support (LTS) version and will be supported until February 2029 as per the Tiki lifecycle policy. This release is more about refining features than major changes. After this release, there will be major changes in Tiki28.
(This will likely be backported to 26x after testing)
Major change for calendar event handling in Tiki - CRUD operations of events now go through the built-in caldav server with the help of internal method invocation (not through the webdav protocol to skip authentication phase). This has the desired consequences of event scheduling, iTIP message generation and other active plugin taking care of corresponding functionality when events are created, updated, deleted.
Several major updates to calendar functionality:
- recurring events extended to support almost all of supported RFC5545 RRULE definition: https://datatracker.ietf.org/doc/html/rfc5545#section-220.127.116.11. Most obvious one - repeat in X amount of days,weeks,months,years but also other possibilities like monthly repetition every last Friday and similar.
- definition and storage of availability blocks per user in caldav user's inbox property storage (implemented in Tiki caldav server). This allows specifying periods of availability when all other time is considered busy. This affect free-busy reports by caldav server and also 'check availability' button in Tiki when creating events.
- availability blocks can be converted to appointment slots when you choose the calendar to store appointments to and the slot duration. Each such availability block has a settings "Schedule" link where you can see available slots in the future, choose a date, click on a slot and create an event with participants (the user owning the appointment slot and yourself). If calendar has anonymous permission to add events, anonymous users can request appointments as well. This page can also be embedded in an external site via iframe with corresponding code provided in the Tiki interface.