Manual talk:Upgrading to 1.12

Jump to navigation Jump to search
Please do not post support questions here.

Instead, use one of these channels:

Further options for contacting appropriate people can be found at Communication .

Should I upgrade my wiki if it is 1.12.0rc? What changes was done form 1.12.0rc to 1.12.0?

They're listed in the release notes. --brion 16:14, 21 March 2008 (UTC)

But those release notes are almost the same...

You probably always should upgrade to the latest stable release, but you get to decide whether or not this upgrade is worth the trouble. Emufarmers 19:38, 21 March 2008 (UTC)

Summer ???[edit]

Need update introduction... --Kaganer 18:52, 21 March 2008 (UTC)

Done. Emufarmers 19:38, 21 March 2008 (UTC)
Thanks ;) --Kaganer 20:00, 21 March 2008 (UTC)
Wasn't this supposed to be the WINTER release? 13:51, 22 March 2008 (UTC)
That's why I wrote "long-awaited." Aren't I cheeky? —Emufarmers(T|C) 01:06, 23 March 2008 (UTC)
Does NPOV also aply to this wiki? Because, Southern Hemisphere may object... Av16ar 11:20, 23 March 2008 (UTC)
The quarterly updates are referred to by the seasons of their release in many places (including the release announcements). —Emufarmers(T|C) 22:00, 23 March 2008 (UTC)

Title Protection?[edit]

I'm getting a bizarre bug whenever I'm trying to create a new page. This is severe enough that if other folks were experiencing it, I'd expect it to have already been reported. Thus, I'm thinking it's something to do with my own installation... Problem is, I'm not sure where to go for help in troubleshooting it. I'm hosted on Dreamhost, and just used their "one-click" upgrade process (MediaWiki 1.12.0; PHP 5.2.3 (cgi-fcgi); MySQL 5.0.24a-standard-log). Now, whenever I try to create a new page, I get this error: Database error A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was: (SQL query hidden) from within function "Database::select". MySQL returned error "1146: Table 'mywiki.wiki_protected_titles' doesn't exist (". I cannot create new pages. I did some searches in Bugzilla, and came up with only this: (bug 12486) Protected titles now give a warning for privileged editors. HELP? Should I create a Bug in Bugzilla? Is there a forum I should go to instead? I turned off all my extensions and got the same error. Advice, please? -- 21:50, 22 March 2008 (UTC)

You need to run the update script; that kind of defeats the purpose of the one-click install, but it's usually better to just maintain software yourself (unless you tend to forget!). —Emufarmers(T|C) 01:06, 23 March 2008 (UTC)
Totally defeats the purpose. Funny how the Dreamhost panel doesn't explain this. I'm sorry, next time I'll complain first to Dreamhost. I'll go be a moron over there now. D'oh. -- 01:20, 23 March 2008 (UTC)

patch-usernewtalk2.sql does no exist[edit]

I have an error upgrading from 1.9.1. becaouse of the file "patch-usernewtalk2.sql" (this file is not in the ZIP). APACHE PHP 5 MYSQL 5 (windows xp) I have downgrading.

Creating user_newtalk table...
Warning:  fopen(D:\webapache\wiki/maintenance/archives/patch-usernewtalk2.sql) [function.fopen]: failed to open stream: No such file or directory in D:\webapache\wiki\includes\Database.php on line 2212
Could not open "D:\webapache\wiki/maintenance/archives/patch-usernewtalk2.sql".

upgrade from 1.7 doesn't work[edit]

If you get

# php update.php 
MediaWiki 1.7.0 Updater

Fatal error: Call to undefined function wfWikiID() in /usr/share/mediawiki/maintenance/update.php on line 43

it maybe that you've still traces left of you old mediawiki installation. Check $IP in LocalSettings.php.

-Herbert, Sat Jun 21 03:27:11 CEST 2008


when is version 1.13 going to be released? you say it's released in quarterly snapshots but it's soon going to be 4 months since the last update. a user waiting for 1.13 22:42, 7 July 2008 (UTC)


Are any intel 64-bit processors affected with the PHP 5.0.x glitch? -- 11:42, 13 July 2008 (UTC)

directory problem: needs a "public" dir?![edit]

I have a mediawiki originally created with mediawiki-1.9.3, updated to mediawiki-1.11.0rc1 and now updated to 1.12. Everything worked fine, except some little adjustments... I'm happy with the new version!

But now I encountered a problem, that is very suspicious to me and I'm not able to understand what exact is the problem. "Googling" around the net could not help me out...

Here is the problem: I have uploads enabled and also allowed '.zip' as filetype. I have already a file in the wiki called '', now if I try to update/overwrite this file by a new one, I get this message:

Interner Fehler

Die Datei „public/5/56/“ konnte nicht nach „public/archive/5/56/20080717085028!“ umbenannt werden. 

I would translate it in this way:

Internal error

The file „public/5/56/“ could not be renamed to „public/archive/5/56/20080717085028!“.

My problem here is I don't know in what place that directory should be. It seems to me that images got replaced with public since the link to this file is .../images/5/56/ Is it possible that 1.12 stores other that default file types to a new directory called 'public'? How to update my old wiki structure to reflect those changes?? Any help would be very welcome!

--DrTrigon 09:01, 17 July 2008 (UTC)

Conclusion (here is the most recent)
First entry in Manual talk:Upgrading to 1.12 (here).
Second entry in Project:Support desk/Sections/System.
Then found a description at Bugzilla (MediaWiki) and this e-mail which explains a lot! Hopefully this explains everything...?!
For further information (e.g. in case of a new appearance of this error) look at Support and contact someone from Project:Support desk/Support team directly.
--DrTrigon 08:22, 29 July 2008 (UTC)

Fatal Error after using "Alternative 2"[edit]

I updated our wiki ( ) from Version 1.11 to 1.12. Since we don't have shell access and "proc_open()" is disabled by our hosting company, there was only "Alternative 2" left. Everything worked fine but after running the installation there was a fatal error when browsing the wiki. It said:"Fatal error: Call to undefined method ParserOptions::enableLimitReport() in /home/httpd/vhosts/ on line 3172". Since I did not know what that meant I replaced "Article.php" with the old 1.11 version (lucky me, I did the back-up before) and now things seem to be running fine again. I hope that this doesn't bring any surprises in the future. --Gollum 22:50, 22 July 2008 (UTC)

There is a more detailed description for "alternative 2" here: Manual_talk:Upgrading_to_1.9#Clarification_of_Alternative_2:_Re-run_the_installer This doesn't solve my problem but it might be helpful to others. -- 09:27, 7 August 2008 (UTC)