Please note: timestamps in egw_cal* tables are in server-time,
tz_id / timezone is only used to (re-)calculate recurrences and to
export in iCals (NOT yet implemented)
- timezone data is imported from SQLite DB from Thunderbird Lighting 1.0pre
- contains iCal VTIMEZONE component
- also contains not yet used latitude and longitude for timezone
- methods to convert between TZID string, nummeric tz_id and VTIMEZONE
iCal component
--> preparation to store timezone information for each events
(using tz_id as foreing key into egw_cal_timezones table)
currently not settable via GUI, but GUI leaves them untouched
- showing quantity for resources in brackets behind resource name
- docu and formatting updates all over the place
doublicates from failed sync
- added cal_recurrences timestamp for exceptions (ts of original
recurrence), for existing exceptions update script uses
the closest recur_exception date/time for it
- using uid of original series for new recurrence exceptions,
update script does NOT update the uid's of existing exceptions
- displaying (maybe temporary) these data in the recurrence tab
If you have alarms set and your calendar is already updated to 1.6, you have to rerun that update by setting the calendar version again to '1.5.002' and visit setup again:
UPDATE egw_applications SET app_version='1.5.002' WHERE app_name='calendar' AND app_version='1.5.002'"
- as required by iCal/CalDAV/GroupDAV/SyncML
- this also fixes problems with LDAP contacts, which have non-numeric
ids
- iCal code now converts to and from all participant types supported by
eGroupWare: some types (eg. ressources) require that the clients keeps
the new X-EGROUPWARE-UID attribute
- calendar UI allows to enter email addresses via the addressbook search
box (dont type search, but direct add)
If an entry which is opened by another user, gets saved by another user before the former commits its changes, the former user is notified at the
time saving the event and asked to reload the event and reedit. A link to reedit is provided.
Additionally there is a feature to inform a user that a given entry is opened by another user within a configurable timespan.
This feature was developed by Stefan Becker
- groups can now be selected as participants again
- groups need to have calendar run-rights, to be selectable in the calendar (as it was in 1.0)
- groups will NOT be enumerated as users anymore
--> new or removed members are taken into account as participants
- error messages: if no participant selected or startdate behind enddate (no more automatic swapping)
- pushing the version to 1.2
