The process for upgrading zTracker has learned from the mistakes of the zForum product. Rather than ask the user to run a series of update files, now zTracker will "detect" what version of zTracker does the user have, and what version of zTracker the user is trying to upgrade to, and apply the appropriate SQL changes automatically.

When a newer version of zTracker is out, here are the general steps to follow and also a couple of tips to ensure a proper system upgrade:

1. Make a backup copy of your current (old) zTracker
2. Remove the zTracker folder entirely from the $INSTANCE_HOME/Products directory
3. Untar the new zTracker version (zTracker-1.x.x.tgz) into your $INSTANCE_HOME/Products directory
4. Restart Zope
5. Manage the Zope site and create a new zTracker instance
6. [TIP] At this point you may copy both "acl_users" and "MailHost" and maybe your database connection object from your BACKUP into your newly created instance, to preserve the original default values
7. Visit the main zTracker index_html page using your web browser.
8. At this point the system will determine the necessary steps to update your zTracker instance (You'll have to have an administrative account for this).

Some notes or suggestions:

You may also write down your original database connection string and your mailhost settings before you add the new zTracker instance so you'll have these values available to you when you are creating (Adding the Product) into your ZODB, also, if you are using LocalFS for attachment repository, you may also have that value ready prior to create your new instance.

Any questions or comments please discuss them in this thread..

-- sb