Allow more advanced element focusing

[squirrelmail.git] / doc / UPGRADE

diff --git a/doc/UPGRADE b/doc/UPGRADE
index 7fc606f9295e220b6c6e9970df4825eef83db956..c7b38b8cb33fcada941ee709577adc7caa9efd13 100644 (file)
--- a/doc/UPGRADE
+++ b/doc/UPGRADE
@@ -256,8 +256,7 @@ Or to create a gzipped tar archive:
 
 Then make sure that you REMOVE the old directory so users can no longer
 access it - if you don't do this, you may be leaving yourself exposed
-to known security exploits.  Of course, don't remove it yet - that's
-your last step after you've been able to make your new installation work.
+to known security exploits.
 
 
 8. How to point the web server to different SquirrelMail installations
@@ -294,15 +293,11 @@ just one example using Apache's Redirect directive:
 9. Version-specific upgrade issues
 ==================================
 
-Upgrading from any version older than 1.2.2 to version 1.2.2 or later
----------------------------------------------------------------------
+Upgrading from the 1.4 release series to the 1.5 release series
+---------------------------------------------------------------
 
-The names used by some translations were changed starting in version 1.2.2.
-In most cases, you won't see any problems due to this change, however,
-the Norwegian Nynorsk (no_NO_ny) translation might need to be fixed.  If
-you decide to retain the same preferences from your old installation, any
-users who have a "language" preference set to "no_NO_ny" will need to
-have it manually changed to "nn_NO".
+The plugin API changed substantially in version 1.5.2.  At the least,
+you should NOT copy your old plugins when making this kind of upgrade.
 
 Upgrading from the 1.2 release series to the 1.4 release series
 ---------------------------------------------------------------
@@ -327,3 +322,20 @@ preserved if you use the same user preferences, although we discourage the
 use of the same preference sets between major release numbers (e.g., 1.4.x
 and 1.5.x).
 
+Upgrading from any version older than 1.2.2 to version 1.2.2 or later
+---------------------------------------------------------------------
+
+The names used by some translations were changed starting in version 1.2.2.
+In most cases, you won't see any problems due to this change, however,
+the Norwegian Nynorsk (no_NO_ny) translation might need to be fixed.  If
+you decide to retain the same preferences from your old installation, any
+users who have a "language" preference set to "no_NO_ny" will need to
+have it manually changed to "nn_NO".
+
+Upgrading from any version older than 1.0.5 to version 1.0.5 or later
+---------------------------------------------------------------------
+
+Some important security upgrades were made to the preferences system
+in version 1.0.5.  It is NOT recommended that you retain user preferences
+when upgrading from versions older than 1.0.5.
+