--> recogniced it's so old and dusty, it does not make sense any more
--> moved content_header() method to html class
- fixed calls of browser->content_header to use html::content_header
instead
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
- phpgw_accounts --> egw_accounts
- phpgw_acl --> egw_acl
- phpgw_log(_msg) --> egw_log(_msg)
- phpgw_config --> egw_config
- phpgw_applications --> egw_applications
This requires code-changes in many apps. Quite often I was able to replace the db access, with calls to the appropreate classes.
- the backup is independent of the used DB and can eg. be used to port an install to an other DB type
- autom. backup before upgrades of the DB structure
- installing backups instead an installation from scratch
- own backup screen in setup and admin to:
+ shedule repeating backups
+ up- and download of backups
+ creating and restoring backups
==> can be used eg. to port an eGW installation to a different DB type
Atm. there no UI, but if you uncomment the code behind the class, you can backup and restore via an URL. UI to come soon.
