Rollover for the manual - Revision history

Patsyblefebre: eg

2013-02-13T03:29:01Z

Nickw at 02:21, 20 December 2012

2012-12-20T02:21:18Z

Nickw at 02:20, 20 December 2012

2012-12-20T02:20:57Z

Nickw at 20:27, 19 December 2012

2012-12-19T20:27:26Z

Nickw at 22:58, 16 March 2012

2012-03-16T22:58:49Z

Nickw at 01:33, 2 March 2012

2012-03-02T01:33:09Z

Nickw at 01:32, 2 March 2012

2012-03-02T01:32:38Z

Nickw at 18:52, 29 February 2012

2012-02-29T18:52:27Z

Grampsd at 19:22, 9 March 2011

2011-03-09T19:22:54Z

Nickw at 23:14, 13 January 2010

2010-01-13T23:14:25Z

@@ Line 1: / Line 1: @@
 On this page, 3.x refers to the 'old' (current) version of the manual - 3.z refers to the new, to be created, version...
 #Use phpmyadmin to backup all of the wiki tables!Locate all pages on the wiki that have 3.x in the title - from the wiki: toolbox, Special pages, All pages to get a full list of wiki pages.
@@ Line 38: / Line 37: @@
   filename-{number of version}-{lang}.extension
 ex:
-  Edit-person-31-en.png
+  Edit-person-40-en.png
 We need to know if we keep the {number of version} or if we use the new one on migration (3.1->3.2->4.0->15.0...) ?

@@ Line 35: / Line 35: @@
 *Screenshots
-As there is no [[Available_screenshots|naming scheme]] we are trying to follow a rule for manual updgrade :
+As there is no [[Available_screenshots|naming scheme]] we are trying to follow a rule for manual upgrade :
   filename-{number of version}-{lang}.extension
 ex:
   Edit-person-31-en.png
 We need to know if we keep the {number of version} or if we use the new one on migration (3.1->3.2->4.0->15.0...) ?

