# HG changeset patch # User Dan # Date 1191792219 14400 # Node ID 492510dddc34ce59916c5ea9ef9ebe0a69a077b7 # Parent 632db5fb4d098c6d6162d0c5c4775df48da3f2cc Upgrade should work (untested) diff -r 632db5fb4d09 -r 492510dddc34 includes/constants.php --- a/includes/constants.php Sat Oct 06 20:51:22 2007 -0400 +++ b/includes/constants.php Sun Oct 07 17:23:39 2007 -0400 @@ -70,7 +70,7 @@ define('MAX_PMS_PER_BATCH', 7); // The maximum number of users that users can send PMs to in one go; restriction does not apply to users with mod_misc rights define('SEARCH_RESULTS_PER_PAGE', 10); define('MYSQL_MAX_PACKET_SIZE', 1048576); // 1MB; this is the default in MySQL 4.x I think -define('SEARCH_MODE', 'FULLTEXT'); // Can be FULLTEXT or BUILTIN +define('SEARCH_MODE', 'BUILTIN'); // Can be FULLTEXT or BUILTIN // Sidebar diff -r 632db5fb4d09 -r 492510dddc34 upgrade.php --- a/upgrade.php Sat Oct 06 20:51:22 2007 -0400 +++ b/upgrade.php Sun Oct 07 17:23:39 2007 -0400 @@ -61,7 +61,7 @@ // Everything related to versions goes here! // Valid versions to upgrade from -$valid_versions = Array('1.0b1', '1.0b2', '1.0b3', '1.0b4', '1.0RC1', '1.0RC2', '1.0RC3', '1.0', '1.0.1', '1.0.1.1', '1.0.2b1'); +$valid_versions = Array('1.0b1', '1.0b2', '1.0b3', '1.0b4', '1.0RC1', '1.0RC2', '1.0RC3', '1.0', '1.0.1', '1.0.1.1', '1.0.2b1', '1.0.2', 'Stable1.0ToUnstable1.1'); // Basically a list of dependencies, which should be resolved automatically // If, for example, upgrading from 1.0b1 to 1.0RC1 requires one extra query that would not @@ -76,9 +76,11 @@ '1.0RC3' => Array('1.0'), '1.0' => Array('1.0.1'), '1.0.1' => Array('1.0.1.1'), - '1.0.1.1' => Array('1.0.2b1') + '1.0.1.1' => Array('1.0.2b1'), + '1.0.2b1' => Array('Stable1.0ToUnstable1.1'), + 'Stable1.0ToUnstable1.1' => Array('1.1.1') ); -$this_version = '1.0.2'; +$this_version = '1.1.1'; $func_list = Array( '1.0' => Array('u_1_0_1_update_del_votes'), '1.0b4' => Array('u_1_0_RC1_update_user_ids', 'u_1_0_RC1_add_admins_to_group', 'u_1_0_RC1_alter_files_table', 'u_1_0_RC1_destroy_session_cookie', 'u_1_0_RC1_set_contact_email', 'u_1_0_RC1_update_page_text'), // , diff -r 632db5fb4d09 -r 492510dddc34 upgrade.sql --- a/upgrade.sql Sat Oct 06 20:51:22 2007 -0400 +++ b/upgrade.sql Sun Oct 07 17:23:39 2007 -0400 @@ -3,7 +3,14 @@ -- ALL NON-SQL LINES, even otherwise blank lines, must start with "--" or they will get sent to MySQL! -- Common tasks (version numbers) DELETE FROM {{TABLE_PREFIX}}config WHERE config_name='enano_version' OR config_name='enano_beta_version' OR config_name='enano_alpha_version' OR config_name='enano_rc_version'; -INSERT INTO {{TABLE_PREFIX}}config (config_name, config_value) VALUES( 'enano_version', '1.0.2' ); +INSERT INTO {{TABLE_PREFIX}}config (config_name, config_value) VALUES( 'enano_version', '1.1.1' ); +---BEGIN Stable1.0ToUnstable1.1--- +UPDATE {{TABLE_PREFIX}}groups SET group_id=9998 WHERE group_id=4; +UPDATE {{TABLE_PREFIX}}group_members SET group_id=9998 WHERE group_id=4; +INSERT INTO {{TABLE_PREFIX}}groups(group_id,group_name,group_type,system_group) VALUES(4, 'Regular members', 3, 1); +---END Stable1.0ToUnstable1.1--- +---BEGIN 1.0.2--- +---END 1.0.2--- ---BEGIN 1.0.2b1--- -- This is really optional, but could reduce confusion if regex page groups get truncated for no apparent reason. ALTER TABLE {{TABLE_PREFIX}}page_groups MODIFY COLUMN pg_target text DEFAULT NULL;