Open main menu

MediaWiki β

Project:Support desk

About this board

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

There are also other places where to askCommunication: IRCCommunication#Chat, mailing listsMailing lists, Q&A etc.

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".
By clicking "Add topic", you agree to our Terms of Use and agree to irrevocably release your text under the CC BY-SA 3.0 License and GFDL

How to make an image simply size to the users screen?

RedKnight7 (talkcontribs)

Hi everyone,

I am familiar with using the thumb option on pictures, to make them a particular size. I have a rather large picture (more than a 4K screen can show) which I would like to appear at a size that is scaled to the user's screen. I don't know any way to have it scale to their screen... if I simply say [[File:Whatever.JPG]], it is HUGE (they only see a tiny portion). The only other option seems to be a thumb, which makes it be some arbitrarily fixed size I have to specify.

How can I let an image fit the user's screen width? Surely there must be a way.

Thanks if you can help!

AhmadF.Cheema (talkcontribs)

There should be a few ways to achieve responsive images.

/* Images should be responsive */
res-img {
@media (-webkit-min-device-pixel-ratio: 1.5), (min-resolution: 1.5dppx), (min-resolution: 144dpi) {
    #mp-topbanner-inner {
        background-image: url(//
@media (-webkit-min-device-pixel-ratio: 2), (min-resolution: 2dppx), (min-resolution: 192dpi) {
    #mp-topbanner-inner {
        background-image: url(//

If the extension doesn't work the CSS should be the best option.

RedKnight7 (talkcontribs)

Thanks greatly for the reply Ahmad,

The CSS page didn't seem to have any effect? The description above is vague, "images should be responsive". Am I missing some further setting in the my call for the graphics file? Should I be saying a thumb of some percent, or something?

Otherwise, I don't want your third (webkit) solution solution because it uses fixed sizes. That's my question - isn't there anything that's NOT a fixed size? That's automatically the user's screen width?

I guess the AdaptiveThumb is a fallback option, but it would be nice to get the CSS to work, if I can. So,

Am I doing something wrong or leave something out? A straight, enormous image ([[File:Whatever.JPG]]) is still much larger than screen width. If the CSS code affects thumbnails somehow, I don't how to turn it on. If I state a thumb that's much larger the screen width (like 10000px), the CSS did not resize it to 100% of my screen width.

Is there a way to specify thumb nails as a PERCENT of user's screen size, instead of fixed pixels?

Thanks so much if you can help! Can't MediaWiki tell a user's screen size??

AhmadF.Cheema (talkcontribs)
/* To make images responsive */
.res-img img {
  • The "responsive" in the description is the term used for the automatic size-change functionality that you want for your images.
  • Here, res-img is the .CSS class name. Including it in your Wiki's MediaWiki:Common.css page makes it available to all pages on your Wiki. This .CSS rule applies the two height and width style attributes to all the images that come under it.
  • Using this class you can use, in your content pages, something of the form:
<div class="res-img">
  • Or if you have a lot of these high-resolution images you can even turn this into a template.
  • For some reason, I was unable to make this work through inline div styling i.e. by using <div style="max-width:100%; height:auto;">
  • Note that using this method, the image will get stretched if the user's screen size is greater than the "100%" size of the image. It shouldn't be an issue for larger images and smaller screen sizes. For details see, Responsive Web Design - Images.
  • You can also automatically apply this .CSS rule to all the images on your Wiki without having to call the class, again and again by inserting the following in your MediaWiki:Common.css
    /* To make images responsive */
    img {
RedKnight7 (talkcontribs)

It worked! Thank you so much Ahmad!

I also noticed you put a period (.) before res-img in your reply, and also, I had no clue on the rest, but you made it all clear. This example is worth a thousand words.

Thank you for all the other notes, which I'll try to remember. You're a good man.

Fokebox (talkcontribs)

You can simply use this extension: MultimediaViewer

RedKnight7 (talkcontribs)

Fokebox, the description for MultimediaViewer says it "Provides a better experience to users when they click on thumbnails in a page".

I don't want to make thumbnails better. I want to simply display a picture on the screen ([[File:Whatever.JPG]]) at full width.

This is what I'm saying... Right now, the only way I know to present it is either with a thumbnail (too small plus forces user to click through) OR the straight-up graphic ([[File:Whatever.JPG]]) is far too large.

I just want to show a pic at full size width, whatever is full width for the user, without me having to specify anything specific. (A percent width is okay, but not fixed pixels.)

Thanks if you can help.

Zoglun (talkcontribs)

So I tried to enable filecache with following settings:

$wgUseFileCache = true; 

$wgUseGzip = true;

$wgFileCacheDirectory = "/var/cache/mw-filecache";

mw-filecache folder were set to 777, php-zlib installed. But nothing generated. So I tried RebuildFileCache.php. Then all the pages showing:

Page 'xxx' (id 962) not cacheable

How can I identify the cause of this "not cacheable" problem?

Reply to "Unable to use FileCache"

Can't identify category for Mediawiki srnamespace parameter

SewerCat (talkcontribs)

I would like to issue requests like the following. I'm unable to find values for the namespace parameter that are acceptable. Please give me some guidance. I want to limit searches to the cookbook itself, preferably to items in the, or a, recipe category.

MacFan4000 (talkcontribs)


SewerCat (talkcontribs)

Thank you. I think I've grasped something of the meaning of that page. I regret to say I don't know what a suitable parameter value might be instead of 'Cookbook:Recipe'. Please, throw me a bone. :)

Ciencia Al Poder (talkcontribs)

List of namespaces:

Cookbook is namespace 102. Note that there's no 'Cookbook:Recipe' namespace

Reply to "Can't identify category for Mediawiki srnamespace parameter"

how to count MW's ParserCache hit rate?

Zoglun (talkcontribs)

There were lots of pages talking about Wikipedia's Parser cache hit rate (e.g.

However, I can't find any page documented in about how to count ParserCache hit rate for their own wiki. Currently I knew that my Varnish cache hold about 70% hit of request, uAPC 85%, and redis 80%. Is there a way to only count hit rate for ParserCache?

Reply to "how to count MW's ParserCache hit rate?"
2A02:AA16:9200:1800:1C8A:8249:48BC:102B (talkcontribs)


I have been running two MediaWiki Sites for a long time without problems. In the summer I made a redesign with small changes in the MediaWiki code.

Problem: No single pictures are more in the Google-Images search available. (Checked via

More specifically, every Image via [[File:filename.extension|options|caption]] are not available in the search results. I testet it: other Images included via html code <img src="image.jpg"> are crawled and are show in image search, but every "[[File:filename..." not.

I also checked my robots.txt and .htaccess file, everything looks good and nothing is locked. (Webmaster Tools)

I remember that in the summer I only add meta robots to the File-Site (/wiki/File:Example.jpg): <meta name="robots" content="noindex,follow" /> via $wgNamespaceRobotPolicies = array ( NS_FILE => 'noindex,follow', );

But now, I removed it and it is still not crawled by Google but 'with it works. Really strange.

What can it be that no Image included via MediaWiki Syntax is searchable, on both MediaWikis? The Article Page is crawled fine, but the images in de article are not visible in the search engine.

thanks Marta

MediaWiki: 1.15.0 PHP: 5.6.29 MySQL: 5.5.53

This comment was hidden by 2A02:AA16:9200:1800:1C8A:8249:48BC:102B (history)
2A02:AA16:9200:1800:1C8A:8249:48BC:102B (talkcontribs)

Correct formatting: "More specifically, every Image via File:filename.extension|options|caption are not available in the search results. "

2A02:AA16:9200:1800:BC06:5961:AD41:D7D7 (talkcontribs)

Mhh, the last days I tested it also without MediaWiki Image Syntax and in different ways, example: I included the test-image directly with only // but without success or with html code in another different image directory.

The new test-site is the index, but without images :/

Can anyone explain me this that?


2A02:AA16:9200:1800:BC9C:695F:1E63:D932 (talkcontribs)

Hi, its me again. Has nobody an idea?


This, that and the other (talkcontribs)

Can you provide a link to your site?

Ciencia Al Poder (talkcontribs)

Note that search engines may take time (days or weeks) to update their indices.

2A02:AA16:9200:1800:5082:A72D:BCA8:287 (talkcontribs)

@This, that and the other @Ciencia Al Poder

I'd rather not say it public, because it's a private family page.

So, I tested it these days with different settings and with these settings it works and the images appears in the google image search index: √ = works, X = don't work

  • √ an Image on the root folder or another own folder like "myimages"
  • √ using a 301 redirect image html code: src="http://www.xy. /mytestreditectimagefolder/w/images/3/32/image.png to the original file in http://xy. /w/wiki/images/3/32/image.png

  • X standard wiki image syntax
  • X in robots.txt allow User-Agent: Googlebot-Image
  • X not a single url like http://xy. /w/File:myimage.png is in the normal index (has no meta robots)
  • X created a manual image <image:loc> sitemap (5 Submitted, 2 Indexed)

I tested various urls and submitted it also via google webmastertoos fetch, submit via Search Console and via mobile-friendly-test.

My current robots.txt looks like: --- User-agent: * Allow: /w/File: Allow: /w/wiki/images/

User-agent: * Disallow: /w/MediaWiki Disallow: /w/Extension ---


  • I have the feeling that ALL the pictures with the MediaWiki-Syntax suddenly disappeared form Google since last summer
  • Images in are in the index
  • Images on the Subdomain (blog= another hosting provider) are also in de index.
  • Never had an error (Fetch and render or blocked files in Webmastertools)
  • Same Problem with two differents MediaWikis (1.15.1 & 1.15.0) on 2 differents domains
  • Never had an Image Problem, 6 months ago every things worked fine

So to this day, Not a single picture via: File:example.jpg|frame|caption is in the Index.

Best regards Marta

2A02:AA16:9200:1800:F153:C35B:E14D:8B4B (talkcontribs)

*So, I have waited a few days and the problem is still there.


Can a deactivation of the PHP Version 5.4 & 5.5 last year be responsible for the problem, that none images from the directory '''"w/images" via Mediawiki Syntax in appears the Google Image Index'''?


but '''''', '''''' and ''''' they show the images.

Ciencia Al Poder (talkcontribs)

You said in the first post made a redesign with small changes in the MediaWiki code. Maybe that's the reason it doesn't work anymore?

2A02:AA16:9200:1800:C79:6098:3D06:749F (talkcontribs)

@ Ciencia Al Poder

I do not think because at the first redesign (larger Mediawiki) the images were indexed (September/October) despite changes. The other Mediawki (smaller one) had no change in the Skin-Template and still no pictures in the index.

The Second Mediawiki has also an other "Mediawiki-Files" directory ss the first with many more photos.


Ciencia Al Poder (talkcontribs)

If no changes were made, you may try contacting google since that's probably their issue. MediaWiki 1.15 is not supported so you may want to upgrade. (talkcontribs)

Hello again,

Now I'm testing it in different ways for two months without solving the problem.

All images in the directory /wiki/images/ with MediaWiki-image-syntax are not are not visible in Google Images (via
🚫 [[File:filename.extension]]
🚫 Site /File:XY.png are not in the index, only URLS with Filetype: PDF are showing
🚫 also with html code <img src="xy.gif" alt="Smiley face"> doesen't work
✅ Images in other (test) directories can be seen in the search
✅ Images included directly like works & are visible by Google
✅ NO errors in Google Webmaster-Tools (robots.txt, sitemap.xml...)
✅ <meta name="robots" content="index, follow">
✅ images are displayed on Bing search
✅ SAME problem with the Google engine with a second Mediawiki (1.15.1 & 1.15.0), both websites have a good ranking

So Why google does not show my pictures? (Can I have a "Google Penalty" i ONLY the MediaWiki image directory wiki/images)?

Best regards


This, that and the other (talkcontribs)

It's unlikely that anyone here can help you unless you link to the site in question. If you choose not to do that, I think it is fairly unreasonable to expect others to guess at what the matter is with your site.

2A02:AA16:9200:E80:582B:A0A0:85F6:F7B6 (talkcontribs)

@This, that and the other
@Ciencia Al Poder

I guess you are right to a certain degree, but technically, the issue is plain:

all pictures in MediaWiki upload directory (/wiki/images/a/b/cd.gif|png|jpeg) are not indexed on Google Images (

that's all.

As a compromise: I found a few old MediaWikis with similar Google index problems:

  • NO Image: any file formats in Google's index but .pdf, .txt, .doc...
    • Demo Site 1
    • Demo Site 2
  • NO File description page in the index (File:):
    • Demo Site 3 (
    • Demo Site 4 (

Hopefully someone can solve this error


Ciencia Al Poder (talkcontribs)

Other MediaWiki sites may choose in the google webmasters tools to not index those pages.

Demo Site 2 display a lot of images in image search. Demo site 1 doesn't, but file description pages contains extra lines before the first line of HTML, so I guess google has some issues indexing that site properly, or it finds the site irrelevant...

No idea about 3 and 4. Did you got a reply from google forums?

2A02:AA16:9200:E80:447E:3001:14A9:FFF4 (talkcontribs)

@Ciencia Al Poder, mhh, yes very confusing :/

The odd thing about it, suddenly the images (and File description page) are on both sides no longer in the index (only by the MediaWiki image directory)

Ps. No, I have the problem not yet published in the google forum

Can I over-list google?

Like change the /wiki/images/ URLs to /common/images/, because the htaccess 301 redirection with test pictures works,

Ciencia Al Poder (talkcontribs)

You may have more luck asking in a google-related forum, because there's no problem displaying images in MediaWiki and nobody has yet raised where in MediaWiki is the problem. We do not know how google decides if a page or image is worth indexing or not so it would be most reasonable to ask them first, and come here when you got an actionable response (something that needs to be changed in MediaWiki)

2A02:AA16:9200:E80:E15A:E832:4CF5:AFA8 (talkcontribs)

@Ciencia Al Poder, OK I will create the topic in a Google-related forum.

I would additionally make a last test:

What is the best way to move the image directory? (step by step)

I would like to see what happens, when the files are saved in a new /upload/thumb/0/0b/XY.png/500px-XY.png instead of /images/thumb/0/0b/XY.png/500px-XY.png directory, because as I see it, Google has only a problem with a direct link to the directory /wiki/images/.

Remember, a redirect image-file from a new url like /image-test/xy.jpg to the original Mediawiki upload directory /wiki/images/0/0a/xy.jpg works.

Ciencia Al Poder (talkcontribs)

Change Manual:$wgUploadDirectory and Manual:$wgUploadPath

2A02:AA16:9200:E80:89B:85E8:7F6B:B05D (talkcontribs)

Hi, it works!

I don't know why, but Google has indexed since the summer every image – just like that.

I haven't made any changes. The images are all in the Google-Image index :)


Can I use the MediaWiki engine for a social media website that works similar to Facebook?

Sapphire Williams (talkcontribs)

I am planning to design a social media site that functions similar to Facebook but using the MediaWiki engine in addition to the Social tools and perhaps Semantic MediaWiki. I don't have any servers yet and I plan to learn PHP, HTML, and Javascript,. How it would work is that the website would have user profiles where they can edit their own profiles, and have personal name spaces for their messages, blogs, personal pages, and posts. Also the users are able to friend other users, and create and join groups, with the group having their own fourm and wiki pages in which the group members can edit, as well as having group chatrooms. Users can also create pages about their businesses and interests. MediaWiki would also be useful for special rights over each groups and the entire wiki. Perhaps I can research some extensions that can be useful, and if there isn't an extension that I need I can develop my own for the website.

Do you think MediaWiki can be used to create a social media site, and if so is it a good idea to use MediaWiki or give it any wiki functionality?

Sapphire Williams (talkcontribs)

And if any traditional social media site has used MediaWiki, may you please give me examples?

AhmadF.Cheema (talkcontribs)

Wouldn't it probably be much easier to use some forum, or better yet, social networking open source application for this purpose?

For all the things you will want in your social wiki, will require MediaWiki to be heavily modified while most of those should be available out-of-the-box for social networking applications.

To make a website successful, a lot of the work needs to be put into the content of the website. If you end up spending most of your time in learning "PHP, HTML, and Javascript" (I'm assuming you already don't have a working knowledge of them) and further customizing extensions, you are going to have no time left for the more important work needed to make a website popular.

See Social Networking and Forum applications for a relevant list. Discourse is one forum application that I think can do all the things you want to do, out-of-the-box.

Sapphire Williams (talkcontribs)

I have two questions: If I decide to make a wiki - based social media site, can I use a wiki engine other than MediaWiki?

Or can the above applications can be used with MediaWiki or other wiki engines?

This comment was hidden by Sapphire Williams (history)
AhmadF.Cheema (talkcontribs)

You can use other Wiki applications too, but you will have to look through the different services to see what fits your needs. I don't have the personal experience to be sure what would be the best fit for you.

Some things one type of application does better, while in other things another type of application is better. Mainly depends on what kind of a community you are trying to create.

Most of your needs in one way or another do get fulfilled by MediaWiki, but it doesn't provide the most smooth and intuitive user experience. For example, live chat extension for MediaWiki is not that impressive while other Social Networking applications and Discourse does much better. A good (but far from the best) chat implementation that I saw used with MediaWiki was a third-party chat application like the one you can see used on some sites for customer support. The feature to restrict all but one group of users from editing a particular page, although does get implemented by a few extensions, as far as I remember, all of them suffered from one issue or another.

It is also possible to use multiple web applications at the same time. For example, to have as the Wiki part of the site and as the Forum. However, you might need a very supportive community to make such an implementation popular.

Sapphire Williams (talkcontribs)

Okay got it, thanks!

But is it okay if you list some extensions that can restrict a group of users from editing a particular page?

AhmadF.Cheema (talkcontribs)

See Extension:Restrict access by category and group and Extension:CategoryPermissions.

But there are usually some limitations and bugs to such restriction extensions.

Reply to "Can I use the MediaWiki engine for a social media website that works similar to Facebook?"

Updating to 1.29 can only be done in non-readonly mode

TheMatt (talkcontribs)

All, this is an odd one. I updated my 1.28.2 install to 1.29 today and at the end I do my usual 'php maintenance/update.php'. But on doing that, things failed. If I tried to load a wikipage I got:

[WXihOq3smIUAAEBThTYAAAAb] 2017-07-26 14:03:39: Fatal exception of type "Wikimedia\Rdbms\DBQueryError".

Huh. So, looking around I followed:

Set $wgShowDBErrorBacktrace = true; at the bottom of LocalSettings.php to show detailed debugging information

and then re-ran the update.php and:

...wl_notificationtimestamp is already nullable.

...index times already set on logging table.

...have ipb_range_start field in ipblocks table.

[37fe685e9f4eecdeed47e3a4] [no req]   Wikimedia\Rdbms\DBReadOnlyError from line 858 of /home/site/ Database is read-only: Maintenance is underway. Website is on read-only mode


#0 /home/site/ Wikimedia\Rdbms\Database->query(string, string)

#1 [internal function]: MysqlUpdater->doPageRandomUpdate()

#2 /home/site/ call_user_func_array(array, array)

#3 /home/site/ DatabaseUpdater->runUpdates(array, boolean)

#4 /home/site/ DatabaseUpdater->doUpdates(array)

#5 /home/site/ UpdateMediaWiki->execute()

#6 /home/site/ require_once(string)

#7 {main}

(urls mangled for safety's sake)

So, I then edited my LocalSettings.php to turn off readonly and, bang, it worked. But I'm sure in the past I'd not needed to and even this page:

Manual:Upgrading#Can my wiki stay online while it is upgrading.3F

seems to say I can do the update in readonly mode.

Any idea what I did wrong? FYI my PHP is 5.6.29 and my MySQL is 5.6.34-log

Reply to "Updating to 1.29 can only be done in non-readonly mode"
Bachounda (talkcontribs)

How do I view a PDF file in my mediawiki?

I tried using PdfHandler and PDF Integrate without success.

I added the plugin to the server / and modified the LocalSettings.php file

you can see the specialpage in :

I forget a setting or what?

MacFan4000 (talkcontribs)

MediaWiki 1.23 is unsupported, we recomend upgrading.

Bachounda (talkcontribs)

to upgrade with a simple FTP access is it possible ?

MacFan4000 (talkcontribs)

It seems that you will also need to update php to 5.5.9 or newer.

Bachounda (talkcontribs)

thanks Mac :) but and how to update php to newer version ...

2002:43F4:3186:1234:394A:44CD:84A4:2CBD (talkcontribs)

You need SSH access.Do you know which version of debian you are using? -MacFan4000 (Logged Out)

Bachounda (talkcontribs)

sorry i haven't SSH access

Reply to "My PDF's Files cant viewed / Showed"

Articles will not save if they are large

Jman444 (talkcontribs)

Hello all and thank you for your help. If I let the length of any my articles extend too long (approximately 4000 characters) I get the following error...

Some parts of the edit form did not reach the server; double-check that your edits are intact and try again.

And all the data is lost. I checked all the php.ini/LocalSetting.php and could not find any reason for this.

I am running

MediaWiki: 1.19.1 PHP: 5.3.13 (cgi-fcgi) MySQL: 5.1.63-cll

Unfortunately I can't provide a link due to the sensitive nature of the wiki. I do have another wiki setup on the server however and that one does not have this problem. I tried reinstalling the wiki completely and that did not solve anything.

I would appreciate any help - Thank you - Jman

Bawolff (talkcontribs)

Basically MediaWiki says that if when you hit submit, the edit box doesn't seem to be submitted.

I think the most likely cause (this is a guess) of this is something wrong with the webserver, cutting off post data if its beyond a certain size

Jman444 (talkcontribs)

WelI have an account on the same server running a wiki perfectly running from the same global php.ini...I can't imagine what is causing this.

Bawolff (talkcontribs)

Sorry, your last post confused me. Are you saying that you have another instance of MediaWiki, running on the same web server, with the same php configuration, that does not have this issue?

If so, that is quite odd. Do you have the same extensions installed on both (and specificly, do you have any captcha extensions installed, simply because they mess with how editing works, so that would be one of the first places I'd look [however, I've never heard of a captcha extension causing this sort of issue])? Are the MediaWiki instances the same versions?

Jman444 (talkcontribs)

You are correct, same server, two separate installs of MediaWiki. Both are bone stock, no modifications what so ever.

Wargo (talkcontribs)

Did you set $wgMaxArticleSize?

Jman444 (talkcontribs)

It wasn't in my LocalSetting.php, I added with a large number 9999999999 and it didn't change anything.

GeorgeBarnick (talkcontribs)

Maybe try a smaller, more "realistic" size for $wgMaxArticleSize? The variable is in kilobytes, so the number you said you used is over 9000 gigabytes. Try 104857600, which is the equivalent of 100GB maybe. Not sure if that would have any effect on it.

Also, I've heard of similar issues like this and experienced them first-hand on a wiki I work at, where the issue is related to the lack of enough RAM on the server. How much RAM does the server you're using have, and do you know if you could increase it?

Daniel Mietchen (talkcontribs)

I just ran into the same problem, which could be fixed by reducing the MTU (cf. this how-to for OSX).

Rlaughton (talkcontribs)

I had the same problem, read the results here and posted my solution. It disappeared?

I use Google Chrome as my primary browser. After reading the results here I tried to also load the page with Microsoft Explorer. That solved the problem. I left the Google page open so I did not lose the information and copied it over to the same page open in Explorer. It loaded without problem and was then available on Chrome. is the page I am working on when the error appeared. (talkcontribs)

hi i am not able save the large amount of tabular format data in mediawiki could you please find out the way and do the needful thanks

Ciencia Al Poder (talkcontribs)

What's your issue? Could you please describe with details any error message you get or what happens?

Cavila (talkcontribs)

For the record. The error message refers to an "edit form". Are you perhaps using Semantic Forms or some other extension enabling you to edit content through a form? I(If so, that would be an important bit of information)

Ahbejuan (talkcontribs)

haha. I just had a problem by the same description. It was my typo in php.ini.

post_max_size = 200MB

// Should not have a B at the end or it's interpreted as 200 bytes. (talkcontribs)


if you somehow still get this error, check if the line

post_max_size = 200M

exists in you php.ini. if not adding this line will solve this issue. i had this issue. accidentally removed the line.

Reply to "Articles will not save if they are large"

Cannot start editing (create) Common.css

B.Shapoval (talkcontribs)

When I type mysitename/mediawiki/w/index.php?title=MediaWiki:Common.css (or MediaWiki:Common.css in serachbox) it shows "Internal Error". Lower in my language someyhing like "[WXcnzmRZrap6EUtZM1v@VwAAAUo] 2017-07-25 11:13:18: Exception cannot be solved «Symfony\Component\Process\Exception\RuntimeException» (Italic is my translation, not exactly). What can I do with this? MediaWiki:Sidebar is working at the same time.

AhmadF.Cheema (talkcontribs)

Do you have syntaxhighlighting enabled?

B.Shapoval (talkcontribs)

It is seen in Special:Version. How does it help me?

AhmadF.Cheema (talkcontribs)

Did you install the extension from Git?

If you did, then it requires composer installation too. Through SSH change to the directory containing the extension and run the following commands:

chmod a+x /pygments/pygmentize
composer install

If composer install, had been run once before and this time the extension was updated then run: composer update.

Reply to "Cannot start editing (create) Common.css"