Jump to content

Project:Support desk

Add topic
From mediawiki.org
Latest comment: 4 minutes ago by MouseCursor in topic Convert timestamp to human-readable text?
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".

Embedding a Google Form into my Miraheze wiki page

[edit]

Need permissions to embed HTML on your wiki page. I tried to embed HTML code generated for my GOOGLE Form. But it's not working. Please help. Jeetudas (talk) 19:03, 3 April 2025 (UTC)Reply

You could try Extension:Widgets. Jonathan3 (talk) 20:24, 3 April 2025 (UTC)Reply
Afraid not. Widgets has been disabled on MH since late December 2020 over security concerns. The only way out is through highly intricate custom JS on your own domain, which not everyone (this wiki-veteran included!) has prolonged experience or confidence with. --Slgrandson (talk) 01:41, 18 April 2025 (UTC)Reply
Thanks. I'd not heard about that, but am currently using the Widgets extension on my own wiki. I've asked for further details on the extension talk page: https://www.mediawiki.org/wiki/Extension_talk:Widgets#Extension_update_since_Miraheze_%222020-12-23_Security_Disclosure%22? Jonathan3 (talk) 20:17, 24 April 2025 (UTC)Reply
@Jeetudas For security reasons only specific bits of HTML are allowed to be used in wiki pages, see Help:HTML in wikitext. You would need to ask the Miraheze system administrators for help, though I suspect they will not allow this for security reasons. Could you not just provide a link to the form? 86.23.109.101 12:55, 4 April 2025 (UTC)Reply

Safe to clear mw_objectcache?

[edit]

I am encountering the known bug with sessions data loss when setting $wgMainCacheType to CACHE_ACCEL. I added $wgSessionCacheType = CACHE_DB; to store the session data in the database to go around this issue. Now I am wondering if I should clear the table mw_objectcache to remove old cache which should now be handled by APCu. I don't really mind to log out all users with this move, but I could also just delete all non-session files. Is this safe to do? Or is it maybe unnecessary 'cause it'll clear itself over time? I had $wgMainCacheType set to CACHE_NONE for years until now. DonnyPro (talk) 12:00, 11 April 2025 (UTC)Reply

Yes, from my experience the object cache can be cleared at any time. But it should not be necessary. Osnard (talk) 14:48, 25 April 2025 (UTC)Reply

Syntax when protecting pages for a non-standard length of time

[edit]

I'm a bureaucrat at Wikispecies and an administrator at Swedish Wikivoyage and Wikimedia Sweden (WMSE). When protecting a page on any of those wikis I'm faced with the option to protect it for a fixed period of time (one week, one month, "infinitely" etc.), but there's also an option to chose "Other time" by entering code into a text box. However, I can't seem to find any information about how this command should be formatted, nor anything about the preferred date format and such. I've looked in Help:Protected pages and similar MediaWiki help pages, but struck no luck. (Most Meta-Wiki pages on the subject simply soft-redirects to MediaWiki). Even though protecting pages is (and should be) a fairly rare event, any help would be much appreciated. –Best regards, Tommy Kronkvist (talk), 19:19, 16 April 2025 (UTC).Reply

I've wondered that too. According to the code, the other time can be 'infinite', 'indefinite', 'infinity', or 'never' to mean infinite, or whatever php's strtotime function accepts (with some qualification that your user timezone is not accounted for). --Clump (talk) 13:57, 1 May 2025 (UTC)Reply
[edit]

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)Reply

@Slgrandson I havent tested, but generally an ISO timestamp will likely work yyyy-mm-dd hh:mm:ss —TheDJ (Not WMF) (talkcontribs) 08:16, 21 April 2025 (UTC)Reply
@TheDJ: If so, which part of the calls is the timestamp appended to? --Slgrandson (talk) 20:58, 21 April 2025 (UTC)Reply

Fediverse Creator meta tag

[edit]

Wiki: https://joinfediverse.wiki Version: 1.41.0

Hi, Mastodon has a feature where you can make sure your profile is linked to with every link to your homepage on the Fediverse. You can see an example here: https://fedi.at/@FediverseFoundation/114065155360271846 On the bottom of the link preview it says "Mehr von Fediverse Foundation" which links back to the same profile that posted the post in that case. I'd like to do that with my wiki's Fediverse profile.

Mastodon's simple instruction is to put the following html code on the website (either in every article or somehow globally):