← Older revision		Revision as of 02:20, 20 December 2012
Line 27:		Line 27:

	UPDATE `grampsd_wiki`.`page` SET `page_restrictions` = 0x656469743d7379736f703a6d6f76653d7379736f70 WHERE `page`.`page_title` ='Title_of_the_page_in_the_wiki' collate utf8_unicode_ci LIMIT 1;		UPDATE `grampsd_wiki`.`page` SET `page_restrictions` = 0x656469743d7379736f703a6d6f76653d7379736f70 WHERE `page`.`page_title` ='Title_of_the_page_in_the_wiki' collate utf8_unicode_ci LIMIT 1;
		+
		+	(You'll need to replace the spaces in the page title with underscores...)
		+
		+	I do that concatenation in a spreadsheet, creating the (long) SQL statements by combining a first part, the page names and the last part...

	That updates a blob field to force protection without having to do the pages individually. You need to do the above sql statement for each page that you want to protect...		That updates a blob field to force protection without having to do the pages individually. You need to do the above sql statement for each page that you want to protect...

@@ Line 10: / Line 10: @@
 #Import the new pages into the wiki: toolbox, Special pages, Restricted special pages (available only to Sysop members of the wiki), Import pages.  Browse to find the .xml file and Upload file.
-There are serious restrictions for both file size and processing time for the scripts - I had to split the .xml file into 8 pieces to get it all uploaded...
+[NOTE: Updating through multiple xml files not necessary now, as we have command line access to our hosting account.]  There are serious restrictions for both file size and processing time for the scripts - I had to split the .xml file into 8 pieces to get it all uploaded...
-For the change to 3.4 I used a script in the maintenance directory to import xml from the command line.  The GoDaddy hosting service uses an old version of php from the command line, but I was successful with:
+For the change to 3.4 and then from 3.4 to 4.0, I used a script in the maintenance directory to import xml from the command line.  The GoDaddy hosting service uses an old version of php from the command line, but I was successful with:
 '''-bash-3.2$ /usr/local/php5/bin/php importDump.php 34.xml'''
@@ Line 26: / Line 26: @@
 Finally, if you want to set all the previous version pages to be protected, so only sysop mediawiki users are able to make changes (so all changes will be forced into the next set of pages...), you can use a series of sql statements in the form:
-UPDATE `grampsd_wiki`.`page` SET `page_restrictions` = 0x656469743d7379736f703a6d6f76653d7379736f70 WHERE `page`.`page_title` ='Title_of_the_page_in_the_wiki' LIMIT 1 ;
+UPDATE `grampsd_wiki`.`page` SET `page_restrictions` = 0x656469743d7379736f703a6d6f76653d7379736f70 WHERE `page`.`page_title` ='Title_of_the_page_in_the_wiki' collate utf8_unicode_ci LIMIT 1;
 That updates a blob field to force protection without having to do the pages individually.  You need to do the above sql statement for each page that you want to protect...

@@ Line 28: / Line 28: @@
 UPDATE `grampsd_wiki`.`page` SET `page_restrictions` = 0x656469743d7379736f703a6d6f76653d7379736f70 WHERE `page`.`page_title` ='Title_of_the_page_in_the_wiki' LIMIT 1 ;
-That updates the blob field to force protection without having to do the pages individually.  You need to do the above sql statement for each page that you want to protect...
+That updates a blob field to force protection without having to do the pages individually.  You need to do the above sql statement for each page that you want to protect...
 *Screenshots

@@ Line 13: / Line 13: @@
 For the change to 3.4 I used a script in the maintenance directory to import xml from the command line.  The GoDaddy hosting service uses an old version of php from the command line, but I was successful with:
 '''-bash-3.2$ /usr/local/php5/bin/php importDump.php 34.xml'''
 followed by:
 '''-bash-3.2$ /usr/local/php5/bin/php rebuildrecentchanges.php'''

@@ Line 12: / Line 12: @@
 There are serious restrictions for both file size and processing time for the scripts - I had to split the .xml file into 8 pieces to get it all uploaded...
-For the change to 3.4 I tried the script in the maintenance directory that was supposed to import xml from the command line - it failed with a syntax error, so didn't persist...
+For the change to 3.4 I used a script in the maintenance directory to import xml from the command line.  The GoDaddy hosting service uses an old version of php from the command line, but I was successful with:
 That should now have created all of the new pages.

← Older revision		Revision as of 18:52, 29 February 2012
Line 11:		Line 11:

	There are serious restrictions for both file size and processing time for the scripts - I had to split the .xml file into 8 pieces to get it all uploaded...		There are serious restrictions for both file size and processing time for the scripts - I had to split the .xml file into 8 pieces to get it all uploaded...
		+
		+	For the change to 3.4 I tried the script in the maintenance directory that was supposed to import xml from the command line - it failed with a syntax error, so didn't persist...

	That should now have created all of the new pages.		That should now have created all of the new pages.

@@ Line 1: / Line 1: @@
 [[Category:Developers/General]]
-#Use phpmyadmin to backup all of the wiki tables!Locate all pages on the wiki that have 3.0 in the title - from the wiki: toolbox, Special pages, All pages to get a full list of wiki pages.
+On this page, 3.x refers to the 'old' (current) version of the manual - 3.z refers to the new, to be created, version...
 #Copy/paste it into text processor - it is in three columns separated by tabs.  Use regular expression search/replace to replace tabs with carriage returns.  Using GEDIT, best to replace \t with \n rather than \r.  You now have a list of all files on the wiki, one title per line.  Save it as a text file (I'll call it myfile.txt for this example).
-#Use grep to find only the pages with 3.0 in the title: ''grep "3\.0" myfile.txt > mynewfile.txt'' The backslash will make the full stop a literal rather than trying tobe part of a regular expression.
+#Use grep to find only the pages with 3.x in the title: ''grep "3\.x" myfile.txt > mynewfile.txt'' The backslash will make the full stop a literal rather than trying tobe part of a regular expression.
-#Use a text editor to view the new file, and delete any pages that you don't want to roll over (That is, some pages may refer to 3.0 in the title, but are not pages that we want duplicated into 3.1...)
+#Use a text editor to view the new file, and delete any pages that you don't want to roll over (That is, some pages may refer to 3.x in the title, but are not pages that we want duplicated into 3.z...)
 #Copy/paste the new list of page titles into the wiki export using toolbox, Special pages, Export pages and create the xml to screen.  Be sure box for Include only the current revision, not the full history is ticked.
-#Copy/paste the xml into a text processor and use search/replace to replace 3.0 with 3.1
+#Copy/paste the xml into a text processor and use search/replace to replace 3.x with 3.z
 #Save the file (I'll call it export.xml for this example).
 #Import the new pages into the wiki: toolbox, Special pages, Restricted special pages (available only to Sysop members of the wiki), Import pages.  Browse to find the .xml file and Upload file.