My Calendar Pro v3.4.0 is released! This is a major release, and includes a number of significant changes worth mentioning.

Importer Improvements

When importing .ics event sources, My Calendar Pro has historically taken each individual occurrence of an event and imported them as separate events. With version 3.4.0, the importer will now insert those occurrences as individual instances of a single event. This greatly reduces clutter in your database and in your events list, making management of your events easier.

If you already have events that were imported individually, the importer will delete the old events, to avoid duplication.

REST (Representational State Transfer) API (Application Programming Interface) Fixed

The REST API actions to update and delete remote events were failing. I’m not sure entirely when this started, but they’re fixed now!

Performance

Performance is really the major place where version 3.4.0 changes. A handful of high-impact changes made in this release should significantly improve performance when submitting or editing front-end events, prevent performance impacts on other plugins processing POST data on the front-end, and speed up the event import processing.

My Calendar v3.7.10

I don’t normally announce minor releases (changes in the third part of the version number), but there are a couple changes worth mentioning in this release.

Performance

I made a number of performance improvements in My Calendar for this release, speeding the return values of numerous frequently-called functions.

New Action

I added a new action: mc_before_delete_event. This was required for the fixes to the My Calendar Pro REST API – so be sure to update both!

Removal of legacy support

This release removes some legacy support for versions of My Calendar Pro that are more than 5 years old and for versions of PHP (Hypertext PreProcessing) earlier than 7.4.