Difference between revisions of "Talk:Wiki maintenance plan"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (JanIversen moved page Talk/Wiki maintenance plan to Talk:Wiki maintenance plan without leaving a redirect)
 
(14 intermediate revisions by 3 users not shown)
Line 1: Line 1:
The state wiki require some maintenance and an urgent upgrade. This page documents what needs to be done, and what should be done. There is a thread on dev (Wiki maintenance) where the decisions are made.
+
  UPDATE table_name SET col_name = CONVERT(CONVERT(CONVERT(col_name USING latin1) USING binary) USING utf8);
 
+
::  
At the moment we have the following work list:
+
Another way to do this (and possibly a more effective solution since it can be done during the MWiki upgrade) is:
 
+
   mysqldump -h DB_HOST -u DB_USER -p DB_PASSWORD --opt --quote-names --skip-set-charset --default-character-set=latin1 DB_NAME > DB_NAME-dump.sql
* Change LocalSettings.php to close for "create user" '''DONE'''
+
  mysql -h DB_HOST -u DB_USER -p DB_PASSWORD --default-character-set=utf8 DB_NAME < DB_NAME-dump.sql
* Update UA- code for google-analyics '''DONE'''
+
:: (source: http://blog.hno3.org/2010/04/22/fixing-double-encoded-utf-8-data-in-mysql/ )
* open for "create page" again  '''DONE'''
+
 
+
* remove accounts older than a year WITHOUT any contributions
+
  Scripts is being prepared, about 24.000 accounts out of 32.000 will be removed.
+
* remove all accounts from the time of the spam period
+
   Scripts are being prepared, but wait for a decision on the time period (see dev)
+
* create directory in SVN and save all new changes to files.
+
 
+
* open for create user
+
* Clean database, for "deleted" pages, unused files.
+
* repair "broken redirect", "double redirect", "non categorized pages"
+
* Convert all pages to UTF8 (mysql),
+
  most pages are defined as latin1, but some have UTF8 content, this will not work after an update.
+
* request (via JIRA) a new VM for test.openoffice.org
+
  test simple alias first
+
* make a test.wiki.openoffice.org, new db and new mediawiki version.
+
* upgrade test db.
+
* make all extensions work in test
+
* have people testing test
+
* Copy production db, and upgrade it
+
* copy test to production.
+

Latest revision as of 19:39, 25 December 2012

 UPDATE table_name SET col_name = CONVERT(CONVERT(CONVERT(col_name USING latin1) USING binary) USING utf8);

Another way to do this (and possibly a more effective solution since it can be done during the MWiki upgrade) is:

 mysqldump -h DB_HOST -u DB_USER -p DB_PASSWORD --opt --quote-names --skip-set-charset --default-character-set=latin1 DB_NAME > DB_NAME-dump.sql
 mysql -h DB_HOST -u DB_USER -p DB_PASSWORD --default-character-set=utf8 DB_NAME < DB_NAME-dump.sql
(source: http://blog.hno3.org/2010/04/22/fixing-double-encoded-utf-8-data-in-mysql/ )
Personal tools