Ah that would be it then thank you, 1.33.4
If it's a fresh install ish, with only the above extension trying to be added, would there be any issue with updating it to latest as far as you know? by changing the setting to true in the template

On 8/8/2022 at 10:40 PM, d8sychain said:

@Eddyall I looked at the extension, from what I can tell it is for MediaWiki version 1.37.0 and above. So unless you've updated the MediaWiki version that is packaged in the docker container then it's probably not compatible.

 

Hello me again, I installed your Beta version of the docker but it is still using a version of Mediawiki too low to get the Infobox extension running (1.37 and up). Is there a way from the template or the like to get a newer version of Mediawiki so I can get the extension working?

If not... may I ask for an update pretty please?

Has anyone done a manual upgrade to get the newest version?

Installation went easy and have access to the wiki but the issue is uplaoding files i get the message "mwstore://local-backend/local-public/e/e0/

Checked settings but cannot figure out the issue  any help would be greatly appreciated

Can't figure out for the life of me how to put an image or video in here. A Youtube video, or picture from a web address.
Also, the whole wiki becomes unusable when trying to install and enable a skin.
All instructions were followed.

https://www.mediawiki.org/wiki/Extension:DarkMode

and https://www.mediawiki.org/wiki/Skin:DarkVector

 

Any pointers would be greatly appreciated!

Extension:DarkMode show MediaWiki version 1.38+.

Skin:DarkVector specifies using a different branch for MediaWiki depending on the version "(for MW 1.39 and above use mw-1.39 branch, for MW 1.34 and below use mw-1.34 branch)"

This docker image is MediaWiki version 1.33.1 and PHP version 7.3.10

Searching Google suggests that '$wgVirtualRestConfig' in 'LocalSettings.php'. However if you're using my docker it will be in a different file 'LocalSettings_Extensions.php'

https://m.mediawiki.org/wiki/Manual:$wgVirtualRestConfig

Here is what mine looks like just as an example.

$wgVirtualRestConfig['modules']['parsoid'] = array('url' => 'http://localhost:8142','domain' => 'localhost','prefix' => '') ;

I'm not sure if it's part of the visual editor plugin i'm using but can the review process be disabled when edit a page?

Hi,

Thought i would give this a go since i could do with mediawiki to allow me to chart progress and docs on several things i am trying to do.

Installed (asked for it to create it's own DB), and off it went. All done.

Went to the Webui, and just a blank page - couldnt even get to the MediaWiki installer... Logs just show 301 error when the page is accessed.

Is anyone able to advise if this still installs please?

 

 

Hi,

I seem to be getting this error

"Error creating thumbnail: File missing"

Sometimes the images load sometime not.

Any help would be appreciated.

Jay

It appears that this is the only support for d8sychain's Mediawiki image so hopefully I am not wasting my time with a forum that sees no users..

I had been running the same Mediawiki image in my environment for six years now and haven't had a single issue. I cannot recall the version, as last week I had to migrate my Docker environment to a new pool I had built. My instance runs a separate MariaDB container, both of which are on a private network in Docker, which is behind NGINX (Let'sEncrypt/SWAG from LS.io). I mention those facts though the relevance may be negligible.

After moving my Dockers, I am only able to get a 500 back, whether I try to access via the IP address or the FQDN through the proxy. In my troubleshooting, I switched to the latest version which I think screwed me. I notice the env variable is for HTTP, which I have never used to access Mediawiki, in fact Nginx is set to issue permanently redirect via 80. I am not sure when that changed but I have been playing with config and adjusting ports with no luck. I also see that somewhere along the line, this container has been set to use an internal database? I am assuming since my config files point to a different IP for the database, that should not be an issue. Can anyone point me in the right direction of what to troubleshoot further?

To add, it does appear that things are operational on the backend and this appears to me to be an issue with the web server. See below logs, which begin following typical startup. Thanks in advance!

[services.d] done.
{"name":"parsoid","hostname":"dc4f34a09752","pid":392,"level":30,"levelPath":"info/service-runner","msg":"master(392) initializing 4 workers","time":"2026-01-19T17:18:42.811Z","v":0}
{"name":"lib/index.js","hostname":"dc4f34a09752","pid":410,"level":30,"levelPath":"info","msg":"loading ...","time":"2026-01-19T17:18:44.761Z","v":0}
{"name":"lib/index.js","hostname":"dc4f34a09752","pid":410,"level":30,"levelPath":"info","msg":"ready on :8142","time":"2026-01-19T17:18:44.800Z","v":0}
{"name":"lib/index.js","hostname":"dc4f34a09752","pid":421,"level":30,"levelPath":"info","msg":"loading ...","time":"2026-01-19T17:18:46.653Z","v":0}
{"name":"lib/index.js","hostname":"dc4f34a09752","pid":421,"level":30,"levelPath":"info","msg":"ready on :8142","time":"2026-01-19T17:18:46.685Z","v":0}
{"name":"lib/index.js","hostname":"dc4f34a09752","pid":432,"level":30,"levelPath":"info","msg":"loading ...","time":"2026-01-19T17:18:48.407Z","v":0}
{"name":"lib/index.js","hostname":"dc4f34a09752","pid":432,"level":30,"levelPath":"info","msg":"ready on :8142","time":"2026-01-19T17:18:48.438Z","v":0}
{"name":"lib/index.js","hostname":"dc4f34a09752","pid":443,"level":30,"levelPath":"info","msg":"loading ...","time":"2026-01-19T17:18:50.169Z","v":0}
{"name":"lib/index.js","hostname":"dc4f34a09752","pid":443,"level":30,"levelPath":"info","msg":"ready on :8142","time":"2026-01-19T17:18:50.203Z","v":0}
{"name":"parsoid","hostname":"dc4f34a09752","pid":392,"level":40,"levelPath":"warn/service-runner","msg":"startup finished","time":"2026-01-19T17:18:50.206Z","v":0}