Topic on Project:Support desk

Hi, I installed media wiki 1.31.1 on my server using Softaculous. When installation was complete and I started to set up my page, no images, including the default logo were displaying.

I removed the installation, database, and all files. I re-tried installing manually by downloading from your website, uploaded, extracted the files, set up a new database, and installation was successful. However, I am still having the same problems.

I do not understand what's going on as I've used previous versions of MediaWiki on my server and not had this problem. Can you please provide some assistance?

The URL to my wiki is https://bible.elgrandoc.uk

"We can’t connect to the server at bible.elgrandoc.uk."

Manual:Errors and symptoms#The wiki appears without styles applied and images are missing

I have the same problem (Edited the info as it is not relevant anymore)

The error seems to come from the use of "srcsets". On my instance instead of generating a 1.5x src (in src set) it generates a 1,5x src, which is understood by the browser as a 1 and another set which contains 5x, etc. I tried to put my instance in English but it does not seem to solve the problem…

<img alt="Logo-rg.png" src="[myserver]/images/thumb/Logo-rg.png/64px-Logo-rg.png" srcset="[myserver]/images/thumb/Logo-rg.png/96px-Logo-rg.png 1,5x, [myserver]/images/thumb/Logo-rg.png/128px-Logo-rg.png 2x" width="64" height="64">

That does come from the srcsets… I have not solved it (as it should not be a problem), but I have contained the problem by setting $wgResponsiveImages = false; in LocalSettings.php. --Loizbec (talk) 18:01, 21 October 2018 (UTC)

The problem about srcsets is a known one. See Manual:Errors and symptoms#Image Thumbnails not working and/or appearing

Thanks a lot for mentioning the insight. Now I can improve my almost “solution” to the problem :)
(a proper solution would be not having to alter the locale, to install the system).

Since it is an expected error when upgrading to 1.31, I would tend to think that it would be a good idea to point to that error in the upgrading manual as it would probably save a lot of time to some people (at least 2 only in this page would have saved hours…). It would also be useful in the installation guide, I'm not sure whether the default localsettings/installation script do that. I don't have the editing rights to modify those pages… Maybe you do know someone who does ;)