Hiding special-page links in Minerva.js

On my Miraheze wiki, the Minerva.js settings currently contain this code:

mw.util.addPortletLink('p-navigation', '/wiki/Special:WhatLinksHere/' + mw.config.get( 'wgPageName' ), 'What links here', 'nav-wlh');

However, it should be quickly noted that "What links here" is invalid for pages in the Special namespace themselves; to that end, I'd like to know exactly what wraparound to use for cancelling it out if special pages are visited. Once I receive a tip (from @Bawolff or otherwise), the same procedure will apply for overviews of related changes.

Still, with Good Friday and Easter weekend close at hand, this might take a little while. --Slgrandson (talk) 01:56, 18 April 2025 (UTC)

@Slgrandson I havent tested, but generally an ISO timestamp will likely work yyyy-mm-dd hh:mm:ss —TheDJ (Not WMF) (talk • contribs) 08:16, 21 April 2025 (UTC)

@TheDJ: If so, which part of the calls is the timestamp appended to? --Slgrandson (talk) 20:58, 21 April 2025 (UTC)

Leaving this message up in case anyone else has a better solution. --Slgrandson (talk) 07:43, 5 May 2025 (UTC)

Giving this appeal another try... --Slgrandson (talk) 02:31, 19 May 2025 (UTC)

Some images not showing after Upgrade from 1.31 to 1.43

I found several tickets to this problem, but the most common solution (run cleanupUsersWithNoId.php and migrateActors.php) is no longer applicable with 1.43 as both scripts are deceprated and removed.

Background: I upgraded from an old LTS (1.31) to the latest LTS with 1.35 as gap version. Exactly as stated on the upgrade page. And at first glance, everything was fine. But then, there are some images which are not there. They still have their description page and history, they're on the webserver, I can find them in the image folder, they have the same permission und owner as all the other images. The missing images also doesn't come from the same folder, as one is from e/e1 and another from 6/67, at the same time other images from these folders are displayed.

I already tried checkImages.php and rebuildImages.php with no luck. And after reading the other tickets to this topic, I'm afraid I have to manually reupload each missing image myself :s --91.42.74.217 18:57, 2 May 2025 (UTC)

EDIT: Here is the link to the affected wiki and one of the example images, which are no longer displayed but still on my server: memory-alpha.wiki/wiki/Datei:Odo_2372.jpg. RebuildImages.php didn't help either. --80.128.152.128 19:18, 4 May 2025 (UTC)

EDIT2: I have tried nearly all maintenance scripts at this point. importImages.php gives me the error "Importing XY.jpg...failed. (at recordUpload stage)". rebuildImages.php says that it did *something* but nothing actually happens. refreshFileHeaders.php makes nothing. Even manually uploading the image in my wiki via the webinterface doesn't work because, surprise, it recognize that its a duplicate. So my wiki knows that there are images, but it simply won't display it? Why? What happend between 1.31 and 1.43? (or 1.31 and 1.35 or 1.35 and 1.43?) 91.42.80.200 20:36, 7 May 2025 (UTC)

"Odo 2372.jpg" has an md5sum of da49172cdaabe195c0a9d6b2c446b159, meaning that it should be located in this the directory https://memory-alpha.wiki/mediawiki/images/d/da/ which it clearly is not. So either the webserver doesn't have the right permissions on that file, in case it DOES exist locally (so then fix the permissions), or it is actually gone. That doesn't seem an upgrade issue, though it is possible that while upgrading you made a mistake with copying or something, that caused it to be lost. —TheDJ (Not WMF) (talk • contribs) 09:10, 8 May 2025 (UTC)

"Odo_2372.jpg" (underscore instead of space) has a hash of 6992464c461e737fd03d1652cde1622b though and is located in the directory matching that hash: memory-alpha.wiki/mediawiki/images/6/69/Odo_2372.jpg. --2A02:2455:812B:BA00:F238:C7D9:4B56:36B6 10:02, 8 May 2025 (UTC)

