Jump to content

Project:Support desk

Add topic
From mediawiki.org
Welcome to the MediaWiki Support desk. This is a place where you can ask any questions you have about installing, using or administrating the MediaWiki software.

(Read this message in a different language)

See also

Before you post

Post a new question

  1. To help us answer your questions, please indicate which version of MediaWiki you are using, as found on your wiki's Special:Version page:
  2. If possible, add $wgShowExceptionDetails = true;error_reporting( -1 );ini_set( 'display_errors', 1 ); to LocalSettings.php in order to make MediaWiki show more detailed error messages.
  3. Please include the web address (URL) to your wiki if possible. It's often easier for us to identify the source of the problem if we can see the error directly.
  4. To start a new thread, click the box with the text "Add topic".

Template:MW file and Template:SettingSummary

[edit]

Template:MW file and Template:SettingSummary links to wmdoc:mediawiki-core/master/php are not working, i.e. where it says Classes: [[]]. Waddie96 (talk) 01:47, 14 August 2025 (UTC)Reply

Works for me here. Ciencia Al Poder (talk) 14:08, 23 August 2025 (UTC)Reply
@Ciencia Al Poder So when you click the link on Manual:Pager.php it takes you to https://doc.wikimedia.org/mediawiki-core/master/php/interfacePager.html and this loads? I get an error: Not Found. The requested URL was not found on this server..
Waddie96 (talk) 03:41, 1 September 2025 (UTC)Reply
I'm sure it worked when I posted the link. However, it does not now. But I've updated the page to make it work (the Interface has been namespaced, maybe the doc page was cached on the server, or it has been namespaced after I posted the message...). On the other hand, I couldn't fix ReverseArrayIterator because it doesn't exist anymore on master. Ciencia Al Poder (talk) 18:09, 1 September 2025 (UTC)Reply
Thanks Waddie96 (talk) 18:50, 1 September 2025 (UTC)Reply

Reference Formatting Error Redux

[edit]

After updating the citation template on my website to the newest version, I receive the error:

Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).

Last time I had a formatting error, I ended up updating the entire website. Is this something I have to do again?

Alternatively, a quick search found a page on a random wiki that mentions the exact same error I'm having. However, it seems to describe an error message that should appear on a case by case basis due to malformed parameters rather than on every single reference as it does in my situation. It does lead me to believe that something was changed in the template that caused the problem though. Any idea on how to fix this? –Noha307 (talk) 23:01, 19 August 2025 (UTC)Reply