<meta name="fediverse:creator" content="@JoinFediverseWiki@climatejustice.social">

Where can I put that in my wiki so it will work with every article on the wiki? Do I need an extension for it? PKFP (talk) 18:19, 19 April 2025 (UTC)Reply

@PKFP You can write a hook in your localsettings.php that hooks into something like Manual:Hooks/BeforePageDisplay adding a setMeta to every single pageview. —TheDJ (Not WMF) (talkcontribs) 08:12, 21 April 2025 (UTC)Reply
Hey, thanks for your tip. Could you explain this a bit further? I forwarded it to the tech person for the wiki, but he didn't get it yet. PKFP (talk) 06:26, 24 April 2025 (UTC)Reply
@PKFP Something like this in LocalSettings.php might work, using the BeforePageDisplay hook, $wgHooks & OutputPage::addMeta():
$wgHooks["BeforePageDisplay"][] = function($out, $skin) {
    $out->addMeta("fediverse:creator", "@JoinFediverseWiki@climatejustice.social");
};
(disclaimer: this code comes with no warranty, etc.!)
Best, ‍—‍a smart kitten[meow] 20:28, 25 April 2025 (UTC)Reply
Maybe this would be a suitable addition to Extension:WikiSEO? It might be worth raising a feature request for that (it used to support twitter:creator). Sam Wilson 09:16, 21 April 2025 (UTC)Reply
Thanks, I'll try. PKFP (talk) 06:26, 24 April 2025 (UTC)Reply

How do I change the article content's background color by assigned category?

[edit]

I tried to use Ciencia Al Poder's Snippets/Style pages based on categories, and modified it to work with the article's content background but it didn't work.

I tried something like this:

/** * Adds CSS classes to the body tag based on the categories this page belongs to * * @source * @revision 2016-01-18 */ (function($, mw) { var fn = function() { var cats = mw.config.get('wgCategories'), newClasses; if (cats) { newClasses = $.map(cats, function(el) { return 'cat-' + encodeURIComponent(el.replace(/[ .]/g, '_')).replace(/%/g, '_'); }).join(' '); $(document.body).addClass(newClasses); } }; if (document.body) { fn(); } else { $(fn); } })(jQuery, mw); WongIsNotOK (talk) 17:26, 21 April 2025 (UTC)Reply

Quickstart

[edit]

I just became an interface administrator of Tagalog Wiktionary. The only admin before me has been very inactive in the site for around a decade now. I'm now lost. I want to begin with UI changes but the MediaWiki FAQ says I should have SSH access or something but how do I have those? How do I run automation bots as well? And how do I know the mediawiki version of the site? Can I upgrade it? Ysrael214 (talk) 11:09, 23 April 2025 (UTC)Reply

SSH access is mainly a means to upgrade the MediaWiki software when it's running on a remote server. Fortunately you don't need any of that because the WMF takes care of upgrades for you. To check the version of MediaWiki you're working with you take a look in Special:Version. For bots, see Manual:Bots. Being an interface admin, I presume you also want to take a look at Manual:CSS and probably to the CSS code used by other chapters of Wiktionary. Tactica (talk) 00:02, 24 April 2025 (UTC)Reply

Diff API for comapring 2 texts (not existing pages)?

[edit]

I'm writing a userscript for editing a page. I let users compose text before saving. So I want to compare 2 text (multi-row) strings with the MW's internal diff logic as it is better than other open source libraries.

How can I pass two text strings to the Diff API? All I found is API:Compare which requires existing pages. Subfader (talk) 13:31, 24 April 2025 (UTC)Reply

@Subfader There is indeed no arbitrary string comparison service inside MediaWiki. —TheDJ (Not WMF) (talkcontribs) 07:51, 25 April 2025 (UTC)Reply

Discussion at Extension_talk:CategoryTree#Suppressing_"no_subcategories"

[edit]

 You are invited to join the discussion at Extension_talk:CategoryTree#Suppressing_"no_subcategories". Sdkbtalk 18:45, 24 April 2025 (UTC)Reply

DNS Blacklist issues

[edit]

Hello. I have been using DNS Blacklist URLs on my wiki to combat spam, and I also have the ConfirmAccount extension installed and enabled on my wiki family. However, I still get account requests from spambots.

Here is the code that I added to my Localsettings.php file:

$wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org.', 'zen.spamhaus.org.', 'dnsbl.tornevall.org.', 'spam.dnsbl.sorbs.net.', 'rbl.dnsbl.im.', 'noptr.spamrats.com.', 'all.s5h.net.', 'z.mailspike.net.' );

Is there something wrong with the DNS blacklist configuration? Does this feature only affect editing from the blacklisted IPs? If there is something wrong, then how do I fix it? Thank you for reading. Newman2 (talk) 20:48, 24 April 2025 (UTC)Reply

@Newman2 All relevant information is collected here Manual:Combating spam. In general, whenever you run a server (of any type) on the internet these modern days, you should be prepared for a barrage of never stopping spam and abuse. I looked at the DnsBlacklistUrl documentation page, and it was a bit sparse, so I perused the source code to figure out how it is supposed to work and added that here Manual:$wgEnableDnsBlacklist. —TheDJ (Not WMF) (talkcontribs) 07:48, 25 April 2025 (UTC)Reply
Isn't this setting supposed to be a boolean? I suspect you edited the wrong article. Tactica (talk) 00:08, 26 April 2025 (UTC)Reply

Gadget for auto numeration and Vector-2022

[edit]

Hello, the auto numeration activated with MediaWiki:Gadget-autonum.css and MediaWiki:Gadget-autonum.js (I load them in my global.js) does not work well together with Vector-2022 skin, because the counter reset does not work, and so all lower sections are just counted up. Note, that in vector-2022 only the else tree of the script is active and the code of the CSS is used. If you think, why I do not just ask the author Krinkle – well he wrote almost a year ago “I do not use the autonum gadget myself. For now, I have exceed the time I'm willing to spend on this gadget. I suggest gathering support and awareness of other people in the community, to hopefully find someone who is able and willing to maintain this JS/CSS snippet for further modifications.” (Krinkle’s user talk page on meta, cf. meta:Special:Diff/26715423 or the full conversation at m:Special:PermaLink/26721127#Section autonumeration with Parsoid). As an example: Manual:FAQ (itself not ready for vector-2022, at least the toc part I looked for) has 12 sections, and the latest one has 6 subsections which is fine displayed in (legacy) Vector from 2010, but with Vector 2022 I see the count 12.107. — Speravir (talk) – 00:35, 25 April 2025 (UTC)Reply