Yes exaclty, and this was also its position in the original image-folder pre-upgrade... Nearly half of all my images (mostly uploaded by users, which don't exist in my database due to the fact I imported the whole wiki back in 2018) are not there anymore. 87.157.182.103 21:05, 8 May 2025 (UTC)

EDIT3: Ok, I go in full error mode. A secound try, where I carefully watched the output of both upgrade.php runs (1.35 and 1.43) revealed a missing cleanupUsersWithNoId.php run in 1.35, but even with that the exact same images are missing in 1.43. 91.42.65.179 07:30, 11 May 2025 (UTC)

SOLUTION!! The error is within the image table! For the missing images, the img_actor field was 0. To correct the error, it only needs to be changed using UPDATE <wiki>image SET img_actor="3" WHERE img_actor="0";. The new value of img_actor must be any existing actor (e.g. the wiki creator is 1). Now ALL my images are back! And this is the solution to a years old problem! 91.42.65.179 19:52, 11 May 2025 (UTC)

Full images not showing when wiki is accessed from domain

I have encountered an issue with displaying original versions of image files when I access my wiki site through a domain, e.g. wiki.mydomain.com. It looks like the page attempts to load the file from my wiki's local IP address, in this case 192.168.1.196. When site is accessed through mentioned IP directly, images work without issues. I have setup wiki behind an nginx proxy, if that is a factor in troubleshooting the issue.

Error message received after image thumbnail is clicked:

There seems to be a technical issue. You can retry if it persists. Error: could not load image from http:// 192.168.1.196/mediawiki/images/9/95/Test_image.jpg

Wiki version information:

Eetu1990 (talk) 10:20, 7 May 2025 (UTC)

Custom colour scheme set in css randomly switches on and off

My wiki (https://cyberpedia.miraheze.org/wiki/Main_Page) has a custom colour scheme, however most of the time the custom colour scheme is not used, expect for a few things like links. The colour scheme is set via https://cyberpedia.miraheze.org/wiki/MediaWiki:Common.css and https://cyberpedia.miraheze.org/wiki/MediaWiki:Vector.css. Occasionally the custom colour scheme is used, however only for a couple of hours at a time before going back to the non-custom colour scheme. I have asked about this elsewhere and the only response I've got is that I might need to use CSS containers in some undefined way, or that it might have something to do with mobile skins despite me being on desktop. Eldomtom2 (talk) 21:20, 8 May 2025 (UTC)

Hidden Namespace pages

Hello,

I would like to block unregistered users from reading TALK pages, VIEW SOURCE pages, VIEW HISTORY pages, TEMPLATE pages and SPECIAL pages + the page Pages_spéciales

I've tried this, but it doesn't always work:

wfLoadExtension( 'Lockdown' );

$wgActionLockdown['history'] = [ 'user' ]; // seems OK

$wgActionLockdown['TalkPage'] = [ 'user' ]; // seems OK

$wgActionLockdown['SpecialPages'] = [ 'user' ]; // not OK

$wgNamespacePermissionLockdown[NS_TALK]['read'] = [ 'user' ]; // seems OK

$wgNamespacePermissionLockdown[NS_TEMPLATE]['read'] = [ 'user' ]; // seems OK

$wgNamespacePermissionLockdown[NS_TEMPLATE_TALK]['read'] = [ 'user' ]; // seems OK

$wgNamespacePermissionLockdown[NS_SPECIAL]['read'] = [ 'user' ]; // not OK

Can you help me, please?

https://www.europe-politique.eu/wiki/

Lo2b (talk) 21:33, 8 May 2025 (UTC)

I've never used [[Extension:Lockdown] but it looks as though $wgActionLockdown relates to actions (Manual:Parameters_to_index.php#Actions) and "SpecialPages" isn't one. Neither is "TalkPage".

Maybe try -1 instead of NS_SPECIAL? Maybe $wgNamespacePermissionLockdown just doesn't work for special pages. Also the existence of $wgSpecialPageLockdown makes me think you might have to use that for all special pages individually. Jonathan3 (talk) 13:49, 9 May 2025 (UTC)

PDF's and Word docs rejected in my upload?

I tied to upload an historica Survey Journal to Wikimedia Commons first in PDF format and that was rejected after I went through all the steps to support and document it, and then I uploaded it in Word format and that was rejected because the newer Word format was not acceptable. What is left? How do I upload this important historical item? NoelSherry (talk) 02:13, 11 May 2025 (UTC)

c:Commons:File types#Textual formats should be relevant, in particular the last paragraph. Otherwise you should ask their Help desk instead, as this is related to Commons' configuration and policies and not to MediaWiki itself. The frontpage there already gives some pointers on where to look for answers. Tactica (talk) 16:47, 11 May 2025 (UTC)

Scribunto/Lua Internal Error, Signal 11

This Scribunto extension is not working for me at all. First I tried hosting locally on Laragon. The Lua binary failures trying to run under WAMP flavors are legendary discussions. Then I have tried several installs of MediaWiki in versions 1.39 and 1.43 on my InMotion Hosting VPS. Every setting anywhere has been configured over and over again with the prevailing wisdom available. Nothing makes much difference, and unlike any of the other Lua errors (1, 2, 126, 127), signal 11 leaves no trace in the log. Just for fun I have created circumstances to cause those former error codes to be logged--they were. Also $showexceptiondetails reveals nothing extra to see.

I simply do not understand why this will not work properly. Even attempts to create simple module invoke scripts like 'Hello' get caught by the editor emulator when trying to save. The site is up and running, and is purposed to accomplish BOLD edits and new namespace content for inclusion into Wikipedia. At the bottom of the landing page are links that deliver phpinfo and system version info. Any thoughts?

The site is located at PT Wikitor Sandbox. There is one active article listed (using a WP Info_Person box), and demonstrates the Lua failure upon on calling up the person Infobox.

A list of things I have done, and all MediaWiki and PHPinfo report pages is here: https://ae1pt.com/wikitor/index.php?title=Actions_Taken_to_Date

Pragmatist (talk) 15:33, 12 May 2025 (UTC)

Restrict access to certain types of resource-intensive requests

Hi everyone. I don't generally mind even malicious bots scanning my wiki, I rather accept a few overzealous ones rather than over-block IP adresses etc. However, I see spikes of bot traffic that call very very odd and specific URL parameter requests, and those appear to be calling version diffs, certain timespans of related changes etc, in short, requests that (even for human users) often take more than a second or two, and are more resource intensive database calls than just accessing regular sites or more common requests (that are served via several layers of caching). Is there a way to restrict use of such specific requests to logged in users only? I see absolutely no value in having bots crawl these things.

Here are some example requests (seeing hundreds per minute - this is copy and paste not all of this may be malignant):

(as you can see, some things keep re-appearing such as limits, recentchangeslinked, "from" and "days" etc. Honestly, knowing the very limited number of my editors and my wiki, these are not humans accessing these sites. And that's just a snapshot. Help is much appreciated. These do not pop up in the firewall or security software of my server so they must be fairly "regular" bots, but they just get a bit too active...

Rebastion2 (talk) 17:23, 13 May 2025 (UTC)

trying extension:lockdown with

$wgActionLockdown['history'] = ['user'];

$wgSpecialPageLockdown['Whatlinkshere'] = [ 'user' ];

$wgSpecialPageLockdown['Recentchangeslinked'] = [ 'user' ];

see if that does anything... but the way these URLs are directly called... not sure if I am messing around a step too deep Rebastion2 (talk) 17:53, 13 May 2025 (UTC)

OK I found Externsion:Lockdown and Externsion:DisableSpedialPages to theoretically lock these down, but the way they are called (via url paramters, not directly) I think makes these moot, plus, of course it doesnt stop these before php kicks in, so maybe the only thing that will really help me is buy Cloudflare? Rebastion2 (talk) 20:42, 14 May 2025 (UTC)

testing as an anonymous user, the lockdown works even for the URL parameters the bots use, but alas, the sheer amount of bot requests just does it.... too bad Rebastion2 (talk) 20:55, 14 May 2025 (UTC)

School-wide database for Google Drive users?

Hi - thank you for giving me your time. I've browsed the guides but don't have the answer . We have a small non-profit school that uses Google drive and Gmail for all of our business. We'd like to incorporate a private wiki so that we can have/share/look up resources by anyone here, present and future. Is there a way to do this with this platform? Can we host a version in Google Drive somehow, accessible by anyone with our @davincisv.org emails? Or am I barking up the wrong tree with WikiMedia? 2603:3024:151B:9200:B019:92C4:2597:8F80 18:12, 14 May 2025 (UTC)

No, that is not really how MediaWiki works. It sounds like you are looking for something like sharepoint or similar solutions. I advise to get some consultation from a professional if you want to run software in a professional setting. —TheDJ (Not WMF) (talk • contribs) 09:34, 17 May 2025 (UTC)

Mediawiki upgrade path

Hello! I am new to media wiki and I am looking for some assistance in identifying the proper upgrade path for our companies implementation of MW. They are running a very old version (1.17.0) on a Centos 6.10 VM with Apache 2.2.15 and PHP 5.3.3. I need to migrate the implementation to a VM running Ubuntu 22.04 and would really appreciate some guidance on an upgrade path. Please let me know if you need any additional information. I apologize if this information has already been identified on this site, I was unable to locate it. Thanks in advance! Sleepinfire (talk) 12:53, 15 May 2025 (UTC)

See Manual:Upgrading#Frequently_asked_questions. Basically you have to upgrade to 1.35, then to 1.39, and lastly to 1.43. Tactica (talk) 17:44, 15 May 2025 (UTC)

@Sleepinfire The biggest advise, lots of backups and go step by step when updating various components. When extensions give you trouble during upgrade, disable them, update the core, then turn the extesion back on and run the same upgrade again. Some old extensions might no longer be supported and will not be able to be upgraded, you might have to find alternatives for them or sacrifice the functionality. —TheDJ (Not WMF) (talk • contribs) 09:39, 17 May 2025 (UTC)

How can I

Make a wiki JadenGotLost (talk) 22:59, 15 May 2025 (UTC)

See Hosting services for details and options. With luck, you can get one through Miraheze's RequestWiki service (as long as you have an e-mail address attached). --Slgrandson (talk) 23:15, 15 May 2025 (UTC)

Keeping Vector 2010--but ditching Vector 2022--on a third-party wiki

If there's really a means of doing so--tried hiding the 2022 option on my site's Special:Preferences as founding bureaucrat, but that interface is still appearing in "useskin" mode--let me know in advance. Pinging @Bawolff/@TheDJ/@Pppery/@Universal Omega/@MacFan4000/@Reception123 just in case. (Based on a recent Miraheze help-desk discussion.) --Slgrandson (talk) 23:34, 15 May 2025 (UTC)

The translation tool and its documentation is very confusing ..

I find the hints and messages that appear in and around the "Wikipedia translate page" very hard to understand. Often I have no idea what they are even referring to.

So I chose to ignore the gibberish and simply try the translation interface to see what happens:

• I open w:Block-stacking problem which is the page I wanted to translate to German. I hover the mouse pointer over "Contributions" in the top right corner and click on "Translations" and I am taken to "https://en.wikipedia.org/w/index.php?title=Special:ContentTranslation&campaign=contributionsmenu&to=en&filter-type=automatic&filter-id=previous-edits&active-list=draft&from=es#/"
• I am asked for the name of the Wikipedia article to be translated which takes me to "https://de.wikipedia.org/w/index.php?title=Spezial:Inhalts%C3%BCbersetzung&from=en&page=Block-stacking+problem&to=de"
• Here the title of the English Wikipedia page is automatically translated to the German "Blockstapelproblem". Exciting! But unfortunately all the following paragraphs are simply copied over to the right column exactly as they appear in the original article. No further translation seems to be happening.
• To the right of the page I read: "Translation services not available for the selected languages. Why?"
• When I click on "Why?" I am taken to "Special:MyLanguage/Help:Content translation/Translating/Initial machine translation" which explains exactly nothing about why the translation service might be able to translate the title but is "not available" for the actual content of the English Wikipedia article.
• The content of "Special:MyLanguage/Help:Content translation/Translating/Initial machine translation" is utterly confusing so I won't even start bothering to mention all the question that this help page raises. But it would be good to know if there is any way to choose between the six translation services listed on this help page and how to go about it.
• When I go to the discussion page of "Special:MyLanguage/Help:Content translation/Translating/Initial machine translation" and try to add a topic I am advised "Please do not post support questions here." Instead I am referred to this page here.
  • User:Prototypeperspective has posted on the discussion page that he is facing the same issue as myself and is pointing to the German page "https://de.wikipedia.org/wiki/Wikipedia_Diskussion:Technik/Skin/Beta/ContentTranslation#Nutzlos_(?)" where it becomes apparent that the problem might have persisted since 2022 or even 2017.
• Also on the right side of the "Wikipedia translate page" 3 "issues" are announced only 2 of which are actually displayed. I was not able to copy the text of the issues but none of them explain why the english passages from the left column are not translated into German when I click "Add translation" in the right column. One issue is titled "Template unavailable" and the other issue is titled "Part of your translation contains 100% unmodified text." Well, yes, this is exactly the problem I am trying to resolve. Below I am directed to "https://www.mediawiki.org/wiki/Help:Content_translation/Translating/Translation_quality" which also does not give any hints as to why the automatic translation might only work for the page title and not for the body of the article.

All of the help pages about the translation service I have been looking at are rather incomprehensible and pose many more question which I would be happy to list if anyone is interested ..

Any suggestions on how to get the automatic translation going?

best regards, KaiKemmann (talk) 01:31, 16 May 2025 (UTC)

This is not what you want to hear but the talk page for Help:Content translation/Translating/Initial machine translation is the right place to ask about this project in particular, or at least better suited than this desk. The "don't post support questions here" bit is meant for people who would mistakenly ask about general problems with MediaWiki itself, which should be done here. Tactica (talk) 12:46, 16 May 2025 (UTC)

Mediawiki with AI capabilities

Do we have any option to integrate AI with MediaWiki?

Like an AI search engine? Has anyone thought about this?

Regards/GT Testergt1302 (talk) 07:40, 16 May 2025 (UTC)

@Testergt1302 All AI systems affectively already search Wikipedia. When you say AI, do you perhaps mean a conversational engine, backed by an AI language model ? —TheDJ (Not WMF) (talk • contribs) 09:44, 17 May 2025 (UTC)

Hi, We have a private wiki, that have huge data/content. So, I am just thinking, if there is any AI capability that we can integrate with our wiki, that can help users while searching or editing etc... Testergt1302 (talk) 07:35, 19 May 2025 (UTC)

MediaWiki provides an API and HTML. AI's can index both generally. So you just need to configure your AI agent to be able to index and search these web pages. —TheDJ (Not WMF) (talk • contribs) 14:42, 20 May 2025 (UTC)

Exporting to xml in english only

Is it possible to export only the English language version of the page code and templates to an xml file? Kszwaba (talk) 11:06, 18 May 2025 (UTC)

@Kszwaba See the answer that you received last time you asked the same question. https://www.mediawiki.org/w/index.php?title=Topic:Yftpbcesi4md3jg3&topic_postId=yfu3hpq909syxm7v&topic_revId=yfu3hpq909syxm7v&action=single-view Malyacko (talk) 15:26, 20 May 2025 (UTC)

Database connection error

I have an arch linux driven server on which I maintain my own wiki using Mediawiki.

Until an update two weeks ago, the whole wiki worked perfectly, but since the update I get an error message that the database cannot be accessed.

I have set up my wiki with the following components:

• mediawiki with php8
• sqlite as database
• lighttpd as webserver

The following updates were made during the update on 05/03/25 (php-cgi & php-sqlite always have the same version number as php):

• mediawiki: 1.42.1-1 -> 1.43.1-1
• php: 8.3.9-1 -> 8.4.6-2
• sqlite: 3.46.0-1 -> 3.49.1-1
• lighttpd: 1.4.76-1 -> 1.4.79-2

On 05/10/2025 I carried out another update as part of a troubleshooting process:

• mediawiki: 1.43.1-1
• php: 8.4.6-2 -> 8.4.7-1
• sqlite: 3.49.1-1 -> 3.49.2-1
• lighttpd: 1.4.79-2

The error persisted. After each update of Mediawiki I have performed php maintenance/run.php update.

After activating the corresponding flag in LocalSettings.php I get the following error message:

MediaWiki internal error.

Original exception: [b923ab9115bdc4186a4ba4d9] /mediawiki/index.php?title=Hauptseite Wikimedia\Rdbms\DBConnectionError: Cannot access the database: Error 14: unable to open database file
Function: Wikimedia\Rdbms\DatabaseSqlite::open
Query: PRAGMA synchronous = NORMAL

Backtrace:
from /usr/share/webapps/mediawiki/includes/libs/rdbms/database/Database.php(1221)
#0 /usr/share/webapps/mediawiki/includes/libs/rdbms/database/DatabaseSqlite.php(230): Wikimedia\Rdbms\Database->newExceptionAfterConnectError()
#1 /usr/share/webapps/mediawiki/includes/libs/rdbms/database/Database.php(263): Wikimedia\Rdbms\DatabaseSqlite->open()
#2 /usr/share/webapps/mediawiki/includes/libs/rdbms/database/DatabaseFactory.php(157): Wikimedia\Rdbms\Database->initConnection()
#3 /usr/share/webapps/mediawiki/includes/language/LCStoreDB.php(143): Wikimedia\Rdbms\DatabaseFactory->create()
#4 /usr/share/webapps/mediawiki/includes/language/LCStoreDB.php(56): LCStoreDB->getWriteConnection()
#5 /usr/share/webapps/mediawiki/includes/language/LocalisationCache.php(566): LCStoreDB->get()
#6 /usr/share/webapps/mediawiki/includes/language/LocalisationCache.php(612): LocalisationCache->isExpired()
#7 /usr/share/webapps/mediawiki/includes/language/LocalisationCache.php(479): LocalisationCache->initLanguage()
#8 /usr/share/webapps/mediawiki/includes/language/LocalisationCache.php(381): LocalisationCache->loadItem()
#9 /usr/share/webapps/mediawiki/includes/language/Language.php(567): LocalisationCache->getItem()
#10 /usr/share/webapps/mediawiki/includes/title/MediaWikiTitleCodec.php(120): MediaWiki\Language\Language->needsGenderDistinction()
#11 /usr/share/webapps/mediawiki/includes/title/Title.php(1157): MediaWiki\Title\MediaWikiTitleCodec->getNamespaceName()
#12 /usr/share/webapps/mediawiki/includes/page/Article.php(494): MediaWiki\Title\Title->getNsText()
#13 /usr/share/webapps/mediawiki/includes/actions/ViewAction.php(78): Article->view()
#14 /usr/share/webapps/mediawiki/includes/actions/ActionEntryPoint.php(733): ViewAction->show()
#15 /usr/share/webapps/mediawiki/includes/actions/ActionEntryPoint.php(510): MediaWiki\Actions\ActionEntryPoint->performAction()
#16 /usr/share/webapps/mediawiki/includes/actions/ActionEntryPoint.php(146): MediaWiki\Actions\ActionEntryPoint->performRequest()
#17 /usr/share/webapps/mediawiki/includes/MediaWikiEntryPoint.php(200): MediaWiki\Actions\ActionEntryPoint->execute()
#18 /usr/share/webapps/mediawiki/index.php(58): MediaWiki\MediaWikiEntryPoint->run()
#19 {main}

Exception caught inside exception handler: [b923ab9115bdc4186a4ba4d9] /mediawiki/index.php?title=Hauptseite Wikimedia\Rdbms\DBConnectionError: Cannot access the database: Error 14: unable to open database file
Function: Wikimedia\Rdbms\DatabaseSqlite::open
Query: PRAGMA synchronous = NORMAL

Backtrace:
from /usr/share/webapps/mediawiki/includes/libs/rdbms/database/Database.php(1221)
#0 /usr/share/webapps/mediawiki/includes/libs/rdbms/database/DatabaseSqlite.php(230): Wikimedia\Rdbms\Database->newExceptionAfterConnectError()
#1 /usr/share/webapps/mediawiki/includes/libs/rdbms/database/Database.php(263): Wikimedia\Rdbms\DatabaseSqlite->open()
#2 /usr/share/webapps/mediawiki/includes/libs/rdbms/database/DatabaseFactory.php(157): Wikimedia\Rdbms\Database->initConnection()
#3 /usr/share/webapps/mediawiki/includes/language/LCStoreDB.php(143): Wikimedia\Rdbms\DatabaseFactory->create()
#4 /usr/share/webapps/mediawiki/includes/language/LCStoreDB.php(56): LCStoreDB->getWriteConnection()
#5 /usr/share/webapps/mediawiki/includes/language/LocalisationCache.php(539): LCStoreDB->get()
#6 /usr/share/webapps/mediawiki/includes/language/LocalisationCache.php(403): LocalisationCache->loadSubitem()
#7 /usr/share/webapps/mediawiki/includes/language/LocalisationCache.php(419): LocalisationCache->getSubitem()
#8 /usr/share/webapps/mediawiki/includes/language/MessageCache.php(1267): LocalisationCache->getSubitemWithSource()
#9 /usr/share/webapps/mediawiki/includes/language/MessageCache.php(1209): MessageCache->getMessageForLang()
#10 /usr/share/webapps/mediawiki/includes/language/MessageCache.php(1103): MessageCache->getMessageFromFallbackChain()
#11 /usr/share/webapps/mediawiki/includes/Message/Message.php(1554): MessageCache->get()
#12 /usr/share/webapps/mediawiki/includes/Message/Message.php(1036): MediaWiki\Message\Message->fetchMessage()
#13 /usr/share/webapps/mediawiki/includes/Message/Message.php(1127): MediaWiki\Message\Message->format()
#14 /usr/share/webapps/mediawiki/includes/exception/MWExceptionRenderer.php(253): MediaWiki\Message\Message->text()
#15 /usr/share/webapps/mediawiki/includes/exception/MWExceptionRenderer.php(399): MWExceptionRenderer::msg()
#16 /usr/share/webapps/mediawiki/includes/exception/MWExceptionRenderer.php(107): MWExceptionRenderer::reportOutageHTML()
#17 /usr/share/webapps/mediawiki/includes/exception/MWExceptionHandler.php(135): MWExceptionRenderer::output()
#18 /usr/share/webapps/mediawiki/includes/exception/MWExceptionHandler.php(239): MWExceptionHandler::report()
#19 /usr/share/webapps/mediawiki/includes/MediaWikiEntryPoint.php(222): MWExceptionHandler::handleException()
#20 /usr/share/webapps/mediawiki/includes/actions/ActionEntryPoint.php(82): MediaWiki\MediaWikiEntryPoint->handleTopLevelError()
#21 /usr/share/webapps/mediawiki/includes/MediaWikiEntryPoint.php(206): MediaWiki\Actions\ActionEntryPoint->handleTopLevelError()
#22 /usr/share/webapps/mediawiki/index.php(58): MediaWiki\MediaWikiEntryPoint->run()
#23 {main}

Opening the corresponding database with

sqlite bp_wiki.sqlite

as http and checking the database with

sqlite> .database

gives

main: /usr/share/webapps/data/bp_wiki.sqlite r/w

showing that the database is present and also readable and writeable. The database is owned by user and group http.

So it seems, that the database containing the wiki content is not accessable by php!?

What could be the cause of this error? Mrpaul2025 (talk) 09:21, 19 May 2025 (UTC)

A common cause for this is an issue with temp file access. In order to work with sqlite, you need to be able to create temp files. —TheDJ (Not WMF) (talk • contribs) 14:40, 20 May 2025 (UTC)

ok, and which folder or path could be the problem? Is there a special path or program, one of the components (mediawiki, php, sqlite) needs?

What I don't understand is, that it worked until my first update listed in the question. But I didn't find any log entry, that the update caused some changes in the permissions. 77.22.252.46 17:29, 20 May 2025 (UTC)

Can't add Gregorian chant due to old bug

I tried to add Gregorian chant to a wiki page with Extension:Score, and I ran into this problem: T289651

It looks like that bug has been stalled for a few years. Is there any workaround I can use in the meantime, or anything I can do to help get that fixed? 50.230.238.42 04:01, 21 May 2025 (UTC)

The details are obscure to me, but the documentation recommends using Shellbox if you can't trust everyone who edits your wiki and configuring LilyPond directly. "Certain functionality will not work in safe mode, the fix for that is to modify LilyPond to allow that functionality in safe mode" - assuming of course, you know what functionality is affected and how to enable it. Rand(1,2022) (talk) 06:47, 21 May 2025 (UTC)