Updating a template as complex as w:Template:Citation isn't necessarily a good idea if the template was working for you and suited your purposes. That said,
  1. you haven't copied Module:Citation/CS1/Suggestions to your site
  2. the w:Module:Citation Lua-based redirect pointing to Module:Cite (which you don't have anyway) is also missing
  3. the line with the error you quote appears to be related to trying to load a .tab file using InstantCommons, which I'm not sure is enabled in your site.
In general, ticking the "Include templates" box while exporting should help prevent at least most of these issues. Tactica (talk) 12:00, 23 August 2025 (UTC)Reply
@Tactica: To respond to a few points:
isn't necessarily a good idea if the template was working for you
The cite web, cite news, etc. was working, but the base "citation" was not. Point taken, however.
you haven't copied Module:Citation/CS1/Suggestions to your site
Apparently, I did have it, but to be fair hadn't been updated since it was initially uploaded.
Module:Cite (which you don't have anyway)
Unless I'm mistaken, I had it as well.
the w:Module:Citation Lua-based redirect pointing to Module:Cite...is also missing
This one was missing. I imported it. (I'm assuming this is why the "citation" template wasn't working.)
InstantCommons, which I'm not sure is enabled in your site.
I just checked my LocalSettings.php file and "$wgUseInstantCommons" is set to "true". So my understanding is that it should be enabled.
I've updated/added all of the templates/modules you mentioned, but it's still giving me the error.
Thanks for your help thus far. If you have further ideas on how to solve the problem I would greatly appreciate it. –Noha307 (talk) 01:22, 26 August 2025 (UTC)Reply
According to the error in the documentation for Module:Citation/CS1 you're missing the JsonConfig extension too. If you keep fixing the obvious errors eventually it should start working :)
BTW the "Citation" template is not the "base" template, it's just one that combines the features of others, a Swiss knife of sorts so to speak. In my own wiki I'm using Citation as the only Cite * CS1/CS2 template. Tactica (talk) 18:55, 26 August 2025 (UTC)Reply
@Tactica: Okay, so I've uploaded JsonConfig and enabled it by adding:
#Enable JsonConfig extension
wfLoadExtension( 'JsonConfig' );
to LocalSettings.php. However, I was still seeing the message:
Lua error in Module:TNT at line 159: Missing JsonConfig extension; Cannot load https://commons.wikimedia.org/wiki/Data:I18n/Uses TemplateStyles.tab.
on the CS1 module page. I tried searching this error message and came across a thread with an individual having the same issue. I did as was suggested and added:
#Enable JsonConfigLuaSupport
$wgJsonConfigEnableLuaSupport = true;
to LocalSettings.php. However, I still have the error:
Lua error: bad argument #1 to "get" (not a valid title).
A second thread describing a similar error to the first, pointed me to a third thread with a proposed fix. However, the fix seems to involve adding code to something based on something called "CommonSettings.php" that I am not familiar with. Where do I put this?
Again, I can't thank you enough for your help so far. I consider myself a power user in many ways, but not when it comes to this sort of "coding". The one strength I do have in this regard is the knowledge and ability to find and follow how to guides online. ;) –Noha307 (talk) 19:20, 2 September 2025 (UTC)Reply

Native translation of a page

[edit]

Hi,

We don't want to use the automated content translation tool. I've added an article in Dutch, then tried the 'translate' button, and added the native English version. Then the system says that I cannot publish this language version since it's allowed for experienced users only. How can we solve this, and get our native English version online? Thanks. KatrienDeVocht (talk) 07:27, 25 August 2025 (UTC)Reply

It seems you're talking about English Wikipedia (where content translation is restricted to certain users). I'd suggest you use the Wikipedia:Articles for creation process to submit the English version. You should also read en:Help:Your first article. – Ammarpad (talk) 09:37, 26 August 2025 (UTC)Reply
Thank you. Ok, so via https://en.wikipedia.org/wiki/Wikipedia:Articles_for_creation I create a new, English article about DECA Packaging Group taking into account all guidelines, right? KatrienDeVocht (talk) 06:04, 27 August 2025 (UTC)Reply

Automatic Backup - LocalSettings.php not readable

[edit]

I use a cronjob script to create automatic database backups on the server, which invokes dumpBackup.php. This worked fine, until I read that for security reasons, it would be reasonable not to grant read-access to the LocalSettings.php to everyone - so I set the Linux rights to 640. However, now the script dumpBackup.php complains that LocalSettings.php cannot be read. As far as I understand, the LocalSettings.php must be owned by www-data. What would then be the normal way to solve this? Run the script as user www-data - would this work? - Then the backup-target directory should also be owned by www-data, I suppose?! It looks a bit complicated, thefore I ask before... Thanks! Xwr111 (talk) 07:58, 29 August 2025 (UTC)Reply

That, or another common way, is have the backup user be part of the www-data usergroup (www-data) and ensure proper group permissions. Or have the backup user run with root permissions of course. Kinda depends on the situation. —TheDJ (Not WMF) (talkcontribs) 09:22, 29 August 2025 (UTC)Reply
Another possibility is to duplicate the LocalSettings file for the backup script, giving its own permissions. Since dumpBackup.php only dumps the wikitext, it doesn't need a full LocalSettings file, only namespace information and database connection, so you can create a trimmed down LocalSettings for use only on the backup script, and giving its path as the parameter for dumpBackup.php Ciencia Al Poder (talk) 12:41, 30 August 2025 (UTC)Reply
Thanks to all, a lot of possible solutions! I chose the one which looked easiest to me, making the backup user part of the www-data usergroup - this seems to work well. Xwr111 (talk) 14:16, 30 August 2025 (UTC)Reply

mean

[edit]

What do accounts like ~2025-42331-7 mean? Banovercheckcross (talk) 19:45, 30 August 2025 (UTC)Reply

Help:Temporary accounts. – Ammarpad (talk) 08:16, 31 August 2025 (UTC)Reply

personal api token and DDOS

[edit]

i hosted a small personal project online than call wikipedia api (thumbnail and titles), its configured with my personal token and my app user-agent as required. i have been under ddos for days. since they can't beat my cloud provider protections when they go full berserk, they are just slowly and constantly poisoning my apis. this is causing my personal token to get rate limited quickly, (i'm already caching everything aggressively to minimize calls to Wikipedia) but its not sufficient. is there any recommended solution for this please ? ~2025-48624-8 (talk) 21:55, 30 August 2025 (UTC)Reply

Most common way would be to block their user-agents. —TheDJ (Not WMF) (talkcontribs) 13:42, 1 September 2025 (UTC)Reply
hey thx for the response, i can't really do that because it would also block nominal users, (i need behavior analysis or pay a fat monthly to my provider) is it allowed to use multiple personal keys or multiple accounts and rotate them ?
~2025-51487-7 (talk) 06:38, 3 September 2025 (UTC)Reply
[edit]

I'm having this problem on my wiki but also see it right here, as with Parser extension tags for example. I seem to recall that in the past this search form would highlight when a link was from transclusion and indent the derivative results under it. But more to the point, if I check the "Hide transclusions" box, this doesn't affect the search returns. It still returns the same number of results, with the transcluding pages. Am I missing something or has this been bugged for a while? Ham Pastrami (talk) 08:52, 31 August 2025 (UTC)Reply

I just updated my wiki to 1.44 but it does not work.

[edit]

I just updated my wiki to 1.44 but it refuses to load the images and the sidebar.

I ran the update script etc, but I get the following error (which seems to be a Mediawiki issue):

Deprecated: Use of MediaWiki\Skin\Skin::appendSpecialPagesLinkIfAbsent was deprecated in MediaWiki 1.44. [Called from MediaWiki\Skin\Skin::buildSidebar in /customers/1/7/b/heraldry-wiki.com/httpd.www/heraldrywiki/includes/skins/Skin.php at line 1639] in /customers/1/7/b/heraldry-wiki.com/httpd.www/heraldrywiki/includes/debug/MWDebug.php on line 386

How do I solve this ?

Secondly images are not loading and I get the error blocked

I get the same error when I try to cet-up the localsettings.php from scrath (set-up the wiki)

What to do ? ~2025-49931-4 (talk) 17:25, 1 September 2025 (UTC)Reply

The display of "Deprecated" notices should be disabled on production sites. They are not errors. This is a php configuration. Also, be sure you have upgraded your extensions and skins too, to match MediaWiki 1.44. Ciencia Al Poder (talk) 18:12, 1 September 2025 (UTC)Reply
The skins etc are all newly updated. How to get rid of thedeprecated error ?
The blocked by the way seems to be separate, a kind of DDOS ~2025-49931-4 (talk) 18:22, 1 September 2025 (UTC)Reply
https://www.google.com/search?client=safari&rls=en&q=php+suppress+deprecation+warnings&ie=UTF-8&oe=UTF-8TheDJ (Not WMF) (talkcontribs) 07:54, 2 September 2025 (UTC)Reply

Something wrong with Extension:Replace Text

[edit]

Once I tried using the replace text extension but it did not work, and it said 2 lines which might be related to the situation:

Warning: preg_replace(): Unknown modifier 'h' in /www/wwwroot/wiki/extensions/ReplaceText/src/SpecialReplaceText.php on line 1015

Warning: Cannot modify header information - headers already sent by (output started at /www/wwwroot/wiki/extensions/ReplaceText/src/SpecialReplaceText.php:1015) in /www/wwwroot/wiki/includes/Request/WebResponse.php on line 80

And I also tried processing the job queue manually (php run.php runJobs), but it said the job queue is empty. ~2025-50094-8 (talk) 00:40, 2 September 2025 (UTC)Reply

See "Post a new question" at the top of this page - which MediaWiki version? Which exact extension version? Malyacko (talk) 07:00, 3 September 2025 (UTC)Reply

PCRE failure

[edit]

It is the problem in 1.44.0 on Wampserver (8.4.0/MariaDB 11.5.2). I thought it was image rendering but now it is something diffrent. I cannot view and use VisualEditor but accessible to code editor. - Ellif (talk) 02:44, 3 September 2025 (UTC)Reply

[d3ec126f5f32820be910b055] /v/index.php/%EC%9C%84%ED%82%A4:%EB%8C%80%EB%AC%B8 RuntimeException: PCRE failure
Backtrace:
from D:\wamp64\www\v\includes\parser\Parser.php(2176)
#0 D:\wamp64\www\v\includes\parser\Parser.php(1636): MediaWiki\Parser\Parser->handleExternalLinks(string)
#1 D:\wamp64\www\v\includes\parser\Parser.php(705): MediaWiki\Parser\Parser->internalParse(string)
#2 D:\wamp64\www\v\includes\content\WikitextContentHandler.php(380): MediaWiki\Parser\Parser->parse(string, MediaWiki\Title\Title, MediaWiki\Parser\ParserOptions, bool, bool, int)
#3 D:\wamp64\www\v\includes\content\ContentHandler.php(1692): MediaWiki\Content\WikitextContentHandler->fillParserOutput(MediaWiki\Content\WikitextContent, MediaWiki\Content\Renderer\ContentParseParams, MediaWiki\Parser\ParserOutput)
#4 D:\wamp64\www\v\includes\content\Renderer\ContentRenderer.php(75): MediaWiki\Content\ContentHandler->getParserOutput(MediaWiki\Content\WikitextContent, MediaWiki\Content\Renderer\ContentParseParams)
#5 D:\wamp64\www\v\includes\Revision\RenderedRevision.php(260): MediaWiki\Content\Renderer\ContentRenderer->getParserOutput(MediaWiki\Content\WikitextContent, MediaWiki\Page\PageIdentityValue, MediaWiki\Revision\RevisionStoreRecord, MediaWiki\Parser\ParserOptions, array)
#6 D:\wamp64\www\v\includes\Revision\RenderedRevision.php(233): MediaWiki\Revision\RenderedRevision->getSlotParserOutputUncached(MediaWiki\Content\WikitextContent, array)
#7 D:\wamp64\www\v\includes\Revision\RevisionRenderer.php(236): MediaWiki\Revision\RenderedRevision->getSlotParserOutput(string, array)
#8 D:\wamp64\www\v\includes\Revision\RevisionRenderer.php(169): MediaWiki\Revision\RevisionRenderer->combineSlotOutput(MediaWiki\Revision\RenderedRevision, MediaWiki\Parser\ParserOptions, array)
#9 D:\wamp64\www\v\includes\Revision\RenderedRevision.php(196): MediaWiki\Revision\RevisionRenderer->{closure:MediaWiki\Revision\RevisionRenderer::getRenderedRevision():167}(MediaWiki\Revision\RenderedRevision, array)
#10 D:\wamp64\www\v\includes\poolcounter\PoolWorkArticleView.php(110): MediaWiki\Revision\RenderedRevision->getRevisionParserOutput()
#11 D:\wamp64\www\v\includes\poolcounter\PoolWorkArticleViewCurrent.php(129): MediaWiki\PoolCounter\PoolWorkArticleView->renderRevision(null, bool, string)
#12 D:\wamp64\www\v\includes\poolcounter\PoolCounterWork.php(173): MediaWiki\PoolCounter\PoolWorkArticleViewCurrent->doWork()
#13 D:\wamp64\www\v\includes\page\ParserOutputAccess.php(364): MediaWiki\PoolCounter\PoolCounterWork->execute()
#14 D:\wamp64\www\v\includes\page\Article.php(834): MediaWiki\Page\ParserOutputAccess->getParserOutput(MediaWiki\Page\WikiPage, MediaWiki\Parser\ParserOptions, MediaWiki\Revision\RevisionStoreRecord, int)
#15 D:\wamp64\www\v\includes\page\Article.php(551): MediaWiki\Page\Article->generateContentOutput(MediaWiki\User\User, MediaWiki\Parser\ParserOptions, int, MediaWiki\Output\OutputPage, array)
#16 D:\wamp64\www\v\includes\actions\ViewAction.php(80): MediaWiki\Page\Article->view()
#17 D:\wamp64\www\v\includes\actions\ActionEntryPoint.php(728): MediaWiki\Actions\ViewAction->show()
#18 D:\wamp64\www\v\includes\actions\ActionEntryPoint.php(505): MediaWiki\Actions\ActionEntryPoint->performAction(MediaWiki\Page\Article, MediaWiki\Title\Title)
#19 D:\wamp64\www\v\includes\actions\ActionEntryPoint.php(143): MediaWiki\Actions\ActionEntryPoint->performRequest()-
#20 D:\wamp64\www\v\includes\MediaWikiEntryPoint.php(202): MediaWiki\Actions\ActionEntryPoint->execute()
#21 D:\wamp64\www\v\index.php(58): MediaWiki\MediaWikiEntryPoint->run()
#22 {main} Ellif (talk) 02:44, 3 September 2025 (UTC)Reply

Phantom block on user?

[edit]

I have noticed that one username on my internal wiki has a line through it, and in the user list it says this user is blocked.

This user is also an editor (standard users can only read), and I have not received complaints from them that they cannot log in anymore.

When I look at the "Blocked" list, this user is not in there.

When I try to unblock the user, the system says the user isn't blocked.

What does the strikethrough mean? How can the user be blocked, but also not blocked at the same time? Techcare.noc (talk) 09:20, 3 September 2025 (UTC)Reply

Is editing with multiple temporary accounts against the rules of this wiki?

[edit]

I tried to withdraw from my "temporary account" and got the following message:

"If you are editing on a shared device like a library or school computer, you can exit this session to prevent other people from using this temporary account.

Please be aware that editing with multiple temporary accounts may be against the rules of this wiki and you could be blocked if this happens frequently."

Is this true? If so, it's quite frightening, as editing with different IP's was never prohibited before. ~2025-52148-5 (talk) 23:13, 3 September 2025 (UTC)Reply

@~2025-52148-5 Prohibited not, but abused of that possibility for the sake of abuse is. IP or temporary account are no different in that regard. —TheDJ (Not WMF) (talkcontribs) 19:30, 5 September 2025 (UTC)Reply

What ElasticSearch (or OpenSearch) version should MediaWiki 1.43.3 use?

[edit]

I am parsing the CirrusSearch extension page (Extension:CirrusSearch) to figure out what product (ElasticSearch or OpenSearch) and what specific version I should use with MediaWiki 1.43.3, and I am having a bit of difficulty determining that.

Would it be possible to get a definitive recommendation from the extension maintainers, or a link to a document that specifies that? Of78990 (talk) 18:56, 4 September 2025 (UTC)Reply

That wiki page has a yellow box in the section "Elasticsearch or Opensearch". Please elaborate what is unclear - thanks! Malyacko (talk) 11:07, 7 September 2025 (UTC)Reply

My startup failed miserably and it was based on mediawiki software

[edit]

I wrote several extensions for a website that I built that is not really working out and I don't know what to do with all these extensions. The website is www.stochiki.com, as you can see it's based on the mediawiki software. What should I do with the software that I wrote?

thanks ~2025-53035-0 (talk) 01:29, 5 September 2025 (UTC)Reply

You are free to publish/host your software code in public places like source-code-hosting facilities. This is entirely up to you (and unrelated to MediaWiki). Malyacko (talk) 11:09, 7 September 2025 (UTC)Reply
@~2025-53035-0: If your extensions are of general use, you could add documentation pages for them here on mediawiki.org and migrate their code to Gerrit. What do the extensions do? (Your Special:Version page is not public, otherwise I'd go and look.) Sam Wilson 04:37, 8 September 2025 (UTC)Reply
Hi Sam, thanks for the interest. It's a content management system for guides with exercises and discussion features. The user can do practice exercises, track performance, ask questions in the discussion forums, rate exercises, etc. You can also create practice exams. There are user groups for each guide that the guide administrator can manage (like moderator groups) enabling users to have more or less rights. The entire thing is built on top of mediawiki. I carefully studied the mediawiki code to mimic the coding practices when I wrote these extensions. ~2025-56303-3 (talk) 14:38, 9 September 2025 (UTC)Reply

Page title with question mark (?) and short URLs

[edit]

I'm using Mediawiki 1.43.0 served by Apache 2.4.62.

Pages with a title containing a question mark give a 403 Forbidden error. This is caused by the short URLs rewrite rule, how the question mark is encoded in the URL and the fix for CVE-2024-3847 in Apache > 2.4.59.

The workaround seems to be using the option AllowUnsafe3F in the rewrite rule, but is this really the recommended way to deal with this issue? Should the documentation be updated accordingly? JPMalhado (talk) 12:37, 6 September 2025 (UTC)Reply

@JPMalhado: It's been a couple of years since I looked into it, but it does seem to fix things. One of my wikis' rules is
RewriteRule ^(.*)$ "%{DOCUMENT_ROOT}/index.php?title=$1" "[L,QSA,B,UnsafeAllow3F]"
Are there problems with adding AllowUnsafe3F? Sam Wilson 04:32, 8 September 2025 (UTC)Reply
Hello. Yes, that is the workaround that I mentioned, but is it the right way to address this though? This is effectively bypassing the measures put in place to address CVE-2024-3847, so by using this option is one not opening up a vulnerability on the server? JPMalhado (talk) 21:57, 8 September 2025 (UTC)Reply

Suddenly logged out, and unable to log back in

[edit]

Site: http://horawiki.org/page/Welcome_to_HoraWiki! Version: 1.44.0

I installed MediaWiki 1.44.0 a few weeks ago and all seemed well. Since then I have added, edited, and deleted pages with no trouble, as have other users.

Today I went to edit a page and the "Edit" button was missing; I noticed that I was logged out, for no reason that I could see. And every attempt to log back in led to the message "There seems to be a problem with your login session; this action has been canceled as a precaution against session hijacking. Please resubmit the form." A little Googling showed some old potential fixes for this problem, but I already have (and have had for years, I think) settings $wgMainCacheType = CACHE_ACCEL and $wgSessionCacheType = CACHE_DB.

I finally realized that I can log it using a private window in my browser (Brave). Also, clearing cookies seems to solve the problem.

I see nothing especially new in error_log. Since installing 1.44.0 I'm getting lots of errors "Undefined array key "packages" in [...]/includes/libs/composer/ComposerInstalled.php on line 30" followed by "foreach() argument must be of type array|object, null given in [...]/includes/libs/composer/ComposerInstalled.php on line 33" but these started long ago and don't seem related.

One scary thing: The last month or two I have had many, many new registered users, sometimes several per day. They can't all be people interested in the content of the wiki, which is on a very specialized subject. (This is despite my use of QuestyCaptcha to prevent automated account creation.) Half a dozen of these new accounts have put a bunch of advertising in their user page, or created spam pages about their business; in this case I delete the page and block the user. Of course I'm terrified that one of these bogus accounts is trying to sabotage the whole wiki.

Any information appreciated on what's wrong, or what I can do, or if there's a connection with all these bogus accounts. Larrydberg (talk) 19:05, 6 September 2025 (UTC)Reply

See Manual:How to debug/Login problems and Manual:Combating spam Malyacko (talk) 11:12, 7 September 2025 (UTC)Reply

Loading CentralAuth extension leads to error: Call to a member function getCanonicalServer() on null

[edit]

MediaWiki version: 1.39.13

PHP version: 7.4.33

Wiki URL: https://penguinicewikis.com/mw19/index.php?title=Main_Page

Hello. I loaded the CentralAuth extension to my wiki family. However, the main wiki displays an error when the extension is loaded (even when changing the skin). The error is asking for a call to a member function getCanonicalServer() on null, and it backtraces to a hook handler called PageDisplayHookHandler.php.

Here is what the backtrace looked like:

Backtrace:

from /home/gjlxrtap/public_html/mw19/extensions/CentralAuth/includes/Hooks/Handlers/PageDisplayHookHandler.php(83)

  1. 0 /home/gjlxrtap/public_html/mw19/includes/HookContainer/HookContainer.php(160): MediaWiki\Extension\CentralAuth\Hooks\Handlers\PageDisplayHookHandler->onBeforePageDisplay(OutputPage, Skins\Chameleon\Chameleon)
  1. 1 /home/gjlxrtap/public_html/mw19/includes/HookContainer/HookRunner.php(946): MediaWiki\HookContainer\HookContainer->run(string, array, array)
  1. 2 /home/gjlxrtap/public_html/mw19/includes/OutputPage.php(2871): MediaWiki\HookContainer\HookRunner->onBeforePageDisplay(OutputPage, Skins\Chameleon\Chameleon)
  1. 3 /home/gjlxrtap/public_html/mw19/includes/MediaWiki.php(922): OutputPage->output(boolean)
  1. 4 /home/gjlxrtap/public_html/mw19/includes/MediaWiki.php(562): MediaWiki->main()
  1. 5 /home/gjlxrtap/public_html/mw19/index.php(50): MediaWiki->run()
  1. 6 /home/gjlxrtap/public_html/mw19/index.php(46): wfIndexMain()
  1. 7 {main}

I've installed all of the required SQL tables for this extension, ran update.php, and looked at various solutions given on the Internet, but I haven't got anything helpful. What can I do? Newman2 (talk) 16:40, 8 September 2025 (UTC)Reply