Released 05/05/2023
Breaking Changes
There are no breaking changes in this release.
Bookings 1.9.147
Bookings Plugins (extra forms added before payment is taken) can now save their data as form data which can be viewed and downloaded from the event manifest. There's a blueprint you can download from Writing Bookings Plugins to get you started (the two important fields are the one to get the booking business key and the database save action which uses that business key as the object label).
Storing plugin data in history works as it did before. If you update existing plugin forms to use the form data storage, only bookings made after the change to the plugin form will have plugin data available in the manifest.
Comms Template Manager 1.1.11
The form used to manage the templates has been redesigned so it can cope with a larger number of templates and variations. Templates can now contain up to 25,000 characters. This resolves an error that was previously worked around by increasing the maxFieldSize setting in the API Server.
Data Exporter 2.4.73
This release improves the previous version included in Standardised Site iCM4j 9.0.530. The change to the way SFTP details are held is now backwards compatible with previous versions (but you should still migrate your credentials to a configuration End Point asap after the upgrade).
A utility End Point,
We've also fixed an error that would prevent exports being sent by email if you chose to use the Comms Template Manager option to customise your emails.
Events 15.8.85
On the Event Search template, the CSS for the margins of the "refine your results" box has been refactored. The left margin is still 20px, but the style is now specific to the '
Multiple Payment Basket 1.2.42
The schema of the End Point that is used to remove items from the basket has been changed. Prior to this change it was sometimes not possible to remove items from your basket.
Report It 3.0.84
This release includes a fix for an error that could cause configuration values not to be populated when editing an existing report type. This is caused by a change in version 1.1.11 of the Comms Template Manager, which is also part of this release of the Standardised Site, so won't actually affect anyone!