Project:Support desk

About this board

Welcome to the MediaWiki Support desk, where you can ask MediaWiki questions!

(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 versions you are using, as found on your wiki's Special:Version page:
    • MediaWiki version
    • PHP version
    • Database type and version
  2. 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.
  3. To start a new thread, click "Start a new topic".
Kk.urban (talkcontribs)

Is it possible for a wiki to restrict pages in certain namespaces in Special:WantedPages?

Reply to "Special:WantedPages"

PHP Deprecated - Visual Editor

Waterlooglass (talkcontribs)

I continue to get this warning message when trying to make any edits to my pages. I have upgrade to mediawiki 1.41 and have installed Visual Editor v 0.1.2 (2e8e3b8) 06:15, 29 June 2023. However, I get this warning and it seems to be crashing my wiki and preventing me from editing, can anyone assist?

, PHP Deprecated:  Use of Modules must target desktop and mobile. Module was deprecated in MediaWiki 1.41. [Called from MediaWiki\ResourceLoader\StartUpModule::getScript in /opt/bitnami/mediawiki/includes/ResourceLoader/StartUpModule.php at line 436] in /opt/bitnami/mediawiki/includes/debug/MWDebug.php on line 386

Reply to "PHP Deprecated - Visual Editor"
HorstKow (talkcontribs)


I have installed MW 1.41 on a Debian 12 system. Generally, it works fine. I have only an issue with users that are remote. It appears they cannot login to their account. They receive a session cookie but after entering the UN/PW the user is not receiving any further cookies. It works when a direct local redirect via SSH is established. But then other issues come into play as the users are isolated behind a firewall (hence the proxy).

The setup failing is such:

Browser -> TinyProxy -> VPN -> MW

I have tried the recommended setting with caching, but they have no effect. Any ideas but leaving MW as "Openwiki"?

Ciencia Al Poder (talkcontribs)

Maybe TinyProxy is filtering/removing some cookies.

After entering the UN/PW you should get those 3 cookies: _session, UserID, and UserName, all prefixed by the cookie prefix (or db name). Those are different from the cookie mwuser-sessionId.

Setting a debug log as described in Manual:How to debug should write all cookies sent, maybe you can discover something there.

Reply to "Login via VPN"
Knighstalker (talkcontribs)

Hello, How does a person modify or change their user name? In my case I would like to capitalize one letter in my user name. My user name now is: Knighstalker. I would like to modify it too: KnighsTalker. I appreciate any assistance with this matter. Thank you.

Ciencia Al Poder (talkcontribs)
Reply to "Modify User Name"

Cannot access the database

Summary by LeyteWolfer

From tech support team: "The issue was due to the PostgreSQL settings enabled, this was used instead of the MySQL settings."

LeyteWolfer (talkcontribs)
  • MediaWiki version: 1.29.2 --> 1.35.14
  • PHP version: 7.3 --> 7.4
  • Database type and version: MySQL 8.0.36

Here are the straight facts:

  • After the previous attempt to upgrade the wiki was not resolved, I had a complete host sever restoration conducted.
  • Post-restoration (MW 1.29.2), the site (and database, apparently) were completely accessible and operable.
  • I let it sit for nine days, so that I could approach it from a fresh (and less frustrated) perspective.
  • Today, I did as clean install. The database update went thru with no identified errors (I have the 2,501-line database update report, if relevant).
  • However, as with last time, when it comes time to start using my wiki, I get the following:
Sorry! This site is experiencing technical difficulties.
Try waiting a few minutes and reloading.
(Cannot access the database)
#0 /home/starsh2/public_html/sfcwiki/includes/libs/rdbms/loadbalancer/LoadBalancer.php(937): Wikimedia\Rdbms\LoadBalancer->reportConnectionError()
#1 /home/starsh2/public_html/sfcwiki/includes/libs/rdbms/loadbalancer/LoadBalancer.php(904): Wikimedia\Rdbms\LoadBalancer->getServerConnection(0, 'starsh2_sfcwiki...', 0)
#2 /home/starsh2/public_html/sfcwiki/includes/libs/rdbms/loadbalancer/LoadBalancer.php(1049): Wikimedia\Rdbms\LoadBalancer->getConnection(-1, Array, 'starsh2_sfcwiki...', 0)
#3 /home/starsh2/public_html/sfcwiki/includes/GlobalFunctions.php(2463): Wikimedia\Rdbms\LoadBalancer->getMaintenanceConnectionRef(-1, Array, 'starsh2_sfcwiki...')
#4 /home/starsh2/public_html/sfcwiki/includes/cache/localisation/LCStoreDB.php(56): wfGetDB(-1)
#5 /home/starsh2/public_html/sfcwiki/includes/cache/localisation/LocalisationCache.php(449): LCStoreDB->get('en', 'deps')
#6 /home/starsh2/public_html/sfcwiki/includes/cache/localisation/LocalisationCache.php(495): LocalisationCache->isExpired('en')
#7 /home/starsh2/public_html/sfcwiki/includes/cache/localisation/LocalisationCache.php(414): LocalisationCache->initLanguage('en')
#8 /home/starsh2/public_html/sfcwiki/includes/cache/localisation/LocalisationCache.php(333): LocalisationCache->loadSubitem('en', 'messages', 'title-invalid-e...')
#9 /home/starsh2/public_html/sfcwiki/languages/Language.php(2645): LocalisationCache->getSubitem('en', 'messages', 'title-invalid-e...')
#10 /home/starsh2/public_html/sfcwiki/includes/cache/MessageCache.php(1047): Language->getMessage('title-invalid-e...')
#11 /home/starsh2/public_html/sfcwiki/includes/cache/MessageCache.php(1005): MessageCache->getMessageForLang(Object(LanguageEn), 'title-invalid-e...', false, Array)
#12 /home/starsh2/public_html/sfcwiki/includes/cache/MessageCache.php(947): MessageCache->getMessageFromFallbackChain(Object(LanguageEn), 'title-invalid-e...', false)
#13 /home/starsh2/public_html/sfcwiki/includes/language/Message.php(1320): MessageCache->get('title-invalid-e...', false, Object(LanguageEn))
#14 /home/starsh2/public_html/sfcwiki/includes/language/Message.php(878): Message->fetchMessage()
#15 /home/starsh2/public_html/sfcwiki/includes/language/Message.php(970): Message->toString('text')
#16 /home/starsh2/public_html/sfcwiki/includes/title/MalformedTitleException.php(51): Message->text()
#17 /home/starsh2/public_html/sfcwiki/includes/title/MediaWikiTitleCodec.php(346): MalformedTitleException->__construct('title-invalid-e...', '')
#18 /home/starsh2/public_html/sfcwiki/includes/Title.php(3422): MediaWikiTitleCodec->splitTitleString('', 0)
#19 /home/starsh2/public_html/sfcwiki/includes/Title.php(427): Title->secureAndSplit('')
#20 /home/starsh2/public_html/sfcwiki/includes/MediaWiki.php(88): Title::newFromURL(NULL)
#21 /home/starsh2/public_html/sfcwiki/includes/MediaWiki.php(151): MediaWiki->parseTitle()
#22 /home/starsh2/public_html/sfcwiki/includes/MediaWiki.php(906): MediaWiki->getTitle()
#23 /home/starsh2/public_html/sfcwiki/includes/MediaWiki.php(547): MediaWiki->main()
#24 /home/starsh2/public_html/sfcwiki/index.php(53): MediaWiki->run()
#25 /home/starsh2/public_html/sfcwiki/index.php(46): wfIndexMain()
#26 {main}
  • There are some slight deviations from the previous attempt, starting with line #4 above.
  • $wgServer is correct and is an exact match for an earlier upgraded and operational wiki.

I'm having the host tech team confirm (as we did last time), that they have access to the database with the password in LocalSettings. Anticipating that confirmation, I'm thinking ahead as to courses of action. Right now, I'm thinking that reverting to the backup or restoring the directory via tech support, back to 1.29.2 (including directory, mysql db, and user db) and maybe doing an interim upgrade (1.32.6?) to test whether the same failure to "contact the database" occurs. However, I'm throwing a wide net for Support Desk volunteers, hoping someone has an inspired idea.

Osnard (talkcontribs)

Apparently your wiki tries to show you an invalid-title-exception (see #17). It then tries to access the L10N cache to show the message in your language. The cache tries to open a connection to the database with a "connection type" of "DB_REPLICA" ("-1"), which then again fails.

You said command line scripts like maintenance/update.php do work. So my best guess is, that the settings file, which contains database credentials may not be accessible by the webserver user, but only by the user used on the CLI.

LeyteWolfer (talkcontribs)

Thank you, @Osnard. I'm going to need to understand that better in order to direct the HostPapa tech support team.

Let me know if I'm mis-understanding the issue: the User database appears not to have access to the 5 lines in LocalSettings that allows it to communicate with the primary MySQL database. Those lines/credentials being some or all of the following from LocalSettings:

  • $wgDBtype
  • $wgDBserver
  • $wgDBname
  • $wgDBuser
  • $wgDBpassword

Is that a correct summation?

Osnard (talkcontribs)

It is not about the "user database". It is about the "user context". Based on whether the application is accessed from CLI (e.g when running update.php) or from the webserver (e.g. when you access the application with your browser) the values of the variables you listed seem to be different.

LeyteWolfer (talkcontribs)

Ok...that makes sense to me as to how it is not the user database, but the "avenue" as to how the user attempts to contact the database.

Edit - This is the report I received from tech support (conducted before your last response):

I checked your site's database settings and all are correct and able to connect.
 I also flushed the MySQL connections of the server but still has the error.
 There were some entries on the server logs from your website, but seems not related to the database error shown on the site. See logs below.
 [Sat Feb 24 09:50:55.997710 2024] [lsapi:warn] [pid 3262496:tid 47586679232256] [client "the IP address":51404] [host] Backend log: PHP Warning: session_write_close(): Failed to write session data (user). Please verify that the current setting of session.save_path is correct (/tmp) in /home/starsh2/public_html/sfcwiki/includes/session/SessionManager.php on line 469\n, referer:
 The warning message itself is indicating an issue with writing session data. It suggests that the function session_write_close() failed to write session data due to a problem with the session save path, which is currently set to /tmp. The warning advises verifying that the session.save_path configuration is correct.
 Can you please check the correct path of the site's session? Does the /tmp folder should be set to 777 instead of 755 permission?

That doesn't seem to contradict what you said was the issue.

Do you have a suggestion as how to resolve that? Or something I should tell the tech support team?

LeyteWolfer (talkcontribs)

From the host server's tech support team:

The issue was due to the PostgreSQL settings enabled, this was used instead of the MySQL settings. Please check and confirm if this is the correct page for /sfcwiki.

I don't quite understand where this was changed, as I see no presence of PostgreSQL settings in any of my archived LocalSettings. However, I have confirmed the wiki is accessible and now on version 1.35.14.

Use Action API to mark watchlist item as read

Aaron Liu (talkcontribs)

Is there a way I can use JavaScript to mark a specific watchlist item as read?

Reply to "Use Action API to mark watchlist item as read"
AlgorithmGG (talkcontribs)

I was getting a composer error and It says use php 8.1 or greater but has an issue with php 8.3. This is regarding composer settings I haven't edited the file yet to see what happens but I thought it used php 7.4?

AlgorithmGG (talkcontribs)

Using php74 i get this error:

Composer detected issues in your platform:

Your Composer dependencies require a PHP version ">= 8.1.0". You are running 7.4.33.

using 8.3 i get this issue that mentions a path I cannot find:

[80598ecae066fcb2abc355ac] [no req]   Error: Class "MediaWiki\User\Options\DefaultOptionsLookup" not found


from /home/admin/domains/

#0 /home/admin/domains/ Wikimedia\Services\ServiceContainer::{closure}()

#1 /home/admin/domains/ Wikimedia\Services\ServiceContainer->createService()

#2 /home/admin/domains/ Wikimedia\Services\ServiceContainer->getService()

#3 /home/admin/domains/ MediaWiki\MediaWikiServices->getService()

#4 /home/admin/domains/ Wikimedia\Services\ServiceContainer->get()

#5 /home/admin/domains/ Wikimedia\Services\ServiceContainer::{closure}()

#6 /home/admin/domains/ Wikimedia\Services\ServiceContainer->createService()

#7 /home/admin/domains/ Wikimedia\Services\ServiceContainer->getService()

#8 /home/admin/domains/ MediaWiki\MediaWikiServices->getService()

#9 /home/admin/domains/ MediaWiki\MediaWikiServices->getGenderCache()

#10 /home/admin/domains/ Wikimedia\Services\ServiceContainer::{closure}()

#11 /home/admin/domains/ Wikimedia\Services\ServiceContainer->createService()

#12 /home/admin/domains/ Wikimedia\Services\ServiceContainer->getService()

#13 /home/admin/domains/ MediaWiki\MediaWikiServices->getService()

#14 /home/admin/domains/ Wikimedia\Services\ServiceContainer::{closure}()

#15 /home/admin/domains/ Wikimedia\Services\ServiceContainer->createService()

#16 /home/admin/domains/ Wikimedia\Services\ServiceContainer->getService()

#17 /home/admin/domains/ MediaWiki\MediaWikiServices->getService()

#18 /home/admin/domains/ MediaWiki\MediaWikiServices->getTitleParser()

#19 /home/admin/domains/ Wikimedia\Services\ServiceContainer::{closure}()

#20 /home/admin/domains/ Wikimedia\Services\ServiceContainer->createService()

#21 /home/admin/domains/ Wikimedia\Services\ServiceContainer->getService()

#22 /home/admin/domains/ MediaWiki\MediaWikiServices->getService()

#23 /home/admin/domains/ MediaWiki\MediaWikiServices->getUserNameUtils()

#24 /home/admin/domains/ MediaWiki\Session\SessionManager->__construct()

#25 /home/admin/domains/ MediaWiki\Session\SessionManager::singleton()

#26 /home/admin/domains/ require_once(string)

#27 {main}

Bawolff (talkcontribs)

Are you sure you installed mediawiki properly with all the correct php files?

AlgorithmGG (talkcontribs)

Yes @Bawolff, i hope all is well. I believe so, I downloaded updates from mediawiki both 140/141 and found a link somewhere for the master via mediawiki I think! As I want to test the automatic extension upgrading, I figured I may as well play with the master version. Do you have a reliable link handy please?

Bawolff (talkcontribs)

Since its complaining about a missing file, is includes/user/Options/DefaultOptionsLookup.php present? If it is, i suppose it could be the wrong version, or autoload.php could be the wrong version.

Normally when it complains of missing files, i would reccomend just redownloading mediawiki.

AlgorithmGG (talkcontribs)

Makes sense has the repository been recently updated? I definitely downloaded via mediawiki.

Failing that if the files are not available is there any guidance to recreate them, or will I have to test php files I already have from previous versions.

AlgorithmGG (talkcontribs)

@Bawolff it turns out fzilla didn't copying the contents of /DefaultOptions.php

i have a few out of date extensions i was looking to update manually but i am getting this error which mentions a extension which is upto date:

[22d68a555c0266af86bcce17] [no req]   MediaWiki\Config\ConfigException: MediaWiki\TimedMediaHandler\WebVideoTranscode\WebVideoTranscode::validateTranscodeConfiguration: Invalid key 'vorbis' specified in wgEnabledTranscodeSet or wgEnabledAudioTranscodeSet.


from /home/admin/domains/

#0 /home/admin/domains/ MediaWiki\TimedMediaHandler\WebVideoTranscode\WebVideoTranscode::validateTranscodeConfiguration()

#1 /home/admin/domains/ MediaWiki\TimedMediaHandler\Hooks::register()

#2 /home/admin/domains/ require_once(string)

#3 {main}

Bawolff (talkcontribs)

It sounds like a LocalSettings.php issue.

AlgorithmGG (talkcontribs)

Cheers it installed just gotta configure the server.

AlgorithmGG (talkcontribs)

I gotta install a load of extensions, the 142.alpha installation completes but I am getting a http 500 error when visiting the wiki homepage the build insisted I use php81 am I missing something? I get no errors running maintenance although it Attempted to insert 225 IP revisions, 0 was actually done.

Reply to "Installing master"

Which windows server version is required for MediaWiki

2 (talkcontribs)

Which windows server version is required for MediaWiki ?

AS we are using MediaWiki 1.39.1, MySQL 8.0.36 and php 8.1.13 version for 3 wikis: FM Wiki, Risk Wiki and Credit-Risk Wiki

Ciencia Al Poder (talkcontribs)

There's no Windows Server requirement, as long as you can install there the other requirements. Maybe you should check which windows server version is required for the supported versions of MySQL and php

Reply to "Which windows server version is required for MediaWiki"

issue locating/downloading extensions

2 (talkcontribs)
Ciencia Al Poder (talkcontribs)

Works for me. Maybe it was a temporary problem

Reply to "issue locating/downloading extensions"

How to skip summaries (to safe faster)?

Tranqullio (talkcontribs)

Hi, is there a way to save page changes with just one click? I would like to ignore or skip the summaries window and save the changes immediately. In my wikis, no one uses or needs this feature, but we often lose changes because users forget to save twice. This is annoying, so I've been looking for a way around this for a while. I would be very grateful for any advice.

Ciencia Al Poder (talkcontribs)

There's no requirement to specify a summary when submitting changes by default. If a wiki has implemented this as mandatory, you should ask the maintainers of the wiki to disable this requirement.

Reply to "How to skip summaries (to safe faster)?"