Project:Support desk

Jump to navigation Jump to search

About this board

Welcome to's Support desk, where you can ask MediaWiki questions!

There are also other places where to ask :

Before you post

Post a new question

  1. To help us answer your questions, please always indicate which versions you are using (reported by your wiki's Special:Version page):
    • MediaWiki
    • PHP
    • Database
  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 topic".
Previous page history was archived for backup purposes at Project:Support_desk/old on 2015-07-30.
Other languages: English  العربية čeština Esperanto français 日本語 中文

How to block all logs whatsoever to non Administrators?

1 (talkcontribs)

I have a personal; non communal (at least at this point); MediaWiki 1.34.0 based, content website in which I publish technical services I offer. As a general rule, this site is not edited communally and I am its only registered user and hence its only administrator/sysop (someday I might appoint an helper or open it for communal edit but for now I don't have such a plan and anyway not prepared for that).

From various reasons, I want deleted (or moved) pages to not appear to anyone besides myself, and if they do, well, only in logs.

The following LocalSettings.php command helped me with deleted pages but not with moved pages:

$wgLogRestrictions['delete'] = 'deletedtext';

Because I know there are many logs (more than just "deleted pages" and "moved pages") and that by principle. new logs can always be added without me knowing it as a user of automatic upgrades, I contemplate to just block all logs whatsoever to non sysops and be done with it; assuming this is a good solution, I ask:

How to block all logs whatsoever to non Administrators?

This command didn't help me: $wgLogRestrictions["*"] = 'deletedtext';

Reply to "How to block all logs whatsoever to non Administrators?"

Unique background image on a category basis?

Krayfishkarl (talkcontribs)

So my wiki used to have the option of displaying unique background images and CSS stylings but I've recently had to look for new methods of implementing it after a MediaWiki update disabled the method I was using before (which was HTML tags). Recently, we got something very basic working that just the changes the background color for certain groups of pages, but the background-image tag does not appear to load correctly. As a matter of fact, it actually disables all other elements. We devised a workaround of just overlaying an image to act as a fake background, but I'm hoping to find a more elegant solution.

tl;dr I'd like some assistance in trying to figure out how to get the background-image option to work on multiple pages.

Long version:

MediaWiki: 1.33.1

PHP: 7.3.14 (litespeed)

MySQL: 5.6.44-cll-lve

ICU: 63.1

Lua: 5.1.5

The goal is to have it so that pages based on categories (determined by a template on each page that automatically adds a category) change background images and CSS stylings on a per page basis.

Here is a link to my wiki:

On the sidebar are "settings" themed after different genres. Depending on what "setting" a page is part of, the background image and link colors change.

Here are some examples of differently colored pages:

The respective templates that control these pages' appearances can be found here:

And lastly, here's an experimental page that attempts to use the template's code on its own CSS page. There's only one of these so far:

Things I've looked in to:

While searching for help, I came across this on the Extension:CSS page:

"Using the parser function to use the CSS from another page does not work to change the color or background of the page, however, using the parser function on a single page by itself does allow the background to be changed. To overcome this problem, it is possible to load the CSS through transclusion, which does not cause the problem of failing to load the change to the page background."

However, I'm not sure I follow what exactly this means.


In the Template Styles Extension, there's a parameter called $wgTemplateStylesAllowedUrls. A default is given as follows:

    "audio" => [



    "image" => [



    "svg" => [



    "font" => [],

    "namespace" => [



    "css" => []


However, replacing the URLs with that of my own site had no noticeable effect and the background-image option still wasn't working. The result was the following error:

'Page MediaWiki:GC.css must have content model "Sanitized CSS" for TemplateStyles (current model is "CSS").'

This occurs on this particular edit revision of the Galactic Crucibles template:

I'm not 100% sure if my syntax is correct so a possible example would be appreciated.

Also, please let me know if there's anything I need to clarify or if you have further questions about what we're trying to do here.

Reply to "Unique background image on a category basis?"
2604:6000:120A:7A0:C4D8:7D7B:FAA3:B6A1 (talkcontribs)

I am not a member how do I listen to the memorial

Malyacko (talkcontribs)

Welcome to the MediaWiki software support desk. Nobody knows what "memorial" this is about. Please provide sufficient context.

Reply to "memorial service"
Davecotter (talkcontribs)

Monobook had a header background image. i'd like to have one (for all pages) now that i'm using Vector. i saw this article which hinted at this, but it neglected to specify exactly how to create this. It mentions "Vector.css" but doesn't say where that file is, or where to create it or how to hook it into the system. Any hints here would be appreciated.

Malyacko (talkcontribs)
Davecotter (talkcontribs)

thanks for that but, as a beginner, finding the info i need is difficult because there's a mountain of information and i don't know HOW to find it. as an experienced user i can understand that you would be frustrated with a beginner, preferring to say "read the f*** manual", but if you remember what it's like to BE a beginner, i can assure you i looked at the manual, and only became confused.

specifically: must i edit a stock file and add something that causes it to include MY css file? if so, what file, and where, and how? that is all. i looked at the page you sent me to and found nothing that seemed to me to indicate the answer to that question. is "Vector.css" an existing file? if so, where is it? if not, where do i create it? and then how do i cause it to be loaded?

Reply to "add a header to Vector"

Class 'Wikimedia\CSS\Parser\Parser' not found

Wertwijn (talkcontribs)

I get this error when trying to import the Infobox template: Class 'Wikimedia\CSS\Parser\Parser' not found

The MediaWiki instruction I found is this: "The error may come up on attempting to save a Wiki CSS page or on changing pages to "Sanitized CSS" content model. This may be caused due to some bugs which require composer install --no-dev to be run even when the extension is not installed from git".

I have NO idea how to run this "composer install --no-dev". I cannot find any instructions on mediawiki that I can understand.

I run my Mediawiki here: The package is provided through my hosting provider. These are my installation details:

Product Versie
MediaWiki 1.34.1
PHP 7.3.15 (litespeed)
MariaDB 10.1.44-MariaDB-cll-lve
ICU 63.1
Lua 5.1.5

I use Dreamweaver to upload extensions. Other than that, I have no idea how to 'run commands'.

Please help me, I cannot import templates!

Malyacko (talkcontribs)
Wertwijn (talkcontribs)

Yes, these topics describe the problem.

I have no problem with installing the MediaWiki extensions. The Parser-extension is also there.

My problem is that I do not understand the instruction given in these topics Topic:Uvxu6mr38dlvbcdh, Topic:Ukv6pdo96a8qfur2, Topic:Uwmi9j36mttx5730. They also say to run something called "composer install --no-dev". I have no idea what this means or what to do. I can upload files to my Mediawiki installation, but I have no idea how to "run" a command on that installation.

Reply to "Class 'Wikimedia\CSS\Parser\Parser' not found"
BensDBN (talkcontribs)


I have a MediaWiki that is set to private and I want a specific user account to be able to programatically signed in and when I browse to the wiki that its automatically signed in.

I followed this post: API:Login but it doesnt tell you what to do after you have logged in and I'm hoping to get some help regarding saving your login to a cookie.

I get a readapidenied error when I try to do a GET token request, I switched to the depricated way of doing it via POST but at least im able to get a token. I now do a login post and I get a return (I'm not sure if this is successful as it shows a different token with a status of "Needs Token".

Any help or links to documentation would be greatly appreciated.

Ciencia Al Poder (talkcontribs)

"Being logged in" from a browser's perspective means you have entered valid credentials, and you got an HTTP cookie with a session identifier, and the browser sends back that cookie with the session identifier on all requests to the wiki that tells the server who's the user (this is what maintains the user logged in, until the cookie expires or the session is no longer valid on the server).

If you're able to programatically set a cookie on the user's browser from the same domain as MediaWiki, you'll be good to go. Otherwise, you won't be able to do so. Maybe Extension:Auth remoteuser is an alternative if you can set up the user on the server level.

About the api, if you receive Needs Token, this means you're not sending back the cookie you received from the first POST.

BensDBN (talkcontribs)

Hi Ciencia,

Thanks for your response. I am using AngularJS, I am just battling to grab to the cookie from the response headers from the first POST. I'm busy looking into how to do this currently.

I can see the cooking on the response header: Set-Cookie: wikidb_session=sd00uqls8o2hi6q7cev6gpg0tjhjbh4t; path=/; HttpOnly

Have any ideas?

All the documentation for API:Login all use request which has been shut down. :(

Ciencia Al Poder (talkcontribs)

You can't grab a cookie set with a HttpOnly flag (that's what you've received) from JavaScript. This is a protection to prevent JavaScript from stealing sessions. However, the cookie will get stored on the browser automatically and be used on future request. However this will only be true if the request comes from the same domain and path.

So basically, if you run the JavaScript code on a page on the same domain as MediaWiki, it should work. If you run the JavaScript code on a page on a different domain or subdomain, it won't work.

I don't know, however, what the solution should be. Maybe implement OAuth on your application and change MediaWiki logins to login against that OAuth server (this won't make users logged-in automatically, but they can click a button to log-in without further credentials if they're already logged in in the OAuth application). That's what happens when you use "login with facebook" buttons on other websites, for example.

BensDBN (talkcontribs)

My IIS server and my Wiki Server are on the same domain. The origin is currently set to localhost as I’m busy testing, which I think is part of the issue. But how does one test when you are developing? we have 3 different levels of security on the wiki, so based on the level of security of the person logged into our SPA that is the level of sites they see in the wiki. With your alternative suggestion, would the process be I log into OAuth from my application, providing a set of credentials and then when the customer is redirected to the wiki they click on Log in and it will automatically log them in with the set of credentials I provided initially?

Ciencia Al Poder (talkcontribs)

I have never set up an OAuth system. You may need to install Extension:WSOAuth and develop a class to handle the login system. From what I understand, OAuth not only authenticates users, but also provides a list of user groups or similar, that can be equivalent to MediaWiki user groups. I don't know how easy is to integrate that with your system.

BensDBN (talkcontribs)


I have tackled this again. I moved mediawiki to our web server. I also updated to the latest version of mediawiki which fixed the token issue. So im now using the recommended way to get the token. I have published my code to the webserver so the Orgin is exactly the same.

I added mediawiki as an application under our main site so now the url to get to the wiki is

In the web.config on IIS i added Access-Control-Allow-Origin and set the orgin to (an example) and on the request headers it is exactly the same.

However my response headers is still :

Set-Cookie: UseDC=master; expires=Fri, 03-Apr-2020 14:18:01 GMT; Max-Age=10; path=/; secure; HttpOnly

Set-Cookie: UseCDNCache=false; expires=Fri, 03-Apr-2020 14:18:01 GMT; Max-Age=10; path=/; secure; HttpOnly

So you can now see that it has secure but still has HttpOnly. Is there a setting that i can add in localSettings to white list a domain?

I'm not entirely sure now why its still HttpOnly.

Ciencia Al Poder (talkcontribs)

Session cookies must be HttpOnly, otherwise any script on the page could tamper with it.

If you're doing the login to MediaWiki through the application server-side (which would be desirable security-wise), you should capture the cookies in the header and then send them back to your application. That way since you have setup them as path=/ it should work.

BensDBN (talkcontribs)

The response im getting from the login request is MediaWiki API help page. Is that correct?

The response looks like this:

data: "<!DOCTYPE html>↵<html class="client-nojs" lang="en"

status: 200

headers: ƒ (name)

config: {method: "POST", transformRequest: Array(1), transformResponse: Array(1), url: "", paramSerializer: ƒ, …}

statusText: "OK"

__proto__: Object

BensDBN (talkcontribs)

I'm also looking at the cookie under application it seems to have saved the cookie correctly.

It has the wikidb_session cookie, domain is correct, path is "/", HttpOnly and Secure are ticked but SameSite isnt ticked. Does that need to be ticked in order for it to work?

Maybe the path should be "/Wiki" ?

BensDBN (talkcontribs)

Ok I dont think that return is correct because when i login through the main site manually there are 3 entries in the cookie, wikidbUserID, wikidbUserName and wikidb_session. Whereas on my login only wikidb_session is there.

Ciencia Al Poder (talkcontribs)

You should send a format=json, format=xml, etc to get a parseable response instead of the HTML one

BensDBN (talkcontribs)

Can we pay for someone to remote on and see what im doing wrong?

Ciencia Al Poder (talkcontribs)
Reply to "Automatic Login"

VisualEditor and Mediawiki over https

Darmoric (talkcontribs)


I don't succeed to make usable VisualEditor.:

visualeditor-docserver-http-error: (curl error: 77) Problem with the SSL CA cert (path? access rights?).

Here is my stunnul4 configuration:

debug = 7

output = /var/log/stunnel4/stunnel.log

verify = 2


cert = /shared/

key = /shared/

CAfile = /shared/chain.mobolab.crt.pem

accept  =

connect =

I can see that certificates are well loaded, but stunnel never communicates with port 8142.

What can be wrong ?

Thanks in advance

(parsoid was working well before trying to use https)

Darmoric (talkcontribs)

Here is my log: 2020.04.06 17:15:52 LOG6[cron]: Executing cron jobs

2020.04.06 17:15:52 LOG6[cron]: Cron jobs completed in 0 seconds

2020.04.06 17:15:52 LOG7[cron]: Waiting 86400 seconds

2020.04.06 17:15:52 LOG7[main]: Found 1 ready file descriptor(s)

2020.04.06 17:15:52 LOG7[main]: FD=4 events=0x2001 revents=0x0

2020.04.06 17:15:52 LOG7[main]: FD=7 events=0x2001 revents=0x1

2020.04.06 17:15:52 LOG7[main]: Service [parsoid] accepted (FD=3) from

2020.04.06 17:15:52 LOG7[1]: Service [parsoid] started

2020.04.06 17:15:52 LOG7[1]: Setting local socket options (FD=3)

2020.04.06 17:15:52 LOG7[1]: Option TCP_NODELAY set on local socket

2020.04.06 17:15:52 LOG5[1]: Service [parsoid] accepted connection from

2020.04.06 17:15:52 LOG6[1]: Peer certificate required

2020.04.06 17:15:52 LOG7[1]: TLS state (accept): before SSL initialization

2020.04.06 17:15:52 LOG3[1]: SSL_accept: Peer suddenly disconnected

2020.04.06 17:15:52 LOG5[1]: Connection reset: 0 byte(s) sent to TLS, 0 byte(s) sent to socket

2020.04.06 17:15:52 LOG7[1]: Local descriptor (FD=3) closed

2020.04.06 17:15:52 LOG7[1]: Service [parsoid] finished (0 left)

Bawolff (talkcontribs)

as a guess, is php/curl set to use the custom cert you are using with stunnel?

Darmoric (talkcontribs)


Many thanks for your reply.

I just add this line in php.ini:


curl.cainfo ="/etc/apache2/ssl/ca.pem"

ca.pem = certificates of CA + Intermediate

Am I wrong ? Do I have to add other certificates, modify options ?


Reply to "VisualEditor and Mediawiki over https"

Upgrade to 1.34, having some pages not displaying. When editing, got a unknown character symbol

Necrat (talkcontribs)

So we just upgraded our MediaWiki to 1.34. After the upgrade, several pages ended up not displaying. When we'd go to edit the page, we found the symbol on the linked example, which I believe is a unknown character in Unicode. This upgrade was from 1.2x something to 1.34, and included an upgrade to PHP. I've tried searching for this but can't find a solution upon search results. The error symbol is below.

Here is an example of the change that fixed the page.

I believe the previous character was the unicode superscript "1" (U+00B9).

Reply to "Upgrade to 1.34, having some pages not displaying. When editing, got a unknown character symbol"

Difference between web and cli installer

Nnaka1 (talkcontribs)

Based on what I see here, my understanding is that there may be some difference in how the web vs cli installer finds and connects with the Percona / MySQL DB.

I have looked through Manual:Installing MediaWiki as well as Manual:FAQ#Installation and configuration

My guess from these are that if there are some external extension dependencies, then the command line installation must be used. Is this true? And, are there other cases of such differences?

Where can I learn more about the differences between these two installation approaches?

Reply to "Difference between web and cli installer"

Problem installing MediaWiki

6 (talkcontribs)


Im trying to Install MediaWiki 1.16.5 on an Windows 2008 R2 Server with IIS 7.5, PHP 5.3.6 and Postgres 9.0.4.

First Step in MediaWiki Installation was apparently sucessfull.

LocalSettings.php was generated and I copied it to the MediaWiki root Dir.

So in next Step I try to access the MediaWiki Website - following Error gets displayed:

A database error has occurred Query: INSERT INTO l10n_cache (lc_lang,lc_key,lc_value) VALUES ('en','messages:clearyourcache','s:438:"''''''Note: After saving, you may have to bypass your browser''s cache to see the changes.''''''

So I take a look in the DB - but the Table l10n_cache is just empty.

Can sombody help? Is this an Bug?

Thank you!

MaxSem (talkcontribs)

Is that all error information you see? Is there more information, like an exact cause of SQL error? (talkcontribs)

No there is a lot more of:

A database error has occurred Query: INSERT INTO l10n_cache (lc_lang,lc_key,lc_value) VALUES ('en','messages:clearyourcache','s:438:"'Note: After saving, you may have to bypass your browsers cache to see the changes.' 'Mozilla / Firefox / Safari:' hold 'Shift' while clicking 'Reload', or press either 'Ctrl-F5' or 'Ctrl-R' ('Command-R' on a Macintosh); 'Konqueror: 'click 'Reload' or press 'F5'; 'Opera:' clear the cache in 'Tools → Preferences'; 'Internet Explorer:' hold 'Ctrl' while clicking 'Refresh,' or press 'Ctrl-F5'.";'),('en','messages:usercssyoucanpreview','s:83:"'Tip:' Use the "Show preview" button to test your new CSS before saving.";'),('en','messages:userjsyoucanpreview','s:90:"'Tip:' Use the "Show preview" button to test your new JavaScript before saving.";'),('en','messages:usercsspreview','s:91:"'Remember that you are only previewing your user CSS.' 'It has not yet been saved!'";'),('en','messages:userjspreview','s:106:"'Remember that you are only testing/previewing your user JavaScript.' 'It has not yet been saved!'";'),('en','messages:userinvalidcssjstitle','s:178:"'Warning:' There is no skin "$1". Remember that custom .css and .js pages use a lowercase title, e.g. User:Foo/monobook.css as opposed to User:Foo/Monobook.css.";'),('en','messages:updated','s:9:"(Updated)";'),('en','messages:note','s:11:"'Note:'";'),('en','messages:previewnote','s:81:"'Remember that this is only a preview.' Your changes have not yet been saved!";'),('en','messages:previewconflict','s:102:"This preview reflects the text in the upper text editing area as it will appear if you choose to save.";'),('en','messages:session_fail_preview','s:179:"'Sorry! We could not process your edit due to a loss of session data.' Please try again. If it still does not work, try logging out and logging back in.";'),('en','messages:session_fail_preview_html','s:338:"'Sorry! We could not process your edit due to a loss of session data.'

'Because MediaWiki has raw HTML enabled, the preview is hidden as a precaution against JavaScript attacks.'

'If this is a legitimate edit attempt, please try again.' If it still does not work, try logging out and logging back in.";'),('en','messages:token_suffix_mismatch','s:259:"'Your edit has been rejected because your client mangled the punctuation characters in the edit token.' The edit has been rejected to prevent corruption of the page text. This sometimes happens when you are using a buggy web-based anonymous proxy service.";'),('en','messages:editing','s:10:"Editing $1";'),('en','messages:editingsection','s:20:"Editing $1 (section)";'),('en','messages:editingcomment','s:24:"Editing $1 (new section)";'),('en','messages:editconflict','s:17:"Edit conflict: $1";'),('en','messages:explainconflict','s:323:"Someone else has changed this page since you started editing it. The upper text area contains the page text as it currently exists. Your changes are shown in the lower text area. You will have to merge your changes into the existing text. 'Only' the text in the upper text area will be saved when you press "Save page".";'),('en','messages:yourtext','s:9:"Your text";'),('en','messages:storedversion','s:15:"Stored revision";'),('en','messages:nonunicodebrowser','s:184:"'Warning: Your browser is not unicode compliant.' A workaround is in place to allow you to safely edit pages: non-ASCII characters will appear in the edit box as hexadecimal codes.";'),('en','messages:editingold','s:135:"'Warning: You are editing an out-of-date revision of this page.' If you save it, any changes made since this revision will be lost.";'),('en','messages:yourdiff','s:11:"Differences";'),('en','messages:copyrightwarning','s:406:"Please note that all contributions to MediaWiki are considered to be released under the $2 (see $1 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!'";'),('en','messages:copyrightwarning2','s:394:"Please note that all contributions to MediaWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, 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 (see $1 for details). 'Do not submit copyrighted work without permission!'";'),('en','messages:editpage-tos-summary','s:1:"-";'),('en','messages:longpagewarning','s:182:"'Warning:' This page is $1 kilobytes long; some browsers may have problems editing pages approaching or longer than 32kb. Please consider breaking the page into smaller sections.";'),('en','messages:longpageerror','s:132:"'Error: The text you have submitted is $1 kilobytes long, which is longer than the maximum of $2 kilobytes.' It cannot be saved.";'),('en','messages:readonlywarning','s:253:"'Warning: The database has been locked for maintenance, so you will not be able to save your edits right now.' You may wish to cut-n-paste the text into a text file and save it for later.

The administrator who locked it offered this explanation: $1";'),('en','messages:protectedpagewarning','s:156:"'Warning: This page has been locked so that only users with administrator privileges can edit it.' The latest log entry is provided below for reference:";'),('en','messages:semiprotectedpagewarning','s:134:"'Note:' This page has been locked so that only registered users can edit it. The latest log entry is provided below for reference:";'),('en','messages:cascadeprotectedwarning','s:186:"'Warning:' This page has been locked so that only users with administrator privileges can edit it, because it is included in the following cascade-protected pages:";'),('en','messages:titleprotectedwarning','s:171:"'Warning: This page has been locked so that specific rights are needed to create it.' The latest log entry is provided below for reference:";'),('en','messages:templatesused','s:51:"Templates used on this page:";'),('en','messages:templatesusedpreview','s:54:"Templates used in this preview:";'),('en','messages:templatesusedsection','s:54:"Templates used in this section:";'),('en','messages:template-protected','s:11:"(protected)";'),('en','messages:template-semiprotected','s:16:"(semi-protected)";'),('en','messages:hiddencategories','s:78:"This page is a member of $1 hidden categories:";'),('en','messages:edittools','s:61:"";'),('en','messages:nocreatetitle','s:21:"Page creation limited";'),('en','messages:nocreatetext','s:157:"MediaWiki has restricted the ability to create new pages. You can go back and edit an existing page, or log in or create an account.";'),('en','messages:nocreate-loggedin','s:47:"You do not have permission to create new pages.";'),('en','messages:sectioneditnotsupported-title','s:29:"Section editing not supported";'),('en','messages:sectioneditnotsupported-text','s:46:"Section editing is not supported in this page.";'),('en','messages:permissionserrors','s:18:"Permissions errors";'),('en','messages:permissionserrorstext','s:86:"You do not have permission to do that, for the following reasons:";'),('en','messages:permissionserrorstext-withaction','s:81:"You do not have permission to $2, for the following reasons:";'),('en','messages:recreate-moveddeleted-warn','s:222:"'Warning: You are recreating a page that was previously deleted.'

You should consider whether it is appropriate to continue editing this page. The deletion and move log for this page are provided here for convenience:";'),('en','messages:moveddeleted-notice','s:100:"This page has been deleted. The deletion and move log for the page are provided below for reference.";'),('en','messages:log-fulllog','s:13:"View full log";'),('en','messages:edit-hook-aborted','s:45:"Edit aborted by hook. It gave no explanation.";'),('en','messages:edit-gone-missing','s:59:"Could not update the page. It appears to have been deleted.";'),('en','messages:edit-conflict','s:14:"Edit conflict.";'),('en','messages:edit-no-change','s:62:"Your edit was ignored, because no change was made to the text.";'),('en','messages:edit-already-exists','s:47:"Could not create a new page. It already exists.";'),('en','messages:addsection-preload','s:0:"";'),('en','messages:addsection-editintro','s:0:"";'),('en','messages:expensive-parserfunction-warning','s:183:"'Warning:' This page contains too many expensive parser function calls.

It should have less than $2 calls, there are now $1 calls.";'),('en','messages:expensive-parserfunction-category','s:51:"Pages with too many expensive parser function calls";'),('en','messages:post-expand-template-inclusion-warning','s:87:"'Warning:' Template include size is too large. Some templates will not be included.";'),('en','messages:post-expand-template-inclusion-category','s:45:"Pages where template include size is exceeded";'),('en','messages:post-expand-template-argument-warning','s:137:"'Warning:' This page contains at least one template argument which has a too large expansion size. These arguments have been omitted.";'),('en','messages:post-expand-template-argument-category','s:43:"Pages containing omitted template arguments";'),('en','messages:parser-template-loop-warning','s:30:"Template loop detected: $1";'),('en','messages:parser-template-recursion-depth-warning','s:44:"Template recursion depth limit exceeded ($1)";'),('en','messages:language-converter-depth-warning','s:44:"Language converter depth limit exceeded ($1)";'),('en','messages:undo-success','s:161:"The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.";'),('en','messages:undo-failure','s:67:"The edit could not be undone due to conflicting intermediate edits.";'),('en','messages:undo-norev','s:70:"The edit could not be undone because it does not exist or was deleted.";'),('en','messages:undo-summary','s:75:"Undo revision $1 by $2 (talk)";'),('en','messages:cantcreateaccounttitle','s:21:"Cannot create account";'),('en','messages:cantcreateaccount-text','s:118:"Account creation from this IP address ('$1') has been blocked by $3.

The reason given by $3 is '$2'";'),('en','messages:cantcreateaccount-nonblock-text','s:0:"";'),('en','messages:viewpagelogs','s:23:"View logs for this page";'),('en','messages:nohistory','s:39:"There is no edit history for this page.";'),('en','messages:currentrev','s:15:"Latest revision";'),('en','messages:currentrev-asof','s:24:"Latest revision as of $1";'),('en','messages:revisionasof','s:17:"Revision as of $1";'),('en','messages:revision-info','s:23:"Revision as of $1 by $2";'),('en','messages:revision-info-current','s:1:"-";'),('en','messages:revision-nav','s:65:"($1) $2 | $3 ($4) | $5 ($6)";'),('en','messages:previousrevision','s:18:"← Older revision";'),('en','messages:nextrevision','s:18:"Newer revision →";'),('en','messages:currentrevisionlink','s:15:"Latest revision";'),('en','messages:cur','s:3:"cur";'),('en','messages:next','s:4:"next";'),('en','messages:last','s:4:"prev";'),('en','messages:page_first','s:5:"first";'),('en','messages:page_last','s:4:"last";'),('en','messages:histlegend','s:279:"Diff selection: mark the radio boxes of the revisions to compare and hit enter or the button at the bottom.
Legend: '(cur)' = difference with latest revision, '(prev)' = difference with preceding revision, 'm' = minor edit.";'),('en','messages:history-fieldset-title','s:14:"Browse history";'),('en','messages:history-show-deleted','s:12:"Deleted only";'),('en','messages:history_copyright','s:1:"-";'),('en','messages:histfirst','s:8:"Earliest";'),('en','messages:histlast','s:6:"Latest";'),('en','messages:historysize','s:31:"($1 bytes)";'),('en','messages:historyempty','s:7:"(empty)";'),('en','messages:history-feed-title','s:16:"Revision history";'),('en','messages:history-feed-description','s:42:"Revision history for this page on the wiki";') Function: LCStore_DB::set Error: 1 FEHLER: Zeichen 0xe28692 in Kodierung »UTF8« hat keine Entsprechung in »WIN1252«


  1. 0 C:\inetpub\wwwroot\MediaWiki\includes\db\Database.php(538): DatabasePostgres->reportQueryError('FEHLER: Zeiche...', 1, 'INSERT INTO l10...', 'LCStore_DB::set', )
  2. 1 C:\inetpub\wwwroot\MediaWiki\includes\db\DatabasePostgres.php(810): DatabaseBase->query('INSERT INTO l10...', 'LCStore_DB::set', )
  3. 2 C:\inetpub\wwwroot\MediaWiki\includes\LocalisationCache.php(822): DatabasePostgres->insert('l10n_cache', Array, 'LCStore_DB::set')
  4. 3 C:\inetpub\wwwroot\MediaWiki\includes\LocalisationCache.php(617): LCStore_DB->set('messages:histor...', 'Revision histor...')
  5. 4 C:\inetpub\wwwroot\MediaWiki\includes\LocalisationCache.php(352): LocalisationCache->recache('en')
  6. 5 C:\inetpub\wwwroot\MediaWiki\includes\LocalisationCache.php(262): LocalisationCache->initLanguage('en')
  7. 6 C:\inetpub\wwwroot\MediaWiki\includes\LocalisationCache.php(205): LocalisationCache->loadItem('en', 'deps')
  8. 7 C:\inetpub\wwwroot\MediaWiki\includes\LocalisationCache.php(514): LocalisationCache->getItem('en', 'deps')
  9. 8 C:\inetpub\wwwroot\MediaWiki\includes\LocalisationCache.php(352): LocalisationCache->recache('de')
  10. 9 C:\inetpub\wwwroot\MediaWiki\includes\LocalisationCache.php(262): LocalisationCache->initLanguage('de')
  11. 10 C:\inetpub\wwwroot\MediaWiki\includes\LocalisationCache.php(205): LocalisationCache->loadItem('de', 'fallback')
  12. 11 C:\inetpub\wwwroot\MediaWiki\languages\Language.php(2526): LocalisationCache->getItem('de', 'fallback')
  13. 12 C:\inetpub\wwwroot\MediaWiki\languages\Language.php(173): Language::getFallbackFor('de')
  14. 13 C:\inetpub\wwwroot\MediaWiki\languages\Language.php(136): Language::newFromCode('de')
  15. 14 C:\inetpub\wwwroot\MediaWiki\includes\StubObject.php(126): Language::factory('de')
  16. 15 C:\inetpub\wwwroot\MediaWiki\includes\StubObject.php(103): StubContLang->_newObject()
  17. 16 C:\inetpub\wwwroot\MediaWiki\includes\StubObject.php(57): StubObject->_unstub('getCode', 5)
  18. 17 C:\inetpub\wwwroot\MediaWiki\includes\StubObject.php(121): StubObject->_call('getCode', Array)
  19. 18 C:\inetpub\wwwroot\MediaWiki\includes\GlobalFunctions.php(576): StubContLang->__call('getCode', Array)
  20. 19 C:\inetpub\wwwroot\MediaWiki\includes\GlobalFunctions.php(576): StubContLang->getCode()
  21. 20 C:\inetpub\wwwroot\MediaWiki\includes\MessageCache.php(506): wfGetLangObj(true)
  22. 21 [internal function]: MessageCache->get('mainpage', true, true)
  23. 22 C:\inetpub\wwwroot\MediaWiki\includes\StubObject.php(58): call_user_func_array(Array, Array)
  24. 23 C:\inetpub\wwwroot\MediaWiki\includes\StubObject.php(76): StubObject->_call('get', Array)
  25. 24 C:\inetpub\wwwroot\MediaWiki\includes\GlobalFunctions.php(742): StubObject->__call('get', Array)
  26. 25 C:\inetpub\wwwroot\MediaWiki\includes\GlobalFunctions.php(742): StubObject->get('mainpage', true, true)
  27. 26 C:\inetpub\wwwroot\MediaWiki\includes\GlobalFunctions.php(707): wfMsgGetKey('mainpage', true, true, true)
  28. 27 C:\inetpub\wwwroot\MediaWiki\includes\GlobalFunctions.php(655): wfMsgReal('mainpage', Array, true, true)
  29. 28 C:\inetpub\wwwroot\MediaWiki\includes\Title.php(284): wfMsgForContent('mainpage')
  30. 29 C:\inetpub\wwwroot\MediaWiki\includes\Wiki.php(117): Title::newMainPage()
  31. 30 C:\inetpub\wwwroot\MediaWiki\index.php(61): MediaWiki->checkInitialQueries(NULL, 'view')
  32. 31 {main}

Thnak you! (talkcontribs)

Make sure your database is created as UTF8. Looks like you might be trying to force UTF8 data into Win1252. (talkcontribs)


I am stuck with the installation on Windows Server 2008 x64. The error I get is the following complaining about the config folder not being writable. I tried giving full access to the network service account to the config folder but still getting the same message as below. I installed it under http://localhost/mediawiki/. Any help is highly appreciated.

Thank you.

MediaWiki 1.16.5 Installation Can't write config file, aborting In order to configure the wiki you have to make the config subdirectory writable by the web server. Once configuration is done you'll move the created LocalSettings.php to the parent directory, and for added safety you can then remove the config subdirectory entirely.

To make the directory writable on a Unix/Linux system:

cd C:\inetpub\wwwroot\mediawiki chmod a+w config Afterwards retry to start the setup.

Reply to "Problem installing MediaWiki"