[Rt-commit] rt branch, 4.0.9-releng, updated. rt-4.0.9rc1-1-g1dee3fd

[Kevin Falcone]

The branch, 4.0.9-releng has been updated
       via  1dee3fd6e761593863734ac0c8e62ae185381e40 (commit)
      from  5bf8bcfcd0527f5b2f3df0c7faefc4cb538bfba3 (commit)

Summary of changes:
 docs/UPGRADING-4.0 | 13 +++++++++++++
 1 file changed, 13 insertions(+)

- Log -----------------------------------------------------------------
commit 1dee3fd6e761593863734ac0c8e62ae185381e40
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Mon Jan 14 18:47:44 2013 -0500

    Flag the @JSFiles change for users who copied RT_Config to RT_SiteConfig

diff --git a/docs/UPGRADING-4.0 b/docs/UPGRADING-4.0
index d17b165..f884c52 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.

-----------------------------------------------------------------------