Hello sir, I saw your problem. From my investigation, Vector-2022 relies on the CSS-based numbering (the else branch in autonum.js, using autonum.css) when no table of contents (TOC) is present, as per the gadget’s design. The CSS (https://en.wikipedia.org/wiki/MediaWiki:Gadget-autonum.css) uses counter-reset properties, but these seem incompatible with Vector-2022’s DOM structure or styling, possibly due to changes in how headings are rendered (e.g., .mw-headingclasses, per Vector-2022 documentation).
I’m aware that Krinkle, the gadget’s author, noted in 2024 that they no longer maintain this gadget and suggested community collaboration for further fixes (see meta:Special:PermaLink/26721127#Section_autonumeration_with_Parsoid). I’m hoping to gather insights or assistance from others familiar with Vector-2022’s CSS/JS or gadget maintenance. Has anyone encountered similar issues with autonum or other CSS-based numbering gadgets in Vector-2022? Are there known workarounds, such as adjusting the counter-reset selectors to match Vector-2022’s heading structure, or modifying the JS to handle TOC-less pages differently? ProfessorNikolaus (talk) 18:53, 25 April 2025 (UTC)Reply
Your reply reminded me that I had myself written to Krinkle about the issue for pages without toc. I just did not consider now that the new skin has the same section structure in DOM. But because I ask for a change of a page gadget I seem to be wrong in the support desk. I'll ask at the Village Pump, instead, see VP: Gadget for auto numeration and Vector-2022. — Speravir (talk) – 00:16, 29 April 2025 (UTC)Reply

Importing pages from old wiki into newest wiki 8.3.0

[edit]

I want to manually insert all my pages from an old wiki project into a new wiki website (using mediawiki 8.3.0). The database in my new wiki shows pages are stored in "ew7o_page". In my old wiki this was calles "page" What is the best way to export from old wiki and import (insert) in newest wiki ? Same for "pagelinks" : need to be inserted in "ew7o_pagelinks" . When I try this now it's creating a new row in my SQL with the name "page". The "ew7o_page" reamains unchanged.

Stevy7 (talk) 10:14, 27 April 2025 (UTC)Reply

@Stevy7: What do you mean by "mediawiki 8.3.0"? The latest version is MediaWiki 1.43. Oh, or do you mean you're updating from MediaWiki 1.8? That's impressive, if you've still got it running! Can you upgrade to 1.35 and then step through LTS versions since then? Or perhaps export the site's pages as XML (see Manual:DumpBackup.php) and then import in to a fresh install? Sam Wilson 03:31, 1 May 2025 (UTC)Reply

Error messages in SkyWiki wikis

[edit]

Hi, I've reported several error messages on SkyWiki wikis, including phabricator.skywiki.org. I've tracked them as issues in Wikimedia Phabricator (see links to issues at the right of this message), but these issues were all rejected as invalid. How can I contact SkyWiki founder in order to have those bugs fixed? --Agusbou2015 (talk) 18:26, 27 April 2025 (UTC)Reply

SkyWiki, which is already outside Wikimedia's purview/priority/attention, has been lingering in the shadows of Miraheze, Fandom, et al.--but not even Google has the home URL indexed on its first results page as I type! (The top result for "SkyWiki", unquoted, is a Fandom site on an unrelated video game.) Afraid I could say otherwise, but unless you or I are lucky to find their support e-mail or social handle(s), there's nothing else that can be done on the matter. --Slgrandson (talk) 08:08, 29 April 2025 (UTC)Reply
"phabricator.skywiki.org" never existed (you can enter literally any domain like "agusbou2015.skywiki.org" and get the very same error for non-existing sites) thus mentioning non-existing subdomains makes no sense. Phabricator is not some subdomain magically included in every MediaWiki installation to report issues but it is a complete separate piece of software hosted by Wikimedia. Malyacko (talk) 14:41, 1 May 2025 (UTC)Reply

Extensions and skins not working (most of the time)

[edit]

Hi everyone, I am new here, so i might not get everything at first or botch some specialistic MW wording.

Getting to the problem - I appear to have a problem with LESS variables. Many skins are affected, like Vector, Minerva and Timeless, possibly many more (currently only one "working" is Chameleon). The symptoms are: broken CSS, buttons not working, extensions not working (happens in Chameleon too). There are images present, so I don't think that the solution from here applies, but I tried it either way and it does not make a change.

With broken LESS variables comes more problems - when I try to enable extensions like WikiEditor or VisualEditor I get 50kB of console errors with Less_Exception_Compiler saying that @variable_name is not defined (which clearly is defined in mediawiki.skins.defaults.less). It also frequently happens with @cdx_variable_name which i deduce is some codex variable which is not defined in mediawiki.skins.defaults.less, but i don't know how to handle this. It's a shame, but it can be worked around by writing in pure wikicode. Yet, there are problems still (which I didn't find the cause for), thumbnails and frames are not rendering correctly. The image is here, there is a caption, but there is no frame, image is not snapping to the right (if set to |right|), text isn't wrapping around it.

I am wandering if this is something on my hosting server side or with my installation, but I don't really know... I'll get you through installation steps i went through:

  1. download and unpack mediawiki, push it to my host ftp, import php.ini file and make /tmp
  2. run the installation following the tutorial
  3. wiki breaks and sends me a giant list of errors with Less_Exception_Compiler
  4. I download and install Chameleon via Composer (site isn't that broken now)
  5. I download a REL1_43 extension and put it in /extensions/, set (eg) wfLoadExtension( 'VisualEditor' );
  6. I try to edit a page using VE, but nothing is showing, console is red full with errors

So yeah, not much here to be honest... Right now I have almost every important extension disables, because it breaks my site. What can be the cause? What am i doing wrong?

I tried installing the 1.43.0 version, but it gives me the same results.

Nazwa Wersja
MediaWiki 1.43.1
PHP 8.4.0 (uwsgi)
ICU 69.1
MySQL 8.0.33-25
Pygments 2.17.2
Lua 5.1.5

Thanks for help in advance! Astroksiezyc wiki (talk) 01:45, 28 April 2025 (UTC)Reply

(for anyone looking at this, there are some stacktrace screenshots at phab:T392761) ‍—‍a smart kitten[meow] 09:50, 28 April 2025 (UTC)Reply
@Astroksiezyc wiki "download and unpack mediawiki," from where ? git, tarball, your linux distro ? —TheDJ (Not WMF) (talkcontribs) 16:47, 2 May 2025 (UTC)Reply
I just downloaded the file from the MediaWiki download website. Tomorrow I might try to get it directly from git if it would be better.
Do the packages differ in some way? Or maybe am I missing some crucial installation step when downloading from official website? Astroksiezyc wiki (talk) 22:39, 2 May 2025 (UTC)Reply

Wikimedia installation repair needed

[edit]

Hello Wikimedians - I'm a non-coder who installed a private Wikimedia wiki on my Go Daddy website, for my own use in organizing local history research. The available installation tools worked fine, and the website worked well until recently, when I got a notice that I needed to upgrade the php. I didn't find any non-coder tools to help me do that, and my efforts have really screwed things up - now I can't even log in. I need someone who knows how to fix the site (for pay, of course). How do I find such a person? WCCasey (talk) 17:41, 29 April 2025 (UTC)Reply

There are some people listed here: Professional development and consulting. Jonathan3 (talk) 19:09, 29 April 2025 (UTC)Reply
@WCCasey: You shouldn't have to be a coder to install and upgrade MediaWiki, although I know that sometimes the process can be a bit tricky. Ideally, we'd make it easier! If you do want to try doing it yourself, you could try posting here describing the issues you're having with the upgrade, and we could try to help. It might not be insurmountable. Sam Wilson 03:11, 30 April 2025 (UTC)Reply

Thanks for pointing me to that list - that's what I was looking for. Also thanks for offering to help me fix things myself. I may be back at some point to try that! WCCasey (talk) 16:20, 1 May 2025 (UTC)Reply

Interwiki issues with vector 2022 for non-languages

[edit]

Dear ∀,

In Vector 2022 I have difficulties with interwiki connections in my local wiki (1.39, ULS activates) as soon as the link happens not to be an ISO language prefix.

In special:interwiki I have defined those interlanguage prefices:

aa https://localhost/mediawiki/index.php/$1 ja nein Bearbeiten, Löschen
en https://en.wikipedia.org/wiki/$1 ja nein Bearbeiten, Löschen
urwiki http://localhost/mediawiki/index.php/$1 ja nein Bearbeiten, Löschen

In Names.php I have defined , as far as my question is concerned, these:

'urwiki' => ' mein Urwiki', # Test für Sprachverknüpfung
'en' => 'English', # English
'aa' => 'Urwiki via aa', # Afar

On my Main Page I added:

[[urwiki:Main Page]][[en:Wikipedia:Village pump]][[aa:Main Page]]

Under vector 2010 I am offered all three links

Under vector 2022, the interwiki popup is flagged with three languages, but if I open the popup, only en and aa are being offered, beside a lot of whitespace.

How can I make mediawiki handle urwiki the same way as ISO prefices?

Thank you in advance!

Yours, Ciciban (talk) 10:49, 30 April 2025 (UTC)Reply

Mediawiki styles not loading after upgrade

[edit]

Hello,

I've been at this for a couple of days now and no online resource could help so far. I upgraded my mediawiki 1.31 to 1.35.14, planning to go to the 1.43. I followed the procedure described in the manual (backed up the db and images folder -> unzipped mw_1.35 tar replaced relevant files -> ran php maintenance/update.php), but after all the steps it seems mw is having issues grabbing the right modules:

Skipped unresolvable module site

Skipped unresolvable module mediawiki.page.startup

Skipped unresolvable module mediawiki.page.ready

Skipped unresolvable module skins.vector.legacy.js

Skipped unresolvable module ext.visualEditor.desktopArticleTarget.init

Skipped unresolvable module ext.visualEditor.targetLoader

There is also this javascript error: Uncaught TypeError: Cannot read properties of undefined (reading 'state')  @https://[redacted].com/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector

And this text in what i assume was suppose to be the css file in sources?

Problematic modules: {"ext.visualEditor.desktopArticleTarget.noscript":"missing","mediawiki.special.version":"missing","skins.vector.styles.legacy":"missing"}

Due to these issues, while the wiki displays my content, there is 0 styling on the website.

I cleared caches, made sure the temp folder is writable, followed the manual for the short url structure (hopefully right), redownloaded the 1.35 Vector skin with no luck, and many others. I also tried activating debug in LocalSettings but that does not show anything on the page.

I would very much appreciate some input if anyone has encountered this before.

Setup:

Product Version MediaWiki 1.35.14

PHP 7.4.33 (apache2handler)

MariaDB 10.11.11-MariaDB-0ubuntu0.24.04.2

ICU 74.2

Entry point URLs

Article path /wiki/$1

Script path /w

index.php /w/index.php

api.php /w/api.php

rest.php /w/rest.php

Thanks in advance. Sorestoreclerk (talk) 08:25, 1 May 2025 (UTC)Reply

ResourceLoader Issue? MediaWiki:Minerva.js not loading/executing (MW 1.43.1, MF 2.4.1)

[edit]

Hello,

I am seeking help diagnosing an issue where JavaScript placed in MediaWiki:Minerva.js is not being loaded or executed in the mobile view (MinervaNeue skin via MobileFrontend). I am new to MediaWiki administration and web development in general and have been heavily assisted by AI (Gemini/ChatGPT) in troubleshooting so far.

Environment:

  • MediaWiki: 1.43.1
  • PHP: 8.1.32 (litespeed)
  • Database: 10.6.21-MariaDB-cll-lve
  • Host: Namecheap Shared Hosting (cPanel, LiteSpeed Web Server)
  • Skin: MinervaNeue (Mobile), Vector 2022 (Desktop)
  • Relevant Extensions: MobileFrontend 2.4.1, UniversalLanguageSelector [2025-03-15 MLEB], Translate [2025-03-15 MLEB] (full list available if needed)
  • Configuration: $wgMFEnableSiteJs = true; added after wfLoadExtension('MobileFrontend'). $wgAllowUserJs is default (true).

Goal: Customize the mobile navigation menu by adding custom links/sections via JavaScript, similar in structure to mariowiki's mobile menu.

Problem & Diagnostics: JavaScript code in MediaWiki:Minerva.js fails to execute.

  1. An initial attempt using simple jQuery .append() did successfully add <li> elements to the menu (targeting #p-navigation), but styling was incorrect(primitive and rugged). I would like the custom links to have the same style as other things in the default menu.
  2. Subsequent attempts using the mw.mobileFrontend.menu.buildLink API failed (no elements added).
  3. Reverting to the simple jQuery .append() code also failed in later tests (no elements added).
  4. Crucial Test: Replacing the entire content of MediaWiki:Minerva.js with only console.log('Test'); results in no output in the F12 browser console when loading the mobile view (after purging cache and hard refreshing).
  5. Network Analysis: Checking the Network tab in F12 Dev Tools (mobile view) confirms that the content of MediaWiki:Minerva.js (the console.log line) is not present in the response body of any relevant load.phprequest. This indicates ResourceLoader is not serving the updated module content.

Troubleshooting Steps Performed (All Ineffective):

  • Confirmed $wgMFEnableSiteJs = true; and $wgAllowUserJs is default (true).
  • Extensive browser cache clearing (hard refresh, incognito mode, multiple browsers).
  • Used ?action=purge on MediaWiki:Minerva.js, MediaWiki:Minerva.css, and main pages.
  • Cleared host-provided CDN cache (Namecheap Supersonic) and LiteSpeed page cache.
  • Attempted to clear server-side PHP OPCache by editing/saving LocalSettings.php (add/remove comment).
  • Checked F12 console repeatedly for relevant JavaScript errors (none found).
  • Checked cPanel error logs for relevant PHP errors (none found).
  • Checked cache/ directory permissions (755) and found it only contains .htaccess (suggesting potential write issues, but unconfirmed).
  • Tested with ?debug=true parameter (no relevant debug output or errors observed).
  • (Note: I am unable to access Phabricator due to an IP block).

Question: Given that MediaWiki:Minerva.js is configured to load ($wgMFEnableSiteJs=true) but is demonstrably not being served by ResourceLoader (load.php), what could be the cause?

  • Is this a known bug in MediaWiki 1.43.1 or MobileFrontend 2.4.1 regarding ResourceLoader module invalidation or loading for MediaWiki:Minerva.js / site.mobile / skins.minerva.site?
  • Are there further steps to debug ResourceLoader module delivery beyond checking the Network response and using ?debug=true?
  • Could this be related to server-side caching mechanisms (OPCache, RL file cache) that resist standard invalidation methods, or a file permission/ownership issue preventing RL cache writes?

Any insights or suggestions would be greatly appreciated. Thank you! Segremost (talk) 12:22, 1 May 2025 (UTC)Reply

Cannot access the database error appearing on wiki

[edit]

MediaWiki Version: 1.36.2

PHP Version: 7.4.33 (litespeed)

Website: https://converter.penguinicewikis.com/mw19/

Hello. I know I may have posted something similar to this before, but I have problems with one of my wikis. When I try to access my wiki, I get a "Cannot access the database" error. And when I try to perform rebuildall.php in SSH, I get a related error. The error may appear on the link to the website above For problems in SSH, this is what the error in the SSH Terminal looked like:

Wikimedia\Rdbms\DBConnectionError from line 1507 of /home/gjlxrtap/public_html/mw19/includes/libs/rdbms/loadbalancer/LoadBalancer.php: Cannot access the database: Unknown error (localhost)

  1. 0 /home/gjlxrtap/public_html/mw19/includes/libs/rdbms/loadbalancer/LoadBalancer.php(995): Wikimedia\Rdbms\LoadBalancer->reportConnectionError()
  2. 1 /home/gjlxrtap/public_html/mw19/includes/libs/rdbms/loadbalancer/LoadBalancer.php(960): Wikimedia\Rdbms\LoadBalancer->getServerConnection(0,'gjlxrtap_mw3455...', 0)
  3. 2 /home/gjlxrtap/public_html/mw19/includes/libs/rdbms/loadbalancer/LoadBalancer.php(1126): Wikimedia\Rdbms\LoadBalancer->getConnection(-1, Array, 'gjlxrtap_mw3455...', 0)
  4. 3 /home/gjlxrtap/public_html/mw19/maintenance/includes/Maintenance.php(1410): Wikimedia\Rdbms\LoadBalancer->getMaintenanceConnectionRef(-1, Array, 'gjlxrtap_mw3455...')
  5. 4 /home/gjlxrtap/public_html/mw19/maintenance/rebuildall.php(44): Maintenance->getDB(-1)
  6. 5 /home/gjlxrtap/public_html/mw19/maintenance/doMaintenance.php(112): RebuildAll->execute()
  7. 6 /home/gjlxrtap/public_html/mw19/maintenance/rebuildall.php(67): require_once('/home/gjlxrtap/...')

Thank you for reading. Newman2 (talk) 14:45, 1 May 2025 (UTC)Reply

@Newman2 There are a few tips in https://www.mediawiki.org/w/index.php?title=Topic:Vgqkw937xxolc0mq&action=history that you may try. —TheDJ (Not WMF) (talkcontribs) 16:29, 2 May 2025 (UTC)Reply
[edit]

My company has an existing wiki that's been around a long time. I'm attempting to get it migrated, upgraded and working (on Windows Server). Original is on MediaWiki 1.18.2, the new one is MediaWiki 1.43.1. Most everything has gone ok with the migration and upgrade. One issue that was discovered is file:// links don't work. Originally, they did nothing when clicking on them. I have since enabled https and added the site to IE compatibility mode in Edge and now the links open saying "access to the file was denied. ...not readable, moved, file permissions." But I can copy/paste the link into a new window and it opens fine (so the file still exists and it's not a permissions issue). Things I've done:

verified $wgUrlProtocols has file: entry

enabled https

added site to local intranet sites, allowed pop-ups, and IE compatibility mode sites

enabled IntranetFileLinksEnabled policy locally

I've done a lot of researching on the internet trying any possible fix I could find. Any other ideas of things to try?

If the files do need to be moved local to the MediaWiki server and linked to there, is there an easy way to update all existing links?

Twittgo (talk) 18:36, 1 May 2025 (UTC)Reply

upgrade process

[edit]

Hi - we recently took over the mediawiki server and it is running version 1.19.23. I would like to know what would be the ideal way to bring it tot he latest version. 128.249.96.18 22:07, 1 May 2025 (UTC)Reply

There's some guidance about which version to upgrade to first at Manual:Upgrading#Check_requirements. Jonathan3 (talk) 13:52, 2 May 2025 (UTC)Reply

Some images not showing after Upgrade from 1.31 to 1.43

[edit]

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)Reply

Convert timestamp to human-readable text?

[edit]

E.g. 20250503162843 to 03/05/2025? (but for any timestamp, not just revision timestamp) MouseCursor (talk) 16:28, 3 May 2025 (UTC)Reply