Project:Support desk

My previous attempt to solve an issue with my wiki made some progress and fixed a few errors, but turned up a new one: "Lua error: bad argument #1 to "get" (not a valid title)." The suggestions in the related threads I found (1, 2) mention "JsonConfig", but I've enabled both "JsonConfig" and "JsonConfigLuaSupport" in LocalSettings and have installed the "REL1_43" (1.2.0) version of the former and the error remains. The following is the backtrace:

1. (tail call): ?
2. [C]: in function "error"
3. MWServer.lua:81: ?
4. (tail call): ?
5. (tail call): ?
6. Module:TNT:162 : in function "loadData"
7. Module:TNT:181 : ?
8. (tail call): ?
9. (tail call): ?
10. Module:Uses_TemplateStyles:21 : in function "renderBox"
11. Module:Uses_TemplateStyles:111 : ?
12. (tail call): ?
13. mw.lua:527: ?
14. (tail call): ?
15. [C]: in function "xpcall"
16. MWServer.lua:99: in function "handleCall"
17. MWServer.lua:313: in function "dispatch"
18. MWServer.lua:52: in function "execute"
19. mw_main.lua:7: in main chunk
20. [C]: ?

Any idea what to do to solve this? –Noha307 (talk) 23:44, 6 October 2025 (UTC) Reply

I tried creating a file named "CommonSettings.php" in the "public_html/w" folder and copy-pasting the code from a page on phabricator into it and adding either "require_once("public_html/w/CommonSettings.php");" or "require_once("CommonSettings.php");" to "LocalSettings.php" based on the instructions on Manual:CommonSettings.php, but it didn't work. –Noha307 (talk) 04:11, 20 October 2025 (UTC) Reply

@Noha307: If you aren't aware of it yet, you might have a look at your site's Category:Pages with script errors page since it collects where Lua errors appear.

For example, it lists this page which points to a missing extension, TitleBlacklist, that may help you resolve part of the problem. -- ☠MarkAHershberger ☢(talk)☣ 14:09, 21 October 2025 (UTC) Reply

I'm suffering from the exact same lue error/backtrace message. I also required TitleBlacklist - which I enabled and fixed it's associated error message - but this hasn't fixed the inital Lua error: bad argument #1 to "get" (not a valid title) error. @Noha307, have you been able to fix the issue? ~2025-30174-48 (talk) 22:17, 26 October 2025 (UTC) Reply

@~2025-30174-48 I did the same – download and enable TitleBlacklist – and it didn't fix the Lua error either. I haven't had a chance to browse the pages with script errors category in detail yet though. Would it be possible for you to link to your wiki so I could compare? –Noha307 (talk) 23:56, 26 October 2025 (UTC) Reply

My wiki looked the exact same as yours with the same errors and backtraces - I've solved the issue by fixing the Json extension config in my LocalSettings.

I changed it to the code below from another support thread on here and the error is resolved:

// Safety: before extension.json, these values were initialized by JsonConfig.php if ( !isset( $wgJsonConfigModels ) ) { $wgJsonConfigModels = []; } if ( !isset( $wgJsonConfigs ) ) { $wgJsonConfigs = []; } $wgJsonConfigEnableLuaSupport = true; // https://www.mediawiki.org/wiki/Extension:JsonConfig#Configuration $wgJsonConfigModels['Tabular.JsonConfig'] = 'JsonConfig\JCTabularContent'; $wgJsonConfigs['Tabular.JsonConfig'] = [ 'namespace' => 486, 'nsName' => 'Data', // page name must end in ".tab", and contain at least one symbol 'pattern' => '/.\.tab$/', 'license' => 'CC0-1.0', 'isLocal' => false, ]; // Enable Tabular data namespace on Commons - T148745 $wgJsonConfigInterwikiPrefix = 'commons'; $wgJsonConfigs['Tabular.JsonConfig']['remote'] = [ 'url' => 'https://commons.wikimedia.org/w/api.php' ]; ~2025-30174-48 (talk) 20:56, 27 October 2025 (UTC) Reply

