Project:Support desk/Archive 23
| This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Vector 2022 dark mode behavior with caching
Does anyone know if you make the "os" setting the default will the caching work correctly? Using regular MediaWiki caching, not Varnish. I remember that was a concern when dark mode was being developed. I want to hear if it is fixed or if there are settings that need to be adjusted. Flounder ceo (talk) 18:18, 22 May 2025 (UTC)
Making -/ and \- turn the text it's enclosing into Title case
I want to make -/ and \- give the text they are enclosing the Title casing. But how? Even after adding it to LanguageConverter.php, Parser.php, Preprocessor.php and PPFrame_Hash.php, still, it took no effect.
What other files do I have to edit to add this functionality? Kxeon (talk) 16:06, 27 May 2025 (UTC)
- If you're editing files at random without understanding how they work, its not surprising it doesn't work. I doubt anyone can answer this question without knowing what you did and if you did it correctly. Bawolff (talk) 19:41, 27 May 2025 (UTC)
- Didn't expect a response just 3 hours after my query. Oops.
- Also, since in this case I should post the code I added here, I will.
- For LanguageConverter, I did this:
switch ( $token ) {
case '-{':
// Check max depth
if ( $depth >= $this->mMaxDepth ) {
$inner .= '-{';
if ( !$warningDone ) {
$inner .= '<span class="error">' .
wfMessage( 'language-converter-depth-warning' )
->numParams( $this->mMaxDepth )->inContentLanguage()->text() .
'</span>';
$warningDone = true;
}
$startPos += 2;
break;
}
// Recursively parse another rule
$inner .= $this->recursiveConvertRule( $text, $variant, $startPos, $depth + 1 );
break;
case '}-':
// Apply the rule
$startPos += 2;
$rule = new ConverterRule( $inner, $this );
$rule->parse( $variant );
$this->applyManualConv( $rule );
return $rule->getDisplay();
case '-/':
// Check max depth
if ( $depth >= $this->mMaxDepth ) {
$inner .= '-/';
if ( !$warningDone ) {
$inner .= '<span class="error">' .
wfMessage( 'language-converter-depth-warning' )
->numParams( $this->mMaxDepth )->inContentLanguage()->text() .
'</span>';
$warningDone = true;
}
$startPos += 2;
break;
}
// Recursively parse another rule
$inner .= $this->recursiveConvertRule( $text, $variant, $startPos, $depth + 1 );
break;
case '\-':
// Apply the rule
$startPos += 2;
$rule = new ConverterRule( $inner, $this );
$rule->parse( $variant );
$this->applyManualConv( $rule );
return $rule->getDisplay();
default:
throw new UnexpectedValueException( __METHOD__ . ': invalid regex match' );
}
}
- For Parser, I added:
public function ucWordsLangConv( $text ) {
$marker = self::MARKER_PREFIX . "-item-/$this->mMarkerIndex\-" . self::MARKER_SUFFIX;
$this->mMarkerIndex++;
$this->ucwords( $marker, $text );
return $marker;
}
- For Preprocessor, this:
'-/' => [
'end' => '\-',
'names' => [ 2 => null ],
'min' => 2,
'max' => 2,
],
- and for PPFrame_Hash, this:
# Not in RECOVER_COMMENTS mode (extractSections) though.
$out .= $this->parser->insertStripItem( $contextChildren[0] );
$out .= $this->parser->ucWordsLangConv( $contextChildren[0] );
- Now then. You might be able to see what I used here over and over again. There's probably something horribly wrong here. Maybe I forgot to add a function?
- I tried to search for any instances of -{ and }- and the function that it is in, insertStripItem. Kxeon (talk) 16:06, 28 May 2025 (UTC)
- @Kxeon: If you want to turn text into title case, I'd suggest a template called 'titlecase' containing something like
<span style="text-transform: capitalize;">{{{1}}}</span>. Adding new wikitext syntax is pretty complicated and usually best avoided. Sam Wilson 23:11, 28 May 2025 (UTC) - It doesn't look like you call ucWordsLangConv from anywhere, so i dont see how it could possibly work (i'd also agree with Sam's point). Bawolff (talk) 02:48, 30 May 2025 (UTC)
- @Kxeon: If you want to turn text into title case, I'd suggest a template called 'titlecase' containing something like
how to run a SQL query to search through all text on my site to find a 'string'
as a follow-up to: Project:Support desk/Flow/2013/10#h-how_to_run_a_query_to_search_through_all_text_on_my_site_to_find_a_'string'-2013-10-27T07:10:00.000Z
SELECT page.page_namespace, page.page_title
FROM page
JOIN revision ON revision.rev_page = page.page_id AND revision.rev_id=page.page_latest
JOIN slots ON slots.slot_revision_id = revision.rev_id
JOIN slot_roles ON slot_roles.role_id = slots.slot_role_id
JOIN content ON content.content_id = slots.slot_content_id
JOIN text ON text.old_id = CAST(SUBSTRING_INDEX(content.content_address, ':', -1) AS UNSIGNED)
WHERE slot_roles.role_name = 'main'
AND LOWER(text.old_text) LIKE '{{MultiClass Object\n%';
Note that CAST statement in the last JOIN ON. Turns out that content.content_address prefixes all of its values with "tt:" such that the JOIN text ON text.old_id=content.content_address won't work unless you strip out the "tt:" first. Revansx (talk) 21:21, 30 May 2025 (UTC)
- @Revansx just FYI, and to subscribe you to this thread, I've moved this here from the subpage which should've been a redirect! Cheers. Quiddity (WMF) (talk) 22:13, 30 May 2025 (UTC)
url + search return=upper→lower-case. how?
xx messenger begins lower case - I fixed the article title with {{ lowercase title }} the url and search returns (I used Qwant) are though capitalized - page move is causing the url to mismatch the title. Onemillionthtree 06:16, 30 May 2025 (UTC) 06:18, 30 May 2025 (UTC) 06:21, 30 May 2025 (UTC) Onemillionthtree (talk) 05:26, 30 May 2025 (UTC)
- Yes, this is expected, those cannot be 'fixed' and they cannot adhere to the 'lowercase title' instruction. —TheDJ (Not WMF) (talk • contribs) 08:46, 30 May 2025 (UTC)
- I think that is ridiculous as this means the mistake cannot be solved - but we as humans created this situation - an encyclopedia-coding- as a solution not a problem - someone made the situation with no possible solution? I think there must be a solution - what is the coding rule that stops pages being moved into non capital letter articles? to then recode that rule to allow non-capital - that would be a way to solve the problem! Where is the location of the code? The isn't any reason that the code-rule "always capital letters" should exist - obviously because it is enforcing an error. Onemillionthtree (talk) 15:57, 30 May 2025 (UTC)
- It's not like I'm asking for immediate immortality or some other extremely difficult/impossible thing to occur - we as humans can't shouldn't settle for - life with an error as a situation which is normal - this isn't a good. It is defined as a bad - as bad - stupid, wrong, a mistake - no intelligent human accepts this situation. Onemillionthtree (talk) 16:00, 30 May 2025 (UTC)
- Manual:$wgCapitalLinks "Set this to false to avoid forcing the first letter of page titles (including included pages, images, and categories) to capitals." - but is set as "true". ldid=329483 12:19, 13 June 2010 was "false" Reverted by Encoderoperations (talk) to last revision by Diego Grez 13 June 2010 = "true". "false" 00:35, 17 January 2016 - "true": "7 January 2016 by Haokan.h1o2r3v4a5t (talk | contribs) (corrected a mistake)" Onemillionthtree (talk) 13:27, 31 May 2025 (UTC)
- All else times were "true" - why not "false" ? Onemillionthtree (talk) 13:31, 31 May 2025 (UTC) @Quiddity:
Problem with Short URL-s after uprgade to Mediawiki 1.43.1
I've run into issue after upgrading my wiki from 1.42.x to 1.43.1. All pages wive error page 404. Looking through all the guidelines and documentation, it seems, that the problem is with Short URL-s.
Details
- Upgrade was done via cPanel (as was original install of the software).
- No error messages during upgrading.
- Upgrade log is all clean - says no errors.
- Wiki is in subdomain of the main doman. (I'm not inclined to share the side address as is it a private hobby project, but is someone is willing to look into it personally, then I can create temporary credentials if needed.)
- Page is configures so, that content can be seen only by users who have logged in.
- Folder /w or /wiki is not in use.
What I've tried so far
- Editing .htaccess
- Editing LocalSettings.php Current settings are:
$wgScriptPath = "";$wgArticlePath = "/$1";$wgScriptExtension = ".php";$wgUsePathInfo = true; - Cache is not enabled
Server information
- PHP: 8.4.6 (litespeed)
- ICU: 71.1
- MariaDB: 10.6.21-MariaDB-cll-lve-log
Used extensions
- Citizen (2.39.3)
- MinervaNeue
- MonoBook
- Timeless (0.9.1)
- Vektor (1.0.0)
- NumberHeadings
- VisualEditor
- Cite
- VisualData
- FontAwesome
Zängov (talk) 15:00, 24 May 2025 (UTC)
- This concerns your webserver configuration. which has to parse the urls correctly and then give the right information to MediaWiki. So that's what you should look into. —TheDJ (Not WMF) (talk • contribs) 08:04, 27 May 2025 (UTC)
- There was no changes on server side as much as I'm aware.
- Only me pressing the update button in cPanel. Zängov (talk) 15:20, 30 May 2025 (UTC)
- I checked the backup and looked up the old version of the MediaWiki was 1.42.6 and it was updated to 1.43.1
- @TheDJ Based on the troubleshooting so far I 100% agree, that it has to be something on the server side, but I can't figure out anything else than .htaccess or LocalSettings.php settings and these two were not changed (at least by me). Could it be that upgrade rewrote file .htaccess? Zängov (talk) 15:36, 30 May 2025 (UTC)
- You should include your .htaccess and any other config related to rewriting urls. Bawolff (talk) 19:43, 27 May 2025 (UTC)
- @Bawolff
- LocalSettings.php you can already see in my original post.
- Content of .htacess is as follows:
- <IfModule mod_rewrite.c>
- RewriteCond %{REQUEST_URI} !^/w/rest\.php
- RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-f
- RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-d
- RewriteRule ^(.*)$ %{DOCUMENT_ROOT}/w/index.php [L]
- </IfModule> Zängov (talk) 15:21, 30 May 2025 (UTC)
- Your .htaccess doesnt match your LocalSettings.php, so one of them has to be wrong. If /w is not in use then your .htaccess should not use it. Bawolff (talk) 16:52, 30 May 2025 (UTC)
- Awesome. Thank you @Bawolff Got a step closer (to something) 404-errors are gone.
- Result is now bunch of error messages (PHP 8.4):
Deprecated: Wikimedia\ScopedCallback::consume(): Implicitly marking parameter $sc as nullable is deprecated, the explicit nullable type must be used instead in /home/*****/vendor/wikimedia/scoped-callback/src/ScopedCallback.php on line 57Deprecated: Wikimedia\ScopedCallback::cancel(): Implicitly marking parameter $sc as nullable is deprecated, the explicit nullable type must be used instead in /home/*****/vendor/wikimedia/scoped-callback/src/ScopedCallback.php on line 66Deprecated: Wikimedia\RemexHtml\DOM\DOMBuilder@anonymous(): Implicitly marking parameter $doctypeName as nullable is deprecated, the explicit nullable type must be used instead in /home/*****/vendor/wikimedia/parsoid/src/Utils/DOMUtils.php on line 50Deprecated: Wikimedia\RemexHtml\DOM\DOMBuilder@anonymous(): Implicitly marking parameter $public as nullable is deprecated, the explicit nullable type must be used instead in /home/*****/vendor/wikimedia/parsoid/src/Utils/DOMUtils.php on line 50Deprecated: Wikimedia\RemexHtml\DOM\DOMBuilder@anonymous(): Implicitly marking parameter $system as nullable is deprecated, the explicit nullable type must be used instead in /home/*****/vendor/wikimedia/parsoid/src/Utils/DOMUtils.php on line 50Deprecated: Wikimedia\RemexHtml\DOM\DOMBuilder::createDocument(): Implicitly marking parameter $doctypeName as nullable is deprecated, the explicit nullable type must be used instead in /home/*****/vendor/wikimedia/remex-html/src/DOM/DOMBuilder.php on line 154Deprecated: Wikimedia\RemexHtml\DOM\DOMBuilder::createDocument(): Implicitly marking parameter $public as nullable is deprecated, the explicit nullable type must be used instead in /home/*****/vendor/wikimedia/remex-html/src/DOM/DOMBuilder.php on line 154Deprecated: Wikimedia\RemexHtml\DOM\DOMBuilder::createDocument(): Implicitly marking parameter $system as nullable is deprecated, the explicit nullable type must be used instead in /home/*****/vendor/wikimedia/remex-html/src/DOM/DOMBuilder.php on line 154Deprecated: Wikimedia\RemexHtml\DOM\DOMBuilder@anonymous(): Implicitly marking parameter $doctypeName as nullable is deprecated, the explicit nullable type must be used instead in /home/*****/vendor/wikimedia/parsoid/src/Utils/DOMCompat.php on line 382Deprecated: Wikimedia\RemexHtml\DOM\DOMBuilder@anonymous(): Implicitly marking parameter $public as nullable is deprecated, the explicit nullable type must be used instead in /home/*****/vendor/wikimedia/parsoid/src/Utils/DOMCompat.php on line 382Deprecated: Wikimedia\RemexHtml\DOM\DOMBuilder@anonymous(): Implicitly marking parameter $system as nullable is deprecated, the explicit nullable type must be used instead in /home/*****/vendor/wikimedia/parsoid/src/Utils/DOMCompat.php on line 382Fatal error: Declaration of MediaWiki\Json\JsonDeserializableCodec::jsonClassHintFor(string $className, string $keyName) must be compatible with Wikimedia\JsonCodec\JsonClassCodec::jsonClassHintFor(string $className, string $keyName): ?string in /home/*****/includes/json/JsonDeserializableCodec.php on line 56- With some PHP-versions I even manage to get to loginpage. Interestingly the error messages are not whown with PHP versions 8.1 and 8.3. Got to login-page. After logging in I got error:
Fatal error: Declaration of MediaWiki\Json\JsonDeserializableCodec::jsonClassHintFor(string $className, string $keyName) must be compatible with Wikimedia\JsonCodec\JsonClassCodec::jsonClassHintFor(string $className, string $keyName): ?string in /home/*****/includes/json/JsonDeserializableCodec.php on line 56- My conclusion here is, that is could be something to do with plugin, that shows the content. Content of Wiki is viewable only after logging in. Special-pages work, but just show that error in top of pages. Am I on the right track here? Zängov (talk) 19:28, 31 May 2025 (UTC)
- Aparently not in the right track.
- Errors are shown regardless if user is logged in or not.
- Every other part of the site is displayed, but content of the page.
- I can even open the search and it finds the content and shows the preview, but article is not shown.
- I didn't have many extensions installed in the first place. I did some cleanup - no change.
- Currently only these extensions are listed in LocalConfig. So basically only 3 are in use.
- wfLoadExtension( 'VisualEditor' );
- wfLoadExtension( 'TemplateData' );
- wfLoadExtension( 'Cite' );
- # wfLoadExtension( 'VisualData' ); Zängov (talk) 22:08, 31 May 2025 (UTC)
- the deprectation warnings are just warnings and can be ignored (typically that means your version of php is too new for your version of mediawiki). For the fatal error - make sure you installed mediawiki in a fresh location. If you extract the zip/tar file over top of an existing install you can get a mix of two versions which is bad. Make sure that all extensions are updated. If you installed via git, ensure composer dependencies are up to date. Bawolff (talk) 05:39, 1 June 2025 (UTC)
- Thanks @Bawolff,
- OK. Ignoring warnings.
- All 3rd party extensions are up to date. I assume I don't have to check it with extensions supplied with MediaWiki?
- It was not a fresh installation or fresh location. It was an UPGRADE.
- Both installation and upgrade was done via cPanel/Installatron
- Currently I'm stuck with error:
Fatal error: Declaration of MediaWiki\Json\JsonDeserializableCodec::jsonClassHintFor(string $className, string $keyName) must be compatible with Wikimedia\JsonCodec\JsonClassCodec::jsonClassHintFor(string $className, string $keyName): ?string in /home/********/includes/json/JsonDeserializableCodec.php on line 56Zängov (talk) 13:49, 1 June 2025 (UTC)
- the deprectation warnings are just warnings and can be ignored (typically that means your version of php is too new for your version of mediawiki). For the fatal error - make sure you installed mediawiki in a fresh location. If you extract the zip/tar file over top of an existing install you can get a mix of two versions which is bad. Make sure that all extensions are updated. If you installed via git, ensure composer dependencies are up to date. Bawolff (talk) 05:39, 1 June 2025 (UTC)
- Aparently not in the right track.
- Your .htaccess doesnt match your LocalSettings.php, so one of them has to be wrong. If /w is not in use then your .htaccess should not use it. Bawolff (talk) 16:52, 30 May 2025 (UTC)
Upgrading stuck at MigrateRevisionActorTemp
Hello, I'm trying to upgrade to MediaWiki 1.43.1 from an older installation, 1.34.0. I've run the built-in web script at /mw-config, but it is getting stuck trying to upgrade the database.
...user_editcount in table user already modified by patch patch-user-user_editcount.sql. Running MigrateRevisionActorTemp... Run update.php to create rev_actor. An error occurred: Execution of MigrateRevisionActorTemp did not complete successfully.
Running applicable php scripts at the command line results in no output:
[user@server mediawiki-1.43.1]# php maintenance/update.php [user@server mediawiki-1.43.1]# php maintenance/migrateRevisionActorTemp.php [user@server mediawiki-1.43.1]#
I've searched but not found any other instances of this happening to someone else. Thanks for any help! Nodoho (talk) 14:41, 31 May 2025 (UTC)
Update: Turns out PHP errors were being suppressed, here is why the update.php script exited silently. Will work on tracking down the solution to this issue. Nodoho (talk) 14:45, 31 May 2025 (UTC)
[31-May-2025 10:43:26 America/New_York] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib64/php/modules/mcrypt.so' - /usr/lib64/php/modules/mcrypt.so: cannot open shared object file: No such file or directory in Unknown on line 0
[31-May-2025 10:43:26 America/New_York] PHP Parse error: syntax error, unexpected 'class' (T_CLASS), expecting identifier (T_STRING) or variable (T_VARIABLE) or '{' or '$' in /site/mediawiki-1.43.1/maintenance/update.php on line 132
Got mcrypt working, but still running into trouble with the second error above. Here is the line with the error:
$composerLockUpToDate = $this->runChild( CheckComposerLockUpToDate::class );
and the context in update.php:
// Check external dependencies are up to date
if ( !$this->hasOption( 'skip-external-dependencies' ) && !getenv( 'MW_SKIP_EXTERNAL_DEPENDENCIES' ) ) {
$composerLockUpToDate = $this->runChild( CheckComposerLockUpToDate::class );
$composerLockUpToDate->execute();
} else {
Looks like command-line php is stuck, for some reason, at version 5.4.16, and suspecting that is the cause of the error. Been stuck in dependency difficulties while trying to compile PHP 8.4, currently cannot get the ./configure script to see the latest recently installed libxml2. Taking a break. Hoping this will eventually fix the above problem at any rate, and leaving everything above in case someone else encounters this issue. Nodoho (talk) 15:35, 31 May 2025 (UTC)
- Returning to say that I successfully upgraded to MediaWiki 1.43.1. Did 1.35.5, then 1.39.12, then finally 1.43.1, with a mix of running maintenance/update.php and mw-config web script, troubleshooting lots of errors along the way—including getting php8 up and running. Hope this helps someone else in the future. Nodoho (talk) 12:10, 1 June 2025 (UTC)
Project in root directory help
I have my mw install in the root directory and followed the advice found in these pages 1, 2, 3 and some advice found in discussions there meaning I have the following:
$wgScriptPath = ""; $wgArticlePath = "/$1";
and in my Apache .conf
ServerName name.wiki
ServerAlias www.name.wiki
DocumentRoot /var/www/wikiname
... SSL stuff
RewriteEngine On
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-f
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-d
RewriteRule ^(.*)$ %{DOCUMENT_ROOT}/index.php [L]
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-f
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-d
RewriteRule ^/?images/thumb/[0-9a-f]/[0-9a-f][0-9a-f]/([^/]+)/([0-9]+)px-.*$ %{DOCUMENT_ROOT}/thumb.php?f=$1&width=$2 [L,QSA,B]
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-f
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-d
RewriteRule ^/?images/thumb/archive/[0-9a-f]/[0-9a-f][0-9a-f]/([^/]+)/([0-9]+)px-.*$ %{DOCUMENT_ROOT}/thumb.php?f=$1&width=$2&archived=1 [L,QSA,B]
<Directory /var/www/wikiname/images>
Options -Indexes
AllowOverride None
AddType text/plain .html .htm .shtml .phtml
AddType image/webp .webp
<Files "*.php">
SetHandler !
</Files>
Header set X-Content-Type-Options nosniff
</Directory>
LocalSettings.php is safe and permissions seem fine, however, I'm able to access random files through the URL in the directory like .txt files and other files like that in directories. How do I go about only having necessary files be web-accessible?
EDIT: This bit of documentation seems like the right direction. Do I have this right?
ServerName name.wiki ServerAlias www.name.wiki DocumentRoot /dev/null ... SSL stuff Alias /index.php /var/www/wikiname/index.php Alias /api.php /var/www/wikiname/api.php Alias /load.php /var/www/wikiname/load.php Alias /thumb.php /var/www/wikiname/thumb.php Alias /img_auth.php /var/www/wikiname/img_auth.php Alias /opensearch_desc.php /var/www/wikiname/opensearch_desc.php Alias /images /var/www/wikiname/images Alias /robots.txt /var/www/wikiname/robots.txt <Directory /var/www/wikiname> Require all granted Options -Indexes AllowOverride None ... Move rewrites here </Directory> <Directory /var/www/wikiname/images> .. Same as before </Directory>
Porcupinez (talk) 13:08, 23 May 2025 (UTC)
- @Porcupinez: By .txt files and other files like that in directories, do you mean in the
images/directory, or just the general MediaWiki application files? If the latter, there's no problem with them being accessible. I think ideally you should be able to restrict it to serve only index.php, api.php, rest.php, thumb.php, thumb_handler.php, img_auth.php, and load.php (i.e. get rid of the-dand-fchecks you've got above) but some extensions still want to serve images etc directly from their directories. Sam Wilson 01:10, 25 May 2025 (UTC)- Thanks for the reply! I meant general MediaWiki application files. I edited a bit onto my initial post. Would getting rid of the !-f and !-d flags be enough instead of all that? I would still want to selectively expose files like robots.txt and not break anything with extensions like you mentioned. Porcupinez (talk) 01:19, 25 May 2025 (UTC)
- @Porcupinez: I wouldn't bother trying to hide application files. It's all open source anyway! But yeah, with some judicious use of rewrite rules you can hide everything but still have just a few things available. Sam Wilson 09:13, 26 May 2025 (UTC)
- @Samwilson Ahh, well, at least it isn't much to worry about. There is a potential issue of LocalSettings.php.save files generated by an IDE, or files potentially blocking the main namespace. I would prefer to, but thankful to confirm it isn't inherently dangerous. Porcupinez (talk) 07:00, 27 May 2025 (UTC)
- @Porcupinez: Are you editing with an IDE on prod?! :-P I guess you could add some LocalSettings-specific deny rule, just to be sure. Sam Wilson 07:18, 27 May 2025 (UTC)
- @Samwilson I test with a local environment and eventually apply changes with nano? If there's a better alternative please let me know lol Porcupinez (talk) 12:48, 27 May 2025 (UTC)
- @Porcupinez: That sounds fine. You might want to add your config files to a Git repo at some point, for easier tracking, but I was more worried that you meant you were e.g. editing in an IDE over SFTP and that somehow temp files were being created on the server. Which might be annoying (although what IDE would do that, I dunno). Sam Wilson 23:23, 28 May 2025 (UTC)
- @Samwilson I test with a local environment and eventually apply changes with nano? If there's a better alternative please let me know lol Porcupinez (talk) 12:48, 27 May 2025 (UTC)
- @Porcupinez: Are you editing with an IDE on prod?! :-P I guess you could add some LocalSettings-specific deny rule, just to be sure. Sam Wilson 07:18, 27 May 2025 (UTC)
- @Samwilson Ahh, well, at least it isn't much to worry about. There is a potential issue of LocalSettings.php.save files generated by an IDE, or files potentially blocking the main namespace. I would prefer to, but thankful to confirm it isn't inherently dangerous. Porcupinez (talk) 07:00, 27 May 2025 (UTC)
- @Porcupinez: I wouldn't bother trying to hide application files. It's all open source anyway! But yeah, with some judicious use of rewrite rules you can hide everything but still have just a few things available. Sam Wilson 09:13, 26 May 2025 (UTC)
- Thanks for the reply! I meant general MediaWiki application files. I edited a bit onto my initial post. Would getting rid of the !-f and !-d flags be enough instead of all that? I would still want to selectively expose files like robots.txt and not break anything with extensions like you mentioned. Porcupinez (talk) 01:19, 25 May 2025 (UTC)
- I wouldn't super worry about this,but yes, the alias setup is one way to prevent this sort of thing. There are quite a few others too, such as apaches access control or rewrite rules. See the apache docs for details. Bawolff (talk) 05:49, 1 June 2025 (UTC)
- Good to know, thank you! I think I'll run with aliases, and maybe expose the extensions folder to not cause issues there. Seems better to explicitly decide what is exposed. Porcupinez (talk) 00:56, 3 June 2025 (UTC)
User email authentication not working: something removes email address and token from user table
Hello,
I hope someone can help me. My mediawiki installation (1.39.10) started to behave strange a couple of days ago. Before that it worked as it should. Strangely enough, I don't recall making any updates to mediawiki or the extensions at that time.
What happens: when a new user registers or an existing user changes the email address ( $wgEmailAuthentication=true ), the authentication email is sent and received ok, but when clicking on the authentication link, it is for most of the times (not always!) expired.
I queried the user table in mysql, and when I create a new user, I can see the "user_email" as well as the "email_token" and "email_token_expires" columns get appropriate values. But when I redo the query after a couple of seconds, all the email related values are "NULL". So for some reason something is removing them right after they are saved in the table.
I receive no error messages ( error_reporting( -1 ); ini_set( 'display_errors', 1 ); ) and can't find anything relevant in any logs. Does anyone have a clue on what is going on, or on how I could try to debug this?
Lindholmm (talk) 14:18, 30 May 2025 (UTC)
- check if it still happens after removing all extensions. Check also if setting $wgMainCacheType = CACHE_NONE; has any effect (you dont want that setting in general it will make your wiki super slow, but it might help narrow down causes). Bawolff (talk) 05:41, 1 June 2025 (UTC)
- After checking all these and server and database and php timezones etc. without any luck, I think I have come up with the cause: something is "clicking" the cancellation link in the authentication email right after it has been sent. Someone (probably my company's IT department) may have installed a new spam filter to the mail server that scans links in outgoing mails?
- Anyway, if I remove the cancellation link from Mediawiki:Confirmemail body the email address won't disappear from the user table, but it will instead get automatically authenticated. So I'm pretty sure something is automatically clicking through the links in the emails.
- I probably can ask my IT department to exclude my authentication emails from the filter. But it would be better to change the authentication and cancellation page Special:ConfirmEmail to have a button that needs to be clicked before the authentication/cancellation actually takes place.
- Do I have to code this myself or is there a setting or an extension that does this?
- Lindholmm (talk) 06:33, 1 June 2025 (UTC)
- This is now confirmed. The new virus/spam filter attached to my company's SMTP server checked the links in outgoing emails, first causing the confirmation of the account (first link in the email) and immediately after, the invalidation of the account (second link in the email). When we excluded the links with Special:ConfirmEmail and Special:InvalidateEmail from being checked by the virus/spam filter, everything returned to normal.
- I have no idea how common it is to have a virus/spam filter that checks links this way, but apparently, it can happen. I think it would be safer to change the behavior of Special:ConfirmEmail and Special:InvalidateEmail so that there is a button that must be pressed (by a human) before the actual confirmation or invalidation takes place.
- Lindholmm (talk) 13:06, 2 June 2025 (UTC)
Installing Hridoy
Hi, I am Installing Hridoy currently want change font on a Wikimedia wiki to via js and css files, however sometimes it stills have default fonts. Could it possible to change to that font everywhere (e.g. like heading, titles, special pages, etc.). INSTALLING HRIDOY (talk) 09:26, 2 June 2025 (UTC)
navigation pane moves with EDGE
I have to use the edge browser. When I do the left side navigation panes go to bottom of page and not next to main body.
170.85.70.254 18:51, 3 June 2025 (UTC)
Use external font for a Wikimedia wiki
Hi, I am currently want change font on a Wikimedia wiki to Cascadia Mono via js and css files, however sometimes it stills have default fonts. Could it possible to change to that font everywhere (e.g. like heading, titles, special pages, etc.).
Here link to my js and css files:
CSS: m:User:DinhHuy2010/global.css JS: m:User:DinhHuy2010/global.js
Thanks. DinhHuy2010 (talk) 13:13, 2 June 2025 (UTC)
- Try adding a !important to the css decleration. Bawolff (talk) 02:44, 4 June 2025 (UTC)
- @Bawolff Thanks, it works! DinhHuy2010 (talk) 12:29, 5 June 2025 (UTC)
mw.user.isTemp is not a function
Hello everybody!
We upgraded our Mediawiki 1.32.2 to 1.43.0 (we first upgraded to 1.39, and then, to 1.43).
We have the "LDAPAuthentication2", "LDAPProvider" and "PluggableAuth" extensions configured to login via LDAP, and the rest of the official extensions of Mediawiki.
We can't logout on special pages or on the home page, for example. It does not affect the applied skin.
We have enabled the following PHP configuration ($wgShowExceptionDetails = true;error_reporting( -1 );ini_set( 'display_errors', 1 );) but it does not show any error messages.
This is the message we see when we click on "logout": "The session is being closed. Please wait a few seconds".
And we get in the devtools the following message:
ready.js:195:15 Uncaught TypeError: mw.user.isTemp is not a function logoutViaPost ready.js:195 fire mediawiki.base.js:566 js ready.js:219 > jQuery 8 js ready.js:218 > jQuery 13 runScript load.php:12 execute load.php:14 doPropagation load.php:6 (Asíncrono: requestIdleCallback handler) setAndPropagate load.php:7 impl load.php:20 <anonymous> jQuery
We did not find any information on this.
Thanks! Diegxalv (talk) 11:49, 29 May 2025 (UTC)
- @Diegxalv Something is out of sync. Newer versions of MediaWiki provide that core javascript function, and clearly some of your other core javascript files know about it. My suspicion is that you installed the newer version on top of the older version, and some old files were not removed, or the copy of the new files was not completed. I would double check your upgrade process. —TheDJ (Not WMF) (talk • contribs) 08:51, 30 May 2025 (UTC)
htmlspecialchars() in HtmlArmor.php file
Hi,
We upgraded our Mediawiki to 1.43.1.
Everything is working but when we enabled the following PHP configuration ($wgShowExceptionDetails = true;error_reporting( -1 );ini_set( 'display_errors', 1 );) , it shows us the following message:
Deprecated: htmlspecialchars(): Passing null to parameter #1 ($string) of type string is deprecated in /var/www/html/wiki/includes/libs/HtmlArmor.php on line 59
Our PHP version is 8.1.32 (MediaWiki 1.43 requires PHP 8.1.0 or later).
We did not find any information on this.
Thanks! Diegxalv (talk) 14:21, 6 June 2025 (UTC)
- Its probably safe to ignore. It might mean one of the extensions you are using have not been updated for php 8.1 Bawolff (talk) 03:51, 7 June 2025 (UTC)
- Hi, @Bawolff!
- This message is quite curious, we are using only the extensions that come bundled with MediaWiki (included with the upgrade package).
- I hope this message doesn't cause any problems.
- Thanks for your help! Diegxalv (talk) 20:43, 7 June 2025 (UTC)
- I was kind of making an assumption that it was an extension and not core as i thought all the cases in core & bundled extensions were fixed, but perhaps we missed one. In any case, its just a harmless warning and can be safely ignored. In production use, its safe to set error_reporting in php.ini to exclude deprecation warnings. (if you know how to get a backtrace, that could be helpful for fixing it, but no worries if that is difficult). Bawolff (talk) 21:06, 7 June 2025 (UTC)
Writing filters for data items using the Abusefilter extension
We have a wiki with Wikibase data items attached. Many of our data items have one label, which we conventionally store as the English label, but there is nothing stopping people from creating other labels. Item properties determine whether or not a data item is subject to this or can have multilingual labels. How could you go about writing a filter that reports adding such a label?
Our version is 1.43.1. 151.186.181.32 15:34, 6 June 2025 (UTC)
- I think I am looking for documentation on Wikibase-specific filter rules such as
wbsetlabeldescriptionaliases.151.186.181.32 11:23, 9 June 2025 (UTC)
About the themes removed in 1.22.
What is stopping me from copying "Standard" over from 1.21 and putting them in 1.39's theme folder? 2A00:23C6:41E6:AC01:3B40:E1AF:DED8:4C58 16:22, 8 June 2025 (UTC)
- Planned obsolescence, maybe: Skin:Standard was phased out from MW way back in 2013 (along with several others from Wikipedia's early days), and is no longer supported. Depending on your tastes/opinion, you might want to consider Nostalgia, which Wikimedia keeps around for WP's December 2001 snapshot. --Slgrandson (talk) 02:02, 9 June 2025 (UTC)
- Or you just fork the skin and fix it up yourself to work with all the new MediaWiki skin logic. —TheDJ (Not WMF) (talk • contribs) 08:10, 10 June 2025 (UTC)
problem of transcluded sections with references defined by name in a {{reflist |refs=
Hi all, In the following example page -> https://commons.wikimedia.org/wiki/Commons:De_minimis , sections of countries are transcluded but the ref définitions were in error for 2.FR 14.IRL 15.Japan and 19.Slovenia transclusions.
One solution I found was to move the ref definitions in the same section where used. This is acceptable in case of uniticy of the ref definition. Ex for Slovenia -> https://commons.wikimedia.org/w/index.php?title=Commons:Copyright_rules_by_territory/Slovenia&diff=prev&oldid=1042377831
But it is not satisfying in other transclusions when the same reference was used in several sections. This leads to copy again the same reference definition in each section where it is used , loosing by this way the benefit of a unique shared déclaration with " {{reflist |refs= ". How to solve that ? Thanks. --Christian 🇫🇷 FR 🚨 (talk) 11:34, 11 June 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)
- Keeping this up for a bit longer before I receive a reply here, or ask around elsewhere. --Slgrandson (talk) 16:45, 29 May 2025 (UTC)
- If this gains no movement, I'll try my luck at Skin talk:Vector/2022. --Slgrandson (talk) 22:19, 12 June 2025 (UTC)
Spanish decimal separator
I just noticed that the official mw.language library for Spanish 'es' shows the format officially used in Spain. In Spain they use commas as decimal separators, different Spanish-speaking countries use either commas (Spain, Argentina, etc.) or dots (Mexico, Guatemala, etc.). However, the consensus reached in Spanish Wikipedia is to use dots and accept the use of commas in articles written by authors from countries that use commas. WP:NÚMERO
I think that the module should be modified to show dots as decimal separators in accordance with Spanish Wikipedia's guidelines. This affects templates and infoboxes that use modules that get information from Wikidata. Can it be localized in real time depending on the IP? JaimeDes (talk) 04:42, 13 June 2025 (UTC)
Unable to access wiki.openoffice.org after creating a Mediawiki account
I was trying to create and save a book on wiki.openoffice.org and I got the impression, that I needed an "account" to do this. Having created a Mediawiki account via the "Login" link there, I am no longer able to access wiki.openoffice.org. (I get error 403: Forbidden You don't have permission to access this resource).
I am somewhat at a loss now, and I wonder, what I have invoked. I have tried reading the user help and FAQ links without finding any general information about access to *read* established wikis, permissions needed etc.
I would like some help on what do do or set up via the web to be able to access the wiki.openoffice.org.
Thank you. Kirthomaoo (talk) 11:02, 13 June 2025 (UTC)
- They are still using MW 1.35 which is long unsupported and their only wiki related help simply points to this site so it wouldn't be surprising that their registration procedure was lacking maintenance. You might try your luck in their forum.
- Edit: just noticed this. Tactica (talk) 17:05, 13 June 2025 (UTC)
- Thank you very much. That may indeed explain matters. :) Kirthomaoo (talk) 07:33, 14 June 2025 (UTC)
where are the site notice located and translated ?
Hi all. I want to translate in FR banner "Nominate your favorite tools..." currently appearing on MW pages. My question is where is it defined in EN ? and where do I provide the FR text ?
On page -> https://www.mediawiki.org/w/index.php?title=MediaWiki:Sitenotice&action=edit they say to go to translatewiki.net but the link they provide is independant of the message. So how do I search ? Thanks. --Christian 🇫🇷 FR 🚨 (talk) 14:15, 13 June 2025 (UTC)
- Since the banner doesn't include a translate link, it's quite likely that it is intended to remain untranslatable.
- Also, the "site notice" is not the banner. The "From Wikipedia..." message appended to every Wikipedia article is an example of a site notice thay may be edited and translated. Tactica (talk) 16:43, 13 June 2025 (UTC)
- so again, where do we find the the site notice declarations and the translations. More of that it would allow to write a request for translation and reach to a larger community. Can someone answer effectively to the topic ? Thanks. --Christian 🇫🇷 FR 🚨 (talk) 07:14, 14 June 2025 (UTC)
Random page raises: InvalidArgumentException: Wikimedia\Rdbms\Platform\SQLPlatform::makeList: unexpected nested array
I have the latest version: 1.43.1
See all the details at: Sürüm - Nurpedia.org - İman ve İslam Hakikatlerine Dair Nur Ansiklopedisi
I got the following error when I try to pick a random page from the main page: Dahili hata - Nurpedia.org - İman ve İslam Hakikatlerine Dair Nur Ansiklopedisi
[683598d1451c472d2cb20af2] /wiki/%C3%96zel:Rastgele InvalidArgumentException: Wikimedia\Rdbms\Platform\SQLPlatform::makeList: unexpected nested array
Backtrace:
from /home/yonlenco/nurpedia.org/includes/libs/rdbms/platform/SQLPlatform.php(281)
#0 /home/yonlenco/nurpedia.org/includes/libs/rdbms/platform/SQLPlatform.php(273): Wikimedia\Rdbms\Platform\SQLPlatform->makeList()
#1 /home/yonlenco/nurpedia.org/includes/libs/rdbms/platform/SQLPlatform.php(724): Wikimedia\Rdbms\Platform\SQLPlatform->makeList()
#2 /home/yonlenco/nurpedia.org/includes/libs/rdbms/database/Database.php(3305): Wikimedia\Rdbms\Platform\SQLPlatform->selectSQLText()
#3 /home/yonlenco/nurpedia.org/includes/libs/rdbms/database/DatabaseMySQL.php(644): Wikimedia\Rdbms\Database->selectSQLText()
#4 /home/yonlenco/nurpedia.org/includes/libs/rdbms/database/Database.php(1337): Wikimedia\Rdbms\DatabaseMySQL->selectSQLText()
#5 /home/yonlenco/nurpedia.org/includes/libs/rdbms/database/Database.php(1354): Wikimedia\Rdbms\Database->select()
#6 /home/yonlenco/nurpedia.org/includes/libs/rdbms/database/DBConnRef.php(127): Wikimedia\Rdbms\Database->selectRow()
#7 /home/yonlenco/nurpedia.org/includes/libs/rdbms/database/DBConnRef.php(369): Wikimedia\Rdbms\DBConnRef->__call()
#8 /home/yonlenco/nurpedia.org/includes/libs/rdbms/querybuilder/SelectQueryBuilder.php(792): Wikimedia\Rdbms\DBConnRef->selectRow()
#9 /home/yonlenco/nurpedia.org/includes/specials/SpecialRandomPage.php(222): Wikimedia\Rdbms\SelectQueryBuilder->fetchRow()
#10 /home/yonlenco/nurpedia.org/includes/specials/SpecialRandomPage.php(169): MediaWiki\Specials\SpecialRandomPage->selectRandomPageFromDB()
#11 /home/yonlenco/nurpedia.org/includes/specials/SpecialRandomPage.php(80): MediaWiki\Specials\SpecialRandomPage->getRandomTitle()
#12 /home/yonlenco/nurpedia.org/includes/specialpage/SpecialPage.php(728): MediaWiki\Specials\SpecialRandomPage->execute()
#13 /home/yonlenco/nurpedia.org/includes/specialpage/SpecialPageFactory.php(1724): MediaWiki\SpecialPage\SpecialPage->run()
#14 /home/yonlenco/nurpedia.org/includes/actions/ActionEntryPoint.php(504): MediaWiki\SpecialPage\SpecialPageFactory->executePath()
#15 /home/yonlenco/nurpedia.org/includes/actions/ActionEntryPoint.php(146): MediaWiki\Actions\ActionEntryPoint->performRequest()
#16 /home/yonlenco/nurpedia.org/includes/MediaWikiEntryPoint.php(200): MediaWiki\Actions\ActionEntryPoint->execute()
#17 /home/yonlenco/nurpedia.org/index.php(58): MediaWiki\MediaWikiEntryPoint->run()
#18 {main}
Your kind help is really appreciated. Thanks. Alyabby (talk) 11:45, 9 June 2025 (UTC)
- The problem is around here in the (SQLPlatform.php file) source code:
- public function makeList( array $a, $mode = self::LIST_COMMA ) {
- $first = true;
- $list = '';
- $keyWarning = null;
- foreach ( $a as $field => $value ) {
- .... (several statements here)
- } elseif ( is_array( $value ) ) {
- throw new InvalidArgumentException( __METHOD__ . ": unexpected nested array" );
- what might have caused to this $value to be an array? Alyabby (talk) 16:47, 13 June 2025 (UTC)
- I further tried to debug and I see that
$modeis 0, and$valueis: Array ([0] => 3000[1] => 3002)- here in the context. Alyabby (talk) 16:22, 14 June 2025 (UTC)
- I commented out this and it works quite good:
} /* elseif ( is_array( $value ) ) {throw new InvalidArgumentException( __METHOD__ . ": unexpected nested array" );} */- I don't know yet if this has a side effect Alyabby (talk) 16:24, 14 June 2025 (UTC)
Current events in uzwikiquote
Hello. Please help me write a link to the 'Current Events' page in Uzbek Wikiquote to the home page. Umarxon III (talk) 07:11, 16 June 2025 (UTC).
- See meta:Tech for Wikimedia wikis. Over there, please link to your current approach and elaborate what exactly you want to achieve. Maybe https://meta.wikimedia.org/wiki/Small_wiki_toolkits/Starter_kit/Main_page_customization might be useful, maybe not. Malyacko (talk) 06:48, 18 June 2025 (UTC)
How can I automate creation of BotPasswords?
I’m managing a MediaWiki instance and need to automate the generation of BotPasswords (from Special:BotPasswords).
Is there a way to achieve this programmatically (e.g., through an API request or another automation method)? Or is manual interaction the only available option?
If anyone has successfully implemented this, I’d appreciate any insights or guidance.
Thanks in advance for your help! 165.51.187.71 13:04, 18 June 2025 (UTC)
- Solved, It could be achieved using Mediawiki maintenance script createBotPassword.php. 165.51.187.71 13:45, 18 June 2025 (UTC)
run vs run.php
We don't seem to have a standard way to refer to run.php: it's often php run.php, but sometimes run or php run (note that I'm leaving out ./maintenance/ for clarity). Even the manual page, which is called run.php, then refers to just run, and there are a bunch of other places that do the same.
I've assumed we tell people to use php run.php because it's guaranteed to work on all systems, and then we leave it to people to find out for themselves that they can use run (if they're on a system with /usr/bin/env). But how many systems don't support that? It's certainly neater to not have to type the 'php's.
Anyway, I guess we should standardise the documentation to use php run.php. Sam Wilson 03:56, 19 June 2025 (UTC)
- I suggested just that in the past and was told to use AWB since I don't have the required rights for a mass replace using ReplaceText (which isn't even installed here anyway), but never got around to it because it was too much hassle. Still today I presume there is plenty of documentation not even saying that running
php foo.phpdirectly is deprecated. Tactica (talk) 04:34, 19 June 2025 (UTC)- @Tactica: I guess I'll just update as I find things! But what do you think about run vs run.php? I sort of seems like it'd be nicer to recommend the former, but that's not a good idea is it? Sam Wilson 05:18, 19 June 2025 (UTC)
I get an error.
You can see the error at bmtbus.infinityfreeapp.com/bmtwiki/index.php?title=Template:Uw-vandalism3&veaction=edit. 23.162.200.138 06:09, 16 June 2025 (UTC)
- Please see Manual:How to debug how to provide a stacktrace. Malyacko (talk) 06:49, 18 June 2025 (UTC)
- The error is Exception caught: Could not open '/home/vol1_4/infinityfree.com/if0_39222541/tmp_elpkgk/mw-GlobalIdGenerator39222541-UUID-128'. 23.162.200.138 09:14, 20 June 2025 (UTC)
Visual editor breaking category tags on 1.43.1
Just updated to 1.43.1 and when editing with the VisualEditor, category tags like "Category: Example" appear as "index.php?title=Category:Example" on the final page. I can edit the page again using source and fix the category tags, but it will break again if someone uses visual again. Any solutions to this? PHP version is 8.3.20. Berimas (talk) 16:01, 16 June 2025 (UTC)
- I'm pretty sure that this indicates a misconfiguration... I've seen it before, I just don't remember what the cause of it is... —TheDJ (Not WMF) (talk • contribs) 14:27, 19 June 2025 (UTC)
open_basedir: restriction in effect...
I upgraded my MediaWiki from 1.39 to 1.43. After running .../mw-config/index.php the Wiki doesn't work correcty. As recommended I changed the name of the .htaccess-file in the /images directory. PHP is set to 8.1.32. But I always get a lot of error messages like this:
Warning: is_readable(): open_basedir restriction in effect. File(/gitinfo/info-extensions-HitCounters.json) is not within the allowed path(s): (/srv/www/vhosts/tstebler.ch/subdomains/pollen/httpdocs/:/tmp/) in /srv/www/vhosts/tstebler.ch/subdomains/pollen/httpdocs/MediaWiki/includes/utils/GitInfo.php on line 163
Warning: Cannot modify header information - headers already sent by (output started at /srv/www/vhosts/tstebler.ch/subdomains/pollen/httpdocs/MediaWiki/includes/utils/GitInfo.php:163) in /srv/www/vhosts/tstebler.ch/subdomains/pollen/httpdocs/MediaWiki/includes/Request/WebResponse.php on line 80
Warning: is_readable(): open_basedir restriction in effect. File(/gitinfo/info-extensions-Cite.json) is not within the allowed path(s): (/srv/www/vhosts/tstebler.ch/subdomains/pollen/httpdocs/:/tmp/) in /srv/www/vhosts/tstebler.ch/subdomains/pollen/httpdocs/MediaWiki/includes/utils/GitInfo.php on line 163
I really do not know what I have to do. I have no SSH access to my Web. In the meantime I returned to my old Wiki version.
Could somebody help me? Thanks in advance.
P.S. I just noticed, that I am not able, to unblock the database with the special page "Unlock Database" (see thread below). Are the error messages because of the blocked database?
Thomas
TS (talk) 12:28, 19 June 2025 (UTC)
- Your wgCacheDirectory seems to evaluate to empty string. The directory should be in the mediawiki directory and then ./cache by default and it is generally autodetected, but on platforms where temp directories are not well configured in the server's PHP, there can be an issue. I suspect that is the problem and you will either need to manually specify the cache directory in your LocalSettings.php or get the php config of the server corrected. —TheDJ (Not WMF) (talk • contribs) 14:35, 19 June 2025 (UTC)
Error: Class "ResourceLoaderSkinModule" not found
Having upgraded Ubuntu from 24.10 to 25.04 my mediawiki stopped to work. I have tried to upgrade to mediawiki 1.43.1 but it still does not work. I get the following result
MediaWiki internal error ... Error: Class "ResourceLoaderSkinModule" not found
I can however not find any reference to the not found class.
How can I solve this problem?
The wiki is internal and can not be reached from outside my LAN. Tommy pollak (talk) 15:47, 18 June 2025 (UTC)
- Someone had a similar problem in the past after upgrading to 1.42.3 because they didn't upgrade the extensions. Better double check that. Tactica (talk) 02:24, 19 June 2025 (UTC)
- First - both includes and extensions are there.
- Second - Question: Do you mean that the extensions must be processed? In that case how can I do that afterwords?
- Third - Backtrace: First line is
- from /var/www/html/mediawiki-1.43.1/includes/ResourceLoader/ResourceLoader.php(416) Tommy pollak (talk) 16:04, 21 June 2025 (UTC)
- I mean the extensions have to match the version of MediaWiki you're using. Upgrading MediaWiki but leaving an odd extension untouched is a common mistake and an easy one to commit especially when the extension isn't bundled with MediaWiki and therefore it won't be updated automatically if you download and install the official package from this site. This may not be a problem when upgrading from 1.43.0 to 1.43.1, but it will if you're upgrading from 1.39 for instance. This includes skins, too.
- From that single line backtrace I have no idea what's going on. Broadly speaking I wouldn't use a distro-based MediaWiki package because I've had bad experiences in the past myself, but YMMV. Tactica (talk) 17:34, 21 June 2025 (UTC)
Unlock database with Special:Unlockdb not possible anymore
For maintenance reason I blocked the database with Special:Lockdb. After finishing maintenance I activated the databse with Special:Unlockdb. After cklicking "Unblock" nothing happend. When I try to change something in my wiki, theres is always the message, that the database is still locked. How can I manually unlock the database? I have a webhosting without SSH access.
TS (talk) 13:29, 19 June 2025 (UTC)
- The page essentially adds/removes a file named 'ReadOnly' to your installation. If the unlock doesn't work, I suspect that this permissions doesn't have the correct user permissions for PHP to delete it. —TheDJ (Not WMF) (talk • contribs) 14:38, 19 June 2025 (UTC)
- Thank you for your answer. Where can I find this 'ReadOnly' file? I restored the complete MediaWiki from my backup of yesterday (no locked database) but I get always the message, that the database is locked.
- Thomas TS (talk) 14:53, 19 June 2025 (UTC)
- I found this message im my log-files:
- [SQLBagOStuff] DBError: Database is read-only: Wechsel auf die neue Version 1.43 <p>(von Stebler am 19. Juni 2025 um 08:22 Uhr)</p> TS (talk) 15:13, 19 June 2025 (UTC)
- @SteblerTh: For the read only file, see $wgReadOnlyFile. It may not be working from the special page because you might be using the database for caching. Sam Wilson 03:54, 22 June 2025 (UTC)
編集できないページが有るのですが?
編集したくても編集できない頁があるので、書き込みました
problem of syntaxhighlight vs code transclusion
Hi all, In order to transclude a given Lua source code I wrote something like
<syntaxhighlight lang="lua">{{Module:Sandbox/Wladek92/myluaXXXmodule}}</syntaxhighlight>
but I get :
{{Module:Sandbox/Wladek92/myluaXXXmodule}}
The Lua code is well transcluded when expressed without tag syntaxhighlight but it appears too poor. On the other side with tag syntaxhighlight only the command line of the transclusion is interpreted, but not its content. How to solve that ? Thanks. -- Christian 🇫🇷 FR 🚨 (talk) 17:03, 29 June 2025 (UTC)
- you can do something like: {{#tag:syntaxhighlight|{{safesubst:Module:Sandbox/Wladek92/luatest1}}|lang=lua}} —TheDJ (Not WMF) (talk • contribs) 08:24, 1 July 2025 (UTC)
- great ! thanks --Christian 🇫🇷 FR 🚨 (talk) 08:50, 1 July 2025 (UTC)
Best file backup command
When I backup my MediaWiki files I exclude the thumb folder as it's absolutely massive, and I think it would regenerate if I ever needed to restore from the backup. Am I making the right choice here?
sudo tar zcvf /var/www/example.com/backups/2025-06-30-mw.tar.gz --exclude="/var/www/example.com/html/media/thumb" /var/www/example.com/html
Jonathan3 (talk) 09:33, 30 June 2025 (UTC)
- @Jonathan3: I do the same, as well as the temp directory. I think it's mainly a concern for very large wikis, where regenerating will take a long time. Sam Wilson 09:58, 30 June 2025 (UTC)
- Excellent, thanks.
- My tar.gz backup is 1.2GB but the uncompressed thumb folder is 23GB!! I have a load of large PDF files, and thumbnails of each page take up space. I wonder whether there's a setting to reduce the quality of them...
- My temp directory now is only 95MB. Jonathan3 (talk) 10:09, 30 June 2025 (UTC)
- Looks like it would be Extension:PdfHandler's $wgPdfHandlerDpi and/or $wgPdfHandlerJpegQuality... Jonathan3 (talk) 10:15, 30 June 2025 (UTC)
No editing possible in version 1.43.1
Hello,
after installing version 1.43.1 on a new system in our intranet (no update, but use of existing DB-content), we aren't able to edit an existing page. It's not possible to click on "Edit" in the tab bar.
In the console of Chrome, we see these messages:
load.php:1 Failed to load resource: the server responded with a status of 500 (Internal Server Error)
index.php:1 Refused to execute script from 'our.wiki.de/wiki/load.php?lang=de&modules=startup&only=scripts&raw=1&skin=vector' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
We use the default skin "Vector" which is contained in the downloaded archive 1.43.1 .
| Software | Version |
|---|---|
| MediaWiki | 1.43.1 |
| PHP | 8.2.28 (apache2handler) |
| ICU | 72.1 |
| MariaDB | 10.11.11-MariaDB-0+deb12u1 |
| Pygments | 2.11.2 |
After using
$wgShowExceptionDetails = true;error_reporting( -1 );ini_set( 'display_errors', 1 );
in LocalSettings.php, we also see these messages in the rendered pages:
Deprecated: Use of wfGetDB was deprecated in MediaWiki 1.39. [Called from MediaWiki\Extension\Gadgets\MediaWikiGadgetsDefinitionRepo::MediaWiki\Extension\Gadgets\{closure} in /var/www/html/wiki/extensions/Gadgets/includes/MediaWikiGadgetsDefinitionRepo.php at line 112] in /var/www/html/wiki/includes/debug/MWDebug.php on line 385
Deprecated: Use of MediaWiki\Parser\Parser::$extCite was deprecated in MediaWiki 1.42. [Called from Cite\Hooks\CiteParserHooks::onParserAfterParse in /var/www/html/wiki/extensions/Cite/src/Hooks/CiteParserHooks.php at line 58] in /var/www/html/wiki/includes/debug/MWDebug.php on line 385
Kind regards UlrichKnaackLGLN (talk) 10:51, 30 June 2025 (UTC)
- Update: we've commented out these two extensions: ConfirmEdit and VisualEditor. Now, we can edit the pages, of course without comfort and the simple captcha UlrichKnaackLGLN (talk) 13:54, 30 June 2025 (UTC)
- It seems to me like you didn't update the extensions. —TheDJ (Not WMF) (talk • contribs) 08:03, 1 July 2025 (UTC)
- we are using the extensions from the tar file 1.43.1 UlrichKnaackLGLN (talk) 09:51, 1 July 2025 (UTC)
- Line 112 of that file in version 1.43 does not have wfGetDb… yours does. So I think you made a mistake during upgrading. —TheDJ (Not WMF) (talk • contribs) 10:19, 1 July 2025 (UTC)
- thanks for your responses. But we didn't perform an upgrade, we started on a blank machine. UlrichKnaackLGLN (talk) 12:53, 1 July 2025 (UTC)
- Line 112 of that file in version 1.43 does not have wfGetDb… yours does. So I think you made a mistake during upgrading. —TheDJ (Not WMF) (talk • contribs) 10:19, 1 July 2025 (UTC)
- we are using the extensions from the tar file 1.43.1 UlrichKnaackLGLN (talk) 09:51, 1 July 2025 (UTC)
Updating to 1.43.2 results in Error: your composer.lock file is not up to date
I have a wiki running 1.43.1 on Ubuntu 24.04 with PHP 8.3. I've never encountered problems updating to the next version using the downloaded tarball.
However when attempting to update to 1.43.2, I when running
php maintenance/run.php update
Results in:
MediaWiki 1.43.2 Updater
symfony/polyfill-php80: not installed, 1.31.0 required.
symfony/polyfill-php81: not installed, 1.31.0 required.
symfony/polyfill-php82: not installed, 1.31.0 required.
symfony/polyfill-php83: not installed, 1.31.0 required.
Error: your composer.lock file is not up to date. Run "composer update --no-dev" to install newer dependencies
The RELEASE-NOTES-1.43 · mediawiki indicate a couple of changes that might be the cause,
Setup: Update error message for composer dependencies check.
| * Updated symfony/polyfill-php80 from 1.29.0 to 1.31.0. |
| * Updated symfony/polyfill-php81 from 1.29.0 to 1.31.0. |
| * Updated symfony/polyfill-php82 from 1.29.0 to 1.31.0. |
| * Updated symfony/polyfill-php83 from 1.29.0 to 1.31.0. |
I am aware of another similar wiki to mine that encounter the same Error message when attempting to update from 1.43.1 to 1.43.2.
Is this a bug in the 1.43.2 update? Peculiar Investor (talk) 13:35, 1 July 2025 (UTC)
- Just noting that I saw the same issue this morning when trying to upgrade. I have not taken any steps to troubleshoot yet and just opted to revert for now.
- Upgrading from 1.43.1 - Debian 12 with latest updates. PHP 8.2.28. ~2025-108998 (talk) 14:47, 1 July 2025 (UTC)
- Looks like they just addressed this very issue in 1.43.3! Haven't tested myself, but sounds like that'll do it. ~2025-108998 (talk) 15:25, 1 July 2025 (UTC)
- I've just tested it and it does indeed resolve the issue that I was experiencing. I can now update from 1.43.1 to 1.43.3 without issue.
- Thanks team for the quick resolution. Peculiar Investor (talk) 16:50, 1 July 2025 (UTC)
- Looks like they just addressed this very issue in 1.43.3! Haven't tested myself, but sounds like that'll do it. ~2025-108998 (talk) 15:25, 1 July 2025 (UTC)
- Yes, see the issue tracker for the bug reports: https://phabricator.wikimedia.org/T398269 Malyacko (talk) 06:29, 2 July 2025 (UTC)
Monolog with Loki - but all I get is a blank screen...
Here's what I'm trying to get working: https://github.com/markusa380/nv-wiki/blob/monolog-loki/mediawiki/LocalSettings.php#L24
I have configured this library to be downloaded through composer.local.json. See the Dockerfile for the exact steps.
However, when I uncomment the configuration of $wgMWLoggerDefaultSpi, all I get is a blank screen, even when I set
error_reporting( -1 );
ini_set( 'display_errors', 1 );
$wgShowExceptionDetails = true;
What am I missing? Not a PHP developer, so it might be something obvious. MarkusA380 (talk) 21:15, 1 July 2025 (UTC)
- A blank screen generally means a very early php error. what errors are you seeing in the web server error log and the php error log ? —TheDJ (Not WMF) (talk • contribs) 13:42, 2 July 2025 (UTC)
- Okay, thanks for the hint. I found out I had to enable these:
- ini_set( 'display_errors', 1 );
- ini_set( 'display_startup_errors', 1 );
- ini_set( 'log_errors', 'On' );
- ini_set( 'error_log', '/dev/stderr' );
- This way, I got to see the PHP errors in the output, and it was a simple fix (args had to be an array in an array). MarkusA380 (talk) 19:48, 2 July 2025 (UTC)
- Here's the change: https://github.com/markusa380/nv-wiki/commit/3faa89d7f8928892f27e34c1acde8a853d7b7239 MarkusA380 (talk) 19:48, 2 July 2025 (UTC)
Integration Help: Embedding Fluxus Executor Tools into MediaWiki
Hello Support Team,
I'm currently working on a MediaWiki-powered documentation site focused on Roblox scripting, modding, and exploit tutorials. One of the key tools we use in the community is Fluxus Executor, which is a popular Lua script executor for Roblox.
I'd like to integrate or embed Fluxus Executor panels, Fluxus Windows, script showcases, or script loaders into MediaWiki pages (primarily for demonstration or UI simulation purposes, not execution within the browser). However, I’ve run into a few issues and would appreciate some help.
❓ What I’m Trying to Do:
- Embed an iframe-based preview of a script dashboard styled like Fluxus Executor.
- Use syntax highlighting or code blocks to display Lua script examples that work with Fluxus.
- Ensure mobile responsiveness for users accessing the wiki from phones or tablets.
⚠️ Issues Encountered:
- Iframe content not rendering — MediaWiki seems to strip or block iframe tags by default.
- Lua code blocks don't support highlighting by default (would prefer something like Pygments or GeSHi).
- When using custom JS/CSS for a mod-style theme, it sometimes conflicts with MediaWiki’s base styles.
🔧 What I’ve Tried So Far:
- Editing
LocalSettings.phpto allow iframe usage via$wgRawHtml = true;(not recommended for public wikis due to security). - Installing
SyntaxHighlight_GeSHiextension for better code rendering. - Customizing
MediaWiki:Common.cssto mimic the Fluxus theme/UI for code demos.
💡 Request for Support:
- Is there a safe method to embed a Fluxus-style script panel (or UI mockup) using external code or iframe alternatives?
- Any recommended extensions for scripting documentation (preferably Lua-focused)?
- How can I make the wiki more flexible for showing mod/exploit UI without compromising site security?
🧠 Context: Why Fluxus Executor?
For those unfamiliar, Fluxus Executor is widely used in the Roblox scripting scene. Many wiki visitors are developers or gamers looking for:
- Safe scripts
- Execution methods
- Fluxus installation help
- Script performance comparisons
Having a more interactive documentation format helps reduce confusion and enhances user experience.
Any help, suggestions, or documentation links would be greatly appreciated.
Thank you in advance!
– Angelina Angelina-jack (talk) 14:18, 2 July 2025 (UTC)
arwiki: Request to Replace Eastern Arabic Numerals with Western Arabic Numerals Across Wikimedia Projects
Hello, I would like to request a general update across Wikimedia projects to replace Eastern Arabic numerals (e.g., ١، ٢، ٣...) with Western Arabic numerals (e.g., 1, 2, 3...) for consistency and improved readability, especially for users who are more familiar with the globally recognized numeric system. This change would help unify formatting across content and enhance accessibility for a wider audience. Thank you for your attention and continued efforts. Best regards. Mohammed Qays (talk) 22:05, 2 July 2025 (UTC)
- For WMF, that would require a lot of support from the community and this would not be the place to establish that consensus. For 3rd party wikis, you can use Manual:$wgTranslateNumerals —TheDJ (Not WMF) (talk • contribs) 18:14, 3 July 2025 (UTC)
How to open inputbox in new tab?
My question about Extension:InputBox. I have this input box to create in new page:
I want to open the create page in a new Tab when click on the button, like target="_blank". How do I do this?
Nimon didarul (talk) 11:58, 3 July 2025 (UTC)
- @Nimon didarul It currently doesn't support that, so you would have to modify the code of the extension. —TheDJ (Not WMF) (talk • contribs) 18:10, 3 July 2025 (UTC)
hyphen
What is the purpose of the hyphen after the last edit date in the footer? ~2025-123627 (talk) 20:31, 3 July 2025 (UTC)
- it's gone now ~2025-123627 (talk) 20:48, 3 July 2025 (UTC)
LTS question
Hi, I was on the Download page. I had read in many places that 1.43 was going to be the next LTS version, but right below the download button under "All Versions" box, it shows 1.44 as LTS. Is that correct? Thx. Mitzzzz (talk) 15:55, 3 July 2025 (UTC)
- No, that's a mistake in the page. The current LTS version is 1.43 as stated in Version lifecycle. 1.44 is just newer, sexier code :) Tactica (talk) 18:39, 3 July 2025 (UTC)
- @Mitzzzz I have corrected the page, thank you for reporting. —TheDJ (Not WMF) (talk • contribs) 09:38, 4 July 2025 (UTC)
TreeAndMenu compatibility with MediaWiki 1.43
I asked this question at Extension_talk:TreeAndMenu#Does_this_work_now_with_MW_1.43? but think there might be more people reading the Support Desk here.
Does anyone know whether this extension works with MediaWiki 1.43? Thanks. Jonathan3 (talk) 19:59, 4 July 2025 (UTC)
Extensions' dependencies in vendor not updated by Composer [solved]
After updating composer.local.json, a few extensions complain about missing methods. It looks like all extensions in the extension folder are properly updated, but Composer has somehow decided to ignore requirements in the extensions' own composer.json files, leaving the vendor folder untouched and in turn crippling the site.
What's the recommended way of dealing with a situation like this? I've heard that the composer.lock file may sometimes prevent updates from happening (there's at least two composer.lock files, one in the root folder and another in the /vendor folder). Should I maybe retry composer update with the --no-lock flag? Rand(1,2022) (talk) 08:47, 4 July 2025 (UTC)
- Solved. There were three separate issues: the merge plugin in composer.local.json did not yet point to the extension's folder (I was once advised against using the default settings "extensions/*/composer.json" but enough time has passed for me to forget what I had to do instead); composer.json must have been edited accidentally with a few lines that locked the version contraints; finally, different extensions require composer/installers but their version constraints are not compatible. Rand(1,2022) (talk) 08:15, 7 July 2025 (UTC)
Total newby having issues
I'm trying to install mediawiki 1.43 on a Windows 10 desktop. In the instructions "Manual:Installing MediaWiki" it says to unzip the zip file, but then immediately after it says: Upload the files to your web server's web directory either by: 1. directly copying the unzipped folder ....
Which is correct? I've tried both. If I use the zipped file I get a "file not found". If I use the unzipped file I get a message that I need to add another extension, but I can't do that unless I can open the program. Please advise. ~2025-145217 (talk) 02:31, 7 July 2025 (UTC)
- @~2025-145217: You need to unzip the files locally, and then copy them all to your web server. I don't think the instructions are contradictory: it says to unzip it, and then copy the unzipped folder. But they could be clearer! (And really I'm not sure it needs to have that much to say about people installing on their local machine, that might be what's confusing? That method is really only for developers and is covered in Local development quickstart anyway.) Sam Wilson 04:30, 7 July 2025 (UTC)
Add email address to account without password?
So, I have the following issue: I am logged in, but when creating my account I did not provide an email address for password recovery. I wanted to add that email address now, but to do so, I need a password, which I don't recall (I probably used the pass the system recommended to me). Is there any way to set an email address without your password? BlaUser234 (talk) 14:57, 8 July 2025 (UTC)
- @BlaUser234: If you used a system-generated password it should've asked you to change it when you used it to log in. If you really can't remember your password you might be a bit stuck. If you can somehow prove who you are to whoever runs your wiki, they can reset your password for you. Sam Wilson 21:23, 8 July 2025 (UTC)
Check logged user from Index.php
hi,
on MW 1.35 I was using $wgUser->isLoggedIn() on index.php to check if the user was logged.
The method isnt available on MW 1.43 but I still need a way to check it and redirect in some cases.
is there an easy way to do this?
thx for help Valeriocipriani (talk) 11:32, 8 July 2025 (UTC)
- This rings a bell. This code extract might help, though I'm checking for "sysop" here:
- Jonathan3 (talk) 12:36, 9 July 2025 (UTC)
: # new code based on https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/EditAccount/+/0f3d1420214a68e4eed5151f4600cf9c68b05661/includes/specials/SpecialCloseAccount.php : : $user = $this->getUser(); : $effectiveGroups = MediaWikiServices::getInstance() : ->getUserGroupManager() : ->getUserEffectiveGroups( $user ); : $isSysop = in_array( 'sysop', $effectiveGroups ); : if ( $isSysop ) { : ... :
I can code on FANDOM but a mainstream coding language is way too complex for me.
I can't access Miraheze, especially this link: https://miraheze.org/
The link doesn't work. That's why i am looking for a simplified way to create a wiki using Media Wiki. UnnamedChannel079 (talk) 17:31, 8 July 2025 (UTC)
- The website works so maybe they've blocked your IP address. (Similarly, I can't post here without disabling my VPN.) Jonathan3 (talk) 12:39, 9 July 2025 (UTC)
- The website works for me now. UnnamedChannel079 (talk) 13:56, 9 July 2025 (UTC)
turning off self-link bolding
Help:Self link is unclear, is this css setting supposed to work to turn off self-link bolding or does it only apply to underlining? Is there a way to turn off bolding? I've put it on my css and it doesn't seem to work. ~2025-17606-3 (talk) 01:33, 12 July 2025 (UTC)
- Apparently I can't copy and paste it here, but I mean the css snippet at the very beginning of Help:Self link ~2025-17606-3 (talk) 01:34, 12 July 2025 (UTC)
- @~2025-17606-3: That only removes the underlining. For bold you could do something like: Sam Wilson 03:23, 12 July 2025 (UTC)
.mw-selflink { font-weight: normal !important; }
- Thank you, Sam! That works! ~2025-17606-3 (talk) 07:52, 12 July 2025 (UTC)
- @~2025-17606-3: That only removes the underlining. For bold you could do something like:
I want to create a wiki using MediaWiki.
I am looking for a simplified way to create a wiki using MediaWiki. UnnamedChannel079 (talk) 08:02, 7 July 2025 (UTC)
- @UnnamedChannel079: You might be interested in something like Miraheze; a wikifarm like that is probably the simplest. But if you want to install your own wiki, start at Manual:Installing MediaWiki and then ask specific questions here with the things you have trouble with. Sam Wilson 08:32, 7 July 2025 (UTC)
- I tried accessing Miraheze but the link doesn't work. UnnamedChannel079 (talk) 08:33, 7 July 2025 (UTC)
- @UnnamedChannel079: Can you be more specific (e.g. which link, and what happened)? Sam Wilson 08:36, 7 July 2025 (UTC)
- I tried accessing this link: https://miraheze.org/
- It doesn't work at all. UnnamedChannel079 (talk) 08:37, 7 July 2025 (UTC)
- That link and the Meta site load fine where I am. Is a local firewall or similar ISP constraint blocking your access, for instance? --Slgrandson (talk) 03:32, 14 July 2025 (UTC)
- It no longer blocks my access. UnnamedChannel079 (talk) 04:37, 14 July 2025 (UTC)
- That link and the Meta site load fine where I am. Is a local firewall or similar ISP constraint blocking your access, for instance? --Slgrandson (talk) 03:32, 14 July 2025 (UTC)
- I can code on FANDOM but a mainstream coding language is way too complex for me. That's why i need a simplified way to create a wiki using MediaWiki. UnnamedChannel079 (talk) 08:39, 7 July 2025 (UTC)
- @UnnamedChannel079: Can you be more specific (e.g. which link, and what happened)? Sam Wilson 08:36, 7 July 2025 (UTC)
- I tried accessing Miraheze but the link doesn't work. UnnamedChannel079 (talk) 08:33, 7 July 2025 (UTC)
12th. July PAWS not functioning
Today, 12th. July 2025 the tool PAWS (Pywikibot) doesn't run: https://hub-paws.wmcloud.org/. Can you check it? Thanks. Leonprimer (talk) 16:54, 12 July 2025 (UTC)
- @Leonprimer Please see the top of that page where to report issues in the right place - thanks. Malyacko (talk) 14:24, 13 July 2025 (UTC)
Error Class "Title" not found with Flex Diagrams extension
Product Version
MediaWiki 1.44.0
PHP 8.3.6 (apache2handler)
ICU 74.2
MariaDB 10.11.13-MariaDB-0ubuntu0.24.04.1
wikidiff2 1.14.1
LDAPAuthentication2 3.0.1
LDAPProvider 3.0.1
PluggableAuth 7.5.0
Flex Diagrams 0.8 07:35, 30 June 2025
After an update from 1.43.0 to 1.44.0 adding my diagram into new article we get an error: Error: Class "Title" not found.
If I call my diagram for editing all works fine.
Any Ideas? ~2025-17160-7 (talk) 09:39, 11 July 2025 (UTC)
- Pinging @Yaron Koren. FWIW I'm having the same problem with Extension:Chartie, so far without a reply from the developer. Tactica (talk) 15:27, 13 July 2025 (UTC)
- Sorry about that! I had mostly fixed handling for MW 1.44+ in Flex Diagrams, but somehow had missed one line, in the handling of the #display_diagram function. I just added a fix, so if you get the latest Flex Diagrams code, it should work correctly. Yaron Koren (talk) 14:19, 14 July 2025 (UTC)
Cannot edit a page after editing and saving it.
Hi!
We have recently upgraded our MediaWiki to 1.43.1.
When we try to edit a page that has been edited and saved a few seconds ago, the blue loading bar does not finish. It only happens with the Visual Editor of MediaWiki. We have to reload the window to be able to edit.
We have enabled the log file, and we detected several [silenced-error] messages like the following one:
[silenced-error] [658fe352037f46d8bb8c4c6e] /wiki/index.php?title=Wiki PHP Warning: filemtime(): stat failed for /var/www/html/wiki/extensions/VisualEditor/editcheck/i18n/api/es.json
#0 [internal function]: MWExceptionHandler::handleError()
#1 /var/www/html/wiki/includes/language/dependency/FileDependency.php(75): filemtime()
#2 /var/www/html/wiki/includes/language/LocalisationCache.php(581): FileDependency->isExpired()
#3 /var/www/html/wiki/includes/language/LocalisationCache.php(612): LocalisationCache->isExpired()
#4 /var/www/html/wiki/includes/language/LocalisationCache.php(479): LocalisationCache->initLanguage()
#5 /var/www/html/wiki/includes/language/LocalisationCache.php(381): LocalisationCache->loadItem()
#6 /var/www/html/wiki/includes/language/Language.php(433): LocalisationCache->getItem()
#7 /var/www/html/wiki/includes/language/Language.php(510): MediaWiki\Language\Language->getNamespaces()
#8 /var/www/html/wiki/includes/title/Title.php(2968): MediaWiki\Language\Language->getNsText()
#9 /var/www/html/wiki/extensions/CategoryLockdown/CategoryLockdown.php(28): MediaWiki\Title\Title->getParentCategories()
#10 /var/www/html/wiki/includes/HookContainer/HookContainer.php(159): CategoryLockdown::onGetUserPermissionsErrors()
#11 /var/www/html/wiki/includes/HookContainer/HookRunner.php(2029): MediaWiki\HookContainer\HookContainer->run()
#12 /var/www/html/wiki/includes/Permissions/PermissionManager.php(553): MediaWiki\HookContainer\HookRunner->onGetUserPermissionsErrors()
#13 /var/www/html/wiki/includes/Permissions/PermissionManager.php(507): MediaWiki\Permissions\PermissionManager->checkPermissionHooks()
#14 /var/www/html/wiki/includes/Permissions/UserAuthority.php(373): MediaWiki\Permissions\PermissionManager->getPermissionStatus()
#15 /var/www/html/wiki/includes/Permissions/UserAuthority.php(237): MediaWiki\Permissions\UserAuthority->internalCan()
#16 /var/www/html/wiki/includes/user/User.php(3318): MediaWiki\Permissions\UserAuthority->authorizeRead()
#17 /var/www/html/wiki/includes/actions/ActionEntryPoint.php(405): MediaWiki\User\User->authorizeRead()
#18 /var/www/html/wiki/includes/actions/ActionEntryPoint.php(146): MediaWiki\Actions\ActionEntryPoint->performRequest()
#19 /var/www/html/wiki/includes/MediaWikiEntryPoint.php(200): MediaWiki\Actions\ActionEntryPoint->execute()
#20 /var/www/html/wiki/index.php(58): MediaWiki\MediaWikiEntryPoint->run()
#21 {main}
Thanks! Diegxalv (talk) 11:56, 8 July 2025 (UTC)
- Hi again!
- I have just performed a clean install of MediaWiki 1.43.3 and this problem persists. I can edit a page, but when I try to edit it again (without reloading the browser tab) the blue loading bar does not finish.
- I have tried different browsers and I deleted the browsing data.
- Is anyone else experiencing the same problem? I'm confused. Thanks Diegxalv (talk) 19:24, 8 July 2025 (UTC)
- Maybe a shot in the dark but does your "clean install" imply not using CategoryLockdown? Assuming its page here is up to date it was last updated in 2021 which is a long time ago especially for an extension that intends to provide functionality that greatly differs from the way MediaWiki works. Tactica (talk) 15:45, 13 July 2025 (UTC)
- Hi!
- This silent error message was detected in our updated MediaWiki instance, but is the same in a clean install (without the CategoryLockdown extension).
- We restored a backup, we upgraded to MediaWiki 1.39.13 (legacy long-term support release of MediaWiki) and this problem disappeared.
- Thanks for your help!! Diegxalv (talk) 13:08, 16 July 2025 (UTC)
- Maybe a shot in the dark but does your "clean install" imply not using CategoryLockdown? Assuming its page here is up to date it was last updated in 2021 which is a long time ago especially for an extension that intends to provide functionality that greatly differs from the way MediaWiki works. Tactica (talk) 15:45, 13 July 2025 (UTC)
EMail doesn't seem to be sending in 1.43.0
I have a server running mediawiki 1.43.0 that doesn't seem to be sending mails. I'm using SMTP to send it and have "$wgEnableEmail = true;" in the LocalSettings.php. Is there a log of what it is trying to do? I don't get any errors when running other than "Warning: Undefined global variable $wgEmailNotificationsMailerConf in /var/www/html/extensions/EmailNotifications/includes/EmailNotifications.php on line 86" when I have the debug line listed above enabled.
Any ideas or tips on where else I can look? MarisaG2025 (talk) 07:48, 15 July 2025 (UTC)
- I'm not sure, but it sounds like you are using Extension:EmailNotifications ? That specific extension seems to use a different mail configuration system than the core mediawiki code. —TheDJ (Not WMF) (talk • contribs) 11:06, 17 July 2025 (UTC)
Updating to 1.44: Skin errors
After upgrading to MediaWiki 1.44, I’m seeing a fatal error on all pages:
Fatal Error After Upgrading to MediaWiki 1.44 — `array_column(): Argument #1 ($array) must be of type array, string given - seems to be traced back to the deprecated sidebar functions (shouldn't be causing an error in 1.44 though?)
TypeError: array_column(): Argument #1 ($array) must be of type array, string given
Backtrace:
from /includes/skins/Skin.php(1548)
#0 /includes/skins/Skin.php(1548): array_column()
#1 /includes/skins/Skin.php(1639): MediaWiki\Skin\Skin->appendSpecialPagesLinkIfAbsent()
#2 /includes/skins/SkinTemplate.php(615): MediaWiki\Skin\Skin->buildSidebar()
#3 /includes/skins/SkinTemplate.php(194): MediaWiki\Skin\SkinTemplate->getPortletsTemplateData()
#4 /includes/skins/SkinMustache.php(131): MediaWiki\Skin\SkinTemplate->getTemplateData()
#5 /includes/SkinVectorLegacy.php(173): MediaWiki\Skin\SkinMustache->getTemplateData()
#6 /includes/skins/SkinMustache.php(93): MediaWiki\Skins\Vector\SkinVectorLegacy->getTemplateData()
#7 /includes/skins/SkinTemplate.php(187): MediaWiki\Skin\SkinMustache->generateHTML()
#8 /includes/skins/Skin.php(682): MediaWiki\Skin\SkinTemplate->outputPage()
#9 /includes/Output/OutputPage.php(3286): MediaWiki\Skin\Skin->outputPageFinal()
#10 /includes/actions/ActionEntryPoint.php(160): MediaWiki\Output\OutputPage->output()
#11 /includes/MediaWikiEntryPoint.php(202): MediaWiki\Actions\ActionEntryPoint->execute()
#12 /index.php(58): MediaWiki\MediaWikiEntryPoint->run()
Ive also tried disabling all extensions and trying all other skins - showing the same error on all.
PenguinBegins (talk) 22:05, 15 July 2025 (UTC)
- Did you upgrade your skins while upgrading to 1.44? If you only upgraded MediaWiki itself but are still using pre-1.44 versions of skins, that might be your problem. Tactica (talk) 00:29, 16 July 2025 (UTC)
- I think someone forgot the remove a line from Skin.php (and I just downloaded the 1.44.0 zip)
- -
- Line 1541: private function appendSpecialPagesLinkIfAbsent() {
- Line 1639: $this->appendSpecialPagesLinkIfAbsent();
- -
- The function comments for appendSpecialPagesLinkIfAbsent() says deprecated in 1.44 but in line 1639 is it being used. This does puzzle me greatly. I have not tried removing it yet (as I'm using the docker image, need to expose the Skins directory otherwise I can't edit it) but I'm sure once you comment out line 1639 the error is gone
- Regards
- Sjoerd Sjoerd72 (talk) 07:13, 16 July 2025 (UTC)
- -
- I can confirm that the "fix" I mentioned works.. - just comment line 1639 in Skins.php and you are good. add // in front of $this->appendSpecialPagesLinkIfAbsent();
- Regards
- Sjoerd Sjoerd72 (talk) 07:25, 16 July 2025 (UTC)
- A deprecation is a deprecation, it is not a removal. It is specifically there to motivate people to fix the code so that the function can eventually be removed safely. Which skin are you using that is calling this path ? —TheDJ (Not WMF) (talk • contribs) 10:01, 17 July 2025 (UTC)
- It seems this code was reworked as well as deprecated, so I suspect a compatibility issue with certain skins. —TheDJ (Not WMF) (talk • contribs) 10:54, 17 July 2025 (UTC)
- Please read Manual:Interface/Sidebar#Deprecation warning for Skin::appendSpecialPagesLinkIfAbsent() for information on why that function is there. That said I don't know what the array issue mentioned by PenguinBegins is caused by. Aaron Liu (talk) 01:17, 18 July 2025 (UTC)
Using new Vector's heading menu on Foreground/Chameleon skins
I dislike the new Vector skin generally, but really like the menu on the left that lets you keep track of which heading you're at.
Can this be used on other skins? Jonathan3 (talk) 13:26, 16 July 2025 (UTC)
- @Jonathan3 It is a skin feature, so no not without development work. —TheDJ (Not WMF) (talk • contribs) 09:58, 17 July 2025 (UTC)
- Thank you. I've now seen Extension:StickyTOC and its comment: "This extension has been archived. Chameleon skin (>4.4) supports this natively. It was archived per T374778." I haven't used Chameleon (only Foreground) but looked at it briefly and didn't see any mention of "sticky" TOCs. But I'll look into it more! Jonathan3 (talk) 13:37, 17 July 2025 (UTC)
Help upgrading software to newest version
Hi there!
Our current wiki is running on software version 1.35.14 and I dont even know where to begin with upgrading to new versions - this has been a job sort of neglected so want to make sure I do it right and dont break anything.
Thank you :) Erinwake (talk) 10:26, 17 July 2025 (UTC)
- Upgrade to 1.39, then to 1.43, then 1.44. General instructions are in Manual:Upgrading. Tactica (talk) 12:49, 17 July 2025 (UTC)
Uploading files under redirecting name
Suppose I have a file that I've moved from Image (Version 1) to Image (Version 2) as a bureaucrat on a third-party wiki, and have decided to make a new upload under the leftover redirect Image (Version 1). Before I conduct this action on Miraheze, is it actually safe to do so? --Slgrandson (talk) 19:07, 14 July 2025 (UTC)
- Replacing the redirect with a new upload will simply make it stop working as a redirect, so pages linking there will use the new upload instead of being redirected to version 2 of the image, that's all. Tactica (talk) 00:01, 16 July 2025 (UTC)
- I'm not sure it will actually work that way. A reupload doesn't modify the file description page when it already exists, and if it contains a redirect, it will still act as a redirect. You'll have to manually edit the rediect page, blanking it or replacing it with a proper description. Ciencia Al Poder (talk) 13:42, 18 July 2025 (UTC)
Intl extension in MW 1.43
Hello,
I have been trying to install Mediawiki 1.43 on a Windows 10 desktop. I have been running into the error below:

This is one of the extensions required by Mediawiki 1.43, as shown to the right:
* ctype; * dom; * fileinfo; * iconv; * intl; * json; * mbstring; * xml
However, I am confused, as my research says that the intl extension has been included in the download version of Mediawiki since 2015. Why is it not included in the installation?
BTW, I am using XAMPP 8.2.12 as my server. Would that have any influence?
Dave at david.axtell@gmail.com Dave Axtell (talk) 14:53, 17 July 2025 (UTC)
- "Why is it not included in the installation?"
- That's a question for the XAMPP maintainers. With a common PHP distribution, you would just enable the extension in php.ini. Tactica (talk) 12:26, 18 July 2025 (UTC)
- intl is a php extension, not a Mediawiki extension. It can't be included by Mediawiki. It needs to be enabled in php.ini. Ciencia Al Poder (talk) 13:39, 18 July 2025 (UTC)
How to open inputbox in new tab?
My question about Extension:InputBox. I have this input box to create in new page:
I want to open the create page in a new Tab when click on the button, like target="_blank". How do I do this?
This is my old question. Currently the extention don't support these feature. Is there any way to do this using common.js ? Nimon didarul (talk) 12:42, 18 July 2025 (UTC)
- @Nimon didarul: You could do something like:Change that selector to
mw.hook( 'wikipage.content' ).add( () => { document.querySelectorAll( '.mw-inputbox-form, .mw-inputbox-form-inline' ).forEach( ( e ) => { e.target = '_blank'; } ); } );
.createbox.mw-inputbox-formif you only want to do page-creation inputboxen. Sam Wilson 08:08, 19 July 2025 (UTC)- @Samwilson Thanks. Its working.👍 Nimon didarul (talk) 08:32, 19 July 2025 (UTC)
Vector-2022 skin is not loading on Chrome
Works fine with edge. I tried the original vector skin and had the same problem.
From the Chrome developer console I am seeing the following errors:
load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:1
Uncaught SyntaxError: Unexpected token '<' (at load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector:1:1)
Refused to apply style from
'...//localhost/mediawiki/load.php?lang=en&modules=skins.vector.styles.legacy&only=styles&skin=vector' because its MIME type ('') is not a supported stylesheet MIME type, and strict MIME checking is enabled. TerryMcP (talk) 13:11, 18 July 2025 (UTC)
- Open the load.php URL directly or on a new tab. It may contain an actual error message, useful to diagnose the issue. Ciencia Al Poder (talk) 13:37, 18 July 2025 (UTC)
- Results from opening load.php
- <!DOCTYPE html><center><b>Terry's Development Wiki</b></center><br />/* This file is the Web entry point for MediaWiki's ResourceLoader:
- <xxxx://www.mediawiki.org/wiki/ResourceLoader>. In this request,
- no modules were requested. Max made me put this here. */ TerryMcP (talk) 14:08, 18 July 2025 (UTC)
- http://myhost/mediawiki/load.php?lang=en&modules=skins.vector.styles.legacy&only=styles&skin=vector
- This link opens some html. no errors TerryMcP (talk) 15:19, 18 July 2025 (UTC)
- I ran 'composer update' from my mediawiki folder and this didn't help TerryMcP (talk) 14:39, 18 July 2025 (UTC)
- Try to open the exact URL that the console shows it's returning an unsupported stylesheet MIME type Ciencia Al Poder (talk) 14:53, 18 July 2025 (UTC)
- Well, they absoultely shouldn't open html. They should open css or js. Check if the HTML is coming from your host or generated by any other application. Ciencia Al Poder (talk) 15:40, 18 July 2025 (UTC)
- Try to open the exact URL that the console shows it's returning an unsupported stylesheet MIME type Ciencia Al Poder (talk) 14:53, 18 July 2025 (UTC)
Obligatory security rules that users cannot decide
Hello, as I couldn't get an answer on TR Wiki, is there a way for me to disable email verification? It seems that this is a new tool, but I seriously don't want to be obliged to log in my e mail adress for a code every single time I try to log in my Wiki account. I really don't care if a log in to my account from Planet Mars is detected, I don't want obligatory security tools. Pardon my language but I'm already tired of "you cannot use an old password, you need to pass this laser trap for verification" types of security rules in various websites and apps. I'd hate if Wikipedia is coming to that point. Should I create a phabricator topic? I need help. Tün (talk) 10:18, 19 July 2025 (UTC)
- This very page is for general questions about MediaWiki configuration and setup. Phabricator is for bug reports and feature requests, not for topics. If you want to discuss technical aspects of Wikimedia wikis, see https://meta.wikimedia.org/wiki/Tech - thanks. Malyacko (talk) 20:32, 19 July 2025 (UTC)
Autologin not working since 1.35 -> 1.43 Update
Hi everyone,
We recently upgraded our MediaWiki instance from version 1.35 to 1.43, and since then, our LDAP autologon setup has stopped working. Previously, users were automatically logged in via LDAP without needing to manually enter credentials. Now, they’re redirected to the login page and must log in manually. Logging in manually via domain credentials still works.
Our Setup:
MediaWiki 1.43
LDAP Stack:
wfLoadExtension( 'PluggableAuth' );
wfLoadExtension( 'LDAPProvider' );
wfLoadExtension( 'LDAPAuthentication2' );
wfLoadExtension( 'LDAPAuthorization' );
wfLoadExtension( 'LDAPGroups' );
wfLoadExtension( 'LDAPUserInfo' );
wfLoadExtension( 'Auth_remoteuser' );
Configuration:
# PluggableAuth
$wgPluggableAuth_Config['Log In (do)'] = [
'plugin' => 'LDAPAuthentication2',
'data' => [ 'domain' => 'do.re.me-so.net' ]
];
$wgPluggableAuth_EnableAutoLogin = true;
$wgPluggableAuth_EnableLocalLogin = false;
# LDAP Provider
$LDAPProviderDomainConfigs = "$IP/provider/ldap.json";
$LDAPProviderDefaultDomain = "do.re.me-so.net";
# LDAPAuthentication2
$LDAPAuthentication2AllowLocalLogin = true;
$LDAPAuthentication2UsernameNormalizer = 'strtolower';
# LDAPAuthorization
$LDAPAuthorizationAutoAuthUsernameNormalizer = 'strtolower';
$LDAPAuthorizationAutoAuthRemoteUserStringParser = 'domain-backslash-username';
#AuthRemoteUser
$wgAuthRemoteuserUserNameReplaceFilter = [
'^do\\' => 'do.re.me-so.net\\'
];
$wgAuthRemoteuserUserName = [
$_SERVER[ 'REMOTE_USER' ]
];
But I can see in the logfiles:
mediawiki: MediaWiki\Extension\LDAPAuthorization\Hook\AuthRemoteuserFilterUserName: Check authorization for user 'DO\aUser'.
mediawiki: Resolved to username 'aUser' and domain 'DO'
mediawiki: Could not check login requirements for DO\aUser
mediawiki: No configuration available for domain 'do'!
If I shorten the domain from "do.re.me-so.net" to just "do" in my ldap.json I end up in a loop, but I can see in the logfiles that it successfully matches the user and domain, but does it endlessly.
Autologon worked perfectly in 1.35
All the extensions are updated to match our 1.43 LTS. Slk-fsk (talk) 13:43, 17 July 2025 (UTC)
- Looks like Extension:Auth_remoteuser may have some issues with MediaWiki 1.43. I recently had a similar issue (probably not the same), where there was a "memory exhaused" error caused by a deadloop, when
$wgAuthRemoteuserAllowUserSwitchwas set tofalse(default). - In your particular case, I believe
$wgAuthRemoteuserUserNameReplaceFilteris not properly executed before Extension:LDAPAuthorization tries to split domain and username inAuthRemoteuserFilterUserNamehook. Renaming your domain in the configuration todoseems reasonable. I'd recommend checking why the loop happens. Have you enabled the log channel for Extension:Auth_remoteuser and MediaWiki'ssessionchannel? - Hint: there is also the new extension Extension:AuthRemoteUser since last year. I haven't used it yet, but it may be worth looking into it. Osnard (talk) 08:23, 22 July 2025 (UTC)
UserGroups does not work
When I use UserGroups, the changes do not apply. It says they apply, and even writes a log entry, but the rights are the exact same as before. ~2025-27293-9 (talk) 02:44, 27 July 2025 (UTC)
Distinguishing Visible Page Links from Template Links in Wikipedia Data
Hello,
Is there a way, using the Wikipedia database (such as dumps or APIs), to differentiate between links that are part of the main visible content of a Wikipedia page and those that only appear in navigation templates (like the "V.T.E" boxes at the bottom), without needing to parse the page's HTML or DOM?
Thank you! ~2025-23955-6 (talk) 20:14, 21 July 2025 (UTC)
- @~2025-23955-6 No, there is not. A link is a link and content does not have a logical subdivision of itself at the database level to distinguish one part of the content from the other. Technically I guess you could take a dump, find all Navboxes, find links on those pages, and substract those from the links in pages that include said Navboxes, but that would also remove any links in the main content that happen to also be inside the Navboxes. —TheDJ (Not WMF) (talk • contribs) 08:05, 22 July 2025 (UTC)
- Thank you for the response. I assume these navigation links were primarily designed with bots and crawlers in mind, as it seems unlikely that human users commonly navigate through them.
- Would you recommend processing the enwiki-latest-pages-articles.xml.bz2 dump (which contains the latest content) to extract and map navigation links for each page, then comparing that against the mappings obtained from the page, pagelinks, and linktarget SQL dumps (which I’ve already processed), in order to identify and filter out such links as outliers?
- This approach seems feasible, but I’m hoping there might be a more efficient or elegant solution that someone else has already explored. ~2025-24445-5 (talk) 19:24, 22 July 2025 (UTC)
- As far as I know, there is not a simpler or more accurate way to achieve this. —TheDJ (Not WMF) (talk • contribs) 09:55, 25 July 2025 (UTC)
- @~2025-23955-6: Depending on what you mean exactly by "the main visible content", you could use the API to get the wikitext of a page, and then filter too keep only links directly in the wikitext (
\[\[[^\]*?\]\]); as opposed to links present through templates (because those are not present in the page wikitext proper). The V·T·E links of w:Template:Barack Obama sidebar are only present in the source through{{Barack Obama sidebar}}. — Alien 3
3 3 15:56, 26 July 2025 (UTC)- hey there thx for the reply, the problem is that when you add Template:Barack Obama to a page X, all the links that are part of Template:Barack Obama get added in the "pages → pagelinks → linktargets → pages" sql tables, in the content they appear in the templates at the bottom, but in the dumps they appear as direct links, and there no way to differentiate between them and the real links that you see when you are reading a page. And you cant call the api on each page you are processing because you will get flagged and rate limited quickly. ~2025-27467-2 (talk) 15:14, 27 July 2025 (UTC)
I am not able to create my Wikipedia, it is telling me that my IP address is blocked, why is this so
I am not able to create my Wikipedia, it is telling me that my IP address is blocked, why is this so ~2025-27676-9 (talk) 11:46, 27 July 2025 (UTC)
- @~2025-27676-9 There is not such thing as 'your wikipedia'. Additionally, this is the support desk for a software package called MediaWiki, it is not the support page for Wikipedia. —TheDJ (Not WMF) (talk • contribs) 13:42, 27 July 2025 (UTC)
Differences between Special:WhatLinksHere and API
Dear ∀,
There is a different behaviour between Special:WhatLinksHere and the api that I do not yet understand:
On https://de.wikipedia.org/w/index.php?title=Spezial:Linkliste/Vorlage:Farblegende&limit=500 you can see that there are beyond 500 links to w:de:Vorlage:Farblegende.
But
- curl "https://de.wikipedia.org/w/api.php?action=query&prop=linkshere&lhprop=title&titles=Vorlage:Farblegende&lhlimit=500&format=json" | jq -r '.query.pages."1090160".linkshere | length'
returns 83
How would I need to modify my api query to get a list returned that compares to the list on the special page?
Thank you in advance.
yours, Ciciban (talk) 16:34, 27 July 2025 (UTC)
- The Special:WhatLinksHere has, in the filter section, checkboxes exclude links, transclusions and redirects. That's because MediaWiki stores those 3 types of link separately. And the api is also divided between them. You'll need to also query transclusions and redirects: see API Sandbox. Ciencia Al Poder (talk) 21:30, 27 July 2025 (UTC)
Login fault
I used the code provided via email and it says the code is invalid when I try to logi. ~2025-27889-9 (talk) 00:34, 28 July 2025 (UTC)
how to retrieve value of the user interface language ?
hi all, on EN page Extension:CentralAuth/API instead of english warning boxes i would like to see them in the user interface language and because they are actually correctly followed by the description in user language.
i.e.
{{Api help|centralauthtoken}}would become in french
{{Api help/fr|centralauthtoken}}
which is ok, so more generally something like :
{{Api help{{#translation:}}|centralauthtoken}}but this last doesnt work
How to solve that please ? Thanks. -- Christian 🇫🇷 FR 🚨 (talk) 07:25, 28 July 2025 (UTC)
- @Wladek92: That page isn't marked for translation, so you can't view it in anything other than English. I might be misunderstanding what you're aiming to do, but it seems like you should set that page up for translation, and use the {{Api help}} template outside of any translate tags. Sam Wilson 08:09, 28 July 2025 (UTC)
- - " so you can't view it in anything other than English." : sorry but if i open the page in the FR interface, i get a happy mix of EN text, EN Warning and FR text
- - "I might be misunderstanding what you're aiming to do" : question is in the title
- - "it seems like you should set that page up for translation": this is not requested. Christian 🇫🇷 FR 🚨 (talk) 08:26, 28 July 2025 (UTC)
- @Wladek92: You can't retrieve the user interface language in the wikitext because it'll differ for everyone viewing the page. Sam Wilson 08:37, 28 July 2025 (UTC)
- And this is precisely what is requested, a dynamic adaptation : the lowest part of the page succeeded doing it. Let me wait for another point of view. Christian 🇫🇷 FR 🚨 (talk) 08:41, 28 July 2025 (UTC)
- @Wladek92. You don't need the user language to load a language specific subpage. You can simply use the translate extension (which is what the ApiHelp template does, which is why THAT part of the page is translated). See also Help:Extension:Translate. —TheDJ (Not WMF) (talk • contribs) 08:04, 29 July 2025 (UTC)
- And this is precisely what is requested, a dynamic adaptation : the lowest part of the page succeeded doing it. Let me wait for another point of view. Christian 🇫🇷 FR 🚨 (talk) 08:41, 28 July 2025 (UTC)
- @Wladek92: You can't retrieve the user interface language in the wikitext because it'll differ for everyone viewing the page. Sam Wilson 08:37, 28 July 2025 (UTC)
MediaWiki internal error: Classes not found despite being in folders?
Hello there, this feels so silly to ask, but I have not made any recent changes to my wiki at all yet it is suddenly now giving an error:
Error: Class "Title" not found and Error: Class "Html" not found
I can not pull up my current version sadly since my special pages are all done. Any help would be much appreciated!
Here is my wiki site:
https://www.vosueh.com/ Vosueh (talk) 01:37, 30 July 2025 (UTC)
- @Vosueh: It looks like the error's coming from the Cosmos skin. Have you upgraded that recently? Sam Wilson 01:42, 30 July 2025 (UTC)
- I have not :(
- It shouldn't auto-update itself or anything, right? All my files look to be in place for that skin Vosueh (talk) 02:33, 30 July 2025 (UTC)
- @Vosueh: It looks like Vector still works on your site, so if you change your skin in LocalSettings.php things should at least get working again. Nothing would normally upgrade itself, but something seems to have definitely changed if this just started happening out of the blue! Sam Wilson 05:04, 30 July 2025 (UTC)
- Thank you! I switched it to Vector and its working, but that's so strange Cosmos broke like that. I really like the way it looked too, is there anyway to possibly troubleshoot why it was suddenly stopped working? The Cosmos skin folder hasn't been modified since 2023, so I don't know how something could've suddenly conflicted. Vosueh (talk) 06:58, 30 July 2025 (UTC)
- Upon looking into the Cosmos Hooks.php, I believe the error might be in trying the "use" statement with html and title, which it appears to be inheriting from MediaWiki. Was that changed with MediaWiki at all? I changed the skin back to Cosmos so the error is visible again.
- Hooks.php:
namespace MediaWiki\Skins\Cosmos;use Html;use Title;Vosueh (talk) 07:05, 30 July 2025 (UTC)- @Vosueh: I don't think it would've been Cosmos that broke it, but rather that core was updated and Cosmos wasn't. But it sounds like you've not intentionally updated core? It's on 1.44, which was released less than a month ago, so it does sound like that might be the issue. Could someone else have updated it and not finished the job? Or are you maybe running it from a Git checkout, and it got switched to master at some point? Sam Wilson 07:23, 30 July 2025 (UTC)
- I am the only person in control of this wiki, so nobody else could've updated it. Is there a way for me to move my wiki to an older version? I do not know the details of the 1.44 deployment, but if its altering class names at all then I think you're right that it's probably the issue, especially considering I haven't made any changes in the last year or so other than adding wiki pages. Vosueh (talk) 07:39, 30 July 2025 (UTC)
- @Vosueh: I think you'd be best to go through your skins and extensions and upgrade them to 1.44. Although it's a bit confusing that something was upgraded without you knowing! Still, if you've got good backups (you do, right? :-P) then keeping up to date is always a good thing. It looks like there's been recent activity on Cosmos, so perhaps it's fine for 1.44 once you upgrade it (maybe @SomeRandomDeveloper knowns?). Sam Wilson 09:02, 30 July 2025 (UTC)
- Cosmos does support 1.44, it's gone through the 1.44 testing program on Miraheze already and is working fine. The Cosmos example wiki is running on 1.44 as well. SomeRandomDeveloper (talk) 11:34, 30 July 2025 (UTC)
- I updated my Cosmos skin and its working again! I checked the Hooks.php file, and it appears the newest Cosmos does not have the "use Title" or "use HTML" lines, so I believe those calls must've been out of date with the newest MediaWiki. Still no clue how/why my version of MediaWiki updated without my input!
- Sadly, it looks like the update appears to have broken most of my pages and infoboxes, I made custom infoboxes and they also reference Title. @SomeRandomDeveloper and @Samwilson, do either of you know what is the 1.44 equivalent to Title?
- This is my infobox templete, and I believe it is this line at the very top breaking it:
<title source="name"><default>{{PAGENAME}}</default></title>- Also, thank you guys so much for your help and input, it means a lot! Vosueh (talk) 22:12, 30 July 2025 (UTC)
- The
<title>tag in infoboxes is not related to the Title class in PHP. Based on the error I can see on the page you linked, you should be able to fix it by updating the PortableInfobox extension as well. - It should not be necessary to edit any articles in your wiki when upgrading to a new MediaWiki version - usually only the extensions and skins need to be updated. SomeRandomDeveloper (talk) 22:17, 30 July 2025 (UTC)
- That did the trick, looks like its all fixed now! Thank you so much, I can't tell you how much I appreciate it. Now I can keep my silly wiki up for my DnD and original character :,)
- Do either of you have something like a Ko-fi? I'd love to show some appreciation for the help you both gave me! Vosueh (talk) 22:26, 30 July 2025 (UTC)
- No worries! Note that some other skins and extensions you're using might need to be updated too. For example, trying to use the Citizen skin on your wiki results in errors as well.
- Also, thank you for the offer, but I don't take donations, I'm happy enough just being able to help :) SomeRandomDeveloper (talk) 22:37, 30 July 2025 (UTC)
- I didn't even catch that one! I loaded a lot of skins early on when I was experimenting with the appearance, it's probably best I keep them all up to date, thanks for the heads up!
- You've been amazing, I hope you have the best day possible, thank you and @Samwilson again for the help. Truly grateful for the work you guys do <3 Vosueh (talk) 23:13, 30 July 2025 (UTC)
- The
- Cosmos does support 1.44, it's gone through the 1.44 testing program on Miraheze already and is working fine. The Cosmos example wiki is running on 1.44 as well. SomeRandomDeveloper (talk) 11:34, 30 July 2025 (UTC)
- @Vosueh: I think you'd be best to go through your skins and extensions and upgrade them to 1.44. Although it's a bit confusing that something was upgraded without you knowing! Still, if you've got good backups (you do, right? :-P) then keeping up to date is always a good thing. It looks like there's been recent activity on Cosmos, so perhaps it's fine for 1.44 once you upgrade it (maybe @SomeRandomDeveloper knowns?). Sam Wilson 09:02, 30 July 2025 (UTC)
- I am the only person in control of this wiki, so nobody else could've updated it. Is there a way for me to move my wiki to an older version? I do not know the details of the 1.44 deployment, but if its altering class names at all then I think you're right that it's probably the issue, especially considering I haven't made any changes in the last year or so other than adding wiki pages. Vosueh (talk) 07:39, 30 July 2025 (UTC)
- @Vosueh: I don't think it would've been Cosmos that broke it, but rather that core was updated and Cosmos wasn't. But it sounds like you've not intentionally updated core? It's on 1.44, which was released less than a month ago, so it does sound like that might be the issue. Could someone else have updated it and not finished the job? Or are you maybe running it from a Git checkout, and it got switched to master at some point? Sam Wilson 07:23, 30 July 2025 (UTC)
- Thank you! I switched it to Vector and its working, but that's so strange Cosmos broke like that. I really like the way it looked too, is there anyway to possibly troubleshoot why it was suddenly stopped working? The Cosmos skin folder hasn't been modified since 2023, so I don't know how something could've suddenly conflicted. Vosueh (talk) 06:58, 30 July 2025 (UTC)
- @Vosueh: It looks like Vector still works on your site, so if you change your skin in LocalSettings.php things should at least get working again. Nothing would normally upgrade itself, but something seems to have definitely changed if this just started happening out of the blue! Sam Wilson 05:04, 30 July 2025 (UTC)
MediaWiki:Anoneditwarning
Why are there parameters $1 and $2 in MediaWiki:Anoneditwarning? - Erik Baas (talk) 22:27, 29 July 2025 (UTC)
Day and night theme
i d like to have a Light and Dark theme.
This is for coherence with my website.
I know that is a little question. Dathewolf (talk) 17:24, 30 July 2025 (UTC)
- @Dathewolf See Dark mode and Manual:Dark mode. —TheDJ (Not WMF) (talk • contribs) 14:22, 31 July 2025 (UTC)
Password reset
I forget my password how can I change password because email is not received yet. ~2025-31071-7 (talk) 07:35, 1 August 2025 (UTC)
Module:Television infoboxes disambiguation check not found.
I’m currently working on cleaning up the errors that appear in relation to the television infobox on my wiki. One of the errors says this:
Lua error in package.lua at line 80: module ‘Module:Television infoboxes disambiguation check’ not found.
I imported the television infobox disambiguation check module from Wikipedia as I thought that would remove the error. Turns out, it didn’t solve the problem and I still don’t know why it’s happening. Here’s a link to the page that features the error. BeanieBear (talk) 16:28, 30 July 2025 (UTC)
- You imported a module but you didn't pay attention to the dependencies. Line #3 in that module clearly attempts to open "Module:Television infoboxes disambiguation check" which is missing.
- Before importing templates and modules from Wikipedia, you should pay attention to the dependencies which are typically listed in floating boxes as part of the documentation, especially because most of the time those dependencies in turn depend on some other stuff. This will get you started, though for accompanying documentation to look proper you may need either additional templates or doing your own adaptations. Tactica (talk) 02:55, 3 August 2025 (UTC)
Edits to Wikipedia page not saving
I have a Wikipedia page about a Marketing and Public Relations client that needs to be updated. It looks like the person who made it speaks a different language and got a LOT of details spelled wrong and got several other details incorrect. I am trying to update it to the correct info. I created an account and did the edits. I hit save several times. It looked like it was updated, but then today I looked at it and it hadn't saved any of the updates at all. What happened and how do I fix it? How do I get it to stay in English, also? Thank you for your time! TheAngieScottMarketing@gmail.com. ~2025-30051-8 (talk) 22:02, 30 July 2025 (UTC)
V1.39.12 -> V1.43.1
lors de la montée en version mon site ne fonctionne plus, je ne sais pas ce qu'il faut faire, pouvez vous m'aider?


Schub srx (talk) 08:22, 3 August 2025 (UTC)
- Turn off deprecation warnings. See https://stackoverflow.com/questions/24559842/turning-off-deprecation-warnings-in-php-ini-file-wamp Ciencia Al Poder (talk) 09:37, 3 August 2025 (UTC)
Discussion at Talk:Codex § Create Template:Codex icon to output a Codex icon in wikitext
You are invited to join the discussion at Talk:Codex § Create Template:Codex icon to output a Codex icon in wikitext . Waddie96 (talk) 07:39, 5 August 2025 (UTC)
MediaWiki:Visualeditor-specialcharacter-group-set-accents
Are spaces allowed in MediaWiki:Visualeditor-specialcharacter-group-set-accents? The reason I'm asking is that this page becomes twice as wide as my browser window, which then shows a horizontal scrollbar. I would like to insert a couple of spaces to break that long line of text. - Erik Baas (talk) 21:30, 29 July 2025 (UTC)
- Never mind, I found another solution:
body.mw-special-Allmessages table#mw-allmessagestable tbody tr td+td {word-break: break-word;}
Database error on login after configuring CentralAuth
MediaWiki Version: 1.36.2
PHP: 7.4.30 (cgi-fcgi)
MySQL Version: 5.6.51-cll-lve
Hello. I had added the CentralAuth extension to my wiki family and configured the settings for that extension on PhpMyAdmin. When I tried to log into my wiki this morning, however, I got a database error on the gu_name column of my globaluser table. It's hard for me to fix this.
[b941d92fe53ccac4b74ff36c] /mw19/index.php?title=Special:UserLogin&returnto=Special:SpecialPages Wikimedia\Rdbms\DBQueryError: A database query error has occurred. Did you forget to run your application's database schema updater after upgrading?
Error 1054: Unknown column 'gu_salt' in 'SELECT' (localhost)
Function: CentralAuthUser::loadFromDatabase
Query: SELECT gu_id,gu_name,lu_wiki,gu_salt,gu_password,gu_auth_token,gu_locked,gu_hidden,gu_registration,gu_email,gu_email_authenticated,gu_home_db,gu_cas_token FROM `mwd50q_globaluser`,`mwd50q_localuser` WHERE gu_name = 'Newman2' LIMIT 1
Backtrace:
from /home/gjlxrtap/public_html/mw19/includes/libs/rdbms/database/Database.php(1719)
#0 /home/gjlxrtap/public_html/mw19/includes/libs/rdbms/database/Database.php(1703): Wikimedia\Rdbms\Database->getQueryException(string, integer, string, string)
#1 /home/gjlxrtap/public_html/mw19/includes/libs/rdbms/database/Database.php(1678): Wikimedia\Rdbms\Database->getQueryExceptionAndLog(string, integer, string, string)
#2 /home/gjlxrtap/public_html/mw19/includes/libs/rdbms/database/Database.php(1244): Wikimedia\Rdbms\Database->reportQueryError(string, integer, string, string, boolean)
#3 /home/gjlxrtap/public_html/mw19/includes/libs/rdbms/database/Database.php(1929): Wikimedia\Rdbms\Database->query(string, string, integer)
#4 /home/gjlxrtap/public_html/mw19/includes/libs/rdbms/database/Database.php(2029): Wikimedia\Rdbms\Database->select(array, array, array, string, array, array)
#5 /home/gjlxrtap/public_html/mw19/includes/libs/rdbms/database/DBConnRef.php(68): Wikimedia\Rdbms\Database->selectRow(array, array, array, string, array, array)
#6 /home/gjlxrtap/public_html/mw19/includes/libs/rdbms/database/DBConnRef.php(331): Wikimedia\Rdbms\DBConnRef->__call(string, array)
#7 /home/gjlxrtap/public_html/mw19/extensions/CentralAuth/includes/CentralAuthUser.php(472): Wikimedia\Rdbms\DBConnRef->selectRow(array, array, array, string, array, array)
#8 /home/gjlxrtap/public_html/mw19/extensions/CentralAuth/includes/CentralAuthUser.php(536): CentralAuthUser->loadFromDatabase()
#9 /home/gjlxrtap/public_html/mw19/includes/libs/objectcache/wancache/WANObjectCache.php(1707): CentralAuthUser->{closure}(boolean, integer, array, NULL, array)
#10 /home/gjlxrtap/public_html/mw19/includes/libs/objectcache/wancache/WANObjectCache.php(1539): WANObjectCache->fetchOrRegenerate(string, integer, Closure, array, array)
#11 /home/gjlxrtap/public_html/mw19/extensions/CentralAuth/includes/CentralAuthUser.php(547): WANObjectCache->getWithSetCallback(string, integer, Closure, array)
#12 /home/gjlxrtap/public_html/mw19/extensions/CentralAuth/includes/CentralAuthUser.php(403): CentralAuthUser->loadFromCache()
#13 /home/gjlxrtap/public_html/mw19/extensions/CentralAuth/includes/CentralAuthUser.php(578): CentralAuthUser->loadState()
#14 /home/gjlxrtap/public_html/mw19/extensions/CentralAuth/includes/CentralAuthUser.php(675): CentralAuthUser->getId()
#15 /home/gjlxrtap/public_html/mw19/extensions/CentralAuth/includes/CentralAuthHooks.php(931): CentralAuthUser->exists()
#16 /home/gjlxrtap/public_html/mw19/includes/HookContainer/HookContainer.php(338): CentralAuthHooks::onGetUserBlock(User, string, NULL)
#17 /home/gjlxrtap/public_html/mw19/includes/HookContainer/HookContainer.php(137): MediaWiki\HookContainer\HookContainer->callLegacyHook(string, array, array, array)
#18 /home/gjlxrtap/public_html/mw19/includes/HookContainer/HookRunner.php(2013): MediaWiki\HookContainer\HookContainer->run(string, array)
#19 /home/gjlxrtap/public_html/mw19/includes/block/BlockManager.php(175): MediaWiki\HookContainer\HookRunner->onGetUserBlock(User, string, NULL)
#20 /home/gjlxrtap/public_html/mw19/includes/user/User.php(1660): MediaWiki\Block\BlockManager->getUserBlock(User, WebRequest, boolean, boolean)
#21 /home/gjlxrtap/public_html/mw19/includes/user/User.php(1958): User->getBlockedStatus(boolean, boolean)
#22 /home/gjlxrtap/public_html/mw19/includes/block/BlockManager.php(484): User->getBlock()
#23 /home/gjlxrtap/public_html/mw19/includes/MediaWiki.php(771): MediaWiki\Block\BlockManager->trackBlockWithCookie(User, WebResponse)
#24 /home/gjlxrtap/public_html/mw19/includes/MediaWiki.php(637): MediaWiki::preOutputCommit(RequestContext, Closure)
#25 /home/gjlxrtap/public_html/mw19/includes/MediaWiki.php(936): MediaWiki->doPreOutputCommit(Closure)
#26 /home/gjlxrtap/public_html/mw19/includes/MediaWiki.php(546): MediaWiki->main()
#27 /home/gjlxrtap/public_html/mw19/index.php(53): MediaWiki->run()
#28 /home/gjlxrtap/public_html/mw19/index.php(46): wfIndexMain()
#29 {main}
Can somebody please tell me what is going on? Thank you for reading. Newman2 (talk) 18:33, 4 August 2025 (UTC)
- @Newman2: Did you run update.php after adding the extension? When you say configured the settings […] on PhpMyAdmin what do you mean? It shouldn't ever be necessary to do anything directly to the database when installing an extension. Sam Wilson 23:41, 4 August 2025 (UTC)
- 1.36.2 is an ancient, insecure, unsupported version. Please run maintained software versions for your own safety. Malyacko (talk) 07:41, 6 August 2025 (UTC)
How to build an internal wiki for traditional tea culture?
Hi everyone,
I’m building a MediaWiki-based knowledge hub focused on traditional East Asian products — in particular, items like teaware, incense tools, and artisan crafts.
This isn’t a commercial store, but more like a structured knowledge wiki that catalogs these cultural products with history, usage, and style comparisons. I’m working solo and trying to get the structure right from the beginning, and would love your advice:
1. What’s the best way to create templates for repeating content sections — for example, for each teaware item (like material, origin, traditional use, care instructions)?
2. Is there a way to set up a lightweight “infobox”-like summary for these product entries — similar to Wikipedia’s right-aligned boxes?
3. What extension(s) are best for showing related articles or auto-linking similar categories?
4. Can I semi-automate formatting using templates for future entries?
For example, I’m adapting this article on [Chinese teaware sets]<commercial link removed> into wiki format and want to make sure I’m not doing things inefficiently from the start.
I’ve already checked the Template and Semantic MediaWiki docs, but I’d love to hear real-world advice from others doing similar kinds of structured product-style wikis.
Thanks a lot! — Preceding unsigned comment added by Tiệm Trà Cảm Xúc (talk • contribs) 13:37, 3 August 2025 (UTC)
How to have sections of a template that only appear if the parameter is specified, including static text
MediaWiki 1.42.3, PHP 8.2.26 (cgi-fcgi), ICU 70.1, MySQL 8.0.28-0ubuntu0.20.04.3
I have some commonly used templates for folks. In general, they have sections that are in the format of:
Example: (paramater)
Currently, I have them set to say "Not specified" if folks didn't add something to "example =". Ideally, what I would want (for at least some of them) would be to not only have them be bank if they don't get something fed to them, but to have the whole line, including the text "Example:" just not appear. I was assuming you would do this with an if statement, but I wasn't getting it to work. Can someone show me how I should be doing that for the below template? Let's say, for the "Offices" line.
An example can be seen here: https://antir.sca.wiki/index.php?title=Template:Populace Medwards98020 (talk) 16:44, 6 August 2025 (UTC)
Quiz extension and the linter
The linter finds errors of type "Duplicate ID's" on pages that contain more than one quiz extension (all "quiz0"). Now, I read somewhere Parsoid should solve this, but this obviously does not work (always). There are 17 errors on nl.wikibooks, I also found a number of them on en.wikibooks. Is there a solution or a workaround? - Erik Baas (talk) 00:30, 6 August 2025 (UTC)
- The MediaWiki Support desk is a place where you can ask any questions you have about installing, using or administrating the MediaWiki software. If you have questions about Wikimedia wikis, see https://meta.wikimedia.org/wiki/Tech instead. Malyacko (talk) 07:40, 6 August 2025 (UTC)
- You could have left the question where it was originally posted on Help_talk:Lint_errors/duplicate-ids, it was reaching the right audience.
- I looked into the issue in https://phabricator.wikimedia.org/T272944#11066063 and it's a bug in how Parsoid interacts with the Quiz extension. ABreault (WMF) (talk) 17:11, 6 August 2025 (UTC)
- That page said "Please do not post support questions here." Oh well, thanks anyway. - Erik Baas (talk) 19:51, 6 August 2025 (UTC)
- It looks like the entire Help namespace has that banner. I think maybe it means that if you're looking for support with your own installation of MediaWiki, that isn't the place to ask, as @Malyacko is saying above.
- As for a solution or workaround, I think it needs to solved in the extension or in Parsoid and unfortunately not on your wiki. The extension could generate a random id rather than a sequentially ordered one and it would avoid it. ABreault (WMF) (talk) 21:18, 6 August 2025 (UTC)
- This is not about my "own installation of MediaWiki" but about nl.wikibooks, like I sort-of wrote in my first message.
- How much time will it take before this problem is solved? - Erik Baas (talk) 22:50, 6 August 2025 (UTC)
- Sorry, I was trying to clarify why you saw that banner and why it didn't apply to the question you had.
- I wrote a patch that fixes issue but it's going to take some time to have it reviewed and deployed. I can't give you a precise amount of time. ABreault (WMF) (talk) 00:04, 7 August 2025 (UTC)
- "403 - You don't have permission to access this resource.". - Erik Baas (talk) 15:37, 7 August 2025 (UTC)
- Due to excessive scraping, gerrit was having issues yesterday. But the resource should be public ABreault (WMF) (talk) 15:48, 7 August 2025 (UTC)
- "403 - You don't have permission to access this resource.". - Erik Baas (talk) 15:37, 7 August 2025 (UTC)
I redesigned the mediawiki logo.
I think that the current logo is starting to look a bit dated. It needs to reflect more modern design trends, so I have updated the logo to look more like it's from 2025, and I want to see what the MediaWiki team thinks of this. I hope to see this in MediaWiki version 45 :)
files.catbox.moe/lp0275.svg ~2025-34569-0 (talk) 08:46, 7 August 2025 (UTC)
- @~2025-34569-0: Are you aware that the current logo is only ~5 years old? See Project:Proposal for changing logo of MediaWiki, 2020. Also, your link is not loading for me. Sam Wilson 08:50, 7 August 2025 (UTC)
- That's a great piece of modern art, however it will not work as a small favicon, the font is cut on my machine, and it is based on the ancient MediaWiki logo which MediaWiki has not been using for more than five years now. I think we are quite happy with the current MediaWiki logo. Malyacko (talk) 14:07, 7 August 2025 (UTC)
Resolving Scribunto and MediaWiki Errors
Environment
- Operating System: Windows 11
- Web Server: XAMPP
- MediaWiki Version: 1.43.1 → updated to 1.43.3 LTS
- PHP and MySQL: Default versions bundled with XAMPP
Core Issue
Internal errors occurred when saving regular and module pages, making the wiki unusable.
Step 1: Initial Problem Analysis
- Symptom: Saving pages in the Module namespace caused server non-responsiveness and browser timeouts
- Log: PHP Fatal error: Maximum execution time of 120 seconds exceeded
- Hypothesis: PHP was executing Scribunto’s external Lua process (lua5.1.exe) and timing out while waiting for a response
Step 2: Scribunto and PHP Environment Validation
Hypothesis 1: Lua Executable Issue
- Created luatest.php to run lua5.1.exe via PHP’s proc_open directly
- Result: Success — Lua version printed correctly, confirming PHP can execute external processes
Hypothesis 2: LocalSettings.php Misconfiguration
- Modified luaPath using various formats
- Enabled errorFile to capture command errors
- Result: Log showed malformed command due to redundant quotes (""C:), indicating command construction issues. Simplified path settings did not resolve the issue
Step 3: MediaWiki Core and Dependency Troubleshooting
Symptoms
- Class LuaStandaloneEngine not found
- Class Wikimedia Equivset Equivset not found
Action 1: MediaWiki Update
- Upgraded to 1.43.3 and ran update.php
- Result: No improvement
Action 2: Composer Dependency Reinstallation
- Deleted vendor folder and ran composer install --no-dev
- Result: Installation succeeded, but class loading errors persisted
Action 3: Internal Cache Rebuild
- Ran rebuildLocalisationCache.php --force
- Result: Cache rebuilt, but issue remained
Step 4: Extension Conflicts and Filesystem Investigation
Action 1: Disable AbuseFilter Extension
- Backtrace showed Equivset error originated from AbuseFilter
- Commented out wfLoadExtension( 'AbuseFilter' )
- Result: Regular page saving worked; module saving still failed — indicating separate issues
Action 2: Filesystem Permissions and Path Analysis
- Symptom: proc_open(...): Failed to open stream: Permission denied
- Verified folder permissions — Everyone had full access to C:\xampp\lua, but error persisted
- Moved Lua folder to C:\xampp\htdocs\masaiwiki\extensions\Scribunto
- Result: Same permission error
Action 3: Direct Scribunto Code Modification
- Commented out command construction code near line 132 in LuaStandaloneInterpreter.php
- Observation: Code was already commented (hard limit)
- Tried broader block comments
- Result: No resolution
some Images and pages missing after upgrade to MW 1.33 or later
I wanted to post this in case someone else comes across this problem and hopefully saves themselves hours of troubleshooting. While testing upgrading astromech.net's wiki from 1.23.x to the current version, we found a large number of images and pages went missing with MediaWiki 1.33 or later.
Staring over, I did the following: I jumped from MediaWiki 1.23 to 1.27.7 and everything worked, no missing images, no missing pages. Cool. he next jump we did was to 1.31.16. Again, no missing images or pages, so far so good. The leap to 1.35.13 was not successful and resulted in missing images and pages. Roll back to the snapshot on 1.31.16 and start troubleshooting. It took a bit, but the database schema changes to MediaWiki were part of the headache.
The problem now identified as database schema changes starting with 1.31 and coming live in 1.33. The new fields first appear in MediaWiki 1.31. During the upgrade process, the scripts should populate those fields. Not always the case for all records. I think the true root of the problem was with an older version of the SSO extension for vBulletin, but that is not too important now. The damage was done and I needed to run a few SQL jobs to fix it.
Problem one was the images.
The first change was with images, and the fix was to populate any img_actor field that had a value of zero. I referenced the uploader ID of an image that survived the other upgrade attempts. I ran the below SQL statement and updated the fields in my lab system. After that was completed, I upgraded to 1.35. All of the missing images made it over this time. The method I used gave my ID to all the images as the uploader. My first attempt to use the uploader ID in img_user field failed, as the ID in the img_user field was the problem. Reviewing the logs I found during the upgrade, I got the User name "Anakin Skywalker" is usable, cannot create an anonymous actor for it. Run maintenance/cleanupUsersWithNoId.php to fix this situation. No amount of running that script fixed the problem or running the migrate actors script. So I decided to just go with a known working ID to populate the blank img_actor fields.
SQL Statement UPDATE mw_image SET img_actor = 525 WHERE img_actor = 0;
Problem Two with Articles
The second problem with the articles was similar to the images. It comes down to the rev_user was not migrated to the rev_actor field. Again, it tracked back to the error "the User name "Anakin Skywalker" is usable, cannot create an anonymous actor for it. Run maintenance/cleanupUsersWithNoId.php" So the user name was the problem again.
INSERT INTO mw_revision_actor_temp (revactor_rev, revactor_actor, revactor_timestamp, revactor_page) SELECT r.rev_id, 442, r.rev_timestamp, r.rev_page FROM mw_revision r LEFT JOIN mw_revision_actor_temp t ON r.rev_id = t.revactor_rev WHERE t.revactor_rev IS NULL;
I hope this helps someone down the road with their upgrade. Bryan Droidwiki (talk) 01:00, 6 August 2025 (UTC)
- The cleanupUsersWithNoId.php script doesn't always fix all inconsistencies, causing migration scripts to fail. You can use this version instead, which I modified to take into account some situations that the original script misses. Ciencia Al Poder (talk) 20:55, 6 August 2025 (UTC)
- Thanks I will give this one a try! I was surprised the migrateActors.php did not have a safety option to assign anything with a null value to an admin account. ~2025-35808-6 (talk) 21:39, 8 August 2025 (UTC)
504 Gateway timeout error
When I hit the wiki application url it will ask for authentication and it will be completedafter SSO authentication it will loading the URL for 1 min and throwing the 504 error with Special:PluggableAuthLogin url ~2025-34685-4 (talk) 07:58, 7 August 2025 (UTC)
- Please see "Post a new question" at the top of the page and provide missing information. Malyacko (talk) 14:05, 7 August 2025 (UTC)
- The SAML Single Sign-On (SSO) integration with MediaWiki is encountering issues during the login flow. Although authentication is successful, users are being redirected back to the login page instead of accessing the application.
- Authentication Flow Behavior:
- The login process involves repeated 302 redirects between PluggableAuthLogin and saml2-acs.php.
- SAML authentication initiates correctly, but after login, the user is redirected back to the login page instead of landing on the intended application page. ~2025-34685-4 (talk) 11:50, 8 August 2025 (UTC)
Broken Mediawiki (oops?)
Hello everyone
(sorry I don't have a lot of time left today, sorry for the bad quality of this message).
I was trying to installe my Mediawiki 1.44 on my Debian 12 and a the end of the "wizard" set-up an error ocurred:
Error 1044: Access denied for user 'wikiadmin'@'localhost' to database 'wikiadmin'
Function: MediaWiki\Installer\MysqlDatabaseCreator::createInConnection
Query: CREATE DATABASE IF NOT EXISTS `wikiadmin'
Please help me
Thank you
Kind regards,
I want to write a page about a public figure
اريد كتابة صفحة عن شخصيه عامه خالد عمر يوسف (talk) 02:27, 9 August 2025 (UTC)
Logging in with Firefox
I've noticed that logging in has changed. When I log in on Wikipedia or Wikisource on my computer with Firefox, I'm only logged in to Wikipedia or Wikisource. Before when I logged in, as recently as April, I was logged in to all wiki projects when I logged in with Firefox on my computer (Wikipedia, Wikisource, Wikidata, Wikimedia Commons, etc). No matter if I was in incognito mode or not, the incognito mode is what I use most actually and I believe many users also do. But when I log in with Microsoft Edge, I'm logged in on all wiki projects at the same time. Do you understand what I mean and what has happened and why? More importantly, could the technical team do something so that it's like how it was earlier this year on Firefox? I've already asked about this issue on Wikipedia, but maybe I'll get a good solution here, after all, the members of the technical team are likely to be around here. Grey ghost (talk) 19:56, 3 August 2025 (UTC)
- I received an answer at enwp here. Apparently it's due to SUL, more specifically SUL3. However, there is no solution good enough right now. Is anyone from the technical team reading this, if so, could they fix this? Regardless, I would like someone from the team to reply. Grey ghost (talk) 18:00, 8 August 2025 (UTC)
- Now I posted about the issue on Phabricator, did I do it correctly? Grey ghost (talk) 12:25, 10 August 2025 (UTC)
WAF blocks articles ending on or containing %3F
I am thinking of having my WAF provider create a rule to allow ^/wiki/.*%3F$ or even ^/wiki/.*%3F. Would this introduce any security risks I should be aware of? Or is it safe? Unfortunately I can't white list these kinds of URLs myself individually. DonnyPro (talk) 10:53, 9 August 2025 (UTC)
- WAFs have a tendency to overblock on any sort of former security problem that applications at some point encountered. If you know what services are behind your waf and you know they are not vulnerable to the specific issue, then you can generally safely remove specific rules. I would choose to disable triggered rules, instead of adding additional rules on top that you might not fully understand the impact of. —TheDJ (Not WMF) (talk • contribs) 11:02, 9 August 2025 (UTC)
What content must Template:Reflist have to generate a lower-alpha liststyle?
I have created a MediaWiki wiki on my website (Version 1.44.0). I want the notes to count in lowercase letters instead of numbers. Following the instructions on Help:Cite I have created Mediawiki:Cite_link_label_group-lower-alpha and used the following code to create the notes:
Text of article.<ref group="lower-alpha">Text of footnote.</ref>.
<references group="lower-alpha"/>
But with that code, only the notes in text are lowercase letters, while the footnotes are still numbered:
Bodytext[a]
1. Text of footnote.
As I understand it, I need to use Template:Reflist to get footnotes with lowercase letters and use {{reflist|group=lower-alpha}} to create the footnotes.
I understand that for that I need to create Template:Reflist, but after about half a day of reading the corresponding documentation and other resources on the interent, I still don't understand what the code for that template must look like. Can someone please explain like I'm five in step-by-step instructions what I need to put on that template page, or better yet, provide a code example?
Edit: I have removed the previous replies as they were based on a misunderstanding and might give the impression that my question has already been sufficiently answered. I have also edited the question itself, hopefully making it clearer what my problem is.DWPEV (talk) 04:39, 13 August 2025 (UTC)
How to translate mediawiki magic words to Pashto?
Hi this is Shah Zaman Pathan from pashto wikipedia
MediaWiki Magic words are not translated in Ps wikipedia, they all need to be translated from English to Pashto, how can I translate them to Pashto and where can I find the full list?
Regards شاه زمان پټان (talk) 13:12, 13 August 2025 (UTC)
- There is a list at https://github.com/wikimedia/mediawiki/blob/master/languages/messages/MessagesEn.php#L212 (starting at line 212). Once you have the translations for all the words, file a request at https://phabricator.wikimedia.org listing what the translation for each one should be. (if you have technical knowledge of how git/gerrit works, you can alternatively submit a patch, but if your not familiar with that dont worry).
- For reference, the current translations for Pashto are located at https://github.com/wikimedia/mediawiki/blob/master/languages/messages/MessagesPs.php Bawolff (talk) 22:57, 14 August 2025 (UTC)
- Thank you I will try my best شاه زمان پټان (talk) 02:47, 15 August 2025 (UTC)
Flash
Hello. I am asking to see if there are any extensions that let you play Flash movies using Ruffle either using or like the multimediaviewer extension? There is a lot of community made flash inside a community that would be great if you could display it in the wiki itself instead of relying on another website. It should also be easy to secure it up using Ruffle's configuration options. Thanks. ~2025-38777-5 (talk) 15:43, 14 August 2025 (UTC)
Fresh Install Stuck in Read-Only Mode
I have a localhost environment using Mac’s built-in Apache, and homebrew installed PHP & MariaDB, which were just updated, and may have caused the following problem:
A local installation of MediaWiki started reporting that the database was in read-only mode. I can’t get it out of that state, and even a fresh install of MediaWiki starting from scratch immediately reports the same for its database during initial set up. Other PHP/MariaDB virtual hosts are functioning just fine.
Although the problem is isolated to that one app, I find it hard to believe that a fresh install behaves the same way, but equally hard to believe that a MariaDB issue only affects one app.
Any advice on troubleshooting or correcting the problem so I don't lose ~20 years of notes would be appreciated. Msypes (talk) 16:11, 14 August 2025 (UTC)
- I'd check the mariadb log file. Maybe it detected some sort of db corruption and put the DB in read only mode as a precaution. Bawolff (talk) 21:40, 14 August 2025 (UTC)
- Hey @Msypes, there's currently a known bug with MediaWiki's compatibility with MariaDB 12 (tracked as phab:T401570) - is that the version of MariaDB you're using? Best, —a smart kitten[meow] 11:42, 15 August 2025 (UTC)
- Yes, that must be it. The latest upgrade brought me to 12.0.2
- Thank you! I've been going off my mind for the past two days. I'll continue following that thread, but it looks like I'll have to wait for a newer release of MediaWiki to deal with the underlying change in MariaDB. Msypes (talk) 13:13, 15 August 2025 (UTC)
MariaDB 12 incompatible Mediawiki
The database is currently locked to new entries and other modifications, probably for routine database maintenance, after which it will be back to normal.
The system administrator who locked it offered this explanation: The primary database server is running in read-only mode.
The Gemini AI says MariaDB 12 incompatible Mediawiki, how can I fix it? Tunglinwu (talk) 08:43, 15 August 2025 (UTC)
- Hey @Tunglinwu, if this is the issue I think it is, it's a known issue and is being tracked in phab:T401570. Thanks for the report :) —a smart kitten[meow] 11:35, 15 August 2025 (UTC)
Can upload files, delete files, but cannot view files
Hi, I have been banging my head up against a wall here for the past few hours. I was able to get files to be uploaded and deleted but I am running into the issue where whenever I click on the image it says "Sorry, the file cannot be displayed" and a thumbnail will not display. I have adjusted permissions, I have also made sure that file uploading was enabled on the Localsettings.php and the php.ini. I have tried changing the upload path and directory from /var/www/html/images and /var/www/data/images. I have also tried chmod 755 and 777 but still no luck. I have also made sure $wgUseImageMagick is set to true. I am running this using a docker-compose file. The files I am trying to view are just images. Any assistance would be greatly appreciated.
Mediawiki Versopm: 1.44.0
Example URLs:
/index.php/File:Images.jpg#/media/File:Images.jpg
/index.php/File:Images.jpg Oaktree501 (talk) 16:56, 16 August 2025 (UTC)
- @Oaktree501 "whenever I click on the image" based on the path, I assume you are using Extension:MediaViewer, and it is when you click the thumbnail and the mediaviewer is opening that only THEN the image cannot be shown ??? —TheDJ (Not WMF) (talk • contribs) 11:53, 18 August 2025 (UTC)
- Even the thumbnail wont show up. Like if I go to Special:ListFiles it has all the information of when the file was uploaded, name, size, user, and description but where it would show the thumbnail, it is blank. Clicking on the blank thumbnail results with the error. Also going to the /index.php/File:Images.jpg link, where the image was suppose to be, it isnt there, it just has the name and the rest of the info. Oaktree501 (talk) 23:04, 18 August 2025 (UTC)
Job Queue stuck and runJobs.php throws Type Error
Hi, I'm currently setting up a private MediaWiki installation (Version 1.43.1) and adding pages with the DataTransfer extension (Version 1.7). I had no problems for a while, batch adding about 100-150 pages at once, until a few days ago when I tried to add 350 entries at once and noticed that they were not processing properly. After three days, the job queue was still stuck. All of this were "dtImport" jobs, which I think is a custom job class used by DataTransfer.
I tried to adjust $wgJobRunRate > no result.
I tried to use the maintenance script runJobs.php, but it would not execute and kept throwing a type error (TypeError: flock(): Argument #1 ($stream) must be of type resource, false given). manageJobs.php threw the same error message; showJobs.php executed without problem.
I deactivated all extensions and tried running the scripts again > no result.
In the end, I deleted the jobs from the job table directly, but the problem remains: new jobs will be added and none of them are executed; this does not only impact the DataTransfer extension at this point but any background job and the type of job doesn't seem to make a difference (some are htmlCacheUpdate, some refreshLinks, etc.).
I'm not really tech savvy and mostly cobbling things together from previous discussions and the manual pages. Any help would be appreciated and please let me know, if any of the things I tried to explain are unclear.
Thank you very much in advance! Blabberdiblab (talk) 09:33, 18 August 2025 (UTC)
- @Blabberdiblab: Can you post the stack trace of that error message? See also Manual:How to debug. Sam Wilson 11:22, 18 August 2025 (UTC)
- I have tried to enable the $wgDebugLogFile but I can't get it to write. I don't know why.
- PuTTY gave me a some more info to the error message, but I can't replicate it atm because the server keeps shutting me out when I try to log in. There might be something else going on on the server side of things...
- I will try again and get back with any results. Blabberdiblab (talk) 13:01, 18 August 2025 (UTC)
- Because everything is back to working as it should, I consider this issue resolved. Thank you for your time, I appreciate the help! Blabberdiblab (talk) 07:00, 19 August 2025 (UTC)
- And HOW do you run your job queue ? via cron, manually, backed by the database ? There are a lot of options. —TheDJ (Not WMF) (talk • contribs) 11:51, 18 August 2025 (UTC)
- I tried to run it manually (using PuTTY) with the "php maintenance/run.php runJobs" command. Other scripts are executed when I run them this way, manageJobs.php and runJobs.php are not. Blabberdiblab (talk) 12:54, 18 August 2025 (UTC)
- @Blabberdiblab: When you say it isn't executed, do you mean there's no output at all? It should say at least "Job queue is empty." or some error. Sam Wilson 12:59, 18 August 2025 (UTC)
- It gives me the error message I mentioned above: "TypeError: flock(): Argument #1 ($stream) must be of type resource, false given" Blabberdiblab (talk) 13:02, 18 August 2025 (UTC)
- so my guess… is that flock is trying to lock a temporary file. As that file was not able to be created, the value false was returned and false is of course not a file resource. Which might mean that the location for writing temp files on your php install or mediawiki is not properly configured or not writeable. —TheDJ (Not WMF) (talk • contribs) 19:04, 18 August 2025 (UTC)
- I will try to look into that further, because there seems to be a general problem with writable files (I'm also still trying to get a debug log file set up and can't get it to write). But because my main issue is resolved now (it was something server-side, apparently), everything is working again and the debug file and maintenance scripts are not a high priority now - more of a curiosity thing, whether I can get them to work.
- Thank you for your time! I appreciate the help and the tips for understanding the error message. Blabberdiblab (talk) 06:58, 19 August 2025 (UTC)
- so my guess… is that flock is trying to lock a temporary file. As that file was not able to be created, the value false was returned and false is of course not a file resource. Which might mean that the location for writing temp files on your php install or mediawiki is not properly configured or not writeable. —TheDJ (Not WMF) (talk • contribs) 19:04, 18 August 2025 (UTC)
- It gives me the error message I mentioned above: "TypeError: flock(): Argument #1 ($stream) must be of type resource, false given" Blabberdiblab (talk) 13:02, 18 August 2025 (UTC)
- @Blabberdiblab: When you say it isn't executed, do you mean there's no output at all? It should say at least "Job queue is empty." or some error. Sam Wilson 12:59, 18 August 2025 (UTC)
- I tried to run it manually (using PuTTY) with the "php maintenance/run.php runJobs" command. Other scripts are executed when I run them this way, manageJobs.php and runJobs.php are not. Blabberdiblab (talk) 12:54, 18 August 2025 (UTC)
- RESOLVED
- There was apparently a server-side issue which is now resolved, so things are back to working as they should. I don't know what the actual problem was, but I guess I'm just going to leave it at that. Blabberdiblab (talk) 06:50, 19 August 2025 (UTC)
Xin giúp đỡ!
Tôi mới bắt đầu đến với Wiki.
Và có đăng ký 1 tài khoản để sử dụng. Thì bị khóa ngay sau đó. Tôi thử đăng nhập thì được báo như này
Bạn không được quyền sửa đổi trang này, vì lý do sau:
Tên người dùng hoặc địa chỉ IP của bạn đã bị cấm.
Lệnh cấm được thực hiện bởi Nguyentrongphu. Lý do được đưa ra là Rối.
- Lệnh cấm có hiệu lực từ: 01:49, ngày 22 tháng 1 năm 2025
- Lệnh cấm hết hạn vào: 01:49, ngày 22 tháng 1 năm 2026
- Mục tiêu cấm: 171.247.176.0/20
Bạn có thể liên hệ với Nguyentrongphu hoặc bảo quản viên khác để thảo luận về lệnh cấm.
Địa chỉ IP hiện tại của bạn là 171.247.181.51. Mã số cấm #123984.
Xin hãy cung cấp tất cả các thông tin trên vào thư yêu cầu của bạn.
Xin giúp đỡ
~2025-42331-7 (talk) 09:51, 19 August 2025 (UTC)
AbuseFilter ERROR
I meet this when I update to mw 1.43.3:
MediaWiki\Extension\AbuseFilter\AbuseFilterPermissionManager::canSeeLogDetailsForFilter(): Argument #2 ($privacyLevel) must be of type int, null given, called in /usr/share/nginx/html/wiki/extensions/AbuseFilter/includes/Pager/AbuseLogPager.php on line 196
Backtrace:
from /usr/share/nginx/html/wiki/extensions/AbuseFilter/includes/AbuseFilterPermissionManager.php(201)
#0 /usr/share/nginx/html/wiki/extensions/AbuseFilter/includes/Pager/AbuseLogPager.php(196): MediaWiki\Extension\AbuseFilter\AbuseFilterPermissionManager->canSeeLogDetailsForFilter()
#1 /usr/share/nginx/html/wiki/extensions/AbuseFilter/includes/Pager/AbuseLogPager.php(84): MediaWiki\Extension\AbuseFilter\Pager\AbuseLogPager->doFormatRow()
#2 /usr/share/nginx/html/wiki/includes/pager/ReverseChronologicalPager.php(134): MediaWiki\Extension\AbuseFilter\Pager\AbuseLogPager->formatRow()
#3 /usr/share/nginx/html/wiki/includes/pager/IndexPager.php(601): MediaWiki\Pager\ReverseChronologicalPager->getRow()
#4 /usr/share/nginx/html/wiki/extensions/AbuseFilter/includes/Special/SpecialAbuseLog.php(673): MediaWiki\Pager\IndexPager->getBody()
#5 /usr/share/nginx/html/wiki/extensions/AbuseFilter/includes/Special/SpecialAbuseLog.php(248): MediaWiki\Extension\AbuseFilter\Special\SpecialAbuseLog->showList()
#6 /usr/share/nginx/html/wiki/includes/specialpage/SpecialPage.php(728): MediaWiki\Extension\AbuseFilter\Special\SpecialAbuseLog->execute()
#7 /usr/share/nginx/html/wiki/includes/specialpage/SpecialPageFactory.php(1717): MediaWiki\SpecialPage\SpecialPage->run()
#8 /usr/share/nginx/html/wiki/includes/actions/ActionEntryPoint.php(504): MediaWiki\SpecialPage\SpecialPageFactory->executePath()
#9 /usr/share/nginx/html/wiki/includes/actions/ActionEntryPoint.php(146): MediaWiki\Actions\ActionEntryPoint->performRequest()
#10 /usr/share/nginx/html/wiki/includes/MediaWikiEntryPoint.php(200): MediaWiki\Actions\ActionEntryPoint->execute()
#11 /usr/share/nginx/html/wiki/index.php(58): MediaWiki\MediaWikiEntryPoint->run()
#12 {main}
Reply conflict with frame
Is there any way to make this frame function with this? Keeps saying "The "reply" link cannot be used to reply to this comment. To reply, please use the full page editor by clicking "Edit"... Lofty abyss 01:52, 20 August 2025 (UTC)
- @Lofty abyss At a first glance, this seems like it might potentially be because of Help:DiscussionTools/Why can't I reply to this comment? § Wrapper templates. That section suggests using plain HTML syntax (rather than using a template) to get the reply-tool to work with decorative frames, and - from quickly testing it - that seemed to work for me in this case :) Best, —a smart kitten[meow] 08:19, 21 August 2025 (UTC)
- Thanks, didn't notice there was a section for my situation. Lofty abyss 10:50, 21 August 2025 (UTC)
- @Lofty abyss fyi, your signature isn't readable in dark mode, because you force black text, which isn't readable on a black background. —TheDJ (Not WMF) (talk • contribs) 07:38, 25 August 2025 (UTC)
- Thanks, didn't notice there was a section for my situation. Lofty abyss 10:50, 21 August 2025 (UTC)
Downloading my entire history of contributions
| 1.45.0-wmf.15 (bdbedd1)
23:15, 18 August 2025 |
Hello. I'm interested in creating an XL list of my contributions to Wikipedia since I joined the project in 2003. I know how to do this piecemeal, by getting the latest 500 entries using XTools: Global Contributions, copying them into an XL spreadsheet, and working my way backwards until I get them all. But I've made well over 200,000 edits, so this would be a long and tedious process.
Can I get all of my contributions in this format in one move (or a few moves), rather than 400+ moves? Thanks. -- JackofOz (talk) 22:28, 24 August 2025 (UTC)
Native translation of a page
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)
- 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)
- 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)
Automatic Backup - LocalSettings.php not readable
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)
- 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) (talk • contribs) 09:22, 29 August 2025 (UTC)
- 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)
mean
What do accounts like ~2025-42331-7 mean? Banovercheckcross (talk) 19:45, 30 August 2025 (UTC)
- Help:Temporary accounts. – Ammarpad (talk) 08:16, 31 August 2025 (UTC)
Transclusions not marked or filtered in What Links Here search
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)
Template:MW file and Template:SettingSummary
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)
- Works for me here. Ciencia Al Poder (talk) 14:08, 23 August 2025 (UTC)
- @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..
- Manual:$wgConf
Works - Manual:ReverseArrayIterator.php
Doesn't work
- Manual:$wgConf
- Waddie96 (talk) 03:41, 1 September 2025 (UTC)
- 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)
- @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..
I just updated my wiki to 1.44 but it does not work.
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)
- 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)
- 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)
- https://www.google.com/search?client=safari&rls=en&q=php+suppress+deprecation+warnings&ie=UTF-8&oe=UTF-8 —TheDJ (Not WMF) (talk • contribs) 07:54, 2 September 2025 (UTC)
Reference Formatting Error Redux
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)
- 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,
- you haven't copied Module:Citation/CS1/Suggestions to your site
- the w:Module:Citation Lua-based redirect pointing to Module:Cite (which you don't have anyway) is also missing
- 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)
- @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)
- 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)
- @Tactica: Okay, so I've uploaded JsonConfig and enabled it by adding:
#Enable JsonConfig extensionwfLoadExtension( '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)
- @Tactica: Okay, so I've uploaded JsonConfig and enabled it by adding:
personal api token and DDOS
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)
- Most common way would be to block their user-agents. —TheDJ (Not WMF) (talk • contribs) 13:42, 1 September 2025 (UTC)
- 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)
Something wrong with Extension:Replace Text
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)
Phantom block on user?
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)
Is editing with multiple temporary accounts against the rules of this wiki?
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)
- @~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) (talk • contribs) 19:30, 5 September 2025 (UTC)
What ElasticSearch (or OpenSearch) version should MediaWiki 1.43.3 use?
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)
Suddenly logged out, and unable to log back in
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)
- See Manual:How to debug/Login problems and Manual:Combating spam Malyacko (talk) 11:12, 7 September 2025 (UTC)
Loading CentralAuth extension leads to error: Call to a member function getCanonicalServer() on null
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)
0 /home/gjlxrtap/public_html/mw19/includes/HookContainer/HookContainer.php(160): MediaWiki\Extension\CentralAuth\Hooks\Handlers\PageDisplayHookHandler->onBeforePageDisplay(OutputPage, Skins\Chameleon\Chameleon)
- 1 /home/gjlxrtap/public_html/mw19/includes/HookContainer/HookRunner.php(946): MediaWiki\HookContainer\HookContainer->run(string, array, array)
- 2 /home/gjlxrtap/public_html/mw19/includes/OutputPage.php(2871): MediaWiki\HookContainer\HookRunner->onBeforePageDisplay(OutputPage, Skins\Chameleon\Chameleon)
- 3 /home/gjlxrtap/public_html/mw19/includes/MediaWiki.php(922): OutputPage->output(boolean)
- 4 /home/gjlxrtap/public_html/mw19/includes/MediaWiki.php(562): MediaWiki->main()
- 5 /home/gjlxrtap/public_html/mw19/index.php(50): MediaWiki->run()
- 6 /home/gjlxrtap/public_html/mw19/index.php(46): wfIndexMain()
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)
PCRE failure
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)
[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 Looking in Phabricator, this error has come up because of an "Array to string conversion" issue in newer PHP versions. Note that PHP 8.4 is officially not yet supported by MediaWiki. See a similar problem with similar symptoms in phab:T392086. —TheDJ (Not WMF) (talk • contribs) 08:24, 10 September 2025 (UTC)
My startup failed miserably and it was based on mediawiki software
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)
- 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)
- @~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)
- 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)
Page title with question mark (?) and short URLs
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)
- @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 Are there problems with adding AllowUnsafe3F? Sam Wilson 04:32, 8 September 2025 (UTC)
RewriteRule ^(.*)$ "%{DOCUMENT_ROOT}/index.php?title=$1" "[L,QSA,B,UnsafeAllow3F]"
- 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)
- It seems so. Wikimedia encountered this in phab:T370110 —TheDJ (Not WMF) (talk • contribs) 08:28, 10 September 2025 (UTC)
- 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)
Can not upgrade from versions older than 1.35, please upgrade to that version or later first.
Hi
i have this problem when i try the update from mediawiki-1.27.1 to 1.44.
I run the command 'php .\maintenance\run.php update' but don't work for this reaseon:
PS C:\EasyPHP-Devserver-17\eds-www\mediawiki-1.44.0> php .\maintenance\run.php update
MediaWiki 1.44.0 Updater
Your composer.lock file is up to date with current dependencies!
Going to run database updates for my_wiki2
Depending on the size of your database this may take a while!
Abort with control-c in the next five seconds (skip this countdown with --quick) ...0
Can not upgrade from versions older than 1.35, please upgrade to that version or later first
how is possible?
I run this script becouse at frontend i have this error
'Notice: Uncommitted DB writes (transaction from Wikimedia\Rdbms\Database::beginIfImplied (LCStoreDB::get)) in C:\EasyPHP-Devserver-17\eds-www\mediawiki-1.44.0\includes\libs\rdbms\database\TransactionManager.php on line 545'
thanks Marcotele2 (talk) 09:38, 11 September 2025 (UTC)
- @Marcotele2: You need to upgrade to 1.35 first, and not jump straight to 1.44. So you should download version 1.35 and upgrade to that. And then probably best to step through the LTS versions, i.e. 1.39 before you go to 1.43. Sam Wilson 09:48, 11 September 2025 (UTC)
- i try.
- Thank you so much Marcotele2 (talk) 10:15, 11 September 2025 (UTC)
mediawiki Http error 502
server is down -- Christian 🇫🇷 FR 🚨 (talk) 10:09, 11 September 2025 (UTC)
- @Wladek92: Which server? I assume you don't mean mediawiki.org because you're posting here! :) Sam Wilson 10:12, 11 September 2025 (UTC)
- check the logs - was transitional. Christian 🇫🇷 FR 🚨 (talk) 10:14, 11 September 2025 (UTC)
- You might be meaning this: https://www.wikimediastatus.net/incidents/nxb5knhp37rl Sam Wilson 10:25, 11 September 2025 (UTC)
- I can only say that I was just displaying on Mediawiki
- -> https://www.mediawiki.org/w/index.php?title=Special%3ATranslate&group=page-Structured+Data+Across+Wikimedia%2FImage+Suggestions&action=page&filter=&language=fr
- when i receive the error 502. The page EN displays normally, the FR too. but not the list of items to translate. Same result on Desktop as on tablette . No deconnexion possible. Support desk New topic was proposed but extinguishes after a while due to no possible exchange.
- -- Christian 🇫🇷 FR 🚨 (talk) 10:38, 11 September 2025 (UTC)
- seems to be a consequence of the /incidents/nxb5knhp37rl
- -- Christian 🇫🇷 FR 🚨 (talk) 10:48, 11 September 2025 (UTC)
- That was a topic for Project:Village Pump instead. (Support desk is only about installing, using or administrating the MediaWiki software itself.) Malyacko (talk) 22:00, 12 September 2025 (UTC)
- You might be meaning this: https://www.wikimediastatus.net/incidents/nxb5knhp37rl Sam Wilson 10:25, 11 September 2025 (UTC)
- check the logs - was transitional. Christian 🇫🇷 FR 🚨 (talk) 10:14, 11 September 2025 (UTC)
Hide/remove some pages from search results
I'm using mediawiki 1.43.0, and I would like to hide/remove certain pages from the search results using the default mediawiki search mechanism (no CirrusSearch extension). To do this I have created a new namespace and moved these pages there leaving a redirect behind. This means that these pages do not come out in a default (Main) namespace search as desired. However there are two remaining issues:
- When typing in a search term in the search box, the suggestions appearing still include the additional non-(Main) namespace if it features on the page title. So suggestions are not restricted to the (Main) namespace. Is it possible disable search suggestions altogether? Or is it possible to stop matching page titles?
- The redirects show up in the search results if the title page includes the search term, which means that the pages become accessible via search on the (Main) namespace. Is it possible to remove redirects from the search results?
I fear that the answer to the above questions may be no. Would there be another strategy to achieve the desired result? JPMalhado (talk) 11:28, 10 September 2025 (UTC)
- @JPMalhado: Does $wgNamespacesToBeSearchedDefault do what you want for the first part? Sam Wilson 03:03, 11 September 2025 (UTC)
- Hello. I did not change this setting, so the default is to only search on the (Main) namespace. Indeed the search results match this, but my point 1 is about the pop-up suggestions that come up as you type in the search box. $wgNamespacesToBeSearchedDefault does not seem to have an effect on those. I am tempted to consider this a bug. Where should this issue be reported? JPMalhado (talk) 10:16, 11 September 2025 (UTC)
- @JPMalhado: What skin are you using? Because most use the opensearch API, but Vector-2022 and some others use the REST search API, and there are differences. T246531 suggests there might be an issue also if you're using the TitleKey extension. Sam Wilson 10:43, 11 September 2025 (UTC)
- Thank you for the hint. It does seem to be skin related: problem 1 manifests on the Vector-2022 skin, but not on other skins that I have tried. But I think issue 1 and 2 are related, in the sense that it seems to be the redirects that are bringing up the search suggestions on the alternate namespace. Deleting the redirect, the page no longer shows up in the suggestions.
- Is there a way to remove redirects from search results? JPMalhado (talk) 09:25, 13 September 2025 (UTC)
- @JPMalhado: What skin are you using? Because most use the opensearch API, but Vector-2022 and some others use the REST search API, and there are differences. T246531 suggests there might be an issue also if you're using the TitleKey extension. Sam Wilson 10:43, 11 September 2025 (UTC)
- Hello. I did not change this setting, so the default is to only search on the (Main) namespace. Indeed the search results match this, but my point 1 is about the pop-up suggestions that come up as you type in the search box. $wgNamespacesToBeSearchedDefault does not seem to have an effect on those. I am tempted to consider this a bug. Where should this issue be reported? JPMalhado (talk) 10:16, 11 September 2025 (UTC)
How do you quickly install MediaWiki and its dependencies on a local machine?
It involves:
- Installing the dependencies easily on Windows, similar to using the Homebrew commands on macOS.
- Running it on localhost, for local testing.
This is part of my personal project involving running a "fake Wikipedia" on my Windows computer not to be published publicly. RaptorsFan2019 (talk) 21:26, 17 September 2025 (UTC)
- Have you read Manual:Installing MediaWiki? What parts are you having trouble with? Sam Wilson 00:50, 18 September 2025 (UTC)
- Installing PHP. I was getting dependency conflicts or some other types of errors. The issue applies on Windows. RaptorsFan2019 (talk) 11:44, 18 September 2025 (UTC)
- Usually people quickly install it. :) Please provide exact errors happening after exact steps to reproduce. Malyacko (talk) 17:52, 18 September 2025 (UTC)
- @RaptorsFan2019: The Local_development_quickstart#Install_prerequisites page suggests that Windows users should use Chocolatey, and install PHP with
choco install -y php composerso that might be worth looking into. I'm afraid it's been many years since I worked with MediaWiki on Windows (back then, I was using Xampp, not sure if that's still a thing). Sam Wilson 01:33, 19 September 2025 (UTC)- To fix the missing PHP dependencies, I simply had to edit php.ini to enable them.
- However, now we have another problem:
For reference (in case you want to go there directly), this is located in MediaWiki's mw-config directory (so using the example above you would go to
http://www.example.com/mw-config/, or on a local machinehttp://localhost/mw-config/).- But, I can't figure out how to access the configuration script on localhost! I'm getting the message "Could not find a suitable database driver!" and then the script crashes. RaptorsFan2019 (talk) 22:46, 19 September 2025 (UTC)
- Never mind. RaptorsFan2019 (talk) 23:41, 19 September 2025 (UTC)
- Installing PHP. I was getting dependency conflicts or some other types of errors. The issue applies on Windows. RaptorsFan2019 (talk) 11:44, 18 September 2025 (UTC)
Trying to add a new item
I am trying to add a new item for <redacted>
I am getting the following Error:" This action has been automatically identified as harmful, and therefore disallowed. if you believe your action was constructive, please inform an administrator of what you were trying to do." Specific spam item Ndaxcanada (talk) 17:46, 19 September 2025 (UTC)
Semantic Mediawiki spinning forever and Refresh is disabled
| MediaWiki | 1.39.10 |
| PHP | 7.4.3-4ubuntu2.29 (apache2handler) |
| MySQL | 8.0.42-0ubuntu0.20.04.1 |
| ICU | 66.1 |
| Semantic MediaWiki | 4.2.0 |
I just installed Semantic Mediawiki on my wiki. I have done this multiple times before on different wikis/instances but for some reason my latest installation doesn't appear to work as expected.
I created a few properties and a new test page where I assign a few values. The properties are saved and I can see the page when I browse the Property. The problem is that the Refresh button is disabled/not clickable and when I browse the properties for the test page via Special:Browse it just shows a never ending spinner and says Information is currently being retrieved from the backend..
I ran the following commands but they didn't solve the issue:
php maintenance/update.php
php extensions/SemanticMediaWiki/maintenance/rebuildData.php
php maintenance/runJobs.php
Does someone know what I need to do in order to fix this? Ellex2 (talk) 23:29, 19 September 2025 (UTC)
How to activate a user account with an expired confirmation token? [closed]
A situation I recently encountered (MW 1.39) is this: a user account was created with an automatically generated password. A confirmation token was sent to the user's email address but the recipient did not respond and the token expired. Now the same user wants to claim the user account.
An option which I thought might work is for the unconfirmed user to go to the login page and hit the message saying something like 'Forgot password? Send new password'. But unfortunately, no email was forthcoming. What did work is to create a new account (new name) for the same user, following the same recipe, and the email arrived just fine.
So I guess my question is: how can a user account that was not confirmed in time be (re)activated? Rand(1,2022) (talk) 18:37, 12 September 2025 (UTC)
- A password reset should trigger the confirmation as well… I think. Are you 100% sure the user used the right emailaddress the first time ? I cant count the times where a user accidentally used the wrong domain name ;) —TheDJ (Not WMF) (talk • contribs) 20:15, 12 September 2025 (UTC)
- Good to know that is how MediaWiki is probably supposed to work. As I can't monitor what that user actually did, I went ahead and created an account to see if I can reproduce the situation. Still need to wait a couple of days for the temporary password to expire. Rand(1,2022) (talk) 20:22, 12 September 2025 (UTC)
Update. I have not been able to reproduce the issue this particular user ran into. The passwords for two accounts I created to test things expired after seven days and I was then able to request new passwords, receive the emails and 'activate' both user accounts. Little else one can do. Rand(1,2022) (talk) 20:00, 21 September 2025 (UTC)
Updater fails to update a 1.39 database to 1.44 (solved)
(solved)
Translation Admin
Hi, who can become a translation admin on MediaWiki? Giorgx12 (talk) 14:44, 22 September 2025 (UTC)
- Project:Requests_for_permissions/JJDCT_(2) gives some hints. Tactica (talk) 14:52, 22 September 2025 (UTC)
Phabricator download script
Continuation of Project:Support desk/Archive 22 - MediaWiki.
I've made a Python script (thanks to Gemini) which downloads any folder from Wikimedia Phabricator. I've meant it initially to download the UsabilityInitiative extension and anything from the SVN archive on WMPhab but I've made it so that it can download anything from a Phabricator repo. Enjoy!
https://gist.github.com/HarommelRabbid/2b6dcaaf9a4e3ab91886e23a3b8456a0 Harommel (talk) 17:22, 22 September 2025 (UTC)
- @A smart kitten @Malyacko @Leaderboard Harommel (talk) 17:24, 22 September 2025 (UTC)
- @Harommel Hmm, why would you not use the "subversion" and "git" software to download code repositories? I guess I don't really get the use case. (Also, why does the script fake being a web browser via the user-Agent header instead of being honest about what it is?) Malyacko (talk) 06:57, 23 September 2025 (UTC)
My MediaWiki site will no longer load
I use a MediaWiki site as my personal website and it won't really load anymore. I believe the issue is that it's become so overloaded with spam pages. But even the Special:Nuke extension won't load. Is there a way to deal with this issue without rebuilding my whole site from scratch? Thanks so much. ~2025-65957-3 (talk) 09:49, 19 September 2025 (UTC)
- Or is there perhaps a way I can delete out all of the content but leave the general formatting of the wiki and start from scratch that way? ~2025-65957-3 (talk) 09:52, 19 September 2025 (UTC)
- Which exact MediaWiki version? What makes you think that it does not load? What is the exact error you get in the browser or the console of your browser's developer tools when you try to load it? Malyacko (talk) 10:18, 20 September 2025 (UTC)
- Thanks for responding. Not sure what MediaWiki version I am using. And I am not getting an onscreen error at all. Literally faced with a white screen of nothing.
- Developer tools shows: mikepomranz.com/:1 Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR
- I do apologize. I am not a programmer. I am a complete novice who followed the basic setup instructions to create the website. That's why I have no idea how to troubleshoot this issue. ~2025-65957-3 (talk) 13:20, 20 September 2025 (UTC)
- If the problem is your wiki being overloaded by bots, an emergency measure would be to restrict access to anyone without an account. See Manual:Preventing access#Simple private wiki and disable account creation, so only you can access it and clean the mess, or to Help:Export the pages you want in case you want to start from scratch. Ciencia Al Poder (talk) 14:48, 24 September 2025 (UTC)
Cannot access the database: MySQL server has gone away (localhost)
I'm attempting to create a MediaWiki setup on a subdomain (archives.agropelter.net). I am using version 1.44.0 and installed it through CPanel > Softaculous Apps Installer. Ever since I installed it and enabled $wgShowExceptionDetails, I have been getting the same error (pasted below) no matter what I try. I'm not very knowledgeable about creating websites or how networking functions, but I've tried forcing it to use a socket, using 127.0.0.1 instead of just localhost for $wgDBserver, and more. I have been trying to get it to display anything other than error codes all weekend and it's driving me crazy, the mediawiki installation tutorial I watched showed it working right out of the box with Softaculous. I am using Spaceship (Pro tier) as my hosting solution.
Error message
MediaWiki internal error.
Original exception: [f72efe89500c4b5b9319785b] / Wikimedia\Rdbms\DBConnectionError: Cannot access the database: MySQL server has gone away (localhost)
Backtrace:
from /home/ufoemzfqym/archives.agropelter.net/includes/libs/rdbms/loadbalancer/LoadBalancer.php(1134)
#0 /home/ufoemzfqym/archives.agropelter.net/includes/libs/rdbms/loadbalancer/LoadBalancer.php(803): Wikimedia\Rdbms\LoadBalancer->reportConnectionError()
#1 /home/ufoemzfqym/archives.agropelter.net/includes/libs/rdbms/loadbalancer/LoadBalancer.php(791): Wikimedia\Rdbms\LoadBalancer->getServerConnection()
#2 /home/ufoemzfqym/archives.agropelter.net/includes/libs/rdbms/database/DBConnRef.php(111): Wikimedia\Rdbms\LoadBalancer->getConnectionInternal()
#3 /home/ufoemzfqym/archives.agropelter.net/includes/libs/rdbms/database/DBConnRef.php(125): Wikimedia\Rdbms\DBConnRef->ensureConnection()
#4 /home/ufoemzfqym/archives.agropelter.net/includes/libs/rdbms/database/DBConnRef.php(338): Wikimedia\Rdbms\DBConnRef->__call()
#5 /home/ufoemzfqym/archives.agropelter.net/includes/libs/rdbms/querybuilder/SelectQueryBuilder.php(780): Wikimedia\Rdbms\DBConnRef->selectField()
#6 /home/ufoemzfqym/archives.agropelter.net/includes/language/LCStoreDB.php(65): Wikimedia\Rdbms\SelectQueryBuilder->fetchField()
#7 /home/ufoemzfqym/archives.agropelter.net/includes/language/LocalisationCache.php(567): LCStoreDB->get()
#8 /home/ufoemzfqym/archives.agropelter.net/includes/language/LocalisationCache.php(613): LocalisationCache->isExpired()
#9 /home/ufoemzfqym/archives.agropelter.net/includes/language/LocalisationCache.php(524): LocalisationCache->initLanguage()
#10 /home/ufoemzfqym/archives.agropelter.net/includes/language/LocalisationCache.php(404): LocalisationCache->loadSubitem()
#11 /home/ufoemzfqym/archives.agropelter.net/includes/language/LocalisationCache.php(420): LocalisationCache->getSubitem()
#12 /home/ufoemzfqym/archives.agropelter.net/includes/language/MessageCache.php(1206): LocalisationCache->getSubitemWithSource()
#13 /home/ufoemzfqym/archives.agropelter.net/includes/language/MessageCache.php(1146): MessageCache->getMessageForLang()
#14 /home/ufoemzfqym/archives.agropelter.net/includes/language/MessageCache.php(1042): MessageCache->getMessageFromFallbackChain()
#15 /home/ufoemzfqym/archives.agropelter.net/includes/language/Message/Message.php(1545): MessageCache->get()
#16 /home/ufoemzfqym/archives.agropelter.net/includes/language/Message/Message.php(1059): MediaWiki\Message\Message->fetchMessage()
#17 /home/ufoemzfqym/archives.agropelter.net/includes/language/Message/Message.php(1151): MediaWiki\Message\Message->format()
#18 /home/ufoemzfqym/archives.agropelter.net/includes/title/MalformedTitleException.php(61): MediaWiki\Message\Message->text()
#19 /home/ufoemzfqym/archives.agropelter.net/includes/title/TitleParser.php(85): MediaWiki\Title\MalformedTitleException->__construct()
#20 /home/ufoemzfqym/archives.agropelter.net/includes/title/TitleParser.php(231): MediaWiki\Title\TitleParser::MediaWiki\Title\{closure}()
#21 /home/ufoemzfqym/archives.agropelter.net/includes/title/Title.php(2748): MediaWiki\Title\TitleParser->splitTitleString()
#22 /home/ufoemzfqym/archives.agropelter.net/includes/title/Title.php(507): MediaWiki\Title\Title->secureAndSplit()
#23 /home/ufoemzfqym/archives.agropelter.net/includes/actions/ActionEntryPoint.php(238): MediaWiki\Title\Title::newFromURL()
#24 /home/ufoemzfqym/archives.agropelter.net/includes/actions/ActionEntryPoint.php(327): MediaWiki\Actions\ActionEntryPoint->parseTitle()
#25 /home/ufoemzfqym/archives.agropelter.net/includes/actions/ActionEntryPoint.php(91): MediaWiki\Actions\ActionEntryPoint->getTitle()
#26 /home/ufoemzfqym/archives.agropelter.net/includes/MediaWikiEntryPoint.php(202): MediaWiki\Actions\ActionEntryPoint->execute()
#27 /home/ufoemzfqym/archives.agropelter.net/index.php(58): MediaWiki\MediaWikiEntryPoint->run()
#28 {main}
Exception caught inside exception handler: [f72efe89500c4b5b9319785b] / Wikimedia\Rdbms\DBConnectionError: Cannot access the database: MySQL server has gone away (localhost)
Backtrace:
from /home/ufoemzfqym/archives.agropelter.net/includes/libs/rdbms/loadbalancer/LoadBalancer.php(1134)
#0 /home/ufoemzfqym/archives.agropelter.net/includes/libs/rdbms/loadbalancer/LoadBalancer.php(803): Wikimedia\Rdbms\LoadBalancer->reportConnectionError()
#1 /home/ufoemzfqym/archives.agropelter.net/includes/libs/rdbms/loadbalancer/LoadBalancer.php(791): Wikimedia\Rdbms\LoadBalancer->getServerConnection()
#2 /home/ufoemzfqym/archives.agropelter.net/includes/libs/rdbms/database/DBConnRef.php(111): Wikimedia\Rdbms\LoadBalancer->getConnectionInternal()
#3 /home/ufoemzfqym/archives.agropelter.net/includes/libs/rdbms/database/DBConnRef.php(125): Wikimedia\Rdbms\DBConnRef->ensureConnection()
#4 /home/ufoemzfqym/archives.agropelter.net/includes/libs/rdbms/database/DBConnRef.php(338): Wikimedia\Rdbms\DBConnRef->__call()
#5 /home/ufoemzfqym/archives.agropelter.net/includes/libs/rdbms/querybuilder/SelectQueryBuilder.php(780): Wikimedia\Rdbms\DBConnRef->selectField()
#6 /home/ufoemzfqym/archives.agropelter.net/includes/language/LCStoreDB.php(65): Wikimedia\Rdbms\SelectQueryBuilder->fetchField()
#7 /home/ufoemzfqym/archives.agropelter.net/includes/language/LocalisationCache.php(540): LCStoreDB->get()
#8 /home/ufoemzfqym/archives.agropelter.net/includes/language/LocalisationCache.php(404): LocalisationCache->loadSubitem()
#9 /home/ufoemzfqym/archives.agropelter.net/includes/language/LocalisationCache.php(420): LocalisationCache->getSubitem()
#10 /home/ufoemzfqym/archives.agropelter.net/includes/language/MessageCache.php(1206): LocalisationCache->getSubitemWithSource()
#11 /home/ufoemzfqym/archives.agropelter.net/includes/language/MessageCache.php(1146): MessageCache->getMessageForLang()
#12 /home/ufoemzfqym/archives.agropelter.net/includes/language/MessageCache.php(1042): MessageCache->getMessageFromFallbackChain()
#13 /home/ufoemzfqym/archives.agropelter.net/includes/language/Message/Message.php(1545): MessageCache->get()
#14 /home/ufoemzfqym/archives.agropelter.net/includes/language/Message/Message.php(1059): MediaWiki\Message\Message->fetchMessage()
#15 /home/ufoemzfqym/archives.agropelter.net/includes/language/Message/Message.php(1151): MediaWiki\Message\Message->format()
#16 /home/ufoemzfqym/archives.agropelter.net/includes/exception/MWExceptionRenderer.php(262): MediaWiki\Message\Message->text()
#17 /home/ufoemzfqym/archives.agropelter.net/includes/exception/MWExceptionRenderer.php(409): MediaWiki\Exception\MWExceptionRenderer::msg()
#18 /home/ufoemzfqym/archives.agropelter.net/includes/exception/MWExceptionRenderer.php(114): MediaWiki\Exception\MWExceptionRenderer::reportOutageHTML()
#19 /home/ufoemzfqym/archives.agropelter.net/includes/exception/MWExceptionHandler.php(137): MediaWiki\Exception\MWExceptionRenderer::output()
#20 /home/ufoemzfqym/archives.agropelter.net/includes/exception/MWExceptionHandler.php(241): MediaWiki\Exception\MWExceptionHandler::report()
#21 /home/ufoemzfqym/archives.agropelter.net/includes/MediaWikiEntryPoint.php(222): MediaWiki\Exception\MWExceptionHandler::handleException()
#22 /home/ufoemzfqym/archives.agropelter.net/includes/actions/ActionEntryPoint.php(79): MediaWiki\MediaWikiEntryPoint->handleTopLevelError()
#23 /home/ufoemzfqym/archives.agropelter.net/includes/MediaWikiEntryPoint.php(208): MediaWiki\Actions\ActionEntryPoint->handleTopLevelError()
#24 /home/ufoemzfqym/archives.agropelter.net/index.php(58): MediaWiki\MediaWikiEntryPoint->run()
#25 {main} Logthrower49 (talk) 03:56, 15 September 2025 (UTC)
- @Logthrower49 You need to fix database access, basically. If you don't host that domain yourself, please ask your hoster to provide you with the required information. Also note that we have no influence which kind of software "Softaculous Apps Installer" provides to you. Malyacko (talk) 11:32, 16 September 2025 (UTC)
- Your localization cache is using the database it seems. It might be that the initial update of the localization cache is taking too long to finish and that the connection is terminated before updating of the localization cache is completed.
- Also please be aware that hosting a website requires some knowledge of how to host a website. Websites are not apps that you install, they have a lot of aspects to them that require knowledge about what you are doing. —TheDJ (Not WMF) (talk • contribs) 18:14, 16 September 2025 (UTC)
- If anyone else has this issue, I was clicking "enable SSL" in the Softaculous install menu, and Spaceship doesn't support SSL connection to mySQL. All you have to do is change $wgDBssl from true to false in localsettings.php. Logthrower49 (talk) 02:16, 20 September 2025 (UTC)
- Thank you, Logthrower49. This was the answer for me. Changed $wgDBssl from true to false in localsettings.php for Inmotion hosted mediawiki and finally up and running. ~2025-26595-35 (talk) 22:51, 26 September 2025 (UTC)
Can I make multiple languages for my wiki?
I have a Miraheze Wiki, and can I add multiple languages to it? DanaroEnEuskara (talk) 05:10, 23 September 2025 (UTC)
- @DanaroEnEuskara While Miraheze runs MediaWiki, MediaWiki does not provide support for Miraheze. —TheDJ (Not WMF) (talk • contribs) 11:39, 29 September 2025 (UTC)
Server Error
404-file or directory not found Ramdasbhil (talk) 12:25, 27 September 2025 (UTC)
- You are going to have to provide much more detailed information than this if you want a useful answer. This is like asking a car mechanic why your home has hole in it. —TheDJ (Not WMF) (talk • contribs) 11:32, 29 September 2025 (UTC)
Moment.js Out-Of-Date High Vulnerability MW 1.43
An Invicti scan has flagged our MW 1.43.3 installation with a High vulnerability: "Out-of-date Version (Moment.js) ... Moment.js Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') ... This problem is patched in 2.29.2". MW 1.43.3 currently comes with momen.js v2.25.2.
I see MW 1.44 has had moment.js upgraded to v2.30.1 (Phabricator T389416). Are there plans to upgrade moment.js in MW 1.43?
Molsen7970 (talk) 18:15, 25 September 2025 (UTC)
- @Molsen7970 You forgot to mention the exact vulnerability, but based on the version I suspect this is CVE-2022-24785 ? If you read the report, that is a serverside vulnerability. MediaWiki uses it clientside, so then you shouldn't be affected. "Are there plans to upgrade moment.js in MW 1.43" based on that very cursory analysis, probably not. If the issue actually affected MediaWiki, it would have already been upgraded. —TheDJ (Not WMF) (talk • contribs) 11:38, 29 September 2025 (UTC)
- @TheDJ Yes, I forgot to mention the vulnerability CVE number. You are correct, we are looking into CVE-2022-24785. I see now that the vulnerability mentions "impacts npm (server) users". https://nvd.nist.gov/vuln/detail/CVE-2022-24785 Thank you for pointing that out!
- On an unrelated note, I am not able to login to mediawiki.org today:
- https://auth.wikimedia.org/mediawikiwiki/w/index.php?title=Special:UserLogin
- Username: Molsen7970
- [8fd7d830-ff05-4a5c-88df-e971305f3c9a] 2025-09-30 20:59:49: Fatal exception of type "Error" ~2025-27254-58 (talk) 21:01, 30 September 2025 (UTC)
- Thank you for reporting back. It seems you fell victim to a bug in one of the A/B experiments. I have filed phab:T406104. —TheDJ (Not WMF) (talk • contribs) 08:52, 1 October 2025 (UTC)
Url blocks remove
Any and all url blocks can we remove them from my server?
~2025-27192-50 (talk) 17:23, 30 September 2025 (UTC)
504 Gateway Timeout After Authentication – MediaWiki 1.34.4 with PluggableAuth + SimpleSAMLphp
We are currently facing an issue with our MediaWiki instance and would appreciate your assistance in diagnosing and resolving it.
Issue Summary :
After completing the SAML authentication process, the application redirects to:
This URL loads for about a minute and then results in a 504 Gateway Timeout error. The final redirected URL when the error occurs is:
System Information :
MediaWiki Version: 1.34.4 (ff6464d)
PHP: 7.4.33 (fpm-fcgi)
MySQL: 8.0.35
ICU: 74.2
Elasticsearch: 6.8.23
LuaSandbox: 4.1.2
Lua: 5.1.5
Authentication Configuration :
We are using the following extensions for authentication:
PluggableAuth
SimpleSAMLphp
This issue started recently and prevents users from logging in via SAML. We have verified that our IdP is reachable and functional independently. ~2025-34685-4 (talk) 12:05, 1 October 2025 (UTC)
After upgrade from a version pre-1.33 to 1.33.0 or newer, about 10% of images are not linked on pages [SOLVED]
After upgrading and safely migrating the files, some percentage of images is not linked - but the image files are present for sure.
How to fix "missing images after upgrade from medaiwiki versions pre-1.33.0" Here is my solution (a long way to find that).
Check the database for images without "actor"
mysql/mariadb
SHOW TABLES LIKE 'actor';
SHOW CREATE TABLE actor\G
DESCRIBE image\G
SELECT COUNT(*) FROM actor;
SELECT actor_id,actor_name FROM actor WHERE actor_name = '' LIMIT 20;
SELECT COUNT(*) FROM image WHERE img_actor IS NULL OR img_actor=0;
+----------------------+
| images_with_no_actor |
+----------------------+
| 55 |
+----------------------+
1 row in set (0,000 sec)
If you see this, then run
-- 1️⃣ Add a new actor "Unknown"
INSERT INTO actor (actor_name) VALUES ('Unknown');
-- 2️⃣ Get the id of the new actor
SET @unknown_id = LAST_INSERT_ID();
-- 3️⃣ Delete empty actor entries if any
DELETE FROM actor WHERE actor_name = '';
-- 4️⃣ Assign all images without an actor to the new actor "Unknown"
UPDATE image SET img_actor = @unknown_id WHERE img_actor IS NULL OR img_actor = 0;
-- 5️⃣ Optional: check that all images have an actor assigned
SELECT img_name, img_actor FROM image WHERE img_actor = @unknown_id;
SELECT COUNT(*) AS images_still_missing_actor FROM image WHERE img_actor IS NULL OR img_actor=0;
Then run
php maintenance/cleanupUsersWithNoId.php
php maintenance/migrateActors.php --force
php maintenance/migrateComments.php
php maintenance/populateContentTables.php
php maintenance/run.php rebuildImages --missing
- @TheDJ: This isn't the first time this problem has been reported here and it should be documented somewhere in the docs as a pitfall to bear in mind while users upgrade from an old MW version, along with the recommended procedure to solve it. I'm assuming it has been fixed in the current version. --Tactica (talk) 12:40, 3 October 2025 (UTC)
- I even think, my procedure steps should become part of the updater. Unfortunately, as I did not contribute for a while to the code, I feel incompetent to present a proper fix in Phabricator or gerrit, but the steps are documented above.
- As I still have the old database dump, I volunteer to test an improved update code which can also fix this old issue. Wikinaut (talk) 14:26, 3 October 2025 (UTC)
- Other, older reports are:
MediaWiki extensions - Unable to fetch extension list!
Page Special:ExtensionDistributor is broken - "Unable to fetch extension list!" MidnightLG (talk) 12:26, 4 October 2025 (UTC)
UPD: resolved, works now
IP Address Blocked
Even after confirming the email address. IP address has been blocked and their is no public policy around this. ~2025-27046-71 (talk) 03:58, 29 September 2025 (UTC)
- Are you using safari on mac? If so in safari you need to go to 'view' and then 'reload and show ip address' Leeshore1966 (talk) 07:55, 7 October 2025 (UTC)
Patching 1.44.0 to 1.44.1 process on dry run stops at "can't find file to patch at input line 17149"
Used patch -p1 --dry-run -i mediawiki-1.44.1.patch
Patching 1.44.0 to 1.44.1 dry run stops at this place:
checking file extensions/DiscussionTools/tests/cases/double-signature2/double-signature2-formatted-desktop.html
checking file extensions/DiscussionTools/tests/cases/double-signature2/double-signature2-formatted-legacy.html
checking file extensions/DiscussionTools/tests/cases/double-signature2/double-signature2-formatted-mobile.html
can't find file to patch at input line 17149
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -Nru mediawiki-1.44.0/extensions/DiscussionTools/tests/cases/en-big-oldparser/en-big-oldparser-formatted-desktop.html mediawiki-1.44.1/extensions/DiscussionTools/tests/cases/en-big-oldparser/en-big-oldparser-formatted-desktop.html |--- mediawiki-1.44.0/extensions/DiscussionTools/tests/cases/en-big-oldparser/en-big-oldparser-formatted-desktop.html2024-12-05 15:51:04.847191600 +0000 |+++ mediawiki-1.44.1/extensions/DiscussionTools/tests/cases/en-big-oldparser/en-big-oldparser-formatted-desktop.html2025-10-02 12:16:30.322104000 +0100
File to patch: Leeshore1966 (talk) 20:09, 2 October 2025 (UTC)
- Tag 1.44.1 removed, use 1.44.2 instead. MidnightLG (talk) 12:30, 4 October 2025 (UTC)
- The only thing is the 1.44.2 patch is much smaller than the 1.44.1 patch. Does that mean it will miss some of the upgrade in 1.44.1 if I only apply the 1.44.2 patch? Leeshore1966 (talk) 10:02, 5 October 2025 (UTC)
- No idea. I didn't use patches but docker containers. Probably you're right MidnightLG (talk) 11:18, 5 October 2025 (UTC)
- Still not sure how to complete this patch without having to just reinstall Leeshore1966 (talk) 07:41, 9 October 2025 (UTC)
- No idea. I didn't use patches but docker containers. Probably you're right MidnightLG (talk) 11:18, 5 October 2025 (UTC)
- The only thing is the 1.44.2 patch is much smaller than the 1.44.1 patch. Does that mean it will miss some of the upgrade in 1.44.1 if I only apply the 1.44.2 patch? Leeshore1966 (talk) 10:02, 5 October 2025 (UTC)
$wgMainCacheType = CACHE_ACCEL; (i.e. APCU) causes PHP error on MW 1.43.3
I've upgraded my MediaWiki from 1.42.6 to 1.43.3 (LTS), then I got this error:
[89b7981d01fd3cdada982ae7] /wiki/%E9%A6%96%E9%A1%B5 Error: Typed property MediaWiki\Language\ReplacementArray::$data must not be accessed before initialization
Backtrace:
from /srv/wiki.gslin.org/public/includes/libs/ReplacementArray.php(104)
#0 /srv/wiki.gslin.org/public/includes/language/LanguageConverter.php(623): MediaWiki\Language\ReplacementArray->replace()
#1 /srv/wiki.gslin.org/public/includes/language/LanguageConverter.php(602): MediaWiki\Language\LanguageConverter->translate()
#2 /srv/wiki.gslin.org/public/includes/language/LanguageConverter.php(829): MediaWiki\Language\LanguageConverter->autoConvert()
#3 /srv/wiki.gslin.org/public/includes/language/LanguageConverter.php(584): MediaWiki\Language\LanguageConverter->recursiveConvertTopLevel()
#4 /srv/wiki.gslin.org/public/includes/language/LanguageConverter.php(829): MediaWiki\Language\LanguageConverter->autoConvert()
#5 /srv/wiki.gslin.org/public/includes/language/LanguageConverter.php(793): MediaWiki\Language\LanguageConverter->recursiveConvertTopLevel()
#6 /srv/wiki.gslin.org/public/includes/language/LanguageConverter.php(781): MediaWiki\Language\LanguageConverter->convertTo()
#7 /srv/wiki.gslin.org/public/includes/parser/Parser.php(1719): MediaWiki\Language\LanguageConverter->convert()
#8 /srv/wiki.gslin.org/public/includes/parser/Parser.php(704): MediaWiki\Parser\Parser->internalParseHalfParsed()
#9 /srv/wiki.gslin.org/public/includes/content/WikitextContentHandler.php(384): MediaWiki\Parser\Parser->parse()
#10 /srv/wiki.gslin.org/public/includes/content/ContentHandler.php(1691): MediaWiki\Content\WikitextContentHandler->fillParserOutput()
#11 /srv/wiki.gslin.org/public/includes/content/Renderer/ContentRenderer.php(79): MediaWiki\Content\ContentHandler->getParserOutput()
#12 /srv/wiki.gslin.org/public/includes/Revision/RenderedRevision.php(263): MediaWiki\Content\Renderer\ContentRenderer->getParserOutput()
#13 /srv/wiki.gslin.org/public/includes/Revision/RenderedRevision.php(236): MediaWiki\Revision\RenderedRevision->getSlotParserOutputUncached()
#14 /srv/wiki.gslin.org/public/includes/Revision/RevisionRenderer.php(239): MediaWiki\Revision\RenderedRevision->getSlotParserOutput()
#15 /srv/wiki.gslin.org/public/includes/Revision/RevisionRenderer.php(172): MediaWiki\Revision\RevisionRenderer->combineSlotOutput()
#16 [internal function]: MediaWiki\Revision\RevisionRenderer->{closure:MediaWiki\Revision\RevisionRenderer::getRenderedRevision():170}()
#17 /srv/wiki.gslin.org/public/includes/Revision/RenderedRevision.php(199): call_user_func()
#18 /srv/wiki.gslin.org/public/includes/poolcounter/PoolWorkArticleView.php(106): MediaWiki\Revision\RenderedRevision->getRevisionParserOutput()
#19 /srv/wiki.gslin.org/public/includes/poolcounter/PoolWorkArticleViewCurrent.php(123): MediaWiki\PoolCounter\PoolWorkArticleView->renderRevision()
#20 /srv/wiki.gslin.org/public/includes/poolcounter/PoolCounterWork.php(171): MediaWiki\PoolCounter\PoolWorkArticleViewCurrent->doWork()
#21 /srv/wiki.gslin.org/public/includes/page/ParserOutputAccess.php(362): MediaWiki\PoolCounter\PoolCounterWork->execute()
#22 /srv/wiki.gslin.org/public/includes/page/Article.php(827): MediaWiki\Page\ParserOutputAccess->getParserOutput()
#23 /srv/wiki.gslin.org/public/includes/page/Article.php(547): Article->generateContentOutput()
#24 /srv/wiki.gslin.org/public/includes/actions/ViewAction.php(78): Article->view()
#25 /srv/wiki.gslin.org/public/includes/actions/ActionEntryPoint.php(733): ViewAction->show()
#26 /srv/wiki.gslin.org/public/includes/actions/ActionEntryPoint.php(510): MediaWiki\Actions\ActionEntryPoint->performAction()
#27 /srv/wiki.gslin.org/public/includes/actions/ActionEntryPoint.php(146): MediaWiki\Actions\ActionEntryPoint->performRequest()
#28 /srv/wiki.gslin.org/public/includes/MediaWikiEntryPoint.php(200): MediaWiki\Actions\ActionEntryPoint->execute()
#29 /srv/wiki.gslin.org/public/index.php(58): MediaWiki\MediaWikiEntryPoint->run()
#30 {main}
After enabled debug log (from https://www.mediawiki.org/wiki/Project:Support_desk):
$wgShowExceptionDetails = true;error_reporting( -1 );ini_set( 'display_errors', 1 );
I've seen it's related to apcu:
Deprecated: Creation of dynamic property MediaWiki\Language\ReplacementArray::$data is deprecated in /srv/wiki.gslin.org/public/includes/libs/objectcache/APCUBagOStuff.php on line 70 Deprecated: Creation of dynamic property MediaWiki\Language\ReplacementArray::$data is deprecated in /srv/wiki.gslin.org/public/includes/libs/objectcache/APCUBagOStuff.php on line 70 Deprecated: Creation of dynamic property MediaWiki\Language\ReplacementArray::$data is deprecated in /srv/wiki.gslin.org/public/includes/libs/objectcache/APCUBagOStuff.php on line 70 Deprecated: Creation of dynamic property MediaWiki\Language\ReplacementArray::$data is deprecated in /srv/wiki.gslin.org/public/includes/libs/objectcache/APCUBagOStuff.php on line 70 Deprecated: Creation of dynamic property MediaWiki\Language\ReplacementArray::$data is deprecated in /srv/wiki.gslin.org/public/includes/libs/objectcache/APCUBagOStuff.php on line 70 Deprecated: Creation of dynamic property MediaWiki\Language\ReplacementArray::$data is deprecated in /srv/wiki.gslin.org/public/includes/libs/objectcache/APCUBagOStuff.php on line 70 Deprecated: Creation of dynamic property MediaWiki\Language\ReplacementArray::$data is deprecated in /srv/wiki.gslin.org/public/includes/libs/objectcache/APCUBagOStuff.php on line 70 Deprecated: Creation of dynamic property MediaWiki\Language\ReplacementArray::$data is deprecated in /srv/wiki.gslin.org/public/includes/libs/objectcache/APCUBagOStuff.php on line 70 Deprecated: Creation of dynamic property MediaWiki\Language\ReplacementArray::$data is deprecated in /srv/wiki.gslin.org/public/includes/libs/objectcache/APCUBagOStuff.php on line 70
So I disabled all cache settings (enabled originally), and the site is back to normal:
#$wgMainCacheType = CACHE_ACCEL;
#$wgParserCacheType = 'apcu';
#$wgMessageCacheType = 'apcu';
#$wgSessionsInObjectCache = true;
#$wgSessionCacheType = 'apcu';
#$wgEnableSidebarCache = true;
Not sure if it's a bug or something required to adjust after the update. Gslin (talk) 17:49, 27 September 2025 (UTC)
- The system is running on Debian (testing) with PHP 8.4.11:
:PHP 8.4.11 (cli) (built: Aug 15 2025 23:34:18) (NTS) :Copyright (c) The PHP Group :Built by Debian :Zend Engine v4.4.11, Copyright (c) Zend Technologies : with Zend OPcache v8.4.11, Copyright (c), by Zend Technologies :
Gslin (talk) 17:51, 27 September 2025 (UTC)
- I wouldn't be surprised if MW 1.43 isn't yet officially compatible with PHP 8.4.11. Maybe try and go back to PHP 8.3? Rand(1,2022) (talk) 21:20, 27 September 2025 (UTC)
- Indeed, while most of MediaWiki should be 8.4 compatible, there might be certain configurations and especially certain extensions that will not be compatible. I have filed this as phab:T405901. when issues like this get fixed, they generally get backported to the LTS releases. —TheDJ (Not WMF) (talk • contribs) 11:30, 29 September 2025 (UTC)
- The problem seems to be that APCU does not support namespace aliases, which is a bug in PHP. The solution is to ensure a restart of PHP (and thus the APCU cache) after the upgrade. —TheDJ (Not WMF) (talk • contribs) 07:42, 10 October 2025 (UTC)
- @Gslin forgot to ping you. —TheDJ (Not WMF) (talk • contribs) 07:43, 10 October 2025 (UTC)
- I wouldn't be surprised if MW 1.43 isn't yet officially compatible with PHP 8.4.11. Maybe try and go back to PHP 8.3? Rand(1,2022) (talk) 21:20, 27 September 2025 (UTC)
how to mass-edit links on my wiki
I've inherited a wiki, and I've (successfully, it appears) moved it to a newer machine and upgraded it to a recent version of MediaWiki. Next, I need to edit a bunch (probably more than 100, less than 1000) of pages with a bunch of external links. The edits that need to be made fit a very simple search-replace pattern. I'm proficient in SQL, but unfamiliar with the MediaWiki database layout. I've done some programming in languages like C/Python.
Are there tools/utilities for this sort of task? Any recommended reading? Bsammon (talk) 21:13, 8 October 2025 (UTC)
- You can do that with Extension:ReplaceText. Jonathan3 (talk) 21:48, 8 October 2025 (UTC)
Remote-Branch REL1_43 nicht im Upstream-Repository origin gefunden
Dear ∀,
I am trying to install mediawiki 1.43 via git following https://w.wiki/FdKg
I managed to clone the branch with
sudo -H -u www-data mkdir REL1_43 cd REL1_43 sudo -H -u www-data bash -c 'git clone https://gerrit.wikimedia.org/r/mediawiki/core.git --branch REL1_43 .' sudo -H -u www-data bash -c 'git submodule update --init --recursive' sudo -H -u www-data bash -c 'composer update --no-dev'
Things went offrail when I tried to get all extensions.
Maybe the extensions deliverd by the initial cloning allready delivered all available extensions, but I doubt this. I counted 33 EXTs and I was missing e.g. Extension:CiteThisPage, that according to Extension:CiteThisPage#Installation should be available. https://w.wiki/FdKg is not explicit about this.
So I continued with
cd extensions sudo -H -u www-data bash -c 'git clone https://gerrit.wikimedia.org/r/mediawiki/extensions --branch REL1_43 .'
which returned
fatal: Zielpfad '.' existiert bereits und ist kein leeres Verzeichnis.
I dared
rm -r extensions sudo -H -u www-data mkdir extensions cd extensions sudo -H -u www-data bash -c 'git clone https://gerrit.wikimedia.org/r/mediawiki/extensions --branch REL1_43 .'
But this returned
Klone nach '.' … fatal: Remote-Branch REL1_43 nicht im Upstream-Repository origin gefunden
Please, can you halp me, especially with the following information:
- Does git clone https://gerrit.wikimedia.org/r/mediawiki/core.git deliver the same extensions as https://gerrit.wikimedia.org/r/mediawiki/extensions?
- Does --branch REL1_43 work for the core but not for the extensions? Or is the problem somewhere else?
- When I decide to manage the extensions separately via their own git commands, will git clone https://gerrit.wikimedia.org/r/mediawiki/core.git override this?
Thank you in advance – Ciciban (talk) 15:13, 10 October 2025 (UTC)
- git clone https://gerrit.wikimedia.org/r/mediawiki/extensions works. My conclusion is, that the command git clone https://gerrit.wikimedia.org/r/mediawiki/extensions --branch REL1_44 does not function. This may be a bug or a feature. In the latter case Download_from_Git#Download_all_extensions should be updated. – Ciciban (talk) 20:01, 10 October 2025 (UTC)
- I'd say that cloning all and any extensions available in Wikimedia Gerrit is a pretty uncommon use case. I'd only recommend that if you desperately need to fill your empty disk space. What's the idea behind that, instead of installing functionality that you are interested in? Malyacko (talk) 20:43, 10 October 2025 (UTC)
switching off "suspicious device" procedure
Hello,
sorry if this question has already been answered, I tried to browse this and other pages, but found it so mind-boggling and complex that I gave up and decided to fire a question here.
Today I tried to log into my usual Wikipedia account from a new place, new device, and got prompted for a code, sent to my e-mail account, reportedly because the system identified this login attempt as "suspicious". Is there a way to switch off this thing, so that my password remains my one and only line of defence, without any extras, codes, e-mails, sms etc?
thanks and regards, Dd1495 Dd1495 (talk) 07:22, 7 October 2025 (UTC)
- @Dd1495 "new device" in that case it is doing exactly what it is supposed to do. You used a new device, from a 'suspicious' IP range (range that is the origin of a lot of account hacking attempts). As long as you have cookies enabled, it should then remember your device and you shouldn't have to repeat this too often. The only way to fully get rid of it is by enabling another form of 2 factor authentication. —TheDJ (Not WMF) (talk • contribs) 08:50, 7 October 2025 (UTC)
- See also Help:Extension:EmailAuth —TheDJ (Not WMF) (talk • contribs) 08:50, 7 October 2025 (UTC)
- thanks for prompt answer. I find it disappointing that I can not switch this automated gendarme, forced upon me, off. I believe I can take care of my own safety, without some blokes helping me. Overdone policing. If you pair this with "extra measures" of some e-mail providers, who also detect "suspicious activity" and try to extort my phone number (so that they can sell it or send spam themselves) this gets irritating. Anyway, thanks again for the info. Dd1495 (talk) 09:26, 7 October 2025 (UTC)
- Oh it's not just your safety that is the concern. It's also the safety of everyone else, including the load that these automated attacks create on the system. The human interaction here features as a brake pedal on illegitimate actions, because they are the only slow and known 'legitimate' element in the system. —TheDJ (Not WMF) (talk • contribs) 12:53, 7 October 2025 (UTC)
- The only way to fully get rid of it is by enabling another form of 2 factor authentication. Technically someone could also remove their email address from their account, though that's understandably (IMO) advised against. —a smart kitten[meow] 16:43, 11 October 2025 (UTC)