diff options
| author | Kevin Falcone <falcone@bestpractical.com> | 2013-01-15 03:47:44 +0400 |
|---|---|---|
| committer | Kevin Falcone <falcone@bestpractical.com> | 2013-01-15 03:47:44 +0400 |
| commit | 1dee3fd6e761593863734ac0c8e62ae185381e40 (patch) | |
| tree | 41e7f8202896a8460227467da4674cf1e87dbf97 | |
| parent | 5bf8bcfcd0527f5b2f3df0c7faefc4cb538bfba3 (diff) | |
Flag the @JSFiles change for users who copied RT_Config to RT_SiteConfigrt-4.0.9
| -rw-r--r-- | docs/UPGRADING-4.0 | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/docs/UPGRADING-4.0 b/docs/UPGRADING-4.0 index d17b165bb1..f884c529a5 100644 --- a/docs/UPGRADING-4.0 +++ b/docs/UPGRADING-4.0 @@ -160,3 +160,16 @@ name of the Lifecycle. The 3.9.2 upgrade step removed all enabled Personal Groups, but missed any disabled groups. We catch and clean up the disabled Personal groups during the 4.0.9 upgrade step. + +=head2 Javascript Changes + +If you have set a custom @JSFiles in RT_SiteConfig.pm, you will need to +amend this to include the new jquery.cookie.js file added to +RT_Config.pm. If you are using an extension that requires manually +tweaking @JSFiles, please contact the developer and ask them to use +RT->AddJavaScript in their extension to avoid these upgrade problems. + +If you have @JSFiles set in your RT_SiteConfig.pm but it appears to be +the same as RT_Config.pm (no local js files added) you can safely remove +the whole setting from RT_SiteConfig.pm and allow our default to be +used. |