RT 4.4.3 Documentation

UPGRADING-4.2

Go to latest version →

UPGRADING FROM RT 4.0.0 and greater

The 4.2 release is a major upgrade and as such there are more changes than in a minor bugfix release (e.g., 4.0.13 to 4.0.14) and some of these changes are backward-incompatible. The following lists some of the notable changes, especially those that might require you to change a configuration option or other setting due to a change in RT. Read this section carefully before you upgrade and look for changes to features you currently use.

See devel/docs/UPGRADING-4.0 for internals changes relevant to extension writers.

UPGRADING FROM 4.2.3 AND EARLIER

RT 4.2.4's upgrade scripts contain two fixes to normalize upgraded RTs with those installed new from a release of RT 4.2.

We neglected to add the "Open Inactive Tickets" action mentioned earlier in this documents. It was available to fresh installs but not on upgrades. This Scrip Action is now created if needed.

RT expects the ___Approvals queue to have a special value in the Disabled column so that it is hidden but tickets can still be created (normal disabled Queues disallow ticket creation). Users who enabled and then disabled the Queue on earlier releases will have the incorrect Disabled value, so we fix that. A similar problem applies to the lifecycle, which must be set to the internal "approvals" lifecycle -- which is not listed as an option. RT 4.2.4 also includes enhancements to the Queue admin page for ___Approvals to prevent editing things which might cause problems.

UPGRADING FROM 4.2.5 AND EARLIER

RT 4.2.6 includes a new Scrip Action "Notify Owner or AdminCc". This action will send the given correspondence to the Owner, if not Nobody, otherwise it will notify the AdminCcs. If using this, you will likely want to modify or remove the Notify Owner and AdminCcs scrip to avoid duplicate notifications. This Scrip Action is not used in any default Scrips at this time.

UPGRADING FROM 4.2.6 AND EARLIER

The $LogoImageHeight and $LogoImageWidth configuration options have been overridden by CSS since 4.0.0, and thus did not affect display. They have been removed, and setting them will trigger an informational message that setting them is ineffective.

UPGRADING FROM 4.2.9 AND EARLIER

An additional optional dependency, HTML::FormatExternal, has been added. This allows RT to use w3m, elinks, html2text, or other external tools to render HTML to text. This dependency is not installed by default; however, its use is strongly encouraged, and will resolve issues with blank outgoing emails.

UPGRADING FROM 4.2.10 AND EARLIER

The $DatabaseRequireSSL option has never affected whether the database connection was performed using SSL, even under Postgres; the functionality can now be implemented via %DatabaseExtraDSN. $DatabaseRequireSSL has been removed, and setting it will trigger an informational message that setting it is ineffective.

The full-text indexing defaults for PostgreSQL have changed; GIN is now the suggested index, as well as storing data in a separate AttachmentsIndex table. Both changes improve lookup speed. For improved search performance, you may wish to drop existing tsvector and GiST indexes on Attachments, and re-generate the index using rt-setup-fulltext-index.

UPGRADING FROM 4.2.12 AND EARLIER

New deployments install an RT_SiteConfig.pm that includes a use utf8; to allow Unicode to be used in config. You may wish to add a use utf8; to the top of your RT_SiteConfig.pm if you haven't already done so.

← Back to index