Ported from Seditio
| GHengeveld |
|
|---|---|
|
Just to let you know, v3.0 is on the way. It will not be directly compatible with v2.0, as I've made some major changes to the way data is stored, to allow for recurring events. Events are split up into events information and individual instances. I've added a new table sed_event_instances which stores the start and ending date/time for each instance of the event. Event participation is linked to the instance, not to the event itself. This will allow you to have multiple instances of a single event (chistmas every year, meeting every week) but still enables users to set a different availability status for each event.
For a preview of how this works, check out this site. |
