comparison doc/upgrading.txt @ 2819:24a5447725a2

note dropped bsddb and bsddb3; note about http-equiv meta brought in sync with current code base.
author Alexander Smishlajev <a1s@users.sourceforge.net>
date Sun, 24 Oct 2004 08:51:23 +0000
parents 37e2b70105f7
children 0998d1b48182
comparison
equal deleted inserted replaced
2818:2317e43609cb 2819:24a5447725a2
13 13
14 .. contents:: 14 .. contents::
15 15
16 Migrating from 0.7.1 to 0.8.0 16 Migrating from 0.7.1 to 0.8.0
17 ============================= 17 =============================
18
19 0.8.0 Backend changes
20 ---------------------
21
22 Backends 'bsddb' and 'bsddb3' are removed. If you are using one of these,
23 please migrate to another backend before upgrade.
18 24
19 0.8.0 API changes 25 0.8.0 API changes
20 ----------------- 26 -----------------
21 27
22 Class.safeget() was removed from the API. Test your item ids before calling 28 Class.safeget() was removed from the API. Test your item ids before calling
52 58
53 (substitute ``koi8-r`` with appropriate charset for your language). 59 (substitute ``koi8-r`` with appropriate charset for your language).
54 Charset preference is kept in the browser cookie ``roundup_charset``. 60 Charset preference is kept in the browser cookie ``roundup_charset``.
55 61
56 Lines ``meta http-equiv`` added to the tracker templates in version 0.6.0 62 Lines ``meta http-equiv`` added to the tracker templates in version 0.6.0
57 are misleading and should be removed. Actual charset is sent in the 63 are misleading and should be changed to include actual character set name::
58 true http header. 64
65 <meta http-equiv="Content-Type"
66 tal:attributes="content string:text/html;; charset=${request/client/charset}"
67 />
68
69 Actual charset is also sent in the http header.
59 70
60 0.8.0 Logging Configuration 71 0.8.0 Logging Configuration
61 --------------------------- 72 ---------------------------
62 73
63 See the `administration guide`_ for information about configuring the new 74 See the `administration guide`_ for information about configuring the new

Roundup Issue Tracker: http://roundup-tracker.org/