In doing some tests on changes I've made for the DB stored configuration, I've discovered how inflexible the current installer is.  I'm going to be posting an feature issue in eventum about this, as the installer has been a pain in the pocket in the past, I think it's high time it get fixed once and for all.

Also, SVN copy for 3.0.0 is currently broken, if it installs for you, your doing something wrong.  This should be straightened out by the weekend I would hope. 

One thing, if your trying to follow the 3.0.0 progress, realize that there is no capacity for upgrading databases as we progress.  That kind of work just wastes time.  However people who would like to see what up can do so by browsing to http://www.m-l-z.com/repos/hcl/branches/3.x.x/hcl-2.1.x/  (ignore the hcl-2.1.x designation.  I goofed.. )

For some it can be problematic, particularly if your ticket system is using the same DB (although in my humble opinion, the module sure at least prefix their records with a unique prefix).  However as I've found in the past month or so, many people really want to keep transcripts, and at least one user has 10 departments and about 30 operators.  So it can be non-trivial.  On the other hand, for small operations, it can be a great idea to drop all the tables and start fresh.  Something that really could be in the installer, quite simply in fact.

we dont use safe mode. oddly enough , safe_mode has its  own set of security issues, thus, ironically, it can actually be safer to run safe_mode off. (read up on it at php.net - http://us2.php.net/manual/en/features.safe-mode.php  - also note it is *removed* in php 6.0)

Also keep in mind it needs to be compatible with php 5.2.2 (See php.net for announcement on php4 end of life)
In fact, might recommend dropping any support for php4, as php5 has a numbmer of wonderful features that would make life easier (and help make the application more secure), such as built in input filtering.. (http://us2.php.net/manual/en/ref.filter.php)

Currently we run php 5.2.2/Apache2.2/MySQL5.0.x and expect to have vast majority of all machines we manage up to those versions by end of 2007.

I leave it off...

If a client needs it on, they can flag it as on by adding a line in their .htaccess file in the directory safe mode=on is required...