1 =head1 UPGRADING FROM 3.6.0 AND EARLIER
3 As there are a large number of code changes, it is highly recommended that you
4 install RT into a fresh directory, and then reinstall your customizations.
6 The database schema has changed significantly for mysql 4.1 and above; please
7 read UPGRADING.mysql for more details.
9 The configuration format has been made stricter. All options MUST be set using
10 the Set function; the historical "@XXX = (...) unless @XXX;" is no longer
13 The RTx::Shredder extension has been integrated into core, and several
14 features have been added, so you MUST uninstall it before upgrading.
16 A new interface for making links in text clickable, and doing other arbitrary
17 text replacements, has been integrated into RT. You can read more in `perldoc
18 docs/extending/clickable_links.pod`.
20 A new feature has been added that allows users to forward messages. There is a
21 new option in the config ($ForwardFromUser), new rights, and a new template.
23 New global templates have been added with "Error: " prefixed to the name to
24 make it possible to configure error messages sent to users.
26 You can read about the new GnuPG integration in `perldoc
27 lib/RT/Crypt/GnuPG.pm`.
29 New scrip conditions 'On Close' and 'On Reopen' have been added.
32 =head1 UPGRADING FROM 3.5.7 AND EARLIER
34 Scrips are now prepared and committed in order alphanumerically by
35 description. This means that you can prepend a number (00, 07, 15, 24) to the
36 beginning of each scrip's description, and they will run in that order.
37 Depending on your database, the old ordering may have been by scrip id number
38 -- if that is the case, simply prepend the scrip id number to the beginning of
42 =head1 UPGRADING FROM 3.5.1 AND EARLIER
44 The default for $RedistributeAutoGeneratedMessages has changed to
45 'privileged', to make out-of-the-box installations more resistant to
46 mail loops. If you rely on the old default of redistributing to all watchers,
47 you'll need to set it explicitly now.