3 RT now defaults to a database name of rt4 and an installation root of /opt/rt4.
5 If you are upgrading, you will likely want to specify that your database
6 is still named rt3 (or import a backup of your database as rt4 so that
7 you can feel more confident making the upgrade).
9 You really shouldn't install RT4 into your RT3 source tree (/opt/rt3)
10 and instead should be using make install to set up a clean environment.
11 This will allow you to evaluate your local modifications and configuration
12 changes as you migrate to 4.0.
14 If you choose to force RT to install into /opt/rt3, or another existing RT 3.x
15 install location, you will encounter issues because we removed the _Overlay
16 files (such as Ticket_Overlay.pm) and relocated other files. You will
17 need to manually remove these files after the upgrade or RT will fail.
18 After making a complete backup of your /opt/rt3 install, you might use a
19 command like the following to remove the _Overlay files:
21 find /opt/rt3/lib/ -type f -name '*_Overlay*' -delete
23 RT has also changed how web deployment works; you will need to review
24 docs/web_deployment.pod for current instructions. The old
25 `fastcgi_server`, `webmux.pl`, and `mason_handler.*` files will not
26 work with RT 4.0, and should be removed to reduce confusion.
31 You will need to carefully review your local settings when moving from
34 If you were adding your own custom statuses in earlier versions of RT,
35 using ActiveStatus or InactiveStatus you will need to port these to use
36 the new Lifecycles functionality. You can read more about it in
37 RT_Config.pm. In most cases, you can do this by extending the default
38 active and inactive lists.
41 Upgrading sessions on MySQL
43 In 4.0.0rc2, RT began shipping an updated schema for the sesions table
44 that specificies a character set as well as making the table InnoDB. As
45 part of the upgrade process, your sessions table will be dropped and
46 recreated with the new schema.
49 UPGRADING FROM RT 3.8.x and RTFM 2.1 or greater
51 RT4 now includes an Articles functionality, merged from RTFM.
52 You should not install and enable the RT::FM plugin separately on RT 4.
53 If you have existing data in RTFM, you can use the etc/upgrade/upgrade-articles
54 script to upgrade that data.
56 When running normal upgrade scripts, RT will warn if it finds existing
57 RTFM tables that contain data and point you to the upgrade-articles script.
59 This script should be run from your RT tarball. It will immediately
60 begin populating your new RT4 tables with data from RTFM. If you have
61 browsed in the RT4 UI and created new classes and articles, this script
62 will fail spectacularly. Do *not* run this except on a fresh upgrade of
67 etc/upgrade/upgrade-articles
69 It will ouput a lot of data about what it is changing. You should
70 review this for errors.
72 If you are running RTFM 2.0 with a release of RT, there isn't currently an upgrade
73 script that can port RTFM's internal CustomField and Transaction data to RT4.
75 You must also remove RT::FM from your @Plugins line in RT_SiteConfig.pm.
78 The deprecated classes RT::Action::Generic, RT::Condition::Generic and RT::Search::Generic
79 have been removed, but you shouldn't have been using them anyway. You should have been using
80 RT::Action, RT::Condition and RT::Search, respectively.
82 * The "Rights Delegation" and "Personal Groups" features have been removed.
84 * Replace the following code in templates:
86 [{$Ticket->QueueObj->SubjectTag || $rtname} #{$Ticket->id}]
90 { $Ticket->SubjectTag }
92 * Unique names are now enforced for user defined groups. New groups cannot be
93 created with a duplicate name and existing groups cannot be renamed to an
94 in-use name. The admin interface will warn about existing groups with
95 duplicate names. Although the groups will still function, some parts of the
96 interface (rights management, subgroup membership) may not work as expected
97 with duplicate names. Running
99 /opt/rt4/sbin/rt-validator --check
101 will report duplicate group names, and running it with --resolve will fix
102 duplicates by appending the group id to the name.
104 Nota Bene: As a result of differing indexes in the schema files, Postgres and
105 SQLite RT databases have enforced group name uniqueness for many years at the
110 UPGRADING FROM 4.0.5 and earlier - Changes:
112 The fix for an attribute truncation bug on MySQL requires a small ALTER TABLE.
113 Be sure you run `make upgrade-database` to apply this change automatically.
114 The bug primarily manifested when uploading large logos in the theme editor on
115 MySQL. Refer to etc/upgrade/4.0.6/schema.mysql for the actual ALTER TABLE that
119 The web-based query builder now uses Queue limits to restrict the set of
120 displayed statuses and owners. As part of this change, the %cfqueues
121 parameter was renamed to %Queues; if you have local modifications to any
122 of the following Mason templates, this feature will not function
125 share/html/Elements/SelectOwner
126 share/html/Elements/SelectStatus
127 share/html/Prefs/Search.html
128 share/html/Search/Build.html
129 share/html/Search/Elements/BuildFormatString
130 share/html/Search/Elements/PickCFs
131 share/html/Search/Elements/PickCriteria