* FIX: correctly destroys standalone calendar events (#66)
Standalone events are mostly created for holidays where we create a calendar event not associated to any post of of the topic, before this change, the loop was exited before collecting the ID of the calendar event to be destroyed.
Custom fields are create in the site settings of the event plugin. Once at least one custom field is created, a new form will appear in each event UI. These custom fields are passed when DIscourseEvent triggers of the plugin are called, allowing you to pass custom data of the even to other plugins.
This is a reimplementation of 17b0147c which ensures the new table has the correct indexes, defaults and sequences
Co-authored-by: Alan Guo Xiang Tan <gxtan1990@gmail.com>
Co-authored-by: Daniel Waterworth <me@danielwaterworth.com>
This method of creating a table does not include any indexes, so we need to create them manually. Reverting temporarily.
This reverts commit 17b0147ccb.
The migration was removing all but one 'on_holiday' user custom field...
Not big deal though since that custom field is being (re)set regularly in the 'update_holiday_usernames' job.
- FIX: update_holiday_usernames wasn't deleting "on_holiday" user custom fields
when no users were on holiday
- FIX: flair wasn't working on mentions when using subfolder
- PERF: only decorateCooked and addPosterIcon if there's at least one user on holiday
- Migration to remove duplicate "on_holiday" user custom fields
- Add unique index for the "on_holiday" user custom field
- Localize the "On Holiday" title
- Add the boolean type to the "on_holiday" user custom field
David Taylor
Krzysztof Kotlarek
Joffrey JAFFEUX
Alan Guo Xiang Tan
Sam Saffron
Jarek Radosz
Bianca Nenciu
Bianca Nenciu
Régis Hanol