Upgrade - Revision history

Gauravm at 14:34, 16 November 2011

2011-11-16T14:34:28Z

2011-11-11T13:11:19Z

2011-10-18T21:47:52Z

2011-10-18T20:59:20Z

‎Fix problems

2011-10-18T20:58:43Z

‎Fix problems

2011-10-18T20:57:38Z

2011-10-18T19:45:59Z

2011-10-18T19:43:09Z

‎Backup

2011-10-18T19:40:38Z

2011-10-18T19:36:16Z

@@ Line 71: / Line 71: @@
 * Gallery tags did not work. Instead of a nice gallery, it started showing a bulleted list of images.
 * $wgEnableMWsuggest function stopped working for some reason.
-* Also upgraded SMW to 1.6. In the ''table'' result format, the columns stopped being sortable. However, class=wikitable still shows the arrows at the top of the table for sorting.
+* <s>Also upgraded SMW to 1.6. In the ''table'' result format, the columns stopped being sortable. However, class=wikitable still shows the arrows at the top of the table for sorting</s>. Is fixed in SMW 1.7 which should be released in late 2011. [[User:Gauravm|Gauravm]] 06:34, 16 November 2011 (PST)
-None of these problems have been fixed so far. Could not find solutions [[User:Gauravm|Gauravm]] 05:11, 11 November 2011 (PST)
+[[User:Gauravm|Gauravm]] 05:11, 11 November 2011 (PST)

@@ Line 60: / Line 60: @@
 ==Fix problems==
+===Skin===
 The one problem which we will ALWAYS encounter is skin. In our case, the "modern" skin was over-written to make brahma skin. Hence, we will always have issues with the skin being overwritten again. So you may have to manually copy all the files in skin/modern/ from your backup. I am going to try and create a new skin called "brahma" to fix this problem. ETA unknown.
@@ Line 68: / Line 68: @@
 '''Update'''
 Ok So the upgrade over-writes some of the scripts as well. they are in ./skin/folder. In our case, the scripts we need to worry are Modern.php and Modern.dep.php. Be on a lookout for possible changes in CSS files.

← Older revision		Revision as of 21:47, 18 October 2011
Line 65:		Line 65:
	'''Update'''		'''Update'''
	Even after copying the skin files, the original skin is not completely restored. I do not know why. One of the image files (header-left.jpg) is not rendering at all.		Even after copying the skin files, the original skin is not completely restored. I do not know why. One of the image files (header-left.jpg) is not rendering at all.
		+
		+	'''Update'''
		+	Ok So the upgrade over-writes some of the scripts as well. they are in ./skin/folder. In our case, the scripts we need to worry are Modern.php and Modern.dep.php. Be on a lookout for possible changes in CSS files.

← Older revision		Revision as of 20:59, 18 October 2011
Line 64:		Line 64:

	'''Update'''		'''Update'''
−	Even after copying the skin files, the original skin is not completely restored. I do not know why. One of the image files is not rendering at all.	+	Even after copying the skin files, the original skin is not completely restored. I do not know why. One of the image files (header-left.jpg) is not rendering at all.

← Older revision		Revision as of 20:58, 18 October 2011
Line 62:		Line 62:

	The one problem which we will ALWAYS encounter is skin. In our case, the "modern" skin was over-written to make brahma skin. Hence, we will always have issues with the skin being overwritten again. So you may have to manually copy all the files in skin/modern/ from your backup. I am going to try and create a new skin called "brahma" to fix this problem. ETA unknown.		The one problem which we will ALWAYS encounter is skin. In our case, the "modern" skin was over-written to make brahma skin. Hence, we will always have issues with the skin being overwritten again. So you may have to manually copy all the files in skin/modern/ from your backup. I am going to try and create a new skin called "brahma" to fix this problem. ETA unknown.
		+
		+	'''Update'''
		+	Even after copying the skin files, the original skin is not completely restored. I do not know why. One of the image files is not rendering at all.

← Older revision		Revision as of 20:57, 18 October 2011
Line 49:		Line 49:
	==Download and Extract the update==		==Download and Extract the update==
	Download the required version(1.17 in my case) from the mediawiki website. The latest version can be found at [http://www.mediawiki.org/wiki/Download this link].		Download the required version(1.17 in my case) from the mediawiki website. The latest version can be found at [http://www.mediawiki.org/wiki/Download this link].
		+
		+	The downloaded program can be extracted directly into your mediawiki installation directory. Or else you can manually extract it in some temporary folder and then copy it to the main folder. Use following command to extract the files.
		+	''tar xvfz TGZ_FILE -C DESTINATION_FOLDER''
		+
		+	Once you copy all the files, you just need to run the update.php script from the maintenance folder. Use following command to do it.
		+	''cd maintenance''
		+	''php update.php''
		+
		+	The script takes a few seconds. So leave it alone. Once it terminates, you are done. The basic upgrade is over.
		+
		+	==Fix problems==
		+
		+	The one problem which we will ALWAYS encounter is skin. In our case, the "modern" skin was over-written to make brahma skin. Hence, we will always have issues with the skin being overwritten again. So you may have to manually copy all the files in skin/modern/ from your backup. I am going to try and create a new skin called "brahma" to fix this problem. ETA unknown.

← Older revision		Revision as of 19:45, 18 October 2011
Line 46:		Line 46:
	* '''Files (such as php scripts, images, everything you can imagine)'''		* '''Files (such as php scripts, images, everything you can imagine)'''
	The most straightforward way of doing this is to copy the entire directory tree using FTP on to your local disk.		The most straightforward way of doing this is to copy the entire directory tree using FTP on to your local disk.
		+
		+	==Download and Extract the update==
		+	Download the required version(1.17 in my case) from the mediawiki website. The latest version can be found at [http://www.mediawiki.org/wiki/Download this link].

@@ Line 38: / Line 38: @@
 ==Backup==
 The two most important things that you need to back up are
-# Database
+* '''Database'''
    To back up the database, use the following mysql command :
 ''mysqldump -u USERNAME -p  --all-databases -h DB_SERVER_NAME  > BACKUP_FILENAME''
@@ Line 44: / Line 44: @@
 You can find values for USERNAME, DB_SERVER_NAME and password from LocalSettings.php file. BACKUP_FILENAME is totally up to you. It is generally a good idea to include the backup date in the filename. Once the command is successful just copy the back up file to your local disk using FTP.
-# Files (such as php scripts, images, everything you can imagine)
+* '''Files (such as php scripts, images, everything you can imagine)'''
 The most straightforward way of doing this is to copy the entire directory tree using FTP on to your local disk.

@@ Line 13: / Line 13: @@
 First, you need to test whether you have required versions of softwares installed. In our case, your primary concerns should be php and mysql. Technically, if you contact the web-hosting service they should be able to tell you the version numbers. To manually test them, first login to your server using ssh.
-* To check current version of php run:
+* To check current version of php, run the following command in the terminal:
 ''php --version''
@@ Line 26: / Line 26: @@
 Version is highlighted in bold text
-* To check current version of mysql run :
+* To check current version of mysql, run the following command in the terminal:
 '' mysql --version''