RT 5.0.8 Documentation
Developer-UPGRADING-5.0
UPGRADING FROM RT 4.4.0 and greater
This documentation notes internals changes between the 4.4 and 5.0 series that are primarily of interest to developers writing extensions or local customizations. It is not an exhaustive list.
The default callback in
Articles/Elements/IncludeArticle
provides a ticket object. However, the template itself does not need this ticket object, so it is no longer guaranteed to be loaded when it is passed.New group options were added to the ticket listings pages in SelfService. With the additions, the
AfterMyRequests
callback is no longer at the bottom of the page. If you previously used this callback to add to the bottom of the SelfService page, a new callbackAfterMyGroupRequests
is now available below the new group ticket listing.When we cored RT::Extension::ConfigInDatabase, we renamed the table to Configurations and also changed the internal implementation to support storing regex there.
DEPRECATED CODE
Code that is no longer used after updates is marked as deprecated so it will log a warning for two versions before we remove it. This gives developers time to update their code. This section lists code that has been removed after this period.
SQLFilter callback in /Elements/QueueSummaryByLifecycle
AfterUpdateCustomFieldValue callback in share/html/Admin/CustomFields/Modify.html
share/html/Elements/Quicksearch, which was renamed to QueueList
The find_expired_rows setting for ObjectCustomFieldValues is now find_disabled_rows.
RT::Queue now has a SetDefaultValue method, so individual methods for setting/getting defaults are removed: SetInitialPriority, InitialPriority, SetFinalPriority, FinalPriority, SetDefaultDueIn, DefaultDueIn.
UPGRADING FROM 5.0.0 AND EARLIER
RT::Crypt::GnuPG
previously had a package variable$RE_FILE_EXTENSIONS
that could be modified to control file types RT should try to decrypt. This has been moved to a configuration option in the%GnuPG
setting inRT_Config.pm
.