- session_(dla|action) is stored in egw_access_log table
- notifications refresh via ajax set notification_heartbeat timestamp in egw_access_log
- if notification_heartbeat is set (happens only for browser sessions with popup notification) sessions get removed from session list one minute after browser is closed
- new static method egw_session::notifications_active($account_id) to check if given user has an open browser with notifications popup checking, to ensure popup notifications can fall back to email
--> REQUIRES DATABASE UPDATE / SETUP
longer use GUIDs containing eGW's install_id, as the information is
irrellevant for SyncML and cause doublications of entries if the
install_id changes.
I plan to have a new rc4 Wednesday or Thursday containing these changes.
- all (sql) accounts have now allways a contact associated with them (account_id is added as new column to the contacts table)
- contacts queries are simplefied a lot now, as no more join with the accouns-table, union and case when statesments are necessary
- lot of the special handling for accounts in the contacts class is no longer needed
- new contact-repository mode "sql-ldap" which additional writes all changes to the ldap repository, to allow to use it read-only from eg. thunderbird and still have the full sql speed and features within eGW (not yet fully working!)
==> requites update of API and addressbook to work (setup!)
- konq: webdav://localhost/egroupware/filemanager/webdav.php/home
- win: http://localhost/egroupware/filemanager/webdav.php/home
You can now you drag and drop to updload files or complete folders and you can edit files directly in the filemanger
a too long account-lid caused the complete lost of run-rigths from all user and groups
--> beside fixing the real bug, I'm changing egw_accounts.account_lid to varchar(64) as varchar(25) was too small anyway
Admin can now define multiple addressbooks each with an own edit / view template and an own icon.
Atm. all Addressbooks are stored in one backend, but this will change soon^tm
1) phpgw_lang(uages) --> egw_lang(uages)
2) mysql 4.0+
- charset gets now set for the connect
- charset gets used for new tables
- some columns shortend to deal with 1000byte (= 333 utf-8 chars) limit for indexes
- update to 1.0.1.019 fixes the charset of existing tables
