![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
diff --git a/MIGRATION.txt b/MIGRATION.txt
index b40b0e81faa8b23bd70349c43e8e969207e60f0e..27bd93ec7ef3854af71690f2082e02083d5b5e8c 100644 (file)
--- a/MIGRATION.txt
+++ b/MIGRATION.txt
0.3.x -> 0.4.x
0.2.x -> 0.3.x
+From CVS
+========
+
+Files storage
+-------------
+
+Messages and files from newly created issues will be put into subdierectories
+in thousands e.g. msg123 will be put into files/msg/0/msg123, file2003
+will go into files/file/2/file2003. Previous messages are still found, but
+could be put into this structure.
+
+Migrating from 0.4.0 to 0.4.1
+=============================
+
+Configuration
+-------------
+
+The USER_INDEX definition introduced in 0.4.1 was too restrictive in its
+allowing replacement of 'assignedto' with the user's userid. Users must change
+the None value of 'assignedto' to 'CURRENT USER' (the string, in quotes) for
+the replacement behaviour to occur now.
+
Migrating from 0.4.0 to 0.4.1
=============================
ANONYMOUS_REGISTER_MAIL rather than overloading ANONYMOUS_REGISTER. If the
variable doesn't exist, then ANONYMOUS_REGISTER is tested as before.
+Configuring the links in the web header is now easier too. The following
+variables have been added to the classic instance_config.py:
+
+ HEADER_INDEX_LINKS - defines the "index" links to be made available
+ HEADER_ADD_LINKS - defines the "add" links
+ DEFAULT_INDEX - specifies the index view for DEFAULT
+ UNASSIGNED_INDEX - specifies the index view for UNASSIGNED
+ USER_INDEX - specifies the index view for USER
+
+See the <roundup source>/roundup/templates/classic/instance_config.py for more
+information - including how the variables are to be set up. Most users will
+just be able to copy the variables from the source to their instance home. If
+you've modified the header by changing the source of the interfaces.py file in
+the instance home, you'll need to remove that customisation and move it into
+the appropriate variables in instance_config.py.
+
+The extended schema has similar variables added too - see the source for more
+info.
+
+
+
+Alternate E-Mail Addresses
+--------------------------
+
+If you add the property "alternate_addresses" to your user class, your users
+will be able to register alternate email addresses that they may use to
+communicate with roundup as. All email from roundup will continue to be sent
+to their primary address.
+
+If you have not edited the dbinit.py file in your instance home directory,
+you may simply copy the new dbinit.py file from the core code. If you used
+the classic schema, the interfaces file is in:
+
+ <roundup source>/roundup/templates/classic/dbinit.py
+
+If you used the extended schema, the file is in:
+
+ <roundup source>/roundup/templates/extended/dbinit.py
+
+If you have modified your dbinit.py file, you need to edit the dbinit.py
+file in your instance home directory. Find the lines which define the user
+class:
+
+ user = Class(db, "msg",
+ username=String(), password=Password(),
+ address=String(), realname=String(),
+ phone=String(), organisation=String(),
+ alternate_addresses=String())
+
+You will also want to add the property to the user's details page. The
+template for this is the "user.item" file in your instance home "html"
+directory. Similar to above, you may copy the file from the roundup source if
+you haven't modified it. Otherwise, add the following to the template:
+
+ <display call="multiline('alternate_addresses')">
+
+with appropriate labelling etc. See the standard template for an idea.
+
Migrating from 0.3.x to 0.4.x