I have lately been looking into increasing the performance of CPSSharedCalendar when you have many events in the database (some tens of thousands or more). There are a couple of things that quickly gets tricky when doing this: No matter what you index on, the result set from each index will be very big. Indexing recurring events is slightly tricky. ...

Today we had a need to extend the CPSSharedCalendar a little bit in a separate project. The functionality needed was not seen as generic enough to go into the CPSSharedCalendar itself. Luckily, since it's written with Five, this can be done easily, and without touching the original code, or monkey patching, and with none of the standard problems of using portal_skins. So I thought ...