changeset 9:3785dfb7b69d 1.2-updates 1.2.5

Fixes #2: Fix validation errors * Fix validation error when creating new rank themes
author IBBoard <dev@ibboard.co.uk>
date Tue, 23 Jun 2009 19:42:15 +0000
parents 4d937925a871
children
files Install.xml
diffstat 1 files changed, 4 insertions(+), 7 deletions(-) [+]
line wrap: on
line diff
--- a/Install.xml	Tue Jun 23 19:34:40 2009 +0000
+++ b/Install.xml	Tue Jun 23 19:42:15 2009 +0000
@@ -55,12 +55,9 @@
 				<rev-version>1.2.5</rev-version>
 				<changelog lang="en-gb">
 					<change>Add: Link to "Special and Normal Rank Images" MOD in description</change>
-					<change>Fix: Move some files in package because MOD packaging instructions keep changing</change>
-					<change>Fix: Don't hard-code link in rank themes text</change>
-					<change>Fix: Update finds of get_user_rank in memberlist.php to newer v3.0.4 parameters</change>
-					<change>Change: Make it clear that people with special ranks won't get a rank selection option in the description</change>
-					<change>Change: Make it clearer that deleting a theme deletes the ranks in it (since we can't guess where to put them and we need a standard confirm page so we can't ask the user)</change>
-					<change>Change: Make the default and special rank theme IDs slightly more flexible</change>
+					<change>Fix: Fix rank theme introduction at start of memberlist.php?mode=ranks</change>
+					<change>Fix: Change subsilver file copying instructions to match new packaging structure</change>
+					<change>Fix: Fixed validation error in ACP when adding new rank themes</change>
 				</changelog>
 			</entry>
 			<entry>
@@ -441,7 +438,7 @@
 					trigger_error($user->lang['NO_RANK_THEME_TITLE'] . adm_back_link($this->u_action), E_USER_WARNING);
 				}
 
-				if ($rank_id == DEFAULT_RANK_THEME_ID || $rank_id == SPECIAL_RANK_THEME_ID || $rank_id <= 0)
+				if ($rank_id == DEFAULT_RANK_THEME_ID || $rank_id == SPECIAL_RANK_THEME_ID || $rank_id < 0)
 				{
 					trigger_error($user->lang['MUST_SELECT_RANK_THEME'] . adm_back_link($this->u_action), E_USER_WARNING);
 				}