@~2025-30174-48: Thank you so much! Adding that code seems to have fixed it – or at least the most immediate error anyway. I particularly appreciate you specifying which file it goes in as well.

I'm still getting a "the time allocated for running scripts has expired" error after the reflist template loads 66 references, but at least its getting to that point now. –Noha307 (talk) 03:56, 2 November 2025 (UTC) Reply

┌───────────────────────┘
So, according to one thread, I need to change max execution time, which can be found in php.ini. (Although I am suspicious because it seems like it shouldn't take that long to load 66 references. Could there be another cause, such as a missing template or extension that could prolong it?) However, a different page seems to suggest that the change can be made to LocalSettings.php. While I do know where the latter file is, I don't how I should change it. What code do I need to add? –Noha307 (talk) 01:24, 3 November 2025 (UTC) Reply

@Noha307: Sorry for the late reply, but you should be able to use set_time_limit() in your LocalSettings.php. If you really want to set max_execution_time in your LocalSettings.php, you can do that like so:

ini_set("max_execution_time", 120);

--☠MarkAHershberger ☢(talk)☣ 01:36, 12 November 2025 (UTC) Reply

Hello, I would like to make the sidebar in Vector 2022 visible to all users by default. Right now, it's hidden from anonymous users. How can I change that? Adding $wgVectorDefaultSidebarVisibleForAnonymousUser = true; or $wgVectorFeatures = array( 'collapsiblenav' => array( 'global' => false, 'user' => false) ); to LocalSettings.php doesn't seem to work for me; neither does adding #sidebar {display: block !important;} to Common.css seem to work. Any ideas? Thanks, cheers and all the best! Till Kraemer (talk) 16:07, 17 October 2025 (UTC) Reply

@Till Kraemer, I think you want to look at Menu Pinning Options. I'm not sure where you got the idea for $wgVectorDefaultSidebarVisibleForAnonymousUser from since that isn't anywhere on this site. --☠MarkAHershberger ☢(talk)☣ 01:34, 20 October 2025 (UTC) Reply

@MarkAHershberger, thank you for your reply! Hmm, it looks like the menu pinning options only affect logged-in users, though, and are already set the way I want them by default. I'm looking for an option to show the menus exactly the same way to anonymous users who aren't logged in. I've found the $wgVectorDefaultSidebarVisibleForAnonymousUser setting on Google and apparently it worked for some people one point in time; the AI Overview still suggests to use that setting, but it doesn't work for me. Till Kraemer (talk) 12:17, 20 October 2025 (UTC) Reply

@Till_Kraemer ALWAYS double-check anything the AI Overview gives you (especially as long as it is using a large language model with generative AI—those things are notorious for making up stuff). Especially if it doesn't work, look to make sure it is actually a thing.

$wgVectorDefaultSidebarVisibleForAnonymousUser cannot be found on mediawiki.org (search) and the only reference I can find to it in code search seems spurious (and may be the source of Google's hallucination).

Tracked in Phabricator
Task T366999

With regards to the menu pinning options, I admit I did not test it when I first mentioned it to you, but I just tried setting $wgDefaultUserOptions['vector-appearance-pinned'] = 0; on a site that I had and that menu disappeared. The other options do not appear to work, though. I feel like this is a bug, though, so I've filed one (which was then closed as a duplicate of task T366999). --☠MarkAHershberger ☢(talk)☣ 00:39, 21 October 2025 (UTC) Reply

@MarkAHershberger: Thanks for pointing out that old config variable, I'm removing it from wikispore-config. It was removed from Vector in Gerrit change 904204. Sam Wilson 00:57, 21 October 2025 (UTC) Reply

@MarkAHershberger, thank you so much for your research, the testing and the bug report! It would be so cool to have those options working. In the meantime, there might be a workaround with CSS, but I can't get that to work either, so I just wait for the bug fix. Till Kraemer (talk) 09:55, 21 October 2025 (UTC) Reply

Since settings like $wgDefaultUserOptions['vector-main-menu-pinned'] = 1; currently don't seem to have any effect on anonymous users, is there another way to achieve the default pinned menu state, like on https://sanat.csc.fi/ - maybe via MediaWiki:Common.js? Till Kraemer (talk) 21:31, 2 November 2025 (UTC) Reply

PS: It seems to be that code. Till Kraemer (talk) 07:30, 3 November 2025 (UTC) Reply

I took the liberty of adding this approach to the menu pinning options. Till Kraemer (talk) 08:15, 3 November 2025 (UTC) Reply

Hello, On the https://joinfediverse.wiki (running MW 1.41.0) we'd like to completely turn off open registrations and only allow registrations with an individual invite-link.
Is that somehow possible and could you point me to the right way forward?
Thanks. PKFP (talk) 15:09, 30 October 2025 (UTC) Reply

@PKFP Set the user rights to disable creating accounts by everyone except admins (which you should be part of). Then you can use Special:CreateAccount when you want to add someone to the wiki - they'll be sent their invitation (such as temp password) by email. Leaderboard (talk) 05:31, 5 November 2025 (UTC) Reply

Thanks. That was easy. Seems to work fine. This topic can be closed. PKFP (talk) 04:54, 7 November 2025 (UTC) Reply

Also read Manual:Preventing access. – Ammarpad (talk) 14:56, 6 November 2025 (UTC) Reply

@PKFP: also see the ConfirmAccount extension if you don't mind installing an extension. This extension allows people to request an account from a special page and gives you a centralized queue to manage the requests. --☠MarkAHershberger ☢(talk)☣ 01:41, 12 November 2025 (UTC) Reply

Hi! I've recently installed https://wiki.lilypond.community, a wiki for the LilyPond music typesetter (which is used on Wikipedia through Extension:Score). Pages consist of small snippets of LilyPond code, with explanatory comments and an image of the result. Is there any way to make the lists of search results (e.g., this) display these images? This would be very helpful for users to quickly finding snippets when they don't know the proper keywords. Jean Abou Samra (talk) 16:35, 31 October 2025 (UTC) Reply

@Jean Abou Samra: The SearchThumbs extension should do what you need. --☠MarkAHershberger ☢(talk)☣ 01:46, 12 November 2025 (UTC) Reply

Thanks a lot, this looks like exactly what I need. Unfortunately, it didn't work on my wiki after installing PageImages and SearchThumbs and running the maintenance script initImageData.php from PageImages as specified in the docs. I strongly suspect it's because the images on this wiki are not inserted with the normal wikitext markup but as inline SVG using <img src="data:image/svg+xml;base64,...">. This is because they're generated by an extension I wrote myself (relevant part of the code here), not MediaWiki's Extension:Score, because this wiki has somewhat peculiar needs. While writing the extension I found it much simpler to just inline the SVG than figure out how to store the images as files and delete the old images when music inputs change. What do you think is the easiest way out of this? Jean Abou Samra (talk) 16:10, 14 November 2025 (UTC) Reply

LS,

Version 1.44

In a page I made a call to a template called {{Piup | 9} This template looks like:

{{#switch: {{lc:{{{status|Unknown}}}}}</br>
| Unknown = {{=}}Pi Updaten= <!insert Header1 --></br>
| 2 = {{=}}{{=}}Pi Updaten== <!insert Header1 --></br>
| 9 = '''Uw PI updaten/upgraden''' <!insert Header in bold text --></br>
}}</br>

But it returns nothing to the caling page. So questiom, am I missing something and if so what???

Regards Harry Gharryh1957 (talk) 22:18, 2 November 2025 (UTC) Reply

Are the br tags in your actual code or did you just add them for this?

You're sending an unnamed parameter "9" (which the template would see as {{{1}}}) but the switch is testing a non-existent named parameter {{{status}}}, or rather it's testing the string "Unknown", possibly followed by a br tag.

What happens when you add a default row at the end, like |#default=DEFAULT TEXT HERE? Jonathan3 (talk) 20:06, 5 November 2025 (UTC) Reply

Why do pages sort in non-alphanumeric order like this in categories?

• Foo 10
• Foo 8
• Foo 9

The only workaround seems to be adding a sort key to each category reference. ~2025-30714-69 (talk) 09:22, 3 November 2025 (UTC) Reply

Category sorting is alphabetic, not alphanumeric. See Help:Categories and Manual:$wgCategoryCollation --Clump (talk) 13:08, 3 November 2025 (UTC) Reply

Manual:$wgCategoryCollation#Numeric_sorting. For Wikimedia, you can find all wiki's that have numeric sorting enabled, by going to https://noc.wikimedia.org/conf/InitialiseSettings.php.txt and looking for all wiki's that have a collocation configured that ends with "-u-kn". —TheDJ (Not WMF) (talk • contribs) 13:53, 3 November 2025 (UTC) Reply

مشکل ورود به حسابم و نمی‌تونم حساب را بازیابی کنم ~2025-31060-99 (talk) 15:56, 3 November 2025 (UTC) Reply

@~2025-31060-99: What have you tried? If your account doesn't have an email address associated with it, there isn't anything we can do. --☠MarkAHershberger ☢(talk)☣ 01:57, 12 November 2025 (UTC) Reply

I have just migrated my wiki from an old version to version 1.44. It has all gone well except that I still have a bold red line around my logo and the link for the Main Page. I assume these were there to remind you to change the logo, which I have done, so how do I get rid of the lines? Here is a link to my wiki: JP1 Remotes Wiki Thanks. Robman94 (talk) 22:04, 3 November 2025 (UTC) Reply

@Robman94 Not sure what you are trying to say - please clarify. Leaderboard (talk) 05:30, 5 November 2025 (UTC) Reply

Are you able to click on the link to my wiki? If so, it should be obvious what I am describing. Robman94 (talk) 19:03, 5 November 2025 (UTC) Reply

@Robman94 No, it is not obvious as I cannot see some red line around some logo after clicking on your link. Please be more specific where you see what, provide a screenshot, inspect the problem via your web browser's development tools, etc. Thanks! Malyacko (talk) 20:58, 5 November 2025 (UTC) Reply

Here is a screenshot: wzVcrVL.png (×ばつ1042) Robman94 (talk) 22:01, 5 November 2025 (UTC) Reply

Are you familiar with what a fresh install of Mediawiki looks like? The default logo and the link to the main page both have think red lines around them, presumably to remind you to change them. The question is, what is supposed to make them go away once you do change them? The fact that you can't see them when you go to my wiki tends to imply that the code that generates the red lines must be stored locally in the cache or something, but I've done ?action=purge already and that didn't clear it. Does anyone here know how that line is generated and how to clear it? Robman94 (talk) 13:55, 6 November 2025 (UTC) Reply

I have never seen those red lines before on any new install, and I'm not seeing them in YOUR wiki neither. However, you can try to inspect them with the browser's developer tools (hit the F12 key in your keyboard) and try to locate from which CSS it comes from. Ciencia Al Poder (talk) 22:31, 6 November 2025 (UTC) Reply

Yeah, I brought up the wiki on a different browser (Firefox) and I don't see them there either, but I do see them using Chrome and Edge. You can see them on the screenshot thought, right? (talk) 02:01, 7 November 2025 (UTC) Reply

@Robman94: Maybe you have an extension installed in Chrome that causes the border? I see it in the screenshot, but when I visit in Chrome, I don't see it.--☠MarkAHershberger ☢(talk)☣ 02:03, 12 November 2025 (UTC) Reply

I am using 1.41.1, and I tried following the manual and uploaded 1.44.2 to my files and moved all the important stuff there, but my wiki just crashes. I thought it might be the extensions not being up to date so I disabled them, still doesn't work. I am quite inexperienced in this sort of thing, so any help is greatly appreciated!

Also, I can't revert back to 1.41.1 with my backups because the Scribunto extension wouldn't match for some reason and there's nowhere to find the 1.41 Scribunto version, only 1.39, 1.43 and 1.44, so Scribunto lua templates would be broken if I reverted back. Please help! Tang Empire (talk) 05:23, 4 November 2025 (UTC) Reply

@Tang Empire Regarding the 1.41 Scribunto, download wikimedia/mediawiki-extensions-Scribunto at wmf/1.41.0-wmf.15 instead. Leaderboard (talk) 08:17, 4 November 2025 (UTC) Reply

Thank you. By the way, do you have any visual/beginner tutorials on how to upgrade? Because I seriously don't know what I did wrong, and I hope that my wiki will be fixed soon. Tang Empire (talk) 15:47, 4 November 2025 (UTC) Reply

Without more information, hard to tell sorry. Leaderboard (talk) 05:29, 5 November 2025 (UTC) Reply

"tutorials on how to upgrade" - Manual:Upgrading.

"uploaded 1.44.2 to my files and moved all the important stuff there" - I think it's considered better to do it the other way round, i.e. extract the MW files to a new directory then move the important stuff you want to keep to that new directory. Jonathan3 (talk) 20:10, 5 November 2025 (UTC) Reply

Yes, that is what I did, I uploaded 1.44 and moved/replaced stuff like Images and LocalSettings into the 1.44 folder. Also regarding Manual:Upgrading, I couldn’t understand a lot of the language so I asked ChatGPT to simply. I followed these instructions:

You’re replacing your old MediaWiki files with the new ones, but you must not just dump them on top of the old folder.

Instead, you:

Put the new version in a separate, empty folder.

Copy your important stuff from the old folder into it.

Then rename or swap the folders so the new one becomes your live wiki.

1. Back up everything

Make a copy of:

Your database (via phpMyAdmin or mysqldump)

Your old wiki folder, including LocalSettings.php, the images/ folder, and any custom skins/extensions.

2. Download the new version

If you can use the command line (SSH):

That creates a new folder like mediawiki-1.44.2.

If you can’t use command line:

Download the .tar.gz file to your computer.

Extract it using 7-Zip.

Upload the extracted folder to your server using FTP or cPanel File Manager, then extract it there.

3. Move your old settings & content

Inside your old wiki folder, copy these into the new folder:

LocalSettings.php, Images, custom Skins, custom extensions

4. Swap folders

Once your new folder has all the copied content:

Rename your old wiki folder (for example, wiki-old).

Rename your new one to the same name as the old one (for example, wiki).

This way your web address doesn’t change.

5. Fix permissions

Make sure the web server can read/write what it needs:

(Replace apache with your web user if needed.)

6. Run the update script

Go to your wiki folder in command line and run it

This updates your database to work with the new version.

7. Test

Visit your wiki and check Special:Version — it should say 1.44.2. Tang Empire (talk) 20:23, 5 November 2025 (UTC) Reply

Looks right at a glance.

Compatibility says that MW1.44 wants PHP 8 whereas 1.41 is happy with PHP 7.4. There's a difference in SQLite compatibility too.

If you really backed up all your files and the database I don't understand why it wouldn't work again (they do say you haven't backed up until you've checked you can restore, or something like that).

Did you get any error messages when running the update script?

What exact files and folders did you move across?

Can you describe "my wiki just crashes"? Jonathan3 (talk) 13:36, 6 November 2025 (UTC) Reply

Well, in some attempts the update script won't work and just have no reaction, other times it would work. I moved across LocalSettings.php, Skins folder, Extensions folder, Images folder.

By "my wiki just crashes", I mean that my wiki would not load and say "(wiki) can't candle the request right now". I can't remember which error message.

I only have backups once a week, and I've already successfully reverted back to 1.41 using the 1.41 Scribunto this discussion provided, so my site could work again. I might try again next week, and look into SQLite, but I've checked PHP and it's larger than 8. Tang Empire (talk) 15:38, 6 November 2025 (UTC) Reply

Good luck next time! Keep a note of exactly what steps you take and exactly what happens, just in case you need to ask again. Jonathan3 (talk) 21:30, 6 November 2025 (UTC) Reply

P.S. I think that's the HTTP 500 error. There are web pages with ideas on how to deal with that generally. It's mentioned here too: Manual:Common_errors_and_symptoms#HTTP_500_Internal_Error_during_installation. Jonathan3 (talk) 21:33, 6 November 2025 (UTC) Reply

hi again. I tried upgrading again, and you were right, it was a http 500 error. here is what i did step by step, do you perhaps know how to fix it? :

1. run

cd /path/to/your/wiki-parent-folder

wget https://releases.wikimedia.org/mediawiki/1.44/mediawiki-1.44.2.tar.gz

tar xvzf mediawiki-1.44.2.tar.gz

rm mediawiki-1.44.2.tar.gz

into the command line

2. move LocalSettings.php, images, extensions, and skins into mediawiki 1.44.2 folder while overwriting the original 1.44.2 ones.

3. Rename 1.44.2 to public_html and the old one to old

4. run

find ./images -type d -exec chmod 755 {} \;

chown -R apache:apache images

in command line (ran through many file names, all followed by "operation not permitted")

5. run update script

6. get http error 500. run the

find . -type f -exec chmod 644 {} \;

find . -type d -exec chmod 755 {} \;

because i got the error after i ran the update script (i didnt check before). nothing happens.

7. run it again, and this time it gave me something. here is the interaction:

[(me) public_html]$ find . -type f -exec chmod 644 {} \;

find: ‘.’: Permission denied

find: Failed to restore initial working directory: /home/(user)/domains/heterodontosaurus-balls.com/public_html_old: Permission denied

[(me) public_html]$ find . -type d -exec chmod 755 {} \;

find: ‘.’: Permission denied

find: Failed to restore initial working directory: /home/(user)/domains/heterodontosaurus-balls.com/public_html_old: Permission denied Tang Empire (talk) 03:20, 10 November 2025 (UTC) Reply

ok I solved it! I forgot to change the permissions in the public_html_old folder, and there were a couple of outdated extensions. Tang Empire (talk) 21:25, 11 November 2025 (UTC) Reply

1) I'm not the host/bureaucrat, just the mediawiki admin for some wiki.

2) Due to a little spam issue I blocked some spammers (or potential spammer).

3) Learned later that some legit user also got blocked.

4) At this point I got the blocked IP address. Which was in the Private IP range (172.16.x.x .. 172.31.x.x) (this was a potential spammer case)

5) As admin only, I do not know in advance what IP is going to be blocked when I block some spammer (or potential spammer)

Anything I, or the wiki-host(private), can do here ? (other than giving me additional rights)

Anything I can tell the users to do that might be effected by such a Private IP range block. Like, I don't know, maybe how they should adjust there lan/router/modem/??? so mediawiki will not log them as coming from such a Private IP address?

MvGulik (talk) 21:17, 6 November 2025 (UTC) Reply

This looks like the wiki is behind a reverse proxy, and the wiki hasn't been configured correctly to detect the private IP as the reverse proxy (see $wgCdnServersNoPurge and $wgCdnServers) and use the X-Forwarded-For header as the real IP from users. Ciencia Al Poder (talk) 22:35, 6 November 2025 (UTC) Reply

Forwarded to host.

(Will report result although that might take a bit of time)

Thanks. MvGulik (talk) 23:46, 6 November 2025 (UTC) Reply

Thanks again. Problem was fixed. Although in this case it was reported as a problem with it picking up a local docker IP. MvGulik (talk) 11:43, 7 November 2025 (UTC) Reply

I signed up by mistake can someone please delete my account Oliver croll (talk) 23:19, 6 November 2025 (UTC) Reply

See meta:Account vanishing Ciencia Al Poder (talk) 17:01, 7 November 2025 (UTC) Reply

I'm trying to add a new category in Module:Message box/doc exactly like this:

[[Category:Testing Modules]]

<includeonly>{{Sandbox other||
<!-- Categories below this line; interwikis at Wikidata -->
[[Category:Modules{{#translation:}}]]
[[Category:Testing Modules]]
}}</includeonly><noinclude>
[[Category:Module documentation pages{{#translation:}}]]
</noinclude>
| #default=
{{#invoke:Template translation|renderTranslatedTemplate|template=Module:Message box/doc|noshift=1|uselang={{int:lang}}}}
}}

But this new category isn't visible in the category list in the Module:Message box.

Am I doing something wrong or is this a bug in the module?

I repeated "translate:" and "purge" but that didn't help solve the problem. Kszwaba (talk) 14:02, 12 November 2025 (UTC) Reply

Project:Support desk/* Module:Message box/doc - transclusion not working */ Reply ~2025-32806-54 (talk) 02:14, 13 November 2025 (UTC) Reply

Did you actually install the Translate extension? If not, you should remove all the #translation bits and anything related to it. The version of the doc from the English Wikipedia is much easier to adapt to third party wikis. Tactica (talk) 03:30, 13 November 2025 (UTC) Reply

My version Mediawiki is 1.43.1 and Module:Message box: 16:31, 2 September 2023 Module:Message box>Pppery 18,558 bytes +18,558

I updated from 1.43.1 to 1.44.2 and noticed this message at the end:

PHP Warning: Undefined array key "directory" in /var/www/html/w/includes/filebackend/FileBackendGroup.php on line 133

The wiki seems to be working ok, if maybe a little slower than before. I then went and upgraded PHP from 8.1 to 8.3. The message is still the same. What does this mean? Buster2223 (talk) 23:08, 13 November 2025 (UTC) Reply

OK I am fairly sure that this is slowing down the wiki. Images that used to load instantly now take a second, and large pages are delayed by several seconds. My guess is that the primary path to the images doesn't work, then it looks for a fallback and finds it.

The documentation is fairly non-existent on Manual:FileBackendGroup.php.

Could someone please help on this? Buster2223 (talk) 17:39, 16 November 2025 (UTC) Reply

I updated this wiki instance a while back, currently running REL1_43 and the specialpages throw this error;

```

[aRevfSkKRKsH1Ux47UpwvQAAAG4] /go/Special:SpecialPages ArgumentCountError: Too few arguments to function MediaWiki\Specials\SpecialRenameUser::__construct(), 0 passed in /srv/www-sugarlabs/wiki/vendor/wikimedia/object-factory/src/ObjectFactory.php on line 240 and exactly 7 expected

Backtrace:

from /srv/www-sugarlabs/wiki/includes/specials/SpecialRenameUser.php(48)

#0 /srv/www-sugarlabs/wiki/vendor/wikimedia/object-factory/src/ObjectFactory.php(240): MediaWiki\Specials\SpecialRenameUser->__construct()

#1 /srv/www-sugarlabs/wiki/vendor/wikimedia/object-factory/src/ObjectFactory.php(149): Wikimedia\ObjectFactory\ObjectFactory::getObjectFromSpec()

#2 /srv/www-sugarlabs/wiki/includes/specialpage/SpecialPageFactory.php(1559): Wikimedia\ObjectFactory\ObjectFactory->createObject()

#3 /srv/www-sugarlabs/wiki/includes/specialpage/SpecialPageFactory.php(1594): MediaWiki\SpecialPage\SpecialPageFactory->getPage()

#4 /srv/www-sugarlabs/wiki/includes/specials/SpecialSpecialPages.php(61): MediaWiki\SpecialPage\SpecialPageFactory->getUsablePages()

#5 /srv/www-sugarlabs/wiki/includes/specials/SpecialSpecialPages.php(50): MediaWiki\Specials\SpecialSpecialPages->getPageGroups()

#6 /srv/www-sugarlabs/wiki/includes/specialpage/SpecialPage.php(728): MediaWiki\Specials\SpecialSpecialPages->execute()

#7 /srv/www-sugarlabs/wiki/includes/specialpage/SpecialPageFactory.php(1724): MediaWiki\SpecialPage\SpecialPage->run()

#8 /srv/www-sugarlabs/wiki/includes/actions/ActionEntryPoint.php(504): MediaWiki\SpecialPage\SpecialPageFactory->executePath()

#9 /srv/www-sugarlabs/wiki/includes/actions/ActionEntryPoint.php(146): MediaWiki\Actions\ActionEntryPoint->performRequest()

#10 /srv/www-sugarlabs/wiki/includes/MediaWikiEntryPoint.php(200): MediaWiki\Actions\ActionEntryPoint->execute()

#11 /srv/www-sugarlabs/wiki/index.php(58): MediaWiki\MediaWikiEntryPoint->run()

#12 {main}

```

This upgrade was done some months back, any help would be appreciated. ~2025-33486-35 (talk) 23:11, 14 November 2025 (UTC) Reply

Is there a RenameUser extension in your extensions directory ? Try disabling and removing that, it got merged into core at some point. —TheDJ (Not WMF) (talk • contribs) 09:19, 15 November 2025 (UTC) Reply

Hi, since I am not familiar with tech-savy stuff and being new to coding in general, I don't know how to run a seperate wiki website. I already downloaded and extracted the file in mobile. I tried to throughly read the process multiple times but it seemed too complicated for me. The thing I need help with is the uploading the files to the web server. Does anyone help me with the basics of installing MediaWiki on Android mobile? VoitieVelocity (talk) 01:59, 15 November 2025 (UTC) Reply

@VoitieVelocity: Which web server? You're going to need MySQL or another database server as well Jasper Deng (talk) 06:27, 15 November 2025 (UTC) Reply

I don't know what web server to use and I don't know how to use a database server, it is so complicated. VoitieVelocity (talk) 07:05, 15 November 2025 (UTC) Reply

Yes, running/hosting a webserver from scratch is indeed complex. I would say that it is very hard to do from a mobile device, i would suggest to use a desktop machine for any serious work where you need lots of information to look at and to enter.

Alternatively you might consider using a 3rd party wiki hosting service like miraheze or another wiki farm. —TheDJ (Not WMF) (talk • contribs) 09:15, 15 November 2025 (UTC) Reply

Welp, I tried making articles for a certain specific topic in English Wikipedia, but it takes time for the draft to get accepted into being a full article and some things may not be considered notable. So I might consider making a seperate wiki website, so that the things related to the topic that are not considered notable would get moved to the seperate wiki website instead. I have experience in using Fandom and I would like to say that it is hard to reach a lot of people since many people might not know the existence of other hosting services that hosts wikis besides Wikipedia. VoitieVelocity (talk) 09:51, 15 November 2025 (UTC) Reply

I might try finishing the draft again and see if that draft gets accepeted into being a full article in English Wikipedia. If that got declined as well, I think I won't likely to create a seperate wiki website using MediaWiki, I still go on Fandom to continue contributing to that unfinished wiki which needs a lot of improvements. Yeah, I am busy on Fandom because I edit a lot of wikis. VoitieVelocity (talk) 14:48, 15 November 2025 (UTC) Reply

Running a MediaWiki website on your own is inherently complex. There are some sites that offer fully-managed solutions for it, but it's rare, and you'll have to pay either way. Jasper Deng (talk) 22:21, 15 November 2025 (UTC) Reply