Project:Support desk

(Redirected from Project:Support)
Jump to: navigation, search
vde   This page is for questions relating to the MediaWiki software.

Welcome to's Support desk, the central on-wiki place to ask MediaWiki questions!

The greater purpose of this page is to make our Manual and other available help so good that you do not have to come here to ask questions, or making them easier to find.

There are other ways for of communication as well (IRC, mailing lists etc.). Read more here.

Before you post

Post a new question

  1. To help us answer your questions, please always indicate which versions you are using:
    • MediaWiki (reported by your wiki's Special:Version page)
    • PHP (likewise)
    • Database (likewise, e.g. MySQL 5.5)
  2. Please include the URL of your wiki unless you absolutely can't. It's often a lot easier for us to identify the source of the problem if we can look for ourselves.
  3. To start a new thread, click "Start a new discussion".

Archiving topics

Topics are automatically archived when they have been inactive for three weeks. If a question you have asked is approaching this limit and still has not been answered, please 'bump' it to prevent it being archived. However do not 'bump' for other reasons.

First page
First page
Previous page
Previous page
Last page
Last page

[RESOLVED] How can I delete pages?

I have made my user:

Member of: Bureaucrats and Administrators

however I still can not delete pages. I been checking all over the web, but sounds like I should have the ability to, but do not have the ability to. Can anyone tell me what I am missing?, 19 July 2014


Basically administrators should be able to delete pages. What is the URL of your wiki?, 19 July 2014

it is private and password protected and I can not allow access to it because has sensitive work info, but some of the old pages our out dated company polices and info. That is why I need to delete the pages. From my user page:

Ryan (bureaucrat, administrator) (Created on 11 December 2012 at 15:13)

Edit user groups Changing user rights of user Ryan (Talk | contribs | block) You may alter the groups this user is in: A checked box means the user is in that group. An unchecked box means the user is not in that group. A * indicates that you cannot remove the group once you have added it, or vice versa. Member of: Bureaucrats and Administrators Implicit member of: Autoconfirmed users Groups you can change

X administrator
X bureaucrat, 19 July 2014

Do I need to have the bot checked too?, 19 July 2014

Is this something I can setup when I start a fresh install? I just started another install on another site so I do not break my current one, Once I have that up I can pass along if that would help., 19 July 2014

Hello! If you are an administrator and not able to delete pages, then check the LocalSettings.php for wgGroupPermissions['sysop']['delete'] please. Is this on true or false (or doesn't exist?)?

Do you see the "delete" link or not (it's in the menu behind the "arrow")? Which MW Version you have installed?

Florianschmidtwelzow (talk)15:20, 19 July 2014

I checked the local settings and was not there. Was not Permissions listed in the file at all, and my version are as follows:

Installed software

Product Version MediaWiki 1.19.11 PHP 5.3.27 (cgi-fcgi) MySQL 5.1.39-log, 19 July 2014

Pagecontent Help

n mediawiki 1.21, i want to append some text in wikitag format at prefix and postfix of the original content(page_content), on which file and where i want to make change regarding this. Please guide me.

Mediawiki 1.21 Postgresql 9.2, 17 July 2014


unhappily i'm not really sure, what you want to do :) Do you want to add some text before and after each content page (but not on Special pages or Category pages?)? If so, you can use templates to add before and after every page, or edit the skin files, or using hooks to add the content (so you can use this one to add content after the content e.g.

Hope that helps you :)

Florianschmidtwelzow (talk)19:18, 17 July 2014

Florian's ideas are good, except the one to edit the skin files. If you are using one of the MediaWiki default skins (or a skin, which you do not maintain yourself), you should not edit its files as your changes will e.g. be overwritten after an update., 17 July 2014

Yeah, right :) Sorry, sometimes i forget, that i'm using a custom skin :) If you created itself there are much more posibillities (and more problems you have to solve too :P)

Florianschmidtwelzow (talk)07:10, 18 July 2014
Edited by another user.
Last edit: 07:09, 18 July 2014

@Florianschmidtwelzow Thanx for your response.Actually in mediawiki 1.12 what we did, we created one customized module like page_precontent and page_postcontent two column we added in page table, by using our module user can add what should print at the beginning of the content and what should print at end of the content can able to add and modify. For ex consider "Test_Page" is containing original content like "Hi This is test Page", by using our customized extension user have to enter only the title of the page then two text area user can able to see ,like precontent and post content, if user is adding some text in precontent text area like "''This this before text''" and in post content text area like "'''This is end of the content'''", if you load the page "Test_Page" it will show like

This this before text Hi This is test Page This is end of the content

In mediawiki 1.12 we customized the article.php like below in custom code you can see.,

public function outputWikiText( $text, $cache = true ) {
		global $wgParser, $wgUser, $wgOut, $wgEnableParserCache;
		$popts = $wgOut->parserOptions();
		/**************** CUSTOME CODE **************************/
                $this->mPreContent = Title::getPreContent($this->mTitle);
                $this->mPostContent= Title::getPostContent($this->mTitle);
                $text = $this->mPreContent.$text.$this->mPostContent;

In mediawiki 1.21 im not able to find where to make this change., 18 July 2014

Like said: Never change skin files, the same is for all other files provided by core, see for this: Do not hack MediaWiki core

Better is to do this with an extension, if possible.

But like i said: I really don't know, what you want to do? You want to save a pre and post content into the database for each text? Then maybe it's really better to instruct your users that they can add this content into the "normal" textfield for content of page?!

Florianschmidtwelzow (talk)07:20, 18 July 2014

@Florianschmidtwelzow it is not possible to instruct the user.already in production if i want to change more than 2000 pages i want to modify it, So i want to customize mediawiki core only, so guide me on which file i want to make change yaar, It is very difficult. Developing extension also right now it is not possible, i want to complete this task within 2 days , so please guide., 18 July 2014

Sorry for the direct answer: I think you go a totally false way. This what we discuss here is one of the reasons why it's never an alternative to hack the core: At some point you don't know, what to do (if you are not in the actual development process or are the Wiki administrator, not the developer). I will give you a possible solution for your problem next to this text, but please (really!) notice, that it will comes the point, where this solution again won't work. And in my opinion, that can't be the right approach.

So, to solve this problem (I have still the opinion that you shouldn't do this) you can change inclueds/page/Article.php (in MW1.24wmf11+) or includes/Article.php (in MW1.24wmf11 and under): Find function getContentObject() (somewhere around line 280 or 250):
Add following before
fProfileOut( __METHOD__ );
return $content;

$text = ContentHandler::getContentText( $content );
$newText = 'preContent' . $text . 'postContent';
$content = ContentHandler::makeContent( $newText, $this->getTitle() );

Like ever: use it for your own risk.

Florianschmidtwelzow (talk)20:45, 19 July 2014

Where to change the powered by MediaWiki link?

The bottom right "powered by MediaWiki" photo was changed by myself, yet when I click on it, it takes me to

Does anyone please know what file contains "" on that bottom right photo so I can change it to point to my website?

Thank you:)

Tonywiki (talk)07:06, 20 July 2014

Hello! You can use this Hook to do this. Just add this code to your LocalSettings.php:

$wgHooks['SkinGetPoweredBy'][] = 'onSkinGetPoweredBy';
function onSkinGetPoweredBy( &$text, $skin ) {
   $url = '<url-to-the-new-poweredby-image>';
   $text = '<a href="<the-link-to-your-new-poweredby-location>"><img src="' . $url
       . '" height="31" width="88" alt="Powered by MediaWiki" /></a>';
Florianschmidtwelzow (talk)13:33, 20 July 2014

Don't expect us to give you support for your wiki if it doesn't contain the MediaWiki logo :)

Ciencia Al Poder (talk)13:39, 22 July 2014

MediaWiki installation and Short URLs

I have tried everything that that anyone has told me to do. I just can't get make it so that the url just reads "". (Athena is my wiki's name). I added the proper DNS settings in my Domain Controller as well so that the Server itself can be resolved by name.

Maybe I did this all wrong from the beginning so if anyone can clarify for me if what I did was right or wrong it would be great:

When I downloaded Mediawiki, the .tar.gz file was placed in the directory /home/mhtadmin/mediawiki-1.23.1.tar.gz then I decompressed the file and it remained in the same directory but was then called "mediawiki-1.23.1" then I renamed the file to just "mediawiki" and moved it (and all of its contents) to /var/www/ because I thought that's what I was supposed to do since /var/www/ is where index.html is. The directory is now /var/www/mediawiki. I then moved the LocalSettings.php into /mediawiki where it needed to be. At this point I was able to access my wiki page but now the URL reads "http://ip-address/mediawiki/index.php or I can browse to it by typing in "" but when I log in it goes back to the IP address URL.

The directions on the mediawiki website on how to create a Short URL for Apache talk about "/w" and "/wiki" directories, I do not have these. This is frustrating me to say the least.

Can anyone help me? Please don't be vague in descriptions, be as specific and detailed as possible. I just wanna get this thing fully working :?(

Gti guy25 (talk)18:47, 11 July 2014

Your steps are not entirely clear to me. (I hope you moved LocalSettings.php into /var/www/mediawiki instead of just /mediawiki and that you forgot to provide a full path only? I'm not sure whic file you renamed to "mediawiki" and hope that you meant a folder instead?) Which "directions on the mediawiki website" do you refer to? Clear links welcome.

In any case: Did you already make some edits to Apache's httpd.conf file?

AKlapper (WMF) (talk)20:52, 12 July 2014

Can somebody please put this back with Thread:Project:Support desk/MediaWiki installation and Short URLs, which it was apparently a reply to? I looked all over but couldn't find out how to undo the thread splitting by what is apparently a vandal (or spammer -- he retitled this thread with a website he seems to be promoting).

Edit: Never mind -- got it fixed. Should have been obvious to begin with. 23:08, 12 July 2014 (UTC)

Cathfolant (talk)22:05, 12 July 2014


I renamed mediawiki.1.23.1 (which is the folder name after downloading the tar.gz from mediawiki website) to "mediawiki", and yes I moved localsettings.php to the proper folder, my mistake I was typing while frustrated. But I moved my "Mediawiki" folder to /etc/. It does not matter where you place it, as long as you change where Apache points to. Having said that, the httpd.conf file exists but is a completely blank file. Apache.conf is the file I have been told is what needs editing. So to answer your question, no I have not made any edits to httpd.conf because the directions and everything else I have read specifically state that httpd.conf is no longer used with Apache.

Gti guy25 (talk)13:54, 21 July 2014

To prevent your wiki from redirecting to the IP URL instead of staying on the domain URL, update Manual:$wgServer so it points to the domain and not the IP.

After that, just follow the instructions about Manual:Short URL. Be sure to plan your URL scheme before trying to follow those instructions.

If you want your "edit" urls be on /w/index.php, you should rename your directory to w instead of mediawiki. That's the directory that needs to exists. the /wiki/PAGENAME directory for short urls shouldn't exist, because it will be a "virtual" one, which would be rewritten internally to point to the first one with rewrite rules.

Ciencia Al Poder (talk)13:34, 22 July 2014

Upgrade Trouble - no content gets loaded anymore


I have a serious issue with my mediawiki installation. I am using Mediawiki as supported by my hoster "Strato". It worked very well. Then it did an update to 1.19.1-2 - and I have got serious problems. I can log in into my wiki - but nearly no page gets loaded. This looks like this: The only pages that get displayed somewhat correct are the special pages. Even the profile is messed up, as there are many field missing and such. The Sourcecode of the page I posted the screenshot of can be found at:

I do have access to the sql database - but it seems that I can't export the sql, as i only do get empty files / folders.

I can nevertheless navigate to a page in my wiki, push the "edit" button - and inside the edit window I do see every information that should be there.

Has anyone an idea how I can rescue my wiki?


Christian, 20 July 2014


This is a rather common upgrade issue. Usually it is a missing PHP extension, iIrc. However, right now I do not remember, which module it was exactly. Maybe the updater at mw-config/index.php shows more information on the missing module., 20 July 2014
Edited by another user.
Last edit: 21:41, 21 July 2014

My Index.php in MC-Config sais the following:

--- (PHP source code of the file) ---

What am I therefore missing?, 20 July 2014

I mean when you execute this file with your webbrowser, enter this update-string it asks for and then... ;-), 20 July 2014

When I open this adress I get at first the language selection. Then I get:

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log., 21 July 2014

Why is this software so complicated?

Looking at open-source wikis, MediaWiki seems to be the best however, extremely confusing when diving into the back-end of it. I don't understand why they want to use complicated variable names and extremely confusing settings that require hard edits to a config file. Why can't there be one administrators panel that contains everything you need without needing FTP to access the wiki files to manage simple things?

Now the template engine, it's crazy. It's way easier to learn HTML than it is to form a table using their confusing engine. I see many bad practices when diving into the back-end and I'm wondering, why? Why does such a popular wiki software have just bad engines? I'm not going to lie, it's a powerful software however it can be written so much better to make it friendly to other developers., 21 July 2014

As for the file system access: Sure, config settings could also be done via a web interface. For MediaWiki that already partly is the case with the pages inside the MediaWiki namespace, where you can e.g. define CSS, which then is used for all users. However, usage of the file system amongst other things is an important barrier of additional security: The credentials of one of your admins might get lost and then attackers can manipulate e.g. these pages inside the MediaWiki namespace. However, what they cannot do is e.g. delete your complete database, because in order to gain access to the DB they would have to know the DB credentials, which only are available with direct file system access. And - another security-relevant aspect: You can have a hugh amount of wiki admins, but there should only be a very limited number of people with actual access on the file system level, which strengthens security even more.

As for the complexity of MediaWiki as a tool for the internet just have a look at other tools: MediaWiki is one of the bigger and more powerful wiki engines, no question. However, compared with other tools it is just like baby software: It does not offer full CMS options, workspaces, versioning, sophisticated user access levels, timed display of content, content rotation and so on, just to name a few.

However, I want to invite you: When you know how MediaWiki can be improved - made more simple, using better practises in the backend, then participate in its programming: Get Developer access and contribute your patches! Welcome aboard!, 21 July 2014

You're right, MediaWiki is complicated to use. The quality of the help guides is inconsistent, editing config files directly rather than using a GUI is counter-intuitive, extending MediaWiki is a pain, and Wiki-markup drives away potential editors in droves.

However, there are some very good extensions, the most comprehensive being Bluespice. It has a comprehensive feature list (including a very good WYSIWYG editor) and since I installed it on my work wiki, editor retention is much higher.

Qiubov (talk)12:51, 22 July 2014

As I said: Baby software. If you want to know, what is really complex, have a look beyond your own nose. E.g. have a look at TYPO3. After a few months, when I successfully work with MediaWiki since a really long time already, we can then speak back and see, how far you made it., 22 July 2014

Points of discussion before going on-line

Dear Sir,

I installed and configured MediaWiki.

Before going on-line I like to discuss next points.

I am creating New York Wiki for New York City organisations.

Sysop, users and guests are the groups.

The MainPage is blocked.

From DefaultSettings.php I copied line 4141 (@ name user rights) to line 4811 (end of user rights settings)

Permission ['*'] all True Permission ['user'] all True Permission ['bot'] all False Permission ['sysop'] all True Permission ['bureaucrat'] all True

Do you have any comment on this?

Thank you in advance.


Hansie (talk)17:52, 29 June 2014
Edited by 2 users.
Last edit: 21:57, 29 June 2014

If you do not configure group permissions yourself, the default from DefaultSettings.php will be applied automatically - you do not have to copy it. Apart from that, information on how to configure user groups properly are available on page Manual:$wgGroupPermissions.

You will e.g. find that the permissions of multiple groups are cumulative: If a user is member of different groups, then the user will get a right if it is granted to at least one of these groups - even if it is not granted to his other groups. That means you do not have to grant all available rights (like the "block" or the "delete" right) to all users - in fact I think that you might not want to give ordinary users special rights like these.

Only grant special rights to the special groups., 29 June 2014

Thank you for your response.

Which rights should I give ordinary users?


Hansie (talk)06:55, 22 July 2014

Supplementary question:

Which rights should I give to "*"?

Hansie (talk)09:38, 22 July 2014

The group "*" is automatically given to all users. Users, who are not logged in, are in this group (and in this group only). The group "user" is automatically assigned to all users, who are logged in. Since user group permissions are cumulative, these users will then have all permissions of group "*" and additionally those, which are assigned to group "user".

Manual:User_rights#List_of_permissions is a list of all possible rights, which a user group can have. Which of them you want to give to e.g. the group "user", depends on what ordinary users should be able to do. See Manual:$wgGroupPermissions for details on how to assign permissions.

Which rights which group currently has can be seen in your wiki on the page Special:ListGroupRights. The rights, which are assigned by default (meaning without you assigning anything special yourself), already are more or less fine for most wikis.

As an example, if your wiki is publicly accessible and you then assign the group "*" the right to edit pages and to upload files, this will be a guarantee that you get spam en masse: In form of spammy pages and in form of trash uploads. You should better not do that. ;-), 22 July 2014

Please do not edit DefaultSettings.php. This configuration file includes, like the name say, default settings, so, if you update your MediaWiki version, this file will be override normally (and your changes are away). To define user rights and/or user groups, please use the LocalSettings.php and $wgGroupPermissions, like explained. Additionally, you can use Manual:$wgRevokePermissions to revoke a permission for a special group (also, if this right is given by another group the user is a member of).

Florianschmidtwelzow (talk)06:16, 30 June 2014

Hello Florian,

What do you mean by ""? It's a German IP address!

Thank you,


Hansie (talk)06:58, 22 July 2014

I mean the user :) The IP adress has no user account, so his ip address is shown as username (that's the only possibility for me to refer to) :) I mean this post:

Florianschmidtwelzow (talk)07:41, 22 July 2014

Cannot go forward when try to Edit ?

The website is Current Mediawiki version is 1.16.0 Php/5.4.28

Whenever we try to edit the help content the following message comes up and there is no apparent way to edit the help files on the websites wiki help. What is the problem with it? and you please provide the solution.

Omer Farooq

Ofarooq (talk)07:23, 20 July 2014

Hello! Can you provide the Error message please? Can you give a link to the page you want to edit?

Please notice, too: MediaWiki 1.16 isn't supported anymore. Please think about to upgrade your Installation.

Florianschmidtwelzow (talk)13:29, 20 July 2014


This message show up every time we hit Edit to do editing on every page

Please note that all contributions to TrueERP wiki are considered to be released under the GNU Free Documentation License 1.2 (see TrueERP wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here. You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

There are different pages; try this one:

Awaiting.. Thanks, 21 July 2014


This message show up every time we hit Edit to do editing on every page

Please note that all contributions to TrueERP wiki are considered to be released under the GNU Free Documentation License 1.2 (see TrueERP wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here. You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

There are different pages; try this one:

Awaiting.. Thanks

Ofarooq (talk)05:31, 22 July 2014

Why is this software so complicated?

16:14, 21 July 2014

That depends on an individual point of view, i think :) In my view MediaWiki isn't complicated all over (yure, there are some points, which are complicated but the most aren't). If you say us, what exactly you feel as complicated, we can help you :)

Florianschmidtwelzow (talk)17:19, 21 July 2014

mediawiki URL

Currently my mediawiki url reads as follows: http://192.168.x.x/mediawiki/index.php/Main_Page

I want it to read http://wiki-name.domain-name.local/index.php/Main_Page. https:// would be nice as well.

I am using Apache2 but the mediawiki directions are too confusing for me to understand. Can anyone help me with this?

MediaWiki ver. 1.23.1

The directory of my mediawiki is /var/www/. I do not know what to edit to change the URL.

Please help, thank you!

Gti guy25 (talk)18:04, 10 July 2014

The URL to your wiki must be set in LocalSettings.php (just like e.g. $wgLogo, which is also set in that file) and you can change it by setting $wgServer to another value. This will then make MediaWiki output URLs starting with the domain you want. Take care however, that Apache also needs to be configured accordingly so that it maps that domain to the webroot directory. (Don't ask me how that is done - I have no clue.), 10 July 2014

And the Apache part is where I get stuck because I do not see where you need to edit the Apache config. I will play around some more and see if I get it. The wiki I'm working on is only a test. Thank you though.

Gti guy25 (talk)19:20, 10 July 2014

You can edit the documenroot in the virtualhost configuration, most in /etc/apache2/sites-available. You can add the ServerName, too, to make an alias to wiki-name.domain-name.local. Be sure, that wiki-name.domain-name.local in your local DNS Server points to 192.168.x.x (the IP adress where apache is running). Https you get, when you use ssl in apache2 (and enable it for your host). Notice, that you can use a self signed certificate, when you use the wiki only locally (which i think, because you want to use a local domain), but you must add the certificate as a trusted (or add an exception in your clients, that they won't check this certificate). If you want to use the wiki on a wider range outside of your local network you can manage, then maybe it's better to use a certificate of a trusted CA (they take money ;)).

Florianschmidtwelzow (talk)19:37, 10 July 2014
Edited by another user.
Last edit: 09:37, 11 July 2014

Florianschmidtwelzow: when you say I can edit the document root in the virtualhost configuration, is it the <VirtualHost *:80> OR do I add what I need under <VirtualHost> at the bottom of the "default" file inside sites-available? And by my "local DNS Server" you mean to add wiki-name.domain-name.local or the IP Address to the DNS settings in Active Directory or something like that, correct? Sorry to be such a newbie, this is a project that was assigned to me at work and I am not a programmer nor do I know anything about Linux stuff.

Maybe this will help you more, this is exactly what I see when I am in /etc/apache2/sites-available/default:

<VirtualHost *:80>
        ServerAdmin webmaster@localhost
        DocumentRoot /var/www
        <Directory />
                Options FollowSymLinks
                AllowOverride None
        <Directory /var/www/>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride None
                Order allow,deny
                allow from all

I know that I need to change one of these AllowOverrides None to AllowOverride All but not sure which

Maybe you can show me what it should look like when it's done?

Anything would be a great help. In the meantime, I will add the appropriate DNS entry.

Gti guy25 (talk)20:25, 10 July 2014

Florianschmidtwelzow: I just added the DNS record, and was able to ping my wiki server by name. Then I opened up IE and browsed to wiki-name.domain-name.local/mediawiki/index.php and it brought me right to my wiki page. Now, my question is how can I get it to just say: wiki-name.domain-name.local/index.php/Main_Page? Do I still need to edit the default file? If so please proceed to respond to my last post, if not please let me know how if you can. Thank you.

Gti guy25 (talk)20:40, 10 July 2014

Hello! You have to edit the file, where you entered the host configuration :) If this is the file you posted in your post, then change DocumentRoot /var/www to DocumentRoot /var/www/mediawiki and <Directory /var/www/> to <Directory /var/www/mediawiki/>. Restart/reload the server settings and navigate to your wiki. In order to use (maybe you want) short URL you can change AllowOverride in the directory section(<Directory /var/www/>) to All, or add the rewrite rules directly in the host configuration and leave allowoverrides to none.

Florianschmidtwelzow (talk)05:49, 11 July 2014

Searching in Documents

Hey, is it possible to search through the content of Uploaded Documents ? I didnt find any extensions and the inbuilt Search feature just looks at tht names of the documents, 21 July 2014

What file formats are "Uploaded Documents"?

AKlapper (WMF) (talk)12:43, 21 July 2014

Sorry i forgot. Im talking about mostly PDF files., 21 July 2014

Weird Navigation items in Sidebar

So trying as best I can to get the 1.23 Monobook skin up to the functionality that we had previously...

And seemingly out of nowhere, some strange stuff appeared at the top of our navigation bar, here: -- I've no idea where that random S or its lavel p-.3c-label came from.

It did appear after I attempted to use the PCR GUI Insert extension to try and place an ad unit in that sidebar, but even after removing it, and even removing the extension, the problem persists. I've looked in SkinTemplate.php and my base skin to see if a stray typo somewhere has caused this, but I'm running empty. Any thoughts as to how I might discover the culprit?

Balerion300 (talk)18:41, 20 July 2014

I don't see a random S or p-.3c-label on that page or in its source code. Any screenshot? Or does one need to be logged in for that and use a different skin?

AKlapper (WMF) (talk)00:00, 21 July 2014

I saw it yesterday, but I didn't have a solution. However, as André says: It is no longer there now., 21 July 2014

Upgrading from 1.17 to 1.23.1


Finally took the plunge to try and get this done. I backed up our database, our backed up the file directory, I copied LocalSettings.php and our logo image -- the only really unique things we have, as we haven't modified skins such as Vector -- and untarred the file...

And now, nothing. php update.php just gives a blank response -- no countdowns, no error messages, no nothing. Trying --schema tells me that it needs a variable of some sort, even though the file says nothing about it. Right now my site -- -- is just giving a blank, and I can't see any error messages to explain what's wrong.

Will continue digging through topics and guides to try and figure out what's going on, but if someone has some experience with problems from 1.17 -> 1.23.1, would appreciate some help.

ETA: May be worth noting that mw-config/ web update script also dies once I go through the language step. PHP version is 5.3.3.

Balerion300 (talk)12:41, 20 July 2014


I guess you have not only untarred the tarball somewhere, but you have also actually overwritten the old files, right? :-)

A blank page points to a PHP error. Follow the steps described on blank page to get the actual error message!, 20 July 2014

Thank you. I had gone through it, and couldn't find the problem that way... but looked at it again, tweaked how I was handling error reporting, and that let me get further. So now I've managed it. Thanks!

Balerion300 (talk)16:06, 20 July 2014

What have you done? What was the error and how could you fix it?, 20 July 2014

Oh, there were an array of error messages once I figured out how to get error reporting sorted properly.

Most had to do with various extensions that were out of date (dutifully turned them off one by one), and some tweaks I needed to the auth plugin I was using (IPBWiki's bridge with the Invision Power Board forum software) that weren't too hard to figure out. Once I did that... well, my old Monobook-based theme didn't work, either, so I got rid of it and started fresh with a new copy of the latest Monobook. That, however, is presenting significant new problems for me (I've posted about inserting advertising in a different topic).

Balerion300 (talk)16:58, 20 July 2014

Ads in 1.23 Monobook noveau

So now I've successfully upgraded to 1.23, but discovered that the Monobook skin has been radically changed in its design. Previously it was easy to insert ads into the skin, but now I'm at a loss for how to do so.

The specific places I'd like ads are a banner (728 x 90) at the top, a skyscraper in the sidebar (160x600), and a banner at the bottom (728x90).

I've looked around and there don't seem to be any good solutions that allow that level of control, so I have to assume I'm supposed to just go ahead and figure out how to place it in the skin... but yeah, it's not easy. For example, there's an array that creates the navigation sidebar, and I'm uncertain how I'd introduce an additional element that would contain an ad unit (and other stuff -- in the past we also had some selected links from included php files).

Balerion300 (talk)16:09, 20 July 2014

Problem Upgrading PHP


I'm a Debian-beginner. I have a running debian server with mediawiki 1.11 and php 5.2. Now i'd like to upgrade to MediaWiki 1.23, so i started with upgrading php to 5.4 I did this simly with apt-get install php5

But when I try to upgrade the wiki now on the browser, it still stands "MediaWiki 1.23 requires at least PHP version 5.3.2, you are using PHP 5.2.17." When I ask php -v I get 5.4 as answer, but if I look at my Wikis Version-Page, there is still 5.2.17

What can I do? What is the problem?

Thanks for your help!


Amstuzmarco (talk)11:22, 11 July 2014


Accessing your webserver with a browser and with a shell are two different things. When you access your webserver with a browser, you can see one PHP version, while on the shell you see another one.

In your case the command "php" executes PHP 5.4, which is fine. However, you also must make sure that the webserver runs that version as well, when asked to deliver a page for a webbrowser. (No, I don't know what to change, but I guess that you have to reference the correct = the new PHP version somewhere in the Apache configuration. Maybe you only have not restarted the server and it already would work correctly, if you did?), 11 July 2014

Thanks for your answer. I have restarted the server already, yes. But it didn't help. But i see your point, it makes sense. Does anybody know what I have to change?

Amstuzmarco (talk)12:10, 11 July 2014

You probably need to apt-get install libapache2-mod-php5.

Ciencia Al Poder (talk)16:58, 11 July 2014

Didnt worked, I still get the same error. But thanks!! Any other Ideas?, 13 July 2014

You may need to uninstall the previous PHP version. Or look how to set which PHP version to use with your webserver. For example: [1]

Ciencia Al Poder (talk)11:01, 20 July 2014

Error: 1146 Table 'pjk_uawiki.user' doesn't exist (localhost)

My host did something to the db and are unable to restore a backup or fix it, so I need to try fixing it myself. I had a massive spam attack, and mostly cleared it up, but seems there is an issue with the db now. See this link:

MediaWiki (reported by your wiki's Special:Version page): can't check, but version that was out about 8 months ago. PHP (likewise): 5.3.26 Database (likewise, e.g. MySQL 5.5): MySQL 5.1.73-cll

Any ideas how to fix this? The only support I have so far is: "It seems like the user table missing is the only error being reported at this time and you may be able to fix this by re-installing a blank user table.

If you pull the "create table" sections from the database install script for this site and run them it may get it functioning again."

But I'm unsure how to actually do this. Any help would be greatly appreciated.

I've tried to run the upgrade process but get this error when upgrading the db: "Turning off Content Handler DB fields for this part of upgrade. ...have ipb_id field in ipblocks table. ...have ipb_expiry field in ipblocks table. ...already have interwiki table ...indexes seem up to 20031107 standards. ...hitcounter table already exists. ...have rc_type field in recentchanges table. ...user table does not exist, skipping new field patch. ...querycache table already exists. ...objectcache table already exists. ...categorylinks table already exists. ...have pagelinks; skipping old links table updates ...il_from OK ...have rc_ip field in recentchanges table. ...index PRIMARY already set on image table. ...have rc_id field in recentchanges table. ...have rc_patrolled field in recentchanges table. ...logging table already exists. ...user table does not exist, skipping new field patch. ...watchlist table does not exist, skipping new field patch.

An error occurred: A database query syntax error has occurred. The last attempted database query was: "SELECT count(*) FROM `watchlist` WHERE wl_namespace & 1 LIMIT 1 " from within function "MysqlUpdater::doWatchlistUpdate". Database returned error "1146: Table 'pjk_uawiki.watchlist' doesn't exist (localhost)" Backtrace:

  1. 0 /home/pjk/public_html/underasia/wiki/includes/db/Database.php(983): DatabaseBase->reportQueryError('Table 'pjk_uawi...', 1146, 'SELECT count(*...', 'MysqlUpdater::d...', false)
  2. 1 /home/pjk/public_html/underasia/wiki/includes/db/Database.php(1434): DatabaseBase->query('SELECT count(*...', 'MysqlUpdater::d...')
  3. 2 /home/pjk/public_html/underasia/wiki/includes/db/Database.php(1148): DatabaseBase->select('watchlist', 'count(*)', 'wl_namespace & ...', 'MysqlUpdater::d...', Array)
  4. 3 /home/pjk/public_html/underasia/wiki/includes/installer/MysqlUpdater.php(346): DatabaseBase->selectField('watchlist', 'count(*)', 'wl_namespace & ...', 'MysqlUpdater::d...')
  5. 4 [internal function]: MysqlUpdater->doWatchlistUpdate()
  6. 5 /home/pjk/public_html/underasia/wiki/includes/installer/DatabaseUpdater.php(435): call_user_func_array(Array, Array)
  7. 6 /home/pjk/public_html/underasia/wiki/includes/installer/DatabaseUpdater.php(387): DatabaseUpdater->runUpdates(Array, false)
  8. 7 /home/pjk/public_html/underasia/wiki/includes/installer/DatabaseInstaller.php(274): DatabaseUpdater->doUpdates()
  9. 8 /home/pjk/public_html/underasia/wiki/includes/installer/WebInstallerPage.php(552): DatabaseInstaller->doUpgrade()
  10. 9 /home/pjk/public_html/underasia/wiki/includes/installer/WebInstaller.php(270): WebInstaller_Upgrade->execute()
  11. 10 /home/pjk/public_html/underasia/wiki/mw-config/index.php(65): WebInstaller->execute(Array)
  12. 11 /home/pjk/public_html/underasia/wiki/mw-config/index.php(33): wfInstallerMain()
  13. 12 {main}

Purging caches...done."

Thanks., 19 July 2014

Your database currently misses at least the tables "user" and "user_newtalk". From browsing a few pages in your wiki I got the error messages that also the tables "valid_tag" and "watchlist" are missing - and almost certainly other tables as well. The table structure of these tables must be restored to give MediaWiki at least a chance to work properly again. However, you will also need the table contents: E.g. the user table contains information on your wiki's user accounts - the wiki cannot work without it. Without the stuff from the watchlist table your wiki might still work, but the information on which user watched which pages would then be lost.

To get your wiki working again, you will at least have to restore the user table - and those other tables, which are missing as well. See DB for an overview of the tables which you should have. If you want to get the wiki working again, it is absolutely essential that you get this information back.

From what you describe, I consider the current state to be broken beyond repair. I would not try to somehow fix the broken state, which you have now (e.g. by manually recreating the structure of missing tables or so). Instead, I would go back to the newest backup. That will be far easier., 19 July 2014

[RESOLVED] Upgrade gerrit to 2.9

Edited by another user.
Last edit: 15:23, 19 July 2014

hi could we update gerrit to 2.9 reason because it includes a new design by default now and also includes a new side by side diff please see this for a full set of changes., 19 July 2014

it also fixes. Fix truncated long lines in new side-by-side diff screen., 19 July 2014

This basically is the same as the Gitblit question, which you brought up a few times in the past already. See Thread:Project:Support_desk/Update_gitblit_on_wikimedia_git and especially Thread:Project:Support_desk/update_git_site#update_git_site_43416 for the answer. Apart from that the question is not related to the function of the MediaWiki software itself and so is displaced here., 19 July 2014

Yes and also the person on that thread told me to give a reason if I ask for an upgrade which I did give a reason it fixes issues and also brings a new design by default., 19 July 2014

Honestly: Who cares? It will be updated when it's updated - and if you post a hundred threads here: It won't change a thing. And all that still does not change anything regarding the fact that the question is not related to the function of MediaWiki and so is displaced here.

You can search other channels like places where wikimedia tech people are around and ask there, but that will most likely have exactly the same impact which this question here has: Absolutely none. That might be different, if you could actually help doing the upgrade - can you?, 19 July 2014

I'm not sure, if you are the guy who opened the bug bug 68271, but if you are, i'm wondering why. The first question after your "it fixes issues" is, are this issues related to the use cases of Wikimedia? We will see, what happens on bugzilla, so i hope, that we don't need to observe this thread AND bugzilla, it's double work, and this is really bad ;)

Florianschmidtwelzow (talk)15:25, 19 July 2014

NewSignupPage: No message appearing

There is an unsolved issue in extension NewSignupPage:
If the user doesn't check the terms checkbox there is no message appearing.
(I have set up a message at Mediawiki:shoutwiki-must-accept-tos)

This happens since the update to MW 1.19.7 - see this thread here.
Just tested it with MW 1.23.1 and there is still no massage appearing...

Should I file a bug or can anyone help here directly?


Stefahn (talk)13:46, 19 July 2014

[RESOLVED for Git] Wiki revisions history --> SVN/Git/Hg repository?

Is it possible to export MediaWiki history into Subversion (Git, Hg, whatever) so later all newer MediaWiki-based wiki revisions could be updated (pulled) into that copy? I would expect that copy to be read-only without committing and pushing back to the wiki, that does not really matter. But is it possible? Thanks!, 25 June 2014

You mean the MediaWiki files, yes? Then yes, you can clone MW from git:

and pull the newest files again, if changed. BUT: This is the master, which isn't for production use, so i would say, that's better to download the latest stable snapshoot of MediaWiki. It's possible to checkout REL branches, but what you do when the branch changes (maybe from REL1_23 to REL1_24)?

Another possible solution is to checkout the branch to a temporary location (e.g. /var/wiki/template) and copy the files to your production (e.g. /var/www/wiki) after a new version.

Florianschmidtwelzow (talk)05:31, 26 June 2014

Thanks for the answer, but sorry I seem to have asked a confusing question. Let me try to explain the subject better. I would like to checkout not the source code of MediaWiki, but the "source" of a wiki content.

For example, if my local wiki has two articles, let's say Foo and Bar, and just two edits at these two, then something like the following steps would be great (I prefer Mercurial, but the idea would be clear for SVN and Git):

  • hg clone %MY_LOCAL_WIKI_CONTENT_URL% - to make a local dump of the wiki
  • hg up 1 - to update to the very first edit in the wiki, so my local dump working copy snapshot at this revision could have just file, let's say, articles/Foo
  • hg up 2 - to update the working copy so a newer edit could appear at the working copy, articles/Bar
  • ... some time passes ... and then hg pull / hg up to sync with the latest wiki changes

So, it's more about the wiki content dump to be able to navigate through revisions and particular content snapshots (it may be one of possible usages), not the wiki engine source code., 26 June 2014

Ok, then my first thought was right :D But: MediaWiki saves the articles and revisions not in files, the content is saved in a database, e.g. MySQL. So you need to export the database first. Alternative you can export the articles as XML and import them (with revisions if selected) in a new wiki (see Special:Export and Special:Import or using commandline). For further information to that, see:

With git/svn or something else it would be simply impossible i think :)

Florianschmidtwelzow (talk)07:38, 26 June 2014

Thanks! That matches what I want much closer. I've just played with the export feature and it looks very similar, yes, but very limited and not that configurable. However, it looks like the incremental changes could be exported only by writing a custom PHP script (MediaWiki stores revision diffs only, right?). If I could write such an extension, I guess I would write an SVN storage driver (or whatever it's called) so it could emulate a storage file system just querying the MediaWiki database, I think or something like that. Thank you again!, 26 June 2014

MediaWiki stores the entire revision of a page in the revision table.

Still, I've seen git frontends for MediaWiki before so I went looking. I came across Leviation which isn't the thing I remember, but maybe it will help you.

MarkAHershberger(talk)13:14, 26 June 2014

I managed to do exactly what I want. To be honest, I thought that mirroring a wiki into a Git repository is the most advanced thing I could ever want for such a scenario, but this following method even allows to push wiki changes back to the wiki. It's all built around a Git built-in concept of remote helpers that can be treated as a sort of bridges between heterogenous systems. Nevertheless, I don't know how to fetch talk pages and categories, but I hope it won't be an issue in the future. So I came across this page and noticed a very similar thing. Here is the manual describing this remote helper also saying that it's a Git built-in. True, this extension is a part of the Git source code repository at Github. Since I couldn't manage to make it work under Cygwin, I had to install a virtual machine with Linux Mint (just a tiny personal preference) where all of necessary operations might be easier. And yes, this here are the commands that work for me:

$ sudo apt-get install libmediawiki-api-perl
$ sudo apt-get install libdatetime-format-iso8601-perl
$ sudo apt-get install git
$ sudo apt-get install git-mediawiki
$ git clone mediawiki::http://localhost:8080/wiki
$ cd wiki

The current known to me, after a short test, issues are:

  1. I have no idea how to fetch categories and the talk pages (didn't check templates, though)
  2. If you just commit, your local changes are signed with your Git identity information, but once you push back to the wiki, the changes are recorded by anonymous user. This seems to work well if you configure the MediaWiki remote helper.
  3. Didn't check what happens if you push changes to protected pages.
  4. Files seem to be not cloned/pulled as well, unfortunately.

I hope to find how to deal with those issues, but I'm not sure :), 18 July 2014

Convert Dokuwiki Tables

I am converting an old Dokuwiki into a new Mediawiki and i am wonderin about how to convert the tables into the wiki without modifying the code by hand. I hope this explains my problem., 17 July 2014

I have not tried this myself. However, the work needed to convert a DokuWiki into a MediaWiki installation will depend on how similar both are (table structure inside the DB, syntax of the wiki text itself) and on, if someone already did that before (and you can more or less re-use, the code he wrote).

In this case it seems like there already is some kind of converter:

Maybe it does not work right out of the box, but it might give you an idea, of what might be needed., 17 July 2014

Hi that link is for converting Mediawiki to dokuwiki not the other way around., 18 July 2014

Eh, yeah, I obviously mixed that up. Sorry!, 18 July 2014
First page
First page
Previous page
Previous page
Last page
Last page