Project:Support desk/Flow/2024/01

This page is an archive.

Please ask questions on the current support desk.

Is it possible to convert MediaWiki datafiles and pages to text documents, or similar format?

To simply put it, is it possible? Is there any kind of program or something that can convert MediaWiki/MySQL databases to a txt format or something similar? I have access to all the files, but my MediaWiki will no longer run because of an error I can't seem to get help on and have no idea what to do anymore. So I want to either start allover again and slowly remake all the pages (which pains me), or migrate to a new program, like dokuwiki. I don't want to lose it all, cause I put far too much work into it for that. There just has to be a way to either convert it, each page is a new document, or migrate it to a new MediaWiki. Does anyone know of any sort of method?

Remember, I do not have access to/run MediaWiki, so no extension or anything that requires me to actually open the page. I need a method that takes the database files and converts them, preferably each page is its own document. Dark gundam (talk) 04:27, 1 January 2024 (UTC)

Your previous post was essentially that you couldn't run mediawiki because the database was either missing files or they were transfered incorrectly.

There are in theory other tools that could extract the data from the database, but none of them will work if the db does not have the correct data in the correct form.

Its unclear how you transfered the database files. Its plausible that you have the data to salvage the situation, it really depends on what you have. My main suggestion would be to ensure you are using the exact same version of mysql as your server was running. Beyond that this isn't really a mediawiki question, but a mysql one, and you might have better luck on a mysql specific forum. Bawolff (talk) 06:07, 1 January 2024 (UTC)

Update Questions

On the Manual:Upgrading page it says:

Warning: Do not upgrade from a MediaWiki version older than 1.33 to MediaWiki 1.39.1, or you may lose data! Upgrade to 1.35 first.

I had already upgraded directly from 1.26.2 to 1.36.0 quite a while ago. Do I now have to worry that something has gone wrong? Because sometimes I get the error message "Did you forget to run your application's database schema updater after upgrading? What can I do afterwards to correct this? Because I wanted to switch to 1.39.6 soon.

Can I simply downgrade to 1.35 and then upgrade to 1.39.6?

Or do I have to put another version in between?

Also, my web host will soon discontinue support for PHP 8 and I will then be forced to switch to PHP 8.2 or 8.3.

Is 1.39.6 compatible with PHP 8.2/8.3? 88.75.238.119 (talk) 07:09, 1 January 2024 (UTC)

Its probably fine (i'd take a backup first just in case).

There was an issue with imported pages sometimes not being updated properly when skipping versions (the pages or revisions would just disappear). But it didn't happen to everyone and lots of people didn't even have any imported pages.

The did you forget message would be about something unrelated to that warning. Probably extension related (use $wgShowExceptionDetails=true; to get detailed error message)

1.39 definitely works with php 8.1 and is well tested with it. Php 8.2 is not quite as well tested on the 1.39 branch. It probably works fine, but might have some php warnings if you have php warnings enabled. (As always if you encounter issues please report them) Bawolff (talk) 01:31, 2 January 2024 (UTC)

Images are not updating

I uploaded a new version of the image, but Wiki refuses to accept it and pushes me the old version, but of a different size, I go to the file page, it shows me the new version, but I point at it image and the old version is shown to me, I tried a bunch of methods like caching, deleting and loading the image, nothing helps. 176.59.133.149 (talk) 14:18, 1 January 2024 (UTC)

Try changing the thumbnail size of the image slightly.

For example, a image inserted as 200px, you can try changing it to 201px:

[[File:Example.jpg|201px|A picture]]

If this works, then the problem is caching. Maybe you're using a (reverse) proxy cache that's caching the old version and it's out of your control. Ciencia Al Poder (talk) 15:59, 1 January 2024 (UTC)

Can you leave any links that will help me set up caching? 2A00:1FA3:4233:4759:B809:9AD3:66C8:9788 (talk) 16:09, 1 January 2024 (UTC)

Images are not updating (2)

Hi all, I have updated the EN page https://www.mediawiki.org/wiki/MediaWiki-Vagrant to use SVG version of the initial .jpg image on Commons. This modification propagates on all translated pages except those I was checking /pl and /ta. A few days later /pl page is aligned correctly to use the .svg but the /ta page is still using the jpg version -> https://upload.wikimedia.org/wikipedia/commons/thumb/3/3e/MediaWiki_Vagrant_Visualization.jpg/1350px-MediaWiki_Vagrant_Visualization.jpg

I have used a lot of page Purges, trying even to do small updates the /ta page but without success.

Question: may be a problem of cache, but how can I force the translated tamoul page to be aligned on its EN root page like other pages are ? This is to get rid of last .jpg uses and allow the deletion Thanks. -- Christian 🇫🇷 FR (talk) 15:38, 1 January 2024 (UTC)

I couldn't get CirrusSearch to work as desired.

Hello, is there a structure other than CirrusSearch that I can use? Saliha96 (talk) 07:52, 2 January 2024 (UTC)

Depends on what you want to achieve. What about making CirrusSearch work instead? Also see "Post a new question" in the sidebar. Malyacko (talk) 12:38, 2 January 2024 (UTC)

Thank you for your reply. I couldn't find the answer I wanted in the "Post a new question" section. Apart from that, I am having a problem with the installation. Is there any other installation method?

For example, can I write a script on PhpMyAdmin for the Elasticsearch installation package? Saliha96 (talk) 14:52, 3 January 2024 (UTC)

Please read the first item under "Post a new question" and provide basic information. Also, if there are problems, you have to describe problems. Malyacko (talk) 16:27, 5 January 2024 (UTC)

create account

unable to create account. getting the following database error message: "A database query error has occurred. This may indicate a bug in the software."

tt 198.51.240.130 (talk) 22:56, 2 January 2024 (UTC)

On which website? – Ammarpad (talk) 16:53, 3 January 2024 (UTC)

I want to turn off the automatic signature feature of MediaWiki.

I'm using MediaWiki as my personal wiki.

Three times the wave is entered, and the text is automatically converted and the signature is entered.

In my case, I don't need this feature, because I use it alone, the signature is meaningless.

When you look at the code, it's located next.

https://github.com/wikimedia/mediawiki/blob/1.41.0/includes/parser/Parser.php#L4554

includes/parser/Parser.php

private function pstPass2( $text, UserIdentity $user ) {
...
	# Signatures
	if ( strpos( $text, '~~~' ) !== false ) {
		$sigText = $this->getUserSig( $user );
		$text = strtr( $text, [
			'~~~~~' => $d,
			'~~~~' => "$sigText $d",
			'~~~' => $sigText
		] );
		# The main two signature forms used above are time-sensitive
		$this->setOutputFlag( ParserOutputFlags::USER_SIGNATURE, 'User signature detected' );
	}
...
}

I think you can add the if syntax to this and add the global option variable.

Is it correct to suggest here? If it is, I would appreciate it if you could add a code. EZXIZT (talk) 09:42, 3 January 2024 (UTC)

I don't think we're planning to add new config options to parser. Having too many options means more things to test which adds complexity.

Potentially it might be possible to do something in an extension. Bawolff (talk) 20:16, 6 January 2024 (UTC)

Thank you for your guidance. EZXIZT (talk) 19:53, 11 January 2024 (UTC)

Roll Back MW Version from 1.39 to 1.36

Hello, I am wondering what the typical process is to roll back to a previous version. We presently have 1.39.1 enabled, and we need to roll back to 1.36.x. We have an extension that will only work with this version. I am wondering what the process is and what sorts of issues we're bound to uncover when this happens?

Thank you Kimmywingz (talk) 19:12, 4 January 2024 (UTC)

You have to place back a copy of the database from when you were using the 1.36 version. Without doing that, code might break because the database structure has changed in a way that the old code might not be able to understand. —TheDJ (Not WMF) (talk • contribs) 09:47, 5 January 2024 (UTC)

Authentication problems

When accessing my wiki, it presents the following error:

Authentication error Problems were detected with your session; This action has been canceled as a protection measure against session interception. Try using the "Back" button and refreshing the page you came from and try again 177.95.190.49 (talk) 13:20, 5 January 2024 (UTC)

If this happens consistently, and in clean browser sessions (incognito mode), then generally this means that the session cannot be saved by the server. You might want to check Manual:$wgSessionCacheType —TheDJ (Not WMF) (talk • contribs) 15:16, 5 January 2024 (UTC)

HotCat gadget not working on hy.wikipedia

Hi!

On Armenian wikipedia (hywiki) HotCat gadget is not working since January 5, 2024.

Please can you help to solve this problem!

Thank you in advance! Kareyac (talk) 16:11, 5 January 2024 (UTC)

@Kareyac This place is for general third-party MediaWiki questions. https://meta.wikimedia.org/wiki/Tech is for tech questions about Wikimedia wikis. Malyacko (talk) 16:26, 5 January 2024 (UTC)

@Malyacko Thanks again. Kareyac (talk) 16:57, 5 January 2024 (UTC)

Complex pages take a long time to save/re-render

Pages that are very large (many headers, and possibly links to) take a long time to save and re-render.

While for a "regular" page that contains a few headers and up to 1KB of text the save/rendering cycle is almost instantaneous, complex pages take up to 15- 20 seconds.

What I can do to speed up and how I can troubleshoot the issue?

These are my dependencies:

Product	Version
MediaWiki	1.39.6
PHP	8.3.1 (apache2handler)
MariaDB	11.2.2-MariaDB
ICU	73.2
Lua	5.1.5
Pygments	2.11.2

Thanks! Of78990 (talk) 01:49, 6 January 2024 (UTC)

Videos unplayable in older Apple mobile devices

Either videos are unplayable in older iPads and iPhones, or browsers in iOS 15 or iOS 12 can't load videos, or web player is too slow to load them on older iOS versions. I tried Safari and then Google on iOS; issue still persistent. George Ho (talk) 01:47, 7 January 2024 (UTC)

Please see "Post a new question" in the sidebar and share some basics, for example the MediaWiki version that you installed. Malyacko (talk) 12:55, 7 January 2024 (UTC)

I don't own a website. I was referring to VideoJS player in Wikimedia projects and the Wikipedia app. George Ho (talk) 13:11, 7 January 2024 (UTC)

@George Ho Ah, that would be https://meta.wikimedia.org/wiki?Tech for questions about Wikimedia wikis. Malyacko (talk) 09:21, 8 January 2024 (UTC)

How to load a js file AFTER jquery is loaded?

I need to load a JavaScript file after jquery is loaded. Otherwise my script fails.

Is there a way to do this via mw.loader.load or via LocalSettings.php (hook "BeforePageDisplay") or any other way?

Thanks! Stefahn (talk) 20:36, 7 January 2024 (UTC)

The default way would load after jquery Bawolff (talk) 10:05, 8 January 2024 (UTC)

MediaWiki 1.39.2 on Synology

Hello

Using DSM 7.1.1 I would like to setup MediaWiki

Web Station is running and during the setup MariaDB 10 has been installed.

But then Unable to start the package.

I tried to repair or to uninstall with the same error message : setup failed !

In logs In can read :

2024/01/08 16:35:38 uninstall MediaWiki 1.39.2-1078 Begin preuninst

2024/01/08 16:35:38 uninstall MediaWiki 1.39.2-1078 End preuninst ret=[0]

User and password are correct during the uninstall.

Is it a way to have more logs ?

Is it a way to uninstall the package manually ?

Thanks a lot Xavlp (talk) 17:37, 8 January 2024 (UTC)

Synology has created these packages and we do not provide support for them. Try the synology forums perhaps ? —TheDJ (Not WMF) (talk • contribs) 21:53, 9 January 2024 (UTC)

Update err 500

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Good evening,

I have a MediaWiki v.1.35.2 (PHP 8.2.3 (litespeed) and MariaDB 10.5.19-MariaDB-cll-lve). I want to upgrade to v.1.41.0

I create a new installation by following the instructions :

Save database, localSettings.php, images

Rename old version to .old

Go to public.html

wget https://releases.wikimedia.org/mediawiki/1.41/mediawiki-1.41.0.tar.gz

tar xvzf mediawiki-1.41.0.tar.gz

rm mediawiki-1.41.0.tar.gz

rename the new version

copy file localSettings.php

cp ccWiki.old/LocalSettings.php ccWiki

copy images folder

cp -RT ccWiki.old/images/ ccWiki/images

Add extensions

* MobileFrontEnd

go to extensions

wget https://extdist.wmflabs.org/dist/extensions/MobileFrontend-REL1_41-964152c.tar.gz

tar -xzf MobileFrontend-REL1_41-964152c.tar.gz

copy custom logos (resources/assets)

cp ccWiki.old/resources/assets/* ccWiki/resources/assets

Run the update script

go to maintenance

php run.php update.php

Nothing happens during scripting: is this normal?

When I launch my index page, it's white (just html/head/body and the development tools indicate error 500).

I've tried the installation 2 times, to no avail.

The old Wiki still works.

I don't know what to do

Thanks for your help CharlesC85 (talk) 21:33, 8 January 2024 (UTC)

It's probably a PHP error. If you add the debugging from Manual:How to debug directly under the php tag in LocalSettings it will give a verbose error. Original Authority (talk) 23:27, 8 January 2024 (UTC)

Thank you

error : Warning: Undefined variable $wgMimeTypeBlacklist in /home/u779420181/domains/ccournault.fr/public_html/ccWiki/LocalSettings.php on line 161

It's fixed : I comment it and I can update

It's ok CharlesC85 (talk) 21:15, 9 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Namespacing issue

I'm working on a wiki farm extension, and having a bit of an issue with namespacing. Everything works, and all of the classes are loaded, but I'm trying to implement some other classes, but they're not being recognised by MediaWiki.

For example, here is the wiki class and its namespace, and the relevant autoloading in extension.json.

That all works, but now I want to create a new file "Functions.php" in the project root:

<?php

use Telepedia\DynamicSettings\Wiki;

class Functions
{

    public function __construct()
    {
        self::getAllDatabases();
    }

    public function getAllDatabases() {
        $wikis = Wiki::loadAll();
    }

}

It uses the Wiki class, and I load it into my LocalSettings.php with $wi = new Functions(), but I'm getting thrown the error that:

Uncaught Error: Class "Telepedia\DynamicSettings\Wiki" not found

Even though the file is correctly namespaced and works for the files within the extension themselves? Does anyone see what I'm doing wrong from my code? I've stepped through it, relevant images here, as you can see, I'm eventually landing at MediaWiki not finding the class despite the fact that I think it's loaded properly? Original Authority (talk) 22:18, 8 January 2024 (UTC)

When you do

$wi = new Functions();

in your LocalSettings.php, do you have the extension already enabled? Osnard (talk) 07:31, 10 January 2024 (UTC)

[Wanted] Script for updating "all" installed extensions to $Version

I suppose you know the problem when updating mediawiki core to $Version that updating all your installed extensions to their latest $Version may by PIA.

Has anyone a working script to fetch all current download urls such as

Example for $Version == 1.41.0

cd wiki/extensions
wget https://extdist.wmflabs.org/dist/extensions/Echo-REL1_41-baf7812.tar.gz
tar -xf Echo-REL1_41-baf7812.tar.gz
rm Echo-REL1_41-baf7812.tar.gz
php ../maintenance/update.php --quick</code>

wget https://extdist.wmflabs.org/dist/extensions/Gadgets-REL1_41-b0f336d.tar.gz
tar -xf Gadgets-REL1_41-b0f336d.tar.gz
rm Gadgets-REL1_41-b0f336d.tar.gz
php ../maintenance/update.php --quick
....

So the wanted script should

1. determine the installed extensions
2. get as input the wanted $Version number to upgrade to
3. fetch the latest extension downloader urls for that $Version
4. prepare a list of these urls
5. prepare sequence of wget / tar -xf / perhaps also php update.php --quick Wikinaut (talk) 10:56, 9 January 2024 (UTC)

ordered lists alignment

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I have created a set of custom ordered lists, but there is some conflict in the CSS code somewhere that is throwing the alignment out. Here is the css I want to use:

☁

This is what the alignment should look like - this works as a piece of css code if tested independently on w3 schools etc.

It almost works (example: Talk:Paragraph numbering - The Jolly Contrarian) but there seems to be some conflicting code somewhere that is forcing the number and paragraph alignment to the right, so that the numbers are not flush with the preceding paragraph.

Any idea what I can do to fix this?

this is the css that is getting in the way

ElectricRay (talk) 11:30, 9 January 2024 (UTC)

css: https://jollycontrarian.com/index.php?title=MediaWiki:Common.css

example page: https://jollycontrarian.com/index.php?title=Talk:Paragraph_numbering ElectricRay (talk) 11:32, 9 January 2024 (UTC)

I have solved it: I had to adjust add the following to the common.css

.mw-content-ltr ol {

margin-top: 0px;

margin-bottom: 0px;

margin-left: 0px;

margin-right: 0px; ElectricRay (talk) 16:17, 9 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

version 4.3 of BlueSpiceFoundation

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Good evening,

I would like to install BlueSpiceUserManager :

- I have downloaded and installed the master version of BlueSpiceFoundation: version 4.2.0-alpha (e16a386) January 9, 2024 at 08:32 AM (with ExtJSBase 3.0.0-alpha and OOJSPlus 3.0.0-alpha) => it's ok

- I have downloaded and installed the master version of BlueSpiceUserManager version 4.2.0-alpha and I get the error: BlueSpiceUserManager is not compatible with the current installed version of BlueSpiceFoundation (4.2.0-alpha), it requires: >= 4.3

Where can I find version 4.3? I've downloaded the latest version. Do I have to wait a little?

Thanks CharlesC85 (talk) 23:05, 9 January 2024 (UTC)

The bluespice people generally don't read this page, it would probably be better to try contacting them directly. Bawolff (talk) 04:15, 10 January 2024 (UTC)

Well, I do read this page :)

But Bawolff is right: You may get help regarding BlueSpice topics more quickly at https://community.bluespice.com/

The BlueSpice team does version tag releases. So rather than using a branch like REL1_38 (which you apparently did), please use the git tags, like 4.4.0. All "BlueSpice"-prefixed extensions are aligned, so you can use a BlueSpiceUserManader 4.4.0 together with a BlueSpiceFoundation 4.4.0.

We also recommend installation using composer.

If you are looking for the whole BlueSpice MediaWiki distribution, please check out the https://sourceforge.net/projects/bluespice/files/ Osnard (talk) 07:25, 10 January 2024 (UTC)

Sorry, I'm glad you do :)

I sort of use that as a generic response for any extension issue that is not one of the ones bundled with MediaWiki. Bawolff (talk) 09:57, 10 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

MediaWiki 1.25.2 on Debian 8

Good Afternoon - I have inherited and MediaWiki 1.25.2 on Debian 8 and would intersted in migrating it to a Windows 2019 server running the latest version. Is this a supported process or something that I can tackle?

Thanks 110.144.34.179 (talk) 03:21, 10 January 2024 (UTC)

See Upgrading.

Well not strictly required, i would recommend doing the server move and the update in separate steps if possible. When moving servers, you may have to adjust some of the settings in LocalSettings.php, especially $wgServer, $wgArticlePath and $wgScriptPath. Additionally, if paths are specified for certain options other than the defaults, you may need to change them due to differences between windows and linux. Bawolff (talk) 04:15, 10 January 2024 (UTC)

Update Error: MediaWiki\Revision\RevisionAccessException

After upgrade (MediaWiki 1.39.6) to MediaWiki 1.41.0 I get this error:

[ZZ6m_N_qHLMyicwO1CNA9QAAABI] /wiki/Hauptseite MediaWiki\Revision\RevisionAccessException: Unable to load fresh row for rev_id: 37405

Backtrace: from /var/www/vhosts/example.com/mediawiki-1.41.0/includes/Revision/RevisionStoreCacheRecord.php(114) #0 /var/www/vhosts/example.com/mediawiki-1.41.0/includes/Revision/RevisionStoreCacheRecord.php(93): MediaWiki\Revision\RevisionStoreCacheRecord->loadFreshRow() #1 /var/www/vhosts/example.com/mediawiki-1.41.0/includes/page/WikiPage.php(858): MediaWiki\Revision\RevisionStoreCacheRecord->getUser() #2 /var/www/vhosts/example.com/mediawiki-1.41.0/includes/actions/CreditsAction.php(113): WikiPage->getUserText() #3 /var/www/vhosts/example.com/mediawiki-1.41.0/includes/actions/CreditsAction.php(97): CreditsAction->getAuthor() #4 /var/www/vhosts/example.com/mediawiki-1.41.0/includes/skins/components/SkinComponentFooter.php(122): CreditsAction->getCredits() #5 /var/www/vhosts/example.com/mediawiki-1.41.0/includes/skins/components/SkinComponentFooter.php(33): MediaWiki\Skin\SkinComponentFooter->getFooterInfoData() #6 /var/www/vhosts/example.com/mediawiki-1.41.0/includes/skins/components/SkinComponentFooter.php(55): MediaWiki\Skin\SkinComponentFooter->getTemplateDataFooter() #7 /var/www/vhosts/example.com/mediawiki-1.41.0/includes/skins/SkinTemplate.php(266): MediaWiki\Skin\SkinComponentFooter->getTemplateData() #8 /var/www/vhosts/example.com/mediawiki-1.41.0/includes/skins/SkinTemplate.php(143): SkinTemplate->prepareQuickTemplate() #9 /var/www/vhosts/example.com/mediawiki-1.41.0/includes/skins/SkinTemplate.php(174): SkinTemplate->generateHTML() #10 /var/www/vhosts/example.com/mediawiki-1.41.0/includes/Output/OutputPage.php(2947): SkinTemplate->outputPage() #11 /var/www/vhosts/example.com/mediawiki-1.41.0/includes/MediaWiki.php(978): MediaWiki\Output\OutputPage->output() #12 /var/www/vhosts/example.com/mediawiki-1.41.0/includes/MediaWiki.php(613): MediaWiki->main() #13 /var/www/vhosts/example.com/mediawiki-1.41.0/index.php(50): MediaWiki->run() #14 /var/www/vhosts/example.com/mediawiki-1.41.0/index.php(46): wfIndexMain() #15 {main} 109.42.241.156 (talk) 14:33, 10 January 2024 (UTC)

Have you run update.php, did it complete successfully, what extensions do you have enabled. etc etc etc. —TheDJ (Not WMF) (talk • contribs) 15:03, 10 January 2024 (UTC)

Show Bot changes in RecentChanges to all users

I want Botedits to be visible to all visitors in RecentChanges, whether logged in or not. Where can I change this? 37.251.227.38 (talk) 15:34, 10 January 2024 (UTC)

No ideas anyone? 37.251.230.105 (talk) 10:24, 13 January 2024 (UTC)

Errors in LCStoreDB

I am getting five error messages at the top of every page in my wiki. I am using php 7.4.3 and MariaDB 10.6.12. I am running on Mint 21.2. The error messages are:

Notice: unserialize(): Error at offset 1382 of 279905 bytes in /var/www/html/mediawiki-1.40.1/includes/language/LCStoreDB.php on line 67

Notice: unserialize(): Error at offset 1470 of 6352 bytes in /var/www/html/mediawiki-1.40.1/includes/language/LCStoreDB.php on line 67

Notice: unserialize(): Error at offset 1470 of 6352 bytes in /var/www/html/mediawiki-1.40.1/includes/language/LCStoreDB.php on line 67

Warning: Invalid argument supplied for foreach() in /var/www/html/mediawiki-1.40.1/includes/language/LocalisationCache.php on line 523

Notice: unserialize(): Error at offset 69 of 70 bytes in /var/www/html/mediawiki-1.40.1/includes/language/LCStoreDB.php on line 67

I have had no luck figuring out what is causing this. The same wiki runs fine on another computer running Rocky 8.9.

Apart from the error messages the wiki appears to run fine. Wbean43 (talk) 21:28, 10 January 2024 (UTC)

Try running (as the same user as your webserver runs as) rebuildLocalisationCache.php --force Bawolff (talk) 00:36, 11 January 2024 (UTC)

visual editor doesnt save category correctly

Started a new fresh wiki, 1.41.0

When editing with the VisualEditor, category tags like [[Category:System]] are converted and saved as [[index.php?title=Kategori:System]]. This of course breaks the page categorising. It's possible to re-edit the page, re-categorise it and it works but it will break again on the next edit.

The WikiText editor does not exhibit this behaviour. It correctly handles the category tags.

Here's rest of the software versions.

Product	Version
MediaWiki	1.41.0
PHP	8.3.1 (fpm-fcgi)
ICU	67.1
MariaDB	10.6.16-MariaDB-1:10.6.16+maria~deb11

Billmackenty (talk) 05:29, 11 January 2024 (UTC)

How is Article Path is set al LocalSettings? Fokebox (talk) 11:56, 11 January 2024 (UTC)

This is https://phabricator.wikimedia.org/T328337 —TheDJ (Not WMF) (talk • contribs) 12:12, 11 January 2024 (UTC)

ImageMap not working

Hello, the imageMap help table on our wiki displays "Error: Image is invalid or non-existent" with no clickable links.

Our Special:Version page shows it has been installed

ImageMap GPL-2.0-or-later

In LS.p currently enabled:

$wgUseImageMagick = true;

$wgImageMagickConvertCommand = "/usr/bin/convert";

wfLoadExtension('ImageMap');

Any additional tips or thoughts on how to troubleshoot?

When ImageMagick is installed should it show up on the Special:Version page? (currently is not)

Thank you for any input and thoughts. Kimmywingz (talk) 18:00, 11 January 2024 (UTC)

Does the image being used for the image map actually exist on your wiki?

> When ImageMagick is installed should it show up on the Special:Version page? (currently is not)

It is normal for this not to show up. Bawolff (talk) 14:02, 12 January 2024 (UTC)

Thank you! Some images were there and some were not. I uploaded new images and I was able to link to them and that made the links work in the image map and the image showed up correctly. However on the images that were already on the wiki it's not working.

For example, I have one image that was previously uploaded. It is currently being used on another page and is showing up as normal. It is not showing up on the imageMap however. I checked the file names and they are the same on both pages. Kimmywingz (talk) 20:10, 12 January 2024 (UTC)

If your wiki is public can you link to it? Bawolff (talk) 20:27, 12 January 2024 (UTC)

Failed to access special:specialpages

Hi, I came to the following error when i tried to access to special:specialpages. Instead, i got this error when i accessed to all mediawiki system pages (those with :).

Forbidden

You don't have permission to access this resource.

This is the error when i checked in apache error logs:

[core:error] [pid 6876:tid 1268] (20024)The given path is misformatted or contained invalid characters: [client 192.168.18.31:56482] AH00127: Cannot map GET /mediawiki/MediaWiki:Sidebar HTTP/1.1 to file

I assume this issue appears after i configure on the url shortcut.

I tried many ways but still failed to resolve. is there any tips or thoughts on how to solve this?

Thank you for any input and thoughts. 211.24.101.22 (talk) 10:01, 12 January 2024 (UTC)

Probably an issue with the configuration of rewrite rules.

Can you paste any rewrite rules in use (They are probably in your .htaccess file) Bawolff (talk) 14:03, 12 January 2024 (UTC)

My page was deleted

My page has been deleted. It has been a long time since I set it up and have let editors maintain it. I cannot find my login. Is my page in an archive? Can it be restored? 173.24.247.247 (talk) 21:04, 12 January 2024 (UTC)

Maybe. If on this wiki, what username? Clump (talk) 21:36, 12 January 2024 (UTC)

Issues with HTML tags

I have a wiki on a shared hosting, when trying to add HTML tags or braces to pages (such as <div style="text-align:center"> or {| style="width: 100% !important;"), I get a 403 Forbidden Error, and after multiple attempts the server's firewall blocks my connection. Not sure if this has to do with my provider, but wanted to ask if it could be caused by something else first. 190.219.188.224 (talk) 22:03, 12 January 2024 (UTC)

After doing some research, I think it might be caused ModSecurity, which is triggering false positives when adding specific syntax (such as html tags). Is it save if I disable it? 190.219.188.224 (talk) 07:52, 13 January 2024 (UTC)

Yes, modsecurity causes a lot of problems and doesn'tceven protect very much. We reccomend you do not use it with mediawiki. Bawolff (talk) 10:10, 14 January 2024 (UTC)

$wgAddGroups Confusion

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I'm currently using Extension:Moderation for a mediawiki install that's at v1.40.1.

This extension adds two groups:

• Moderator
• Automoderated user

I'd like to enable the moderator group to add users to the "Automoderated user" group. To do this I've added the following lines to my LocalSettings.php.

$wgGroupPermissions['moderator']['userrights'] = false;

$wgAddGroups['moderator'][] = 'automoderated user';

Based on my understanding of Manual:$wgAddGroups this should be valid, but users in the "moderator" group cannot add other users to the automoderated user group.

What am I doing wrong? ProbablePrime (talk) 00:21, 13 January 2024 (UTC)

Config seems correct, do you have any config elsewhere that is overwriting that? Original Authority (talk) 02:14, 13 January 2024 (UTC)

I don't do any other manual group settings and these entries are at the bottom of my LocalSettings.

It is possible there are overwrites somewhere else, but I'm not entirely sure where to check. ProbablePrime (talk) 03:41, 13 January 2024 (UTC)

The wgAddGroups line is wrong because the group is named automoderated not "automoderated user".

Keep in mind internal group names can be different than their friendly names. Bawolff (talk) 10:12, 14 January 2024 (UTC)

Thank you!, I have updated my settings.

$wgGroupPermissions['moderator']['userrights'] = false;

$wgAddGroups['moderator'][] = 'automoderated';

However, this still doesn't work. I am lost as to why :'( ProbablePrime (talk) 02:52, 15 January 2024 (UTC)

Can you include the output of Special:ListGroupRights on your wiki? Bawolff (talk) 03:28, 15 January 2024 (UTC)

I figured it out BaWolff, thank you.

Moderator members will only see the checkboxes for groups on pages for users who have not already had the auttomoderated group added. This makes sense as I haven't allowed them to remove that membership.

I've allowed them to remove the membership with $wgRemoveGroups

With both set to my values above, I'm fixed. Thank you! ProbablePrime (talk) 12:49, 15 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Block duplicate uploads

Currently, if a user uploads a file with the same data/checksum as an existing file, they are shown a warning and given an option to ignore it and upload a duplicate. Can the wiki be configured to completely block duplicates? Ham Pastrami (talk) 01:28, 13 January 2024 (UTC)

number headings in mediawiki 1.41

Hey there I got a new installed mediawiki and I am unable to enable number headings inside articles, I tried many solutions which can be found by google (LocalSettings.php, css, js, ...) nothing seems to works.

Thanks for any help, regards

Christian 178.191.128.176 (talk) 02:49, 13 January 2024 (UTC)

Unable to Login to My Wiki

MW v1.41.0

PHP 7.4.3

When I try to login to my wiki I have this error at the login page:

[ZaLWQFq7YZgADP-fwx5YkwAAAFU] 2024-01-13 18:28:17: Fatal exception of type "Error"

Here is the backtrace of the error, I am not very knowledgeable for this, can someone please give me some direction on how to fix? Thank so much.

[ZaLVxlq7YZgADP-fwx5UcgAAAFY] /mw/index.php?title=Special:UserLogin&returnto=Main+Page Error: Class 'Wikimedia\Equivset\Equivset' not found

Backtrace:

from /public_html/mw/extensions/AbuseFilter/includes/ServiceWiring.php(125)

#0 /public_html/mw/vendor/wikimedia/services/src/ServiceContainer.php(447): Wikimedia\Services\ServiceContainer::{closure}(MediaWiki\MediaWikiServices)

#1 /public_html/mw/vendor/wikimedia/services/src/ServiceContainer.php(411): Wikimedia\Services\ServiceContainer->createService(string)

#2 /public_html/mw/includes/MediaWikiServices.php(351): Wikimedia\Services\ServiceContainer->getService(string)

#3 /public_html/mw/vendor/wikimedia/services/src/ServiceContainer.php(419): MediaWiki\MediaWikiServices->getService(string)

#4 /public_html/mw/extensions/AbuseFilter/includes/ServiceWiring.php(292): Wikimedia\Services\ServiceContainer->get(string)

#5 /public_html/mw/vendor/wikimedia/services/src/ServiceContainer.php(447): Wikimedia\Services\ServiceContainer::{closure}(MediaWiki\MediaWikiServices)

#6 /public_html/mw/vendor/wikimedia/services/src/ServiceContainer.php(411): Wikimedia\Services\ServiceContainer->createService(string)

#7 /public_html/mw/includes/MediaWikiServices.php(351): Wikimedia\Services\ServiceContainer->getService(string)

#8 /public_html/mw/vendor/wikimedia/services/src/ServiceContainer.php(419): MediaWiki\MediaWikiServices->getService(string)

#9 /public_html/mw/vendor/wikimedia/object-factory/src/ObjectFactory.php(204): Wikimedia\Services\ServiceContainer->get(string)

#10 /public_html/mw/vendor/wikimedia/object-factory/src/ObjectFactory.php(149): Wikimedia\ObjectFactory\ObjectFactory::getObjectFromSpec(array, array)

#11 /public_html/mw/includes/auth/AuthManager.php(2496): Wikimedia\ObjectFactory\ObjectFactory->createObject(array, array)

#12 /public_html/mw/includes/auth/AuthManager.php(2528): MediaWiki\Auth\AuthManager->providerArrayFromSpecs(string, array)

#13 /public_html/mw/includes/auth/AuthManager.php(2213): MediaWiki\Auth\AuthManager->getPreAuthenticationProviders()

#14 /public_html/mw/includes/specialpage/AuthManagerSpecialPage.php(290): MediaWiki\Auth\AuthManager->getAuthenticationRequests(string, MediaWiki\User\User)

#15 /public_html/mw/includes/specialpage/LoginSignupSpecialPage.php(160): MediaWiki\SpecialPage\AuthManagerSpecialPage->loadAuth(NULL)

#16 /public_html/mw/includes/specialpage/LoginSignupSpecialPage.php(252): MediaWiki\SpecialPage\LoginSignupSpecialPage->load(NULL)

#17 /public_html/mw/includes/specialpage/SpecialPage.php(727): MediaWiki\SpecialPage\LoginSignupSpecialPage->execute(NULL)

#18 /public_html/mw/includes/specialpage/SpecialPageFactory.php(1621): MediaWiki\SpecialPage\SpecialPage->run(NULL)

#19 /public_html/mw/includes/MediaWiki.php(357): MediaWiki\SpecialPage\SpecialPageFactory->executePath(string, RequestContext)

#20 /public_html/mw/includes/MediaWiki.php(960): MediaWiki->performRequest()

#21 /public_html/mw/includes/MediaWiki.php(613): MediaWiki->main()

#22 /public_html/mw/index.php(50): MediaWiki->run()

#23 /public_html/mw/index.php(46): wfIndexMain()

#24 {main} John Morris (talk) 18:31, 13 January 2024 (UTC)

Looking at the back trace I saw a reference to AbuseFilter, I commented out the AbuseFilter in LocalSettings and I am able to login now. How important is AbuseFilter in a "closed for public editing" wiki?

Thanks John Morris (talk) 00:41, 14 January 2024 (UTC)

So the error means that abusefilter is missing dependencies. You need to either run composer update --no-dev or download via special:ExtensionDistributor.

AbuseFilter allows users to make custom filters. It is not a generic out of the box anti-spam solution. If you haven't made any filters than it does nothing. So if you don't know if you need it then you probably aren't using it. Bawolff (talk) 10:08, 14 January 2024 (UTC)

Thank you Bawolff, since my instance of MW is authorized users only, I probably don't need any type of anti spam solution. So I'll just leave it commented out for now. I checked the box for it at time of installation not truly understanding what it was but for convenience I included it in the initial installation, probably not a good idea for me to do if I don't know what it is.

Thanks for your explanation, truly appreciate your time.

John Morris (talk) 15:12, 14 January 2024 (UTC)

John Morris (talk) 15:11, 14 January 2024 (UTC)

[Developer question] How to modify the css of buttons on Special:Login to show even longer texts on the button [solved, solution added]

I use E:PluggableAuth and wish to deliberately modify the css of the buttons ("Login with password" and "Login with SSO of Server...").

The texts are too long for the buttons (mw1.41.0).

I cannot find in the source how to modify the button layout and kindly ask for your help how to change the layout (css and texts) of the registration/login page. Wikinaut (talk) 04:06, 14 January 2024 (UTC)

Modifying styles on Special:Userlogin is not that simple. AFAIK, pages like MediaWiki:Common.css and MediaWiki:Common.js are not being loaded in context of Special:Userlogin, due to security considerations.

Extension:PluggableAuth uses the standard AuthManager mechanism to create those buttons. So, unless you create a custom MediaWiki extension to load CSS on Special:Userlogin, I don't think you can influence this. Osnard (talk) 08:12, 15 January 2024 (UTC)

@Osnard:

thanks for your swfit reply.

Your reply exactly confirms my multiple observations before I filed my support request.

Especially I think that the development of such a custom extension as proposed by you might be required.

Perhaps anyone has a stub for such a type of custom extension which modifies the layout - or do you have a pointer to an suited extesnion to start with? Wikinaut (talk) 09:04, 15 January 2024 (UTC)

Actually you may be able to add such small thing directly to the LocalSettings

Example:

$GLOBALS['wgHooks']['BeforePageDisplay'][] = function( OutputPage &$out, Skin &$skin ) {
	$style = "<style type=\"text/css\">\n";
	$style .= "YOUR CSS GOES HERE";
	$style .= "</style>\n";
	$out->addHeadItem( 'change-login-button', $style );
	return true;
};

This is not really recommended though, as this kind of hook registration may be removed in the future.

Also have a look at Extension:BoilerPlate. Osnard (talk) 10:22, 16 January 2024 (UTC)

@Osnard

This is the finally working version, fixed.

It makes the buttons (here the standard Login-button and the Extension:OpenIDConnect-Login-button) to display all texts on the buttons, even if the texts are longer:

# https://www.mediawiki.org/w/index.php?title=Project%3ASupport%20desk/Flow/2024/01#h-%5BDeveloper_question%5D_How_to_modify_the_css_of_buttons_on_Special%3ALogin_to_show_e-20240114040600
# How to modify the Login-Page
$GLOBALS['wgHooks']['BeforePageDisplay'][] = function( OutputPage &$out, Skin &$skin ) {
        $style = <<<EOT
            <style type="text/css">
                    button#wpLoginAttempt {
                            white-space: normal;
                            word-wrap: break-word;
                            height: auto !important;
                    }
                    button#mw-input-pluggableauthlogin0 {
                            background-color: salmon !important;
                            border-color: salmon !important;
                            white-space: normal;
                            word-wrap: break-word;
                            height: auto !important;
                    }
            </style>
EOT;
        $out->addHeadItem( 'change-login-button', $style );
        return true;
};

Wikinaut (talk) 20:14, 24 January 2024 (UTC)

Get old pagename?

Suppose I create a page called "First name", and I later move it to "Other name", is there a way to get the first name of the page (that is, "First name") via the API?

Thanks! צמא לדעת (talk) 09:14, 14 January 2024 (UTC)

You can use the logevents api module with the move log.

Api:Logevents Bawolff (talk) 10:04, 14 January 2024 (UTC)

הוספת קטגוריה

איך אני מגדיר הוספת קטגוריה כמו תמיכה ו פיתוח, אני רוצה לעשות סקריפט שיהיה תחת לשונית "חדשה". תודה. Navrcbu (talk) 17:53, 14 January 2024 (UTC)

blank php file

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

i've recently moveed my server from nginx to apache2 (because of my wiki, and blank php files). i've removed php-fpm, nginx, nginx-common, moved everything to my web folder, and yet it's still a blank php file. is there anyway to fix this? (i used to have my wiki on a diffrent port using apache, but it did work, until i moved it to my main folder) 2601:447:C080:8820:E5E0:54B:53C4:5487 (talk) 20:53, 14 January 2024 (UTC)

what? 2601:447:C080:8820:E5E0:54B:53C4:5487 (talk) 22:16, 14 January 2024 (UTC)

MediaWiki needs a non-blank php file. In fact, it needs a complete installation like what you can download at Download.

If what you get is a "blank page", see Blank page Ciencia Al Poder (talk) 12:17, 15 January 2024 (UTC)

the error is "syntax error, unexpected variable '$wgEnableEmail'" 2601:447:C080:8820:FDA4:EF3E:43DC:AAC6 (talk) 23:29, 16 January 2024 (UTC)

You seem to have an error in LocalSettings.php, apparently, "around" that variable (it may be before or after). Ciencia Al Poder (talk) 14:52, 17 January 2024 (UTC)

patebin with my localsettings (i've changed stuff for security and privacy reasons)

https://pastebin.com/MakMiwSX 2601:447:C080:8820:515D:8DC:F05:9570 (talk) 00:41, 23 January 2024 (UTC)

$wgUsePathInfo = TRUE is missing a semicolon at the end of that statement. Taavi (talk!) 09:19, 23 January 2024 (UTC)

i did that and no luck 2601:447:C080:8820:4553:6A55:AC88:9CB6 (talk) 23:44, 23 January 2024 (UTC)

$wgEnableUserEmail requires $wgEnableEmail to be true as well 94rain ^Talk 00:23, 24 January 2024 (UTC)

Also, try to check LocalSettings.php syntax here for more errors like the missing semicolons: https://phpcodechecker.com/ Ciencia Al Poder (talk) 11:05, 24 January 2024 (UTC)

One question, does mediawiki allow http:// instead of https:// in the wgServer 209.237.103.236 (talk) 14:34, 24 January 2024 (UTC)

By default it should be http://. HTTP requires no extra configuration. What's the problem that you are facing? check Manual:HTTPS and see if you have any HTTPS configurations in LocalSettings.php and remove them. 94rain ^Talk 06:31, 25 January 2024 (UTC)

That was just a random question, sorry 209.237.103.236 (talk) 17:33, 25 January 2024 (UTC)

fixing wgEnableUserEmail didn't fix the issue 2601:447:C080:8820:7D85:1ABE:F5FD:8B0E (talk) 00:25, 26 January 2024 (UTC)

Try commenting out the lines where there are errors? 94rain ^Talk 01:24, 26 January 2024 (UTC)

Ok 209.237.103.236 (talk) 14:31, 26 January 2024 (UTC)

I tried commenting out $wgEnableEmail, the error went to $wgEnableUserEmail, then the $wg that comes after enableuseremail, and it just keeps going. (Also I’m currently at school so that’s why my ip is different) 209.237.103.236 (talk) 17:16, 26 January 2024 (UTC)

Nvm, the code checker passed when I added the semicolon so :/ 209.237.103.236 (talk) 17:18, 26 January 2024 (UTC)

You can also create an account here on this site so you can have a fixed name :) It would also be easier to keep track of the post updates. 94rain ^Talk 17:59, 26 January 2024 (UTC)

so now the error is that it cant find the extention "Array", not Arrays. (also btw i'm not getting a blank php file, but i'm still going to carry on until my problem is fixed) RealPaxtonPenguin (talk) 02:38, 27 January 2024 (UTC)

nvm, the new error is that firefox is saying: "The page isn’t redirecting properly" so :/ RealPaxtonPenguin (talk) 02:59, 27 January 2024 (UTC)

Can you give more context? 94rain ^Talk 22:34, 27 January 2024 (UTC)

bump RealPaxtonPenguin (talk) 22:32, 27 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Do I make pages on MediaWiki, or do I HAVE to make a wiki?

Dearest and most trusted MediaWiki helpers and founders:

(Backstory.) I tried to make an account on MicroWiki, (to be honest, one of my favorite websites!) [aka micronations.wiki.] but it said I HAD to put in my email address, and, if you know me, I am not wanting to share personal information like that. So, I went on to here: MediaWiki.

(Main.) I want to make one or two, (I certainly do not know.) micronation-related pages on MediaWiki. (because if I make an entire wiki to micronations, that is LITERALLY copying MicroWiki. So, is that okay, or violating the MediaWiki requirements? Please let me know!

From one of your biggest fans: PolskiMazowiecka! PolskiMazowieckowa! (talk) 00:22, 15 January 2024 (UTC)

I meant: PolskiMazowieckowa! PolskiMazowieckowa! (talk) 00:23, 15 January 2024 (UTC)

I also meant: (.......copying MicroWiki.) PolskiMazowieckowa! (talk) 00:29, 15 January 2024 (UTC)

I might do a couple, (maybe 12?????) micronation-related pages. PolskiMazowieckowa! (talk) 00:30, 15 January 2024 (UTC)

Good? PolskiMazowieckowa! (talk) 00:30, 15 January 2024 (UTC)

No you can't, see Project:About#What MediaWiki.org is not. But you can host your own wiki and anything you want; see Download and Hosting_services. – Ammarpad (talk) 11:28, 15 January 2024 (UTC)

Thank you so much! Can I do it on Meta-Wiki? PolskiMazowieckowa! (talk) 13:04, 15 January 2024 (UTC)

I could not find "Project:About#What MediaWiki.org is not" on my own. PolskiMazowieckowa! (talk) 13:04, 15 January 2024 (UTC)

Eariler. PolskiMazowieckowa! (talk) 13:06, 15 January 2024 (UTC)

Yeah, but I do not want to make an entire micronation website, (like I said: it is copying MicroWiki.) PolskiMazowieckowa! (talk) 13:06, 15 January 2024 (UTC)

You can create your own wiki if you so desire. Either by hosting it yourself or using a provider like https://miraheze.org (you probably want the second option)

You cannot use meta wiki as that is not its purpose. Bawolff (talk) 07:32, 16 January 2024 (UTC)

Importing / Transferring from Wikipedia

This image could be transferred from Wikipedia to the Wikimedia Commons:

https://en.wikipedia.org/wiki/File:ODF_mask.svg

I read that the file importer is the way to do that, but the steps provided don't match what is seen over at Wikipedia. How can it be imported? Larsnooden (talk) 03:15, 15 January 2024 (UTC)

Please give step by step what you did and what you saw. – Ammarpad (talk) 11:24, 15 January 2024 (UTC)

Thanks

1) I looked at the following page: https://en.wikipedia.org/wiki/Wikipedia:Moving_files_to_Commons

2) and found there is nothing to click on in the Wikipedia page to export anything. Larsnooden (talk) 17:16, 15 January 2024 (UTC)

The export process should starts from https://en.wikipedia.org/wiki/File:ODF_mask.svg.

If you go to the page, look at the navigation ba, you'll see 'Export to Wikimedia Commons' link. (You may not see the link if you're not autoconfirmed) on enwiki. – Ammarpad (talk) 19:29, 15 January 2024 (UTC)

I am not seeing the link. Can someone please import the page to the Wikimedia Commons? 80.220.102.95 (talk) 11:10, 16 January 2024 (UTC)

Thanks, however, it seems that I do not have the 'Export to Wikimedia Commons' link. I'm not autoconfirmed on Wikimedia and am mostly over on Wikibooks. So it might be better if the page can be imported by someone who does have the 'Export to Wikimedia Commons' link available for https://en.wikipedia.org/wiki/File:ODF_mask.svg

It'd be nice to have the history with since it is so old, even though it is so short. That'd be preferable to just adding a fresh page without the provenance. Larsnooden (talk) 10:11, 23 January 2024 (UTC)

Standard for picture upload in MediaWiki

Hi everyone,

we are currently building our own wiki in the it department of a hospital and we installed the MediaWiki Package on our Synology NAS. Everything works fine, but we have a real big problem with the uploading process of pictures. It works, but it needs like 5 or 6 steps to finally upload the picture in your documentation. In every other wiki we tested you just made a screenshot, pressed CTRL + V and you had the picture. Here I have to upload, give it a name, give it a description, give it a size (for example "without border"), change the pixels and then finally upload it. Is there any possibility to change that and reduce the steps as much as possible? For example make a standardsize or anything.

I searched in the FAQ but probably with the wrong words. If there is an explanation or an idea that could help us, I would appreciate it very much.

thank you

greetings

Calvin 80.228.61.67 (talk) 14:21, 15 January 2024 (UTC)

How to list all references of wiki

Hello,

I set up a mediawiki to store operational documents needed for my company.

On each pages I specify regulatory requirements by using cite module (<ref>xxx</ref>)

When there is a modification in a regulatory requirement, I have to update the information contained on pages where that regulatory requirement is used.

In order to retrieve all the pages on wich modifications are required after a regulatory requirement modification, I would need to retrieve all the references used in the whole mediawiki with the pages where a specific reference is used.

- Is there a way to display all the references used in a media wiki with the pages names where they are cited in ?

So far, I did not found my answer in the documentation, that is why I ask to the community.

Thank you very munch for your help.

Best regards Frd2929 (talk) 16:45, 15 January 2024 (UTC)

i would suggest using a template for the reference. You can then use Special:whatlinkshere to find all usages.

If using extension:CirrusSearch you can use the insource operator to search page text, possibly using a regex. See help:extension:CirrusSearch

If the reference uses a specific url, see Special:LinkSearch Bawolff (talk) 13:33, 27 January 2024 (UTC)

GPG keys in "plain text bundle" mentioned in Wikimedia public key list are expired

Hi all,

The "plain text bundle" advertised at https://www.mediawiki.org/keys/keys.html (https://www.mediawiki.org/keys/keys.txt) contains mostly expired keys. These keys can no longer be used to verify MediaWiki downloads as prescribed in the "Download" article. Whom can I alert to this problem, so it can be updated (or removed)?

For the edification of anyone trying to import the GPG keys in order to verify current MediaWiki downloads, there's no actual need to use the plain text version. This is sufficient, since the GPG keys are clearly delimited in the HTML verion:

url https://www.mediawiki.org/keys/keys.html | gpg --import

--Ernstkm (talk) 23:39, 15 January 2024 (UTC)

I think the idea is that this contains historical (now expired) keys to be used to verify old releases as well as modern keys for modern releases. Bawolff (talk) 07:30, 16 January 2024 (UTC)

The real problem is that keys.txt doesn't contain the keys necessary to verify modern releases. Hence the second part of my explanation above. Ernstkm (talk) 21:38, 24 January 2024 (UTC)

Ah i see. Can you file a bug at https://phabricator.wikimedia.org being sure to add mediawiki-releasing to the project field, and be sure that Reedy is added to the subscribers field. Bawolff (talk) 06:32, 25 January 2024 (UTC)

Certainly, thanks for the guidance. Ernstkm (talk) 03:40, 6 February 2024 (UTC)

Bot help

Good evening. I would like to utilize a bot that can create hundreds of pages with the same data. I was curious if there is a bot already made for this and how I could use it. Thank you. New Blue 77 (talk) 04:13, 16 January 2024 (UTC)

why now page name instead of page title ?

Tracked in Phabricator
Task T355318

Tracked in Phabricator
Task T355314

Hi all, When I display a translated page -> https://www.mediawiki.org/wiki/Continuous_integration/Entry_points/fr the page tille now shows the page name "Continuous Integration/Entry Points/Fr"

I expected it to be the value of -> Translations:Continuous integration/Entry points/Page display title/fr that is -> "Intégration continue/Points d'entrée" as done previously. If we observe, the page title is effectively displayed initially but blinks and is overwritten permanently then by the page name.

Why this change occured recently ? Can someone explain ? -- Thanks Christian 🇫🇷 FR (talk) 11:33, 16 January 2024 (UTC)

Please check https://www.mediawiki.org/wiki/Continuous_integration/Entry_points/fr?safemode=1 first. – Ammarpad (talk) 09:12, 18 January 2024 (UTC)

Thanks, sounds better, but does it does not mean we need now to add 'safemode' to all Special:MyLanguage to get the previous result. The safemode seems a blocking action for gadgets and I use some. Then I will investigate a bit around and file a ticket in Phabricator. -- Christian 🇫🇷 FR (talk) 09:24, 18 January 2024 (UTC)

No, it does not mean that. It means your problem is isolated to onwiki user scripts or gadgets. If you do not see a problem with safemode=1 you should probably not create a phabricator task unless you're certain of what you're doing. – Ammarpad (talk) 16:38, 18 January 2024 (UTC)

It is due to Editing gadgets [X] Work in progress: Make pages look like there are common clean up tasks to be done. Unchecking gives now satisfying results. Christian 🇫🇷 FR 🚨 (talk) 18:58, 18 January 2024 (UTC)

Translate Extensions-Editing single sections

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Hi,

I just installed my first mediaWiki (1.40.1) and also installed all necessary extensions to use the extension translate (2023-12-01 MLEB).

I also created many sites in german and create a translation in english.

For now this works great, but I now notice that I'm not able to edite a single section because in the end of the source text there is always a marker.

I tried to adjust the syntax from this:

<languages/>

<translate>

== heading abc ==

Text for translation

</translate>

<translate>

== heading def ==

Text2 for translation

</translate>

to

<languages/>

<translate>

== heading abc ==

Text for translation

</translate>

<translate>

== heading def ==

Text2 for translation

</translate>

But after recreating the translation the marker went back to the original position.

This results in an error that a single section can't be editing because the section looks lilke this:

<languages/>

<translate>

== heading abc ==

Text for translation

</translate>

<translate>

And when I want so safe this he tells me that the maker 2 is empty.

How can I fix this?

Very thanks for your help.

Greeting

90Chris90 90Chris90 (talk) 15:59, 16 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Hook Error after Upgrading from 1.24 to 1.41

I updated a wiki from 1.24 to 1.41 (via 1.33, 1.38). It seems like it mostly went fine but after upgrading the wiki, an error occured while the skin is not loaded:

/wiki/main Exception from line 222 of /var/www/vhosts/wiki/httpdocs/w/includes/Hooks.php: Detected bug in an extension! Hook Cite::checkRefsNoReferences has invalid call signature; Parameter 2 to Cite::checkRefsNoReferences() expected to be a reference, value given

I checked Hooks.php but there is no line 222, the file ends at line 174. I made sure to disable every extension before upgrading. Jap130fritz (talk) 19:34, 16 January 2024 (UTC)

Did you update all extensions as well? Or just the MediaWiki core software? Osnard (talk) 07:27, 17 January 2024 (UTC)

I updated only the extensions that are still supported and deleted the rest of them but I also deactivated every plugin before updating within my LocalSettings. Jap130fritz (talk) 08:03, 17 January 2024 (UTC)

Did you deactivate the Cite extension? Bawolff (talk) 18:28, 18 January 2024 (UTC)

yes, I tried several things with it (updating, removing, deactivating it), but nothing worked Jap130fritz (talk) 08:30, 22 January 2024 (UTC)

File content does not match file extension.

Hie I am uploading pdf documents in application system for my masters and some documents are failing with that message ''File content does not match file extension''

. 105.234.160.2 (talk) 14:28, 17 January 2024 (UTC)

Set collapsible menu as not-exanded on page load?

I have the below code on an index page and would like to have the expandable headers remain closed/collapsed until clicked so that content within these is hidden on page load. I have looked at css for 'aria-expanded' but had no luck applying this to the page - any ideas?

<h3>Introduction</h3>

#[[Link One]]

#[[Link Two]]

<h3>Follow up</h3>

#<h6>Title 1</h6>

##[[Link One]]

##[[Link Two]] David.bucknor (talk) 09:41, 18 January 2024 (UTC)

See if you can use Manual:Collapsible elements —TheDJ (Not WMF) (talk • contribs) 12:56, 18 January 2024 (UTC)

Does this allow the changing of the word 'collapse' and 'expand' to an icon e.g. an arrow?

I'm having a looking at .a.mw-collapsible-text.

The below gets rid of the brackets either side but I want to remove the wording and add an icon ideally.

.mw-collapsible-toggle-default:before, .mw-collapsible-toggle-default:after {

   display: none;

} David.bucknor (talk) 16:33, 24 January 2024 (UTC)

ConfirmEdit/QuestyCaptcha extension throwing on "edit page"

I recently upgraded our Debian OS from old buster to new bookworm (2 major versions) which had mediawiki installed and made a mistake with mediawiki by not running upgrade.php in between, on bullseye, which is explicitly being flagged in the Upgrade document, due to the potential of data loss.

Now it seemed it's all fine at first (luckily), but now users complained that they can't edit sites anymore and receive the error TypeError: in_array(): Argument #2 ($haystack) must be of type array, bool given. I looked at what extensions were installed and commenting out wfLoadExtensions( array( 'ConfirmEdit', 'ConfirmEdit/QuestyCaptcha' ) ); worked. The backtrace is

from /usr/share/mediawiki/extensions-core/ConfirmEdit/includes/Store/CaptchaStore.php(50)

#0 /usr/share/mediawiki/extensions-core/ConfirmEdit/includes/Store/CaptchaStore.php(50): in_array()

#1 /usr/share/mediawiki/extensions-core/ConfirmEdit/SimpleCaptcha/SimpleCaptcha.php(1139): MediaWiki\Extension\ConfirmEdit\Store\CaptchaStore::get()

#2 /usr/share/mediawiki/extensions-core/ConfirmEdit/QuestyCaptcha/includes/QuestyCaptcha.php(83): MediaWiki\Extension\ConfirmEdit\SimpleCaptcha\SimpleCaptcha->storeCaptcha()

#3 /usr/share/mediawiki/extensions-core/ConfirmEdit/SimpleCaptcha/SimpleCaptcha.php(232): QuestyCaptcha->getFormInformation()

#4 /usr/share/mediawiki/extensions-core/ConfirmEdit/SimpleCaptcha/SimpleCaptcha.php(304): MediaWiki\Extension\ConfirmEdit\SimpleCaptcha\SimpleCaptcha->addFormToOutput()

#5 /usr/share/mediawiki/extensions-core/ConfirmEdit/includes/Hooks.php(117): MediaWiki\Extension\ConfirmEdit\SimpleCaptcha\SimpleCaptcha->editShowCaptcha()

#6 /usr/share/mediawiki/includes/HookContainer/HookContainer.php(160): MediaWiki\Extension\ConfirmEdit\Hooks->onEditPageBeforeEditButtons()

#7 /usr/share/mediawiki/includes/HookContainer/HookRunner.php(1501): MediaWiki\HookContainer\HookContainer->run()

#8 /usr/share/mediawiki/includes/EditPage.php(4832): MediaWiki\HookContainer\HookRunner->onEditPageBeforeEditButtons()

#9 /usr/share/mediawiki/includes/EditPage.php(4186): EditPage->getEditButtons()

#10 /usr/share/mediawiki/includes/EditPage.php(3351): EditPage->showStandardInputs()

#11 /usr/share/mediawiki/includes/EditPage.php(779): EditPage->showEditForm()

#12 /usr/share/mediawiki/includes/actions/EditAction.php(73): EditPage->edit()

#13 /usr/share/mediawiki/includes/MediaWiki.php(542): EditAction->show()

#14 /usr/share/mediawiki/includes/MediaWiki.php(322): MediaWiki->performAction()

#15 /usr/share/mediawiki/includes/MediaWiki.php(904): MediaWiki->performRequest()

#16 /usr/share/mediawiki/includes/MediaWiki.php(562): MediaWiki->main()

#17 /usr/share/mediawiki/index.php(50): MediaWiki->run()

#18 /usr/share/mediawiki/index.php(46): wfIndexMain()

#19 {main}

I tried upgrading the extensions with MwExtUpgrader, but that should probably not be necessary, AFAICT it's a debian controlled extension.

Anyone got an idea what to try? Nilsnolde (talk) 21:32, 18 January 2024 (UTC)

Wanted to give FancyCaptcha a try, but after going through all the steps to create the images, it generates another "Fatal Error" (after I had to copy the deprecated "blacklist" file to "badwordfile", the captcha.py script literally expects both!)..

Since this is all PHP/Python and not MySQL related, I just can't see how my failed upgrade path can cause this.. On the other hand this extension must be one of the most popular ones around, on one of the most popular Linux distros, Debian:bookworm. Did maybe the MwExtUpgrader mess things up for some reason?

Should I manually try to re-install the extension with git or tarball or? Nilsnolde (talk) 22:14, 18 January 2024 (UTC)

What is $wgCaptchaStorageClass set to? You might get this error if it is set to an incorrect value (Note its default value should be fine, so normally you wouldn't set it).

Its also possible you might get an error like this if the update didn't work properly and you have a mix of files from different versions of the extension. Bawolff (talk) 13:12, 20 January 2024 (UTC)

Thanks for the reply!

It's the default $wgCaptchaStorageClass = 'CaptchaSessionStore';.

I guess I'll need to manually re-install. It must've been part of the Debian distribution I guess, but maybe MwExtUpgrader did mess it up. I'll try that and report if it helped. Nilsnolde (talk) 08:46, 22 January 2024 (UTC)

> $wgCaptchaStorageClass = 'CaptchaSessionStore';

Note, that is not the current default on more recent versions of the extension, and may cause this error on recent versions of ConfirmEdit. Bawolff (talk) 09:10, 22 January 2024 (UTC)

Huh, thanks for the warning! Strange, can't find anything on that, even the ConfirmEdit Git repo references it as the default class: https://gerrit.wikimedia.org/g/mediawiki/extensions/ConfirmEdit. It doesn't seem to be documented anywhere. I can't make sense of the appropriate code either. Do you have a link to docs by any chance?

FWIW, I just commented out $wgCaptchaStorageClass in LocalSettings.php and that works. Just not sure what the default is and what the implications of that default are.. Nilsnolde (talk) 18:23, 25 January 2024 (UTC)

Tracked in Phabricator
Task T355991

Bawolff (talk) 13:22, 27 January 2024 (UTC)

Is there an extension that requires a user to specify which category the article they're creating is part of before publishing?

Hello, I was wondering (before I try to develop anything myself) if there was some sort of extension or plugin that exists in which each time a user is creating an article they are required to specify which category that this new article is going to be under.

I am trying to keep all of the new articles on the website that I started into categories for people to easily search and use so that incredibly niche topics (which the website will include many INCREDIBLY niche topics so files relating to that thing and also the articles themselves could be easily forgotten and lost) for example could easily be found.

Before publishing the article the user would ideally be required to select from a list of general categories that the prompt would give you, and if you don't select from any, you can't proceed to publish the article. Thanks! Guillaume Taillefer (talk) 21:51, 18 January 2024 (UTC)

Maybe you could do something with Extension:PageForms, but that is probably a pretty heavy handed approach to what you are trying to accomplish. Bawolff (talk) 13:13, 20 January 2024 (UTC)

Upgrade results in MediaWiki internal error

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I have four personal wikis that are in desperate need of updates, due to PHP 7.3 no longer the standard with my host.

Of the four, I chose the smallest, least valued, and newest to test my upgrading skills. After downloading a backup locally and making a copy on the server, I followed this helpful guidance; I had no issues at all, until I tested it by reloading my main page. This is what greeted me:

MediaWiki internal error.
 
Original exception: [ZalabLKgWqslXHQQ5LsYUQAAAAM] /.../index.php/Main_Page   Error: Call to a member function makeKey() on null
Backtrace:
from /home/.../skins/Refreshed/includes/RefreshedTemplate.php(138)
#0 /home/.../includes/skins/SkinTemplate.php(148): RefreshedTemplate->execute()
#1 /home/.../includes/skins/SkinTemplate.php(174): SkinTemplate->generateHTML()
#2 /home/.../includes/Output/OutputPage.php(2947): SkinTemplate->outputPage()
#3 /home/.../includes/MediaWiki.php(978): MediaWiki\Output\OutputPage->output(boolean)
#4 /home/.../includes/MediaWiki.php(613): MediaWiki->main()
#5 /home/.../index.php(50): MediaWiki->run()
#6 /home/.../index.php(46): wfIndexMain()
#7 {main}

Exception caught inside exception handler: [ZalabLKgWqslXHQQ5LsYUQAAAAM] /.../index.php/Main_Page   Error: Call to a member function makeKey() on null
Backtrace:
from /home/.../skins/Refreshed/includes/RefreshedTemplate.php(138)
#0 /home/.../includes/skins/SkinTemplate.php(148): RefreshedTemplate->execute()
#0 /home/.../includes/skins/SkinTemplate.php(174): SkinTemplate->generateHTML()
#0 /home/.../includes/Output/OutputPage.php(2947): SkinTemplate->outputPage()
#0 /home/.../includes/exception/MWExceptionRenderer.php(188): MediaWiki\Output\OutputPage->output()
#0 /home/.../includes/exception/MWExceptionRenderer.php(105): MWExceptionRenderer::reportHTML(Error)
#0 /home/.../includes/exception/MWExceptionHandler.php(134): MWExceptionRenderer::output(Error, integer)
#0 /home/.../includes/exception/MWExceptionHandler.php(251): MWExceptionHandler::report(Error)
#0 /home/.../includes/MediaWiki.php(635): MWExceptionHandler::handleException(Error, string)
#0 /home/.../index.php(50): MediaWiki->run()
#0 /home/.../index.php(46): wfIndexMain()
#10 {main}

I am not that a proficient of a troubleshooter; I tend to follow instructions to the best of my ability, but this is beyond my immediate understanding.

I really do want to understand where I went wrong, so that I can upgrade my more important wikis, presuming this will repeat with each of them.

• MediaWiki version: 1.31
• PHP version 7.3 (orig), 8.1 (current), with earlier versions available
• Database type and version: I don't understand what to put here LeyteWolfer (talk) 22:15, 18 January 2024 (UTC)

Disable the skin refreshed for now. It seems to need an update. —TheDJ (Not WMF) (talk • contribs) 22:19, 18 January 2024 (UTC)

How do I do that? Do I change the Refreshed file name?

Edit: answer is to modify the LocalSettings.php.

Place # in front of the LocalSettings line

#wfLoadSkin( 'Refreshed' );

Also, change

$wgDefaultSkin =

to a different, working skin (ex: monobook). Reupload the LocalSettings file.

Once wiki is working again, update the skin itself to the latest version. (This can be your first & only step, if you're certain your default skin is out-of-date.)

Revert LocalSettings to it's original, pre-commented out state.

Thank you, @TheDJ LeyteWolfer (talk) 22:33, 18 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Can I make tables with rounded corners?

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I want to create a wikitable with rounded corners (of the table-boarder, not the cells), is that possible? PKFP (talk) 10:09, 19 January 2024 (UTC)

See https://developer.mozilla.org/en-US/docs/Web/CSS/border-radius Bawolff (talk) 12:51, 20 January 2024 (UTC)

Thanks, but that doesn't really work as expected.

When I write this code:

{|class="wikitable"; style="border-radius:50px" |Test |Test 2 |- |Test 3 |Test 4 |}

I get this:

So clearly there is something round, but not really the boarder, but the grey background.

Well let's see if it works here:

Test	Test 2
Test 3	Test 4

No, same result. PKFP (talk) 16:31, 20 January 2024 (UTC)

Oh, border collapsing in tables does make that hard.

The best i could come up with was:

{|class="wikitable"; style="border-collapse: separate; border-spacing: 0; border:none;padding:0"
|style="border-top-left-radius: 7px"| Test
|style="border-top-right-radius: 7px"|Test 2
|-
|Test 3
|Test 4
|-
|style="border-bottom-left-radius: 7px"|Test 5
|style="border-bottom-right-radius: 7px"|Test 6
|}

Making:

Test	Test 2
Test 3	Test 4
Test 5	Test 6

Bawolff (talk) 10:00, 21 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Debug Echo notification failiures

Hi. We use Echo for core MediaWiki stuff but also for custom extensions. It seems that it only works when it wants to and while sometimes notifications are received, sometimes they simply aren't even if user preferences are clearly for them to be received. I'm wondering if anyone here can provide some assistance on how to debug this issue and figure out why some notifications aren't getting sent (both web and email wise). Reception123 (talk) 10:31, 19 January 2024 (UTC)

Have you checked for errors ? Manual:How to debug —TheDJ (Not WMF) (talk • contribs) 12:55, 19 January 2024 (UTC)

Yes, I haven't seen anything there related to Echo Reception123 (talk) 20:34, 20 January 2024 (UTC)

I would suggest looking for errors in job queue, and also errors related to DeferredUpdates in the mediawiki debug log. Bawolff (talk) 13:16, 27 January 2024 (UTC)

Can I make expandible elements that replace each other?

So here is a table I made with expendible text:

1	2	3
Text 1 Text 2 Text 3

This is the code for it:

{| class="wikitable" |- |<span class="mw-customtoggle-1">1</span> |<span class="mw-customtoggle-2">2</span> |<span class="mw-customtoggle-3">3</span> |- |colspan="3"|<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-1">Text 1</div><div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-2">Text 2</div><div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-3">Text 3</div> |}

What it does is I have 3 cells in the table that all toggle text into a 4th cell. Now I'd like to make it so, that if I expand one of the Texts with the toggle, that the other Texts disappear, without having to click the toggles for those texts again.

Is that possible? PKFP (talk) 12:29, 19 January 2024 (UTC)

Not with mw-collapsible —TheDJ (Not WMF) (talk • contribs) 12:57, 19 January 2024 (UTC)

How then? PKFP (talk) 13:13, 19 January 2024 (UTC)

Okay, but I think by now I found out, that what I really want is the tab extension. PKFP (talk) 13:14, 19 January 2024 (UTC)

ParserFunctions configuration error

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I'm updating the second of four personal wikis. When it came time to update the database, several extension and skin errors popped up. I updated both extensions and then moved on to the skins. However, following the last skin and running the database update, the two extensions were reported as errors again.

This time, I deleted the entire directory for each extension (instead of overwriting) and then replaced it with the updated extension. However, the errors have not been cleared. LocalSettings has been updated in both cases.

The two extensions are ParserFunctions and Cite.

The error for ParserFunctions:

MediaWiki is unable to load the extension ParserFunctions. Please check that the extension's name is correct and all of its files are properly installed.
Details:
Error reading /ParserFunctions/extension.json. filemtime(): stat failed for /ParserFunctions/extension.json.
#0 /home/.../includes/GlobalFunctions.php(54): ExtensionRegistry->queue('/ParserFunction...')
#1 /home/.../LocalSettings.php(159): wfLoadExtension('ParserFunctions')
#2 /home/.../includes/Setup.php(212): require_once('/home/starsh2/p...')
#3 /home/.../includes/WebStart.php(92): require_once('/home/starsh2/p...')
#4 /home/.../index.php(44): require('/home/starsh2/p...')
#5 {main}

The Cite error is similar., which I have commented out for the time being.

• MediaWiki version: 1.32.2 --> 1.41.0
• PHP version 7.3 --> 7.4
• Database type and version: MySQL 5.7.44 LeyteWolfer (talk) 16:39, 19 January 2024 (UTC)

/ParserFunctions/extension.json

It’s looking at the root of the file system /. That can’t be right.

possibly your Manual:$wgExtensionDirectory variable isn’t being properly constructed. Is one of the skins possibly accidentally overriding this variable ? —TheDJ (Not WMF) (talk • contribs) 19:17, 19 January 2024 (UTC)

@TheDJ, it happened because I was stupid.

I completely left out adding the /mw-config to the URL when I was ready to update the database. And then I was responding to the errors that resulted from trying to open the main page.

So, for the last 4 hours, I've copy my (clean) backup over to the previous directory's place and uploaded MW 1.41.0.

However, now when I run the database update, I get only a white screen. No errors...nothing. I've set PHP to 7.4 and 8.1: same thing. Any ideas? LeyteWolfer (talk) 20:01, 19 January 2024 (UTC)

Please ensure PHP errors are set to be displayed. See How to debug Bawolff (talk) 12:50, 20 January 2024 (UTC)

Will do, @Bawolff. Thank you. LeyteWolfer (talk) 14:04, 20 January 2024 (UTC)

@Bawolff

cc: @TheDJ

That addition allowed me to work thru some errors myself.

Full background: I started all over, clean slate. I reuploaded my backups (database & files), added MW 1.41.0, made the change to LocalSettings and I feel more confident now handling the errors. Here's what I'm seeing now:

• "Warning: Undefined variable $wgCommandLineMode in /home/starsh2/public_html/fangs/LocalSettings.php on line 30"
• This appears above (and somewhat obscured by the MediaWiki logo) the "MediaWiki 1.41.0 installation: Existing wiki" screen. It's asking for the Upgrade Key, which I am ready to provide, but I'm not sure if I should resolve that line 30 error first.

Lines 30-34, LocalSettings:

if ( $wgCommandLineMode ) {
	if ( isset( $_SERVER ) && array_key_exists( 'REQUEST_METHOD', $_SERVER ) ) {
		die( "This script must be run from the command line\n" );
	}
}

I'm anticipating you'll tell me that has been deprecated (as it's a holdover from MW 1.32.2); if so, do I just delete the lines from the LocalSettings? LeyteWolfer (talk) 19:02, 20 January 2024 (UTC)

Yes, it is safe to delete those lines. Bawolff (talk) 20:15, 20 January 2024 (UTC)

@Bawolff

cc: @TheDJ

Thank you for the help, both of you. I appear to have the 2nd wiki up and running again. LeyteWolfer (talk) 20:39, 20 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

just a short question

I can figure out what Template Code is, but how is it used? Duiepyle (talk) 04:34, 20 January 2024 (UTC)

Does help:Templates answer your question? Bawolff (talk) 12:49, 20 January 2024 (UTC)

Qui merci beaucoup et bonne nuit 74.56.50.196 (talk) 05:44, 23 January 2024 (UTC)

Brunsviga

Hello, I'm a french contributor. I'm trying to put an English version of my article Brunsviga. I cretated a sandbox but I'm unable to :

find the level of titles (main title, section1, subtitle...)

and to insert the sources, when I type Insert it doesn't propose to me the frame to writte name of. the autthor, title of the book, and so on. how please can I do ?thank you very much best regards Thémisté (talk) 10:54, 20 January 2024 (UTC)

if this is about wikipedia, consider asking at w:WP:TEAHOUSE Bawolff (talk) 13:14, 27 January 2024 (UTC)

Thank you very much Bawolff

Regards Thémisté Thémisté (talk) 19:32, 28 January 2024 (UTC)

Unable to login

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Have just upgraded my MW from 1.32.2 to 1.41.0.

After a number of problems—and assistance from here—the database update went through. However, now neither of my bureaucrat accounts work; both get the "Auto-creation of a local account failed: Automatic account creation is not allowed" message. A user also got the same message, when asked to test.

Might be relevant: I do have auto-creation turned off and I build new accounts (rarely) from phpMyAdmin. I thought about doing that now, but then I wouldn't have bureaucrat authority.

Also relevant: I do have a pre-upgrade backup of both the wiki and the database.

How do I recover from this?

• MediaWiki version: 1.32.2 --> 1.41.0
• PHP version 7.3 --> 8.1
• Database type and version: MySQL 5.7.44

• Browser: Firefox 121.0.1, standard settings
• cookies cleared

I found this similar problem, assisted by @Bawolff, from three years ago, but don't have a clue as how to try OP's method of restoring his admin account. LeyteWolfer (talk) 21:34, 20 January 2024 (UTC)

We do not recommend creating new accounts by editing the database manually (Changing passwords of existing accounts via the DB as a last resort is ok). This may result in referential integrity issues, especially with the actor table on newer versions of MediaWiki.

Instead i would suggest using the CreateAndPromote.php command line maintenance script.

What method are you using to restrict account creation? Bawolff (talk) 09:46, 21 January 2024 (UTC)

Thank you, @Bawolff. Lesson understood (reg: manual DB creation).

The CreatandPromote script looks ideal for getting back in. I have a friend to instruct me on how to access and use it.

As for how I restrict account creation, my LocalSettings has $wgGroupPermissions['*']['createaccount'] set to false. LeyteWolfer (talk) 14:32, 21 January 2024 (UTC)

@Bawolff,

My host was unable to give me command line access for security reasons, but offered to run it for me with the guidance from Manual:createAndPromote.php.

The following is the reports they received with each attempt (their narrative is in bold); I've included placeholder name & temporary passwords:

All scripts were executed from the following folder:

- home/starsh2/public_html/fangs/maintenance

1st:

[starsh2@s145 maintenance]$ php createAndPromote.php Dan G,%HwW$cyK --bureaucrat --force
*******************************************************************************
NOTE: Do not run maintenance scripts directly, use maintenance/run.php instead!
      Running scripts directly has been deprecated in MediaWiki 1.40.
      It may not work for some (or any) scripts in the future.
*******************************************************************************
starsh2_fangs: Promoting User:Dan into bureaucrat...
InvalidArgumentException from line 810 of /home/starsh2/public_html/fangs/includes/user/UserGroupManager.php: UserGroupManager::addUserToGroup() needs a positive user ID. Perhaps addUserToGroup() was called before the user was added to the database.
#0 /home/starsh2/public_html/fangs/includes/user/UserGroupManager.php(928): MediaWiki\User\UserGroupManager->addUserToGroup()
#1 /home/starsh2/public_html/fangs/maintenance/createAndPromote.php(154): MediaWiki\User\UserGroupManager->addUserToMultipleGroups()
#2 /home/starsh2/public_html/fangs/maintenance/includes/MaintenanceRunner.php(703): CreateAndPromote->execute()
#3 /home/starsh2/public_html/fangs/maintenance/doMaintenance.php(100): MediaWiki\Maintenance\MaintenanceRunner->run()
#4 /home/starsh2/public_html/fangs/maintenance/createAndPromote.php(213): require_once('/home/starsh2/p...')
#5 {main}

As per the warning message found in step one, I adjusted the script:

2nd:

[starsh2@s145 maintenance]$ php run.php createAndPromote.php dan G,%HwW$cyK --bureaucrat --force
starsh2_fangs: Promoting User:dan into bureaucrat...
InvalidArgumentException from line 810 of /home/starsh2/public_html/fangs/includes/user/UserGroupManager.php: UserGroupManager::addUserToGroup() needs a positive user ID. Perhaps addUserToGroup() was called before the user was added to the database.
#0 /home/starsh2/public_html/fangs/includes/user/UserGroupManager.php(928): MediaWiki\User\UserGroupManager->addUserToGroup()
#1 /home/starsh2/public_html/fangs/maintenance/createAndPromote.php(154): MediaWiki\User\UserGroupManager->addUserToMultipleGroups()
#2 /home/starsh2/public_html/fangs/maintenance/includes/MaintenanceRunner.php(703): CreateAndPromote->execute()
#3 /home/starsh2/public_html/fangs/maintenance/run.php(51): MediaWiki\Maintenance\MaintenanceRunner->run()
#4 {main}

Tried to use a different password and skip the group option:

3rd:

[starsh2@s145 maintenance]$ php run.php createAndPromote.php Dan G314HwW2cyK --force
[69af9edaeef173527e09b595] [no req]   TypeError: MediaWiki\User\UserNameUtils::getCanonical(): Argument #1 ($name) must be of type string, null given, called in /home/starsh2/public_html/fangs/includes/auth/LocalPasswordPrimaryAuthenticationProvider.php on line 217
Backtrace:
from /home/starsh2/public_html/fangs/includes/user/UserNameUtils.php(257)
#0 /home/starsh2/public_html/fangs/includes/auth/LocalPasswordPrimaryAuthenticationProvider.php(217): MediaWiki\User\UserNameUtils->getCanonical()
#1 /home/starsh2/public_html/fangs/includes/auth/AuthManager.php(990): MediaWiki\Auth\LocalPasswordPrimaryAuthenticationProvider->providerAllowsAuthenticationDataChange()
#2 /home/starsh2/public_html/fangs/includes/user/User.php(1894): MediaWiki\Auth\AuthManager->allowsAuthenticationDataChange()
#3 /home/starsh2/public_html/fangs/maintenance/createAndPromote.php(165): MediaWiki\User\User->changeAuthenticationData()
#4 /home/starsh2/public_html/fangs/maintenance/includes/MaintenanceRunner.php(703): CreateAndPromote->execute()
#5 /home/starsh2/public_html/fangs/maintenance/run.php(51): MediaWiki\Maintenance\MaintenanceRunner->run()
#6 {main}

Can you check with MediaWiki on how to proceed?

As you can see, they are being rather accommodating in seeing me through this. In the second and third attempts, they used the run.php script called for by MW 1.41.0.

Would you please interpret the relevant errors? LeyteWolfer (talk) 19:11, 21 January 2024 (UTC)

I don't know what is up with the third attempt with run.php. I guess run.php is buggy. Personally I don't understand what the point of run.php is, but i suppose that is neither here nor there.

Anyways, for the first version, where you run it directly: Could you try using a new username that doesn't exist yet (So it is creating a brand new account), and not running it with --force argument ? Bawolff (talk) 21:04, 21 January 2024 (UTC)

I'll pass that along. I actually suggested they do that exact same thing, but with the run.php method. I'll pass this along and will let you know the result.

Thank you. LeyteWolfer (talk) 21:31, 21 January 2024 (UTC)

@Bawolff,

We're in...sorta. Your idea of running createAndPromote without the run.php script and for a new account worked.

[starsh2@s145 maintenance]$ php createAndPromote.php NewAdmin G53HwW1cyK --bureaucrat
 
 ******************************
*************************************************
 NOTE: Do not run maintenance scripts directly, use maintenance/run.php instead!
      Running scripts directly has been deprecated in MediaWiki 1.40.
      It may not work for some (or any) scripts in the future.
 *******************************************************************************
 
 starsh2_fangs: Creating and promoting User:NewAdmin into bureaucrat...
 done.

There are some massive errors encountered that prevents anything else from being done, but I'll put that into a new ticket.

Thank you, Bawolff. I'm frustrated that with each victorious solution uncovers new errors, but it is progress. LeyteWolfer (talk) 22:55, 21 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Upgrading with no content, no functionality

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

As part of the success from the preceding topic, a new bureaucrat account was created (via createAndPromote.php).

However, there is no content and every action results in an error:

• Main page:

Error
There is currently no text in this page. You can search for this page title in other pages, search the related logs, or create this page.

The search link displays an identical error, the related logs link does load the proper page (All public logs), but with no results, and the creation link opens up a blank text field with the following error just above it:

The revision #0 of the page named "Main Page" does not exist.
This is usually caused by following an outdated history link to a page that has been deleted. Details can be found in the deletion log.

• Recent changes:

Does work as expected, but has the maintenance script use (from the previous topic) as the only entry.

• Special pages:

[Za2k5Gy3C8PjhKP5Rw0CFAAAAI0] /fangs/index.php/Special:SpecialPages   ArgumentCountError: Too few arguments to function MediaWiki\Specials\SpecialRenameUser::__construct(), 0 passed in /home/starsh2/public_html/fangs/vendor/wikimedia/object-factory/src/ObjectFactory.php on line 240 and exactly 8 expected

Backtrace:

from /home/starsh2/public_html/fangs/includes/specials/SpecialRenameUser.php(45)
 #0 /home/starsh2/public_html/fangs/vendor/wikimedia/object-factory/src/ObjectFactory.php(240): MediaWiki\Specials\SpecialRenameUser->__construct()
 #1 /home/starsh2/public_html/fangs/vendor/wikimedia/object-factory/src/ObjectFactory.php(149): Wikimedia\ObjectFactory\ObjectFactory::getObjectFromSpec()
 #2 /home/starsh2/public_html/fangs/includes/specialpage/SpecialPageFactory.php(1474): Wikimedia\ObjectFactory\ObjectFactory->createObject()
 #3 /home/starsh2/public_html/fangs/includes/specialpage/SpecialPageFactory.php(1509): MediaWiki\SpecialPage\SpecialPageFactory->getPage()
 #4 /home/starsh2/public_html/fangs/includes/specials/SpecialSpecialPages.php(64): MediaWiki\SpecialPage\SpecialPageFactory->getUsablePages()
 #5 /home/starsh2/public_html/fangs/includes/specials/SpecialSpecialPages.php(53): MediaWiki\Specials\SpecialSpecialPages->getPageGroups()
 #6 /home/starsh2/public_html/fangs/includes/specialpage/SpecialPage.php(727): MediaWiki\Specials\SpecialSpecialPages->execute()
 #7 /home/starsh2/public_html/fangs/includes/specialpage/SpecialPageFactory.php(1621): MediaWiki\SpecialPage\SpecialPage->run()
 #8 /home/starsh2/public_html/fangs/includes/MediaWiki.php(357): MediaWiki\SpecialPage\SpecialPageFactory->executePath()
 #9 /home/starsh2/public_html/fangs/includes/MediaWiki.php(960): MediaWiki->performRequest()
 #10 /home/starsh2/public_html/fangs/includes/MediaWiki.php(613): MediaWiki->main()
 #11 /home/starsh2/public_html/fangs/index.php(50): MediaWiki->run()
 #12 /home/starsh2/public_html/fangs/index.php(46): wfIndexMain()
 #13 {main}

• Preferences:

[Za2lNWy3C8PjhKP5Rw0CgAAAAIE] /fangs/index.php/Special:Preferences   Error: Class "MonoBookTemplate" not found

Backtrace:

from /home/starsh2/public_html/fangs/skins/Modern/SkinModern.php(51)
 #0 /home/starsh2/public_html/fangs/includes/AutoLoader.php(221): require()
 #1 /home/starsh2/public_html/fangs/vendor/wikimedia/object-factory/src/ObjectFactory.php(240): AutoLoader::autoload()
 #2 /home/starsh2/public_html/fangs/vendor/wikimedia/object-factory/src/ObjectFactory.php(149): Wikimedia\ObjectFactory\ObjectFactory::getObjectFromSpec()
 #3 /home/starsh2/public_html/fangs/includes/skins/SkinFactory.php(139): Wikimedia\ObjectFactory\ObjectFactory->createObject()
 #4 /home/starsh2/public_html/fangs/includes/skins/SkinFactory.php(188): SkinFactory->makeSkin()
 #5 /home/starsh2/public_html/fangs/includes/preferences/DefaultPreferencesFactory.php(959): SkinFactory->getSkinOptions()
 #6 /home/starsh2/public_html/fangs/includes/preferences/DefaultPreferencesFactory.php(254): MediaWiki\Preferences\DefaultPreferencesFactory->skinPreferences()
 #7 /home/starsh2/public_html/fangs/includes/preferences/DefaultPreferencesFactory.php(1895): MediaWiki\Preferences\DefaultPreferencesFactory->getFormDescriptor()
 #8 /home/starsh2/public_html/fangs/includes/specials/SpecialPreferences.php(147): MediaWiki\Preferences\DefaultPreferencesFactory->getForm()
 #9 /home/starsh2/public_html/fangs/includes/specials/SpecialPreferences.php(114): MediaWiki\Specials\SpecialPreferences->getFormObject()
 #10 /home/starsh2/public_html/fangs/includes/specialpage/SpecialPage.php(727): MediaWiki\Specials\SpecialPreferences->execute()
 #11 /home/starsh2/public_html/fangs/includes/specialpage/SpecialPageFactory.php(1621): MediaWiki\SpecialPage\SpecialPage->run()
 #12 /home/starsh2/public_html/fangs/includes/MediaWiki.php(357): MediaWiki\SpecialPage\SpecialPageFactory->executePath()
 #13 /home/starsh2/public_html/fangs/includes/MediaWiki.php(960): MediaWiki->performRequest()
 #14 /home/starsh2/public_html/fangs/includes/MediaWiki.php(613): MediaWiki->main()
 #15 /home/starsh2/public_html/fangs/index.php(50): MediaWiki->run()
 #16 /home/starsh2/public_html/fangs/index.php(46): wfIndexMain()
 #17 {main}

What should be my first step in triage? I feel like this is just a connection problem between the MW install and the content. My wiki is huge (by my standards) at 24.4 gb and the material is still there. LeyteWolfer (talk) 23:14, 21 January 2024 (UTC)

Ok, the special page errors sound like there might be a mix of files from two different versions of mediawiki installed. I would reccomend redownloafing MediaWiki and replacing all its files with a new version (see Upgrading) along with extension files.

For the missing content - i would try and fix the special page issue first in case it is related. I highly reccomend backing up the database just in case. If the fix for special page doesnt fix it, my guess is it is related to actor table. (If you have a backup) some people have better luck upgrading to mediawiki 1.31 first, and then 1.35, then running cleanupUsersWithNoId.php, and then migrateActors.php and then 1.39. If that is not an option there are other things we could try. Bawolff (talk) 09:21, 22 January 2024 (UTC)

@Bawolff,

== Addressing the errors ==

This is an upgrade from 1.32.2. Did I do something wrong when I put 1.41.0 directly into the top directory?

As for extensions: I hadn't upgraded the extensions before I did the database upgrade. Would it be cleaner to just remove ALL the extensions and update them after a successful upgrade?

== Starting Over ==

In light of the large number of errors I've experienced with the 1.32.2-->1.41.0 attempt, would you recommend I start over (I have the original backups) and upgrade incrementally to 1.39 per the above?

Edit: Reading thru that entire page, it seems like it would be best for me to start over, so I'm off to do that. My plan is to go 1.32.2 -->1.35.14-->1.41.0 for this wiki (running cleanupUsersWithNoId.php and then migrateActors.php after 1.35), and then my two most valued wikis 1.29.2-->1.35.14-->1.41.0. If you have any warnings about this plan, I'd like to know. You also suggested up to 1.39; was that a preference over the latest stable version of 1.41 or another intermediary step to 1.41?

Thank you for leading me to the information I've needed to educate myself better on this, as well as all the other assistance you've provided. LeyteWolfer (talk) 12:31, 22 January 2024 (UTC)

> This is an upgrade from 1.32.2. Did I do something wrong when I put 1.41.0 directly into the top directory?

I would recommend extracting to a different directory and replacing the directory. Extracting directly over top can sometimes leave different versions of files intermixed, which can cause problems.

> Reading thru that entire page, it seems like it would be best for me to start over, so I'm off to do that. My plan is to go 1.32.2 -->1.35.14-->1.41.0 for this wiki (running cleanupUsersWithNoId.php and then migrateActors.php after 1.35), and then my two most valued wikis 1.29.2-->1.35.14-->1.41.0. If you have any warnings about this plan, I'd like to know. You also suggested up to 1.39; was that a preference over the latest stable version of 1.41 or another intermediary step to 1.41?

I meant 1.39 as an intermediary step. Well most people don't need this, some people have reported issues with the actor migration, and reported that using more intermediary steps fixed their problem. Bawolff (talk) 18:39, 22 January 2024 (UTC)

> I would recommend extracting to a different directory and replacing the directory. Extracting directly over top can sometimes leave different versions of files intermixed, which can cause problems.

I was missing that step, as I've always unpacked locally and then uploaded into the existing directory. This "other files" section was the entire checklist that I haven't been doing. Thank you for this tidbit, as well. LeyteWolfer (talk) 18:48, 22 January 2024 (UTC)

@Bawolff,

Ok...I've been rather methodical preparing for this new attempt. I've prepped for each stage up to 1.41.0 and just now, for the 1.32.2-->1.35.14 phase, I started the configuration process with mw-config/index.php. When I "continue"-ed from the installation screen to the Existing Wiki screen, I received the following error:

[Za-1WBtC_Wd9E_wQiw6_uAAAAhc] /fangs/mw-config/index.php?page=ExistingWiki   Exception from line 185 of /home/starsh2/public_html/fangs/includes/registration/ExtensionRegistry.php: Unable to open file /home/starsh2/public_html/fangs/extensions/ParserFunctions/extension.json: filemtime(): stat failed for /home/starsh2/public_html/fangs/extensions/ParserFunctions/extension.json
<code>
Backtrace:
# 0 /home/starsh2/public_html/fangs/includes/GlobalFunctions.php(51): ExtensionRegistry->queue(string)
 #1 /home/starsh2/public_html/fangs/LocalSettings.php(160): wfLoadExtension(string)
 #2 /home/starsh2/public_html/fangs/includes/installer/Installer.php(661): require(string)
 #3 /home/starsh2/public_html/fangs/includes/installer/WebInstallerExistingWiki.php(29): Installer::getExistingLocalSettings()
 #4 /home/starsh2/public_html/fangs/includes/installer/WebInstaller.php(269): WebInstallerExistingWiki->execute()
 #5 /home/starsh2/public_html/fangs/mw-config/index.php(82): WebInstaller->execute(array)
 #6 /home/starsh2/public_html/fangs/mw-config/index.php(40): wfInstallerMain()
 #7 {main}

I upgraded the ParserFunctions extension to the 1.39 version (oldest one I found available) prior to starting the configuration process.

What do I need to fix (and how)? LeyteWolfer (talk) 12:54, 23 January 2024 (UTC)

Its essentially saying that ParserFunctions extension doesn't exist on the file system at all. Like that is probably not a version issue.

Im not sure what that is about, but if it makes things easier, consider just disabling extensions (commenting out wfLoadExtension() in LicalSettings.php) for the upgrade and reenabling them at the end. You shouldnt really need extensions installed to do update. Bawolff (talk) 14:20, 23 January 2024 (UTC)

Well...this is...interesting.

I did as you said: commented out each extensions as the errors progressed and some skins too^{Note 1}. That allowed me to progress to the pre-database update page. When I ran that, I received a long error which included a direction to check out Manual:$wgServer. That led me to add $wgServer = false; as the default value. I got the same/similar error:

Original exception: [Za_i7P-UMmMiWHg2juxnTwAAABE] [no req] FatalError from line 545 of /home/starsh2/public_html/fangs/includes/Setup.php: $wgServer must be set in LocalSettings.php. See <a href="https://www.mediawiki.org/wiki/Manual:$wgServer">https://www.mediawiki.org/wiki/Manual:$wgServer</a>.

I then did as the Details section directed and added my base URL for the server: http://mypersonaldomain.com. No wwww., no wiki directory (/fangs), putting it right before the :

if ( $wgCommandLineMode ) {
	if ( isset( $_SERVER ) && array_key_exists( 'REQUEST_METHOD', $_SERVER ) ) {
		die( "This script must be run from the command line\n" );
	}
}

This time, when I refreshed the browser, it was all white: no errors, no Main Page...nothing. I then vaguely remembered either @TheDJ or yourself had told me to comment out that last statement (the $wgCommandLineMode), so I commented out all 5 lines. Refresh: same result, all white.

So, for clarity's sake, this is what my LocalSettings has right now:

$wgServer = http://mypersonaldomain.com;
#if ( $wgCommandLineMode ) {
#	if ( isset( $_SERVER ) && array_key_exists( 'REQUEST_METHOD', $_SERVER ) ) {
#		die( "This script must be run from the command line\n" );
#	}
#}

Note 1: On each of the Extension and Skin pages, the extensions/skins mentioned they were bundled since MW 1.21, but "you still need to follow the other instructions provided." So, I had added them to the LocalSettings. I'm now interpreting that to support your statement about "re-enabling them at the end." LeyteWolfer (talk) 16:13, 23 January 2024 (UTC)

You are missing quote marks:

$wgServer = 'http://mypersonaldomain.com'; Bawolff (talk) 18:05, 23 January 2024 (UTC)

Yes I did...yes...I...did. Thank you for catching that.

Ok, so after I corrected that, I received some errors regarding skins (Modern & MonoBook), so I uncommented those and then received different errors related to them; I commented them back again and after a few other rabbit trails, I lost confidence in my changes. I believed that the database may have been altered too much to get out from under it.

So, I started over: clean (backup) database, clean (backup) MW directory. I went through all the steps, up until I came to the MediaWiki 1.35.14 installation screen with Install: Setting up database on it; This error appeared right under the Setting up database:

[ZbAM_8DXDS01OMMjpVyT7AAAAMM] /fangs/mw-config/index.php?page=Install   Wikimedia\Rdbms\DBQueryError from line 1713 of /home/starsh2/public_html/fangs/includes/libs/rdbms/database/Database.php: A database qu

It ends just like that, as if it was going to say "query" but got cut off. The right sidebar offers "Restart installation" as the only active link. I did try that, but the errors started cropping up again. So—once again—I started over: clean (backup) database, clean (backup) MW directory. I decided to get up to this first error (above) and contact you again. And here is where I'm at.

Edit: Line 1713 of Database.php reads:

			return new DBQueryError( $this, $error, $errno, $sql, $fname );

Edit: I've found this problem discussion, where running update.php is suggested. I have to have the host run it, but will hold off on doing so, in case there is a better solution (one I can do myself). LeyteWolfer (talk) 19:09, 23 January 2024 (UTC)

@Bawolff: I went ahead and had my host's tech support team run update.php. They also corrected a misspelling of "true" I had written in for $wgShowSQLErrors and assigned the starsh2_fangs MySQL user to starsh2_fangs Mysql database.

So, I re-ran the installation. The Main Page attempted to load, but cried about not having MonoBook installed. Since version 1.39 of that skin is the latest available on this site, I copied the one I had in my previous MW (v 1.32.2) over to the new directory.

Reloading the main page then displayed a main page with everything in a lines aligned to the left side, which was limited to "Login required", "Jump to navigationJump to search", "Please log in to view other pages.", and the basic contents of the Navigation menu.

What do you recommend?

Edit: I also received a 22-page transcript of the installation from my host. It has an interesting error (User name "Jimmy the Tulip" is usable, cannot create an anonymous actor for it. Run maintenance/cleanupUsersWithNoId.php to fix this situation.) that repeats three more times at different times over the 7-second process. That was the only one that caught my eye, because of the familiarity with that user, so there might be others. LeyteWolfer (talk) 09:59, 25 January 2024 (UTC)

That error may explain why some pages are missing. Its important to run the script and to run it on a version somewhere around 1.32 to 1.35.

I wouldnt worry about ui issues until you have updated to the latest version. Its probably due to using the wrong version of monobook. Its possible to download older versions of monobook from github, but i wouldnt bother as that is superficial. What is more important is making sure data is present. Bawolff (talk) 16:01, 25 January 2024 (UTC)

The host tech support is questioning why I want them to run this particular script (maintenance/cleanupUsersWithNoId.php). Am I to tell them it is to make sure data is present and it is important to run it prior to upgrading past 1.35?

To be clear: I appear to have successfully installed 1.35 (though I could email you the transcript, if you were so inclined). Was maintenance/cleanupUsersWithNoId.php (or update.php) to be run prior to my going from upgrading from 1.32? LeyteWolfer (talk) 16:21, 25 January 2024 (UTC)

@Bawolff, I went ahead and presumed it was the cleanup script you wanted me to run and I've finally reached tech support personnel this evening ready to do so. Now, however, they are reporting two issues. Right after running the script with php /home/starsh2/public_html/fangs/maintenance/cleanupUserWithNoID.php:

• the first return in the report is sh: http://mypersonaldomain.com: No such file or directory
• then Param prefix required!

I'm have enough clues to understand they are supposed to append something from [1], but not what other ones than --prefix. The screencap they sent me shows far more arguments that could be appended.

If you would, please provide me with some context as to what I need to be telling them (other than just running the script). LeyteWolfer (talk) 00:01, 26 January 2024 (UTC)

Manual:cleanupUsersWithNoId.php has more info on arguments. The --prefix argument is the only one you need. The other optional parameters probably dont matter to your usecase. A common value is 'imported>' however, be sure to put the prefix value in quotes.

for the

sh: http://mypersonaldomain.com: No such file or directory

Im not 100% sure, but my guess would be that maybe one of the arguments wasn't quoted properly.

After the cleanupUsersWithNoID.php script runs succesfully, run migrateActors.php after it. Bawolff (talk) 02:57, 26 January 2024 (UTC)

Building on what you just posted, @Bawolff: I've been told that an earlier Tech Support rep "assigned starsh2_fangs MySQL user to starsh2_fangs Mysql database" earlier today. It turns out that when I renamed & then dropped the starsh2_fangs database those two times before, to start fresh with a backup, the "starsh2_fangs MySQL user" stayed with the original dropped database. The rep fixed that.

Knowing that, what do you recommend:

• should I run the installation process again, against the present database (with the connected mySQL user), to see if that clears up the problems?
• would you suggest starting all over again (loading a copy of the backup database), but assign those contacts to the new database first, before running the installation against that?
• on the present status, run Manual:cleanupUsersWithNoId.php (with the --prefix argument this time) and then migrateActors.php before anything else?
• another suggestion from you? LeyteWolfer (talk) 03:16, 26 January 2024 (UTC)

If the mysql user didn't have sufficient rights, you would be getting permission errors when doing all these steps. If you haven't then its probably ok.

I would run the cleanupUsersWithNoID.php followed by migrateActors.php and see where that gets you. If you get no errors (and all the contents of the wiki seem to still be there), i would continue upgrading to the next mediawiki version. Bawolff (talk) 03:44, 26 January 2024 (UTC)

@Bawolff, please correct my submission below, as I have littleo clue as to what it should look like exactly and I have doubts about that greater-than symbol after "imported" you included 16 hours ago.

$ php maintenance/cleanupUsersWithNoId.php --prefix 'imported>' LeyteWolfer (talk) 19:25, 26 January 2024 (UTC)

Oh,i guess it adds the > automatically so you dont need to specify it. You can chose whatever you want as the prefix. Bawolff (talk) 12:59, 27 January 2024 (UTC)

@Bawolff, to be clear, you are telling me that I should/can submit

$ php maintenance/cleanupUsersWithNoId.php --prefix 'imported'

as the argument to run?

The reason I'm asking for this specificity is because HostPapa, my host, is extremely inconsistent and is averaging less than one response a day to my requests. I'd really like to get thru this as soon as possible. 70.108.11.203 (talk) 13:20, 27 January 2024 (UTC)

Yes Bawolff (talk) 13:22, 27 January 2024 (UTC)

@Bawolff, tech support reports both scripts run with no errors:

[starsh2@s145 fangs]$ php maintenance/cleanupUsersWithNoId.php --prefix 'imported'
 [starsh2@s145 fangs]$ php maintenance/migrateActors.php
 [starsh2@s145 fangs]$

From the browser side, it is showing a blank page. I've adjusted PHP from 8.1 back to 7.3 with the exact same result.

What do you think this indicates and what do you suggest I do now? (I have taken no more actions after they ran those two scripts, not even /mw-config/index.php.) LeyteWolfer (talk) 16:32, 27 January 2024 (UTC)

Can you add error_reporting( -1 );

ini_set( 'display_errors', 1 ); to the top (right after <?php ) of LocalSettings.php ? That may make an error message show up instead of blank page. Also check your php error log. Bawolff (talk) 17:09, 27 January 2024 (UTC)

@Bawolff,

• I did add error_reporting( -1 ); ini_set( 'display_errors', 1 ); to the LocalSettings.php. Refreshing the browser resulted in the same blank page, no error message.
• Just found the error log. Last entry: [27-Jan-2024 17:17:40 UTC] PHP Parse error: syntax error, unexpected end of file in /home/starsh2/public_html/fangs/LocalSettings.php on line 179

In LocalSettings.php, Line 179 reads: $wgActorTableSchemaMigrationStage = MIGRATION_WRITE_NEW. When I reviewed Manual:$wgActorTableSchemaMigrationStage, there were no details for MediaWiki 1.35 nor 1.36 (it skips from 1.34 to 1.37). Googling PHP Parse error: syntax error, unexpected end of file led me to add a space and a semicolon (;) after MIGRATION_WRITE_NEW.

Progress! Now, the page is no longer blank. It shows the sidebar aligned to the far left again.

Checking the error log again (after refreshing the left-aligned browser), I see there are no more new entries.

• Going further back in the error log, two days ago it had the last of 25 entries reading PHP Warning: Trying to access array offset on value of type bool in /home/starsh2/public_html/fangs/includes/Setup.php on line 562.

Line 562 reads: $wgServerName = $serverParts['host'];.

I did not want to attempt any amateurish changes to that line, because it may no longer be relevant based on its older date, right? Suggestions on next step? LeyteWolfer (talk) 18:04, 27 January 2024 (UTC)

Do pages in the wiki work properly? If so continue upgrading to latest mediawiki. (If things seem good right now, consider taking a backup just in case) Bawolff (talk) 19:49, 27 January 2024 (UTC)

I was able to access files, yes, surprisingly. I'm glad you asked me to check.

I'll make that backup and will proceed. Thank you much, @bawolff. LeyteWolfer (talk) 20:05, 27 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Is there a MediaWiki extension that allows for pull request-like proposed changes on-wiki?

What I am looking for is a mechanism that lets git-unaware users of a MediaWiki instance propose changes in a way that allows those changes to be (1) visible by anyone and (2) pulled into a given page or rejected by users with merge rights.

I am aware of Extension:FlaggedRevs and Extension:Approved Revs but both of them operate on the level of revisions of a full page, after the edits have been made. What I am looking for is rather a mechanism to propose changes (similar to a pull request on GitHub), so that those changes can be reviewed (and perhaps modified) before an eventual incorporation into the target page. I know that Extension:Moderation can do that in principle but only for moderators - I would like the proposed changes (whether accepted or not) to be publicly visible, and a straightforward mechanism to merge them into the target. Any pointers are welcome. Daniel Mietchen (talk) 20:30, 22 January 2024 (UTC)

Lua error: Cannot create process: proc_open(/dev/null): failed to open stream: Operation not permitted

Greetings. I've been trying to create a new module on my MediaWiki instance but I'm constantly getting this error. I'm using DirectAdmin for my server. Any help would be appreciated :) Lidistat67 (talk) 20:56, 22 January 2024 (UTC)

That looks like a common error if you have difficulties installing Lua on the server or just don't have the right permissions to do so. See

• https://www.mediawiki.org/wiki/Project%3ASupport%20desk/Flow/2022/10#h-Lua_error%3A_Cannot_create_process%3A_proc_open%28/dev/null%29%3A_failed_to_open_stream%3A_O-20221031125500
• https://www.mediawiki.org/wiki/Extension%20talk%3AScribunto/2017#h-Lua_error%3A_Cannot_create_process%3A_proc_open%28/dev/null%29%3A_failed_to_open_stream%3A-2017-11-05T16%3A51%3A00.000Z

Hope that helps. Cavila 10:12, 23 January 2024 (UTC)

How can I create a bio for and artist

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Wanted to create a bio for and artist Skhid (talk) 03:30, 23 January 2024 (UTC)

@Skhid That's out of scope of this project, though it might fit into Wikipedia's scope if the artist is notable enough. Svartava (talk) 04:59, 23 January 2024 (UTC)

But can you upload that Skhid (talk) 05:01, 23 January 2024 (UTC)

How can I create biography for and artist? Skhid (talk) 05:02, 23 January 2024 (UTC)

Please go to w:WP:AFC 94rain ^Talk 05:02, 23 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Error when attempting to save changes to pages with inserted image

Whenever I save a page that has an image inserted, I receive the following error:

"[6afa48c420945a042fdb8e89] Caught exception of type Wikimedia\Rdbms\DBQueryError"

I'm fairly new to Mediawiki and I'm not sure how to even begin to debug this error. I did try some debug settings in my LocalSettings.php but they haven't been more descriptive than this. Wastelandgunner (talk) 03:53, 23 January 2024 (UTC)

I'm still receiving this issue. I'm running Mediawiki 1.41 and using the following extensions:

HeaderFooter

TemplateData

OATHAuth

ArticleMetaDescription

AdvancedSearch

AdminLinks

CategoryTree

Cargo

CharInsert

CheckUser

cldr

Cite

CiteThisPage

CommonsMetadata

FileImporter

CustomLogs

CodeEditor

Disambiguator

DeleteBatch

Editcount

timeline

EmbedVideo

Gadgets

InputBox

ImageSizeInfoFunctions

LinkSuggest

Loops

WikiEditor

MsUpload

MultimediaViewer

Nuke

PageForms

PageImages

ParserFunctions

Poem

Popups

PDFEmbed

PdfHandler

PortableInfobox

ProtectSite

MobileFrontend

SandboxLink

TimedMediaHandler

UploadWizard

VisualEditor

SyntaxHighlight_GeSHi

Scribunto

SemanticMediaWiki

AjaxShowEditors

CreatePageUw

DataTransfer

Interwiki

Moderation

CodeMirror

Comments

HeaderTabs

Theme

ImageMap

TemplateStyles

Widgets Wastelandgunner (talk) 00:09, 25 January 2024 (UTC)

Please set $wgShowExceptionDetails=true; in LocalSettings.php

Did you try running update.php? Bawolff (talk) 09:03, 25 January 2024 (UTC)

@Bawolff Thanks for the response!

I've already run update.php with no errors, but I still receive the error when saving the page with an image. Setting $wgShowExceptionDetails to true results in the following error when attempting to save the page:

[c96a2f63186b66a46d10fe71] Exception caught: A database query error has occurred. This may indicate a bug in the software. Wastelandgunner (talk) 15:30, 25 January 2024 (UTC)

Is that all? The error message should be much longer than that. Bawolff (talk) 15:56, 25 January 2024 (UTC)

Yep, that was all, unfortunately. That's part of why I'm struggling to figure this out. It's very non-descript. Here's a screenshot as well . Wastelandgunner (talk) 16:44, 25 January 2024 (UTC)

Can you check your php error log. See also How to debug.

This is from js, so looking at your web browser console network tab may have more information.

If you cant figure it out, try disabling extensions one by one to try and narrow it down. Bawolff (talk) 13:12, 27 January 2024 (UTC)

VisualEditor Extensions and paragraphs

Hi,

I using Mediawiki 1.40.1 and VisualEditor 0.1.2.

When I write a Text in VisualEditor and want to go the the next line, he added me a blank line and then start in the third line tiping.

How can I prohibit this?

Thanks for help. 90Chris90 (talk) 08:20, 23 January 2024 (UTC)

Automated Plugin for Language Translation

Dear Support,

I was looking for a plugin to translate our mediawiki automatically from DE -> EN and vise versa. If i enter something i would see like a button "Traslate"

Is something available? Otacon01 (talk) 14:17, 23 January 2024 (UTC)

Magic Word returning username of logged in user?

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Is there a magic word that returns the username of a logged in user? I'm trying to let editors create their own navbars, embedded in the standard navbar we have on the bottom of (almost) every page. I'm thinking of something like this to include a personal navbar in the navbar, if that exists:

{{#ifexist: Template:Navbar/Personal/{{USERNAME}} | {{Navbar/Personal/{{Username}}}} | }}

PS: Okay it seems I have to install Extension:UserFunctions and enable it on all namespaces. Then I can use {{#username:alt}} for exactly that. Can someone confirm? PKFP (talk) 15:09, 23 January 2024 (UTC)

Showing the currently logged in user breaks the caching that MediaWiki generally provides for content. This is why you won't find it in vanilla MediaWiki. While the UserFunctions extension provides this functionality, it comes with concerns of cache ability and data leaking that a site administrator should take into account when deciding to use this extension or not. —TheDJ (Not WMF) (talk • contribs) 16:00, 23 January 2024 (UTC)

What does "breaking the caching" mean exactly?

And about data leakage: If I just enable the username feature:

$wgUFEnabledPersonalDataFunctions = [

'username',

];

Will the other data, like IP and stuff, still possibly leak? Because usernames are public anyway, so leaking them shouldn't be too bad, right? PKFP (talk) 09:13, 25 January 2024 (UTC)

Well if you include the username, then every time someone views the page, it will have to be rendered from scratch, while normally Mediawiki will try to reuse previously rendered pages. I’m also not sure how things like cloudflare or other caches react to this.

i can’t say what is and is not dangerous/working, because this code has not gone through Wikimedia code review, its up to you to trust its author. —TheDJ (Not WMF) (talk • contribs) 22:38, 25 January 2024 (UTC)

Okay thanks. Then I guess I'll wait for another solution. :) PKFP (talk) 09:26, 26 January 2024 (UTC)

Extension:MyVariables has a version that still allows caching for logged out users and only messes with caching if logged in, which is slightly better. Bawolff (talk) 13:10, 27 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Hiding text from anonymous users depending on the section

Hello, I'm not sure if this is even possible but I'm trying to hide text from anonymous users in the <div></div> section completely while everything in <span></span> shall only hide the URL of a link (the title shall be still visible).

I added span.anonymous-show {display: inline !important; pointer-events: none !important;} to Group-user.css and "pointer-events: auto !important;" to the "span.user-show" section.

However, when I use <span style="pointer-events: none" class="user-show">[https://www.domain.com/ Domain]</span>, everything is completely hidden, display: none is still applied.

Any idea on how to fix this? Thanks, cheers and all the best! Till Kraemer (talk) 16:55, 23 January 2024 (UTC)

Im confused, where did you specify display:none Bawolff (talk) 13:08, 27 January 2024 (UTC)

I think it's .user-show {display: none;} in Common.css. Till Kraemer (talk) 15:55, 27 January 2024 (UTC)

Well in the above you said span.anonymous-show not span.user-show so the fact they don't match would be the first problem.

Please include all relavent styles and where you put them so we can understand what you have set up (or link to your wiki). Bawolff (talk) 17:12, 27 January 2024 (UTC)

My Group-user.css (NSFW) looks like the one from Wikipedia except for the span.anonymous-show {display: inline !important; pointer-events: none !important;} part and the "pointer-events: auto !important;" part in the "span.user-show" section. My Common.css (NSFW) seems to be pretty similar too. The way I understand it is everything will be hidden with .user-show {display: none;} in Common.css unless it is made visible again in Group-user.css. What I don't understand is how Group-user.css can affect anonymous users. Till Kraemer (talk) 22:18, 27 January 2024 (UTC)

InstantCommons: no images

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Software	Version
MediaWiki	1.41.0
PHP	8.1.27 (fpm-fcgi)
ICU	70.1
MariaDB	10.6.12-MariaDB-0ubuntu0.22.04.1
Pygments	2.16.1
Elasticsearch	7.10.1

Overnight, the $wgUseInstantCommons function ceased functioning. All images sourced from Wikimedia Commons are no longer displayed. However, images hosted internally within the wiki are still working. Vincenʈ  10:34, 25 January 2024 (UTC)

Could the bandwidth usage have been too high? In our wiki, we have about 800 images from Wikimedia Commons, most of the used images are from me. The wiki is accessed only by about 500 visitors a day, with around 2000 page views. Vincenʈ  20:16, 25 January 2024 (UTC)

Apparently there was an error with the Plesk software. After a server restart, the images from Commons are displayed again. Vincenʈ  08:22, 26 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

categorytree on sidebar: some category is not expandible

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I added categorytree on sidebar setting

$wgCategoryTreeSidebarRoot = 'Category:...'; on LocalSettings.php.

It works but some category are not expandible.

The same tree works perfectly if I included it in the page.

The situation is show in figure Gigisoave (talk) 12:03, 25 January 2024 (UTC)

Maybe $wgCategoryTreeSidebarOptions is set to something different than then the default for pages. Bawolff (talk) 13:07, 27 January 2024 (UTC)

Hi Bawolff

thank you for your answer.

$wgCategoryTreeSidebarOptions is not set in the localsettings.php, anyway, after reading your hint, I set

$wgCategoryTreeSidebarOptions['mode'] = "pages";

(that should be the default) and now all the branches are expandible.

It seems that before was set as category. Gigisoave (talk) 13:22, 27 February 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

setting centrelauth to show a List of local accounts, and keep track of global edits.

hello i would like to set centrelauth to show a List of local accounts, and keep track of global edits however im unsure how to set it could someone guide me please and thank youǃ

How it currently looks

How i want it set

Extension:CentralAuth#/media/File:CentralAuth administration demo screenshot.png Cocopuff2018 (talk) 22:49, 25 January 2024 (UTC)

anything? Cocopuff2018 (talk) 18:40, 26 January 2024 (UTC)

Filtering block logs

Is there any way in the api in which i can get usernames only ? Cyberwolf (talk) 13:09, 26 January 2024 (UTC)

Its unclear what you are asking but see Api Bawolff (talk) 13:03, 27 January 2024 (UTC)

where to report security issue to be resolved

Hello, all

can anyone guide me the right resources where can I report security issues reported by DAST analysis on media.wiki used by my organization ? 2603:9001:2300:5E42:351C:2243:EDB8:1ABF (talk) 17:31, 26 January 2024 (UTC)

Please read Reporting security bugs P858snake (talk) 23:22, 26 January 2024 (UTC)

That said, you should determine if the dast findings are real or false positives first. Dast is notorious for having false positives and a dump of findings from a dast without filtering out false positives is not very useful. Bawolff (talk) 13:02, 27 January 2024 (UTC)

Help needed to fight malware injection

Hi there,

we've had our mediawiki in place for 15 years, with little issue until recently. (It's been upgraded periodically over those years, currently to mediawiki 1.41.0).

For the past 6 months or so, users have been complaining that their antivirus SW sees malware on our site. (Same is true of our phpbb forum install on the same site). Avast identifies it as JS/Agent Trojan.

Each javascript file in the install has a little bit of added malicious code at the end.

I have been finding and removing the offending code via grep/sed/vim, and avast is happy for a few days, but then it keeps coming back.

My hosting service was not very helpful, but said that vulnerabilities in the php SW are the reason it keeps coming back.

Has anyone encountered this or something similar? Is there a patch or some setting I can us in mediawiki to block it from recurring? 96.242.218.80 (talk) 18:16, 26 January 2024 (UTC)

No, you should rebuild your mediawiki install from a known-good backup, you never know what they've done. After that, make sure you're running a supported version of MediaWiki, of the extensions, of phpBB, and of PHP itself as well. AllUsernamesArePicked (talk) 18:21, 26 January 2024 (UTC)

Custom Namespaces and Extensions

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Hi there, I have created a custom namespace in my wiki, however I see that the Visual Editor extension is no longer available in that new custom namespace. Does anyone know how to fix this? Do I have to start all over again? Waterlooglass (talk) 21:02, 26 January 2024 (UTC)

I believe you've to use $wgVisualEditorAvailableNamespaces to add your custom namespace. – Ammarpad (talk) 23:08, 26 January 2024 (UTC)

I'll give that a shot, thank you! Waterlooglass (talk) 17:45, 29 January 2024 (UTC)

@Ammarpad that worked, thanks! Waterlooglass (talk) 18:45, 30 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

mediawiki is trying to find extention "Array"

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

after fixing another issue, i'm stuck on an ungoogleable one. i know that "Arrays" exists but when i rename the folder it just fails to load so :/ RealPaxtonPenguin (talk) 02:46, 27 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

wiki keeps redirecting me to wiki/wiki/chaz, instead of wiki/chaz

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

wiki keeps redirecting me to wiki/wiki/chaz, instead of wiki/chaz. not much i can say. wiki/ is a redirect to ./chaz/index.php. wgScriptPath="/wiki/chaz" and wgServer = "http://example.com/wiki" (well not actually but who cares about domain name) RealPaxtonPenguin (talk) 22:56, 27 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

anomally from upgrade from 1.37.1 to 1.41

I upgraded as titled and the VisualEditor extension is no longer an option. I added 4 skins to 1.41 and 1 extension: Renameuser. Generally I run a fairly vanilla mediawiki. Any help is greatly appreciated! 72.196.204.32 (talk) 00:07, 28 January 2024 (UTC)

Clarification, it only works on some of the pages on my wiki. What I can do to see an error message that may be generated on those non-VisualEditor-editable pages? ~ Smashed Cookie (talk) 00:25, 28 January 2024 (UTC)

Is the issue limited to specific namespace or all namespaces? – Ammarpad (talk) 08:37, 28 January 2024 (UTC)

Do the pages that don’t work have spaces or other special characters ?

FYI, rename user is now part of core, you don’t have to install it any longer. —TheDJ (Not WMF) (talk • contribs) 13:35, 28 January 2024 (UTC)

Thank you for the tip about RenameUser, @TheDJ. I'll take it out to avoid version conflicts.

@Ammarpad Yes, this issue appears to be limited to all the pages belonging to any of my portals. Right, the portal pages include a ':' (colon) in the URL. Smashed Cookie (talk) 18:35, 29 January 2024 (UTC)

@TheDJ, @Ammarpad,

Is this a known defect or are portal pages no longer supported by VisualEditor? Smashed Cookie (talk) 14:01, 3 February 2024 (UTC)

Have you followed the instructions at Extension:VisualEditor#Changing active namespaces in order to add the portal namespace to the list of namespaces where VisualEditor is enabled? 86.23.109.101 (talk) 22:37, 3 February 2024 (UTC)

Thank you so much! That solved it!! Smashed Cookie (talk) 22:46, 5 February 2024 (UTC)

Moving pages between wikis

We run two wikis (with interwiki linking set up), and sometimes face the need to move pages from one to the other. So far I've done this by manually copying over the wikitext from one to the other, fixing up images as necessary, then deleting/redirecting the page on the source wiki, but this is a bit tedious - is there a native feature or extension to speed this up? Marksomnian (talk) 16:09, 28 January 2024 (UTC)

meta:help:import#Implementation may be what you need. Arlo Barnes (talk) 16:47, 28 January 2024 (UTC)

Wiki als iFrame einbinden

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Hallo, ich würde gerne mein Wiki zu unserer Software als iFrame in die Software einbinden. Welche Einstellungen muss ich in meiner Mediawiki-Installation vornehmen um das Wiki als iFrame einzubinden?

Danke!

Bertram Bertram Grabert-Naß (talk) 17:02, 28 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

how to setup an account

How to create page in name of saurabh sharma SaurabhSharma2203 (talk) 04:26, 29 January 2024 (UTC)

Blank page, part deux (1.35.14-->1.39.6)

{{{text}}}

Back again with the upgrade greatest hits! (I'm getting a bit punch happy.)

I've done a methodical review of my updated procedures before attempting the upgrade from 1.35.14 (as per the previous incremental upgrade). When starting the upgrade process (i.e., mypersonaldomain.com/fangs/mw-config/index.php), instead of the first expected installation page, I once again saw only the blank page.

In the error log, there were three listed. The first was regarding the (missing) default MonoBook skin, which I took care of. The other two were:

[29-Jan-2024 16:11:34 UTC] PHP Fatal error:  Uncaught Error: Interface "MediaWiki\Hook\BookInformationHook" not found in /home/starsh2/public_html/fangs/includes/HookContainer/HookRunner.php:40
Stack trace:
#0 /home/starsh2/public_html/fangs/includes/AutoLoader.php(244): require()
#1 /home/starsh2/public_html/fangs/includes/Hooks.php(174): AutoLoader::autoload()
#2 /home/starsh2/public_html/fangs/includes/exception/MWExceptionHandler.php(762): Hooks::runner()
#3 /home/starsh2/public_html/fangs/includes/exception/MWExceptionHandler.php(193): MWExceptionHandler::logException()
#4 /home/starsh2/public_html/fangs/includes/exception/MWExceptionHandler.php(247): MWExceptionHandler::rollbackPrimaryChangesAndLog()
#5 /home/starsh2/public_html/fangs/includes/exception/MWExceptionHandler.php(216): MWExceptionHandler::handleException()
#6 [internal function]: MWExceptionHandler::handleUncaughtException()
#7 {main}
  thrown in /home/starsh2/public_html/fangs/includes/HookContainer/HookRunner.php on line 40
[29-Jan-2024 16:13:02 UTC] PHP Fatal error:  Uncaught Error: Interface 'MediaWiki\Hook\BookInformationHook' not found in /home/starsh2/public_html/fangs/includes/HookContainer/HookRunner.php:40
Stack trace:
#0 /home/starsh2/public_html/fangs/includes/AutoLoader.php(244): require()
#1 [internal function]: AutoLoader::autoload('MediaWiki\\HookC...')
#2 /home/starsh2/public_html/fangs/includes/Hooks.php(174): spl_autoload_call('MediaWiki\\HookC...')
#3 /home/starsh2/public_html/fangs/includes/exception/MWExceptionHandler.php(762): Hooks::runner()
#4 /home/starsh2/public_html/fangs/includes/exception/MWExceptionHandler.php(193): MWExceptionHandler::logException(Object(Error), 'mwe_handler')
#5 /home/starsh2/public_html/fangs/includes/exception/MWExceptionHandler.php(247): MWExceptionHandler::rollbackPrimaryChangesAndLog(Object(Error), 'mwe_handler')
#6 /home/starsh2/public_html/fangs/includes/exception/MWExceptionHandler.php(216): MWExceptionHandler::handleException(Object(Error), 'mwe_handler')
#7 [internal function]: MWExceptionHandler::handleUncaughtExce in /home/starsh2/public_html/fangs/includes/HookContainer/HookRunner.php on line 40

After uploading the skin, I tried the mw-config process. Still blank, but now the error log only reported one:

[29-Jan-2024 17:35:27 UTC] PHP Fatal error:  Uncaught Error: Interface "MediaWiki\Hook\BookInformationHook" not found in /home/starsh2/public_html/fangs/includes/HookContainer/HookRunner.php:40
Stack trace:
#0 /home/starsh2/public_html/fangs/includes/AutoLoader.php(244): require()
#1 /home/starsh2/public_html/fangs/includes/Hooks.php(174): AutoLoader::autoload()
#2 /home/starsh2/public_html/fangs/includes/exception/MWExceptionHandler.php(762): Hooks::runner()
#3 /home/starsh2/public_html/fangs/includes/exception/MWExceptionHandler.php(193): MWExceptionHandler::logException()
#4 /home/starsh2/public_html/fangs/includes/exception/MWExceptionHandler.php(247): MWExceptionHandler::rollbackPrimaryChangesAndLog()
#5 /home/starsh2/public_html/fangs/includes/exception/MWExceptionHandler.php(216): MWExceptionHandler::handleException()
#6 [internal function]: MWExceptionHandler::handleUncaughtException()
#7 {main}
  thrown in /home/starsh2/public_html/fangs/includes/HookContainer/HookRunner.php on line 40

While the last one in the first block above and this latest both appear to be errors associated with BookInformationHook and HookRunner.php, their stack traces are significantly different.

What shall I do? LeyteWolfer (talk) 17:49, 29 January 2024 (UTC)

Are you sure you extracted mediawiki's files correctly? The error seems to be saying that includes/specials/Hook/BookInformationHook.php is missing. Bawolff (talk) 07:48, 30 January 2024 (UTC)

I've checked: BookInformationHook.php is definitely there.

My working hypothesis was that HookRunner.php line 40 is missing a reference to BookInformationHook.php.

Looking that file up, line 40 reads class HookRunner implements. Down on line 129: \MediaWiki\Hook\BookInformationHook,. My version of the uploaded file matches both of those lines.

That makes me wonder: should BookInformationHook.php be/also be in /includes/Hook?

What do you think? LeyteWolfer (talk) 11:31, 30 January 2024 (UTC)

> That makes me wonder: should BookInformationHook.php be/also be in /includes/Hook

No, its not supposed to be there.

It could be something wrong with autoload.php or another file like that. sometimes problems like this happen when the mediawiki archive is extracted over an existing mediawiki install, instead of into a clean directory. Bawolff (talk) 16:15, 30 January 2024 (UTC)

I learned that from you with the Phase 1 (1.32–>1.35) part of this upgrade process, so avoided doing that again. IF it’s relevant, then it would be from an earlier upgrade (1.29–>1.32, or earlier).

What’s the next step from the displayed errors? Should I load a clean autoload.php? LeyteWolfer (talk) 16:48, 30 January 2024 (UTC)

I would try getting a fresh copy of the version of MediaWiki you are trying to upgrade to. (Assuming you are using tar/zip versions of MediaWiki - extract the files to a clean directory, copy over LocalSettings.php, images/ and any extensions, replace the original directory with the new directory.) Bawolff (talk) 00:00, 31 January 2024 (UTC)

Quick question before I do those steps. Everything you just said to do I have been doing...except for the extensions. Both times (to 1.35 and now 1.39) I've left the extensions out, since you enlightened me they could cause problems. I intended to just add any ones I might want/need once 1.41 was up and running.

Could the blank installation page have anything to do with the extensions not in the fresh directory? LeyteWolfer (talk) 02:20, 31 January 2024 (UTC)

It would be fine to leave the extensions out. The error message is not related to extensions. Bawolff (talk) 09:08, 31 January 2024 (UTC)

This is interesting:

I uploaded MW 1.39.6 (after having downloaded a new zip of it) to my remote drive. Two files—both composer.json from differing locations—had failed to transfer, so I moved them manually. Then, I did as you said: "copy over LocalSettings.php, images/" and renamed it as the new directory. (I did not choose to move any extensions.). This time the first installation page loaded, but when I pressed continue, I got this error:

PHP Deprecated:  DefaultSettings.php is deprecated and will be removed. Use the ConfigSchema service object instead. [Called from require_once in /home/starsh2/public_html/fangs/LocalSettings.php at line 25] in /home/starsh2/public_html/fangs/includes/debug/MWDebug.php on line 381
PHP Fatal error:  Uncaught Exception: Unable to open file /MonoBook/skin.json: filemtime(): stat failed for /MonoBook/skin.json in /home/starsh2/public_html/fangs/includes/registration/ExtensionRegistry.php:199
Stack trace:
#0 /home/starsh2/public_html/fangs/includes/GlobalFunctions.php(86): ExtensionRegistry->queue()
#1 /home/starsh2/public_html/fangs/LocalSettings.php(172): wfLoadSkin()
#2 /home/starsh2/public_html/fangs/includes/Setup.php(218): require_once('/home/starsh2/p...')
#3 /home/starsh2/public_html/fangs/includes/WebStart.php(86): require_once('/home/starsh2/p...')
#4 /home/starsh2/public_html/fangs/index.php(44): require('/home/starsh2/p...')
#5 {main}
  thrown in /home/starsh2/public_html/fangs/includes/registration/ExtensionRegistry.php on line 199

Of course it couldn't find it: skins/ was empty of any skins, despite MonoBook supposedly being bundled with 1.39.6. I then uploaded the MonoBook directory from MonoBook-REL1_39-26f5e09 (i.e., the 1.39 version) into /skins and ran /mw-config/ again, but this time, no first installation page showed; it was just a similar error:

Deprecated:  DefaultSettings.php is deprecated and will be removed. Use the ConfigSchema service object instead. [Called from require in /home/starsh2/public_html/fangs/LocalSettings.php at line 25] in /home/starsh2/public_html/fangs/includes/debug/MWDebug.php on line 381
[ZbqOkrnA698KSW8CQWcJnQAAAFY] /fangs/mw-config/   Exception: Unable to open file /MonoBook/skin.json: filemtime(): stat failed for /MonoBook/skin.json
Backtrace:
from /home/starsh2/public_html/fangs/includes/registration/ExtensionRegistry.php(199)
 #0 /home/starsh2/public_html/fangs/includes/GlobalFunctions.php(86): ExtensionRegistry->queue()
 #1 /home/starsh2/public_html/fangs/LocalSettings.php(172): wfLoadSkin()
 #2 /home/starsh2/public_html/fangs/includes/installer/Installer.php(707): require(string)
 #3 /home/starsh2/public_html/fangs/includes/installer/WebInstallerExistingWiki.php(29): Installer::getExistingLocalSettings()
 #4 /home/starsh2/public_htm

I swapped out the 1.39 version of MonoBook and replaced it with the "monobook" I had in my original backup (from 1.32.2), since it makes sense that an upgrade from before 1.39 would be working with a pre-1.39 version of the skin. Exact same response.

What I find interesting is that the installation page never shows up again when the /mw-config/ process is re-attempted.

So, I'm thinking I should start fresh again: new MW 1.39.6 directory, legacy files/directory from the 1.35.15 backup, but this time make sure the older "monobook" skin is also copied over.

Unless you have a better idea? LeyteWolfer (talk) 18:35, 31 January 2024 (UTC)

Ran the process once again, with the 1.39 version of MonoBook. Got this error as soon as I pressed the Continue button on the first installation page:

 Deprecated:  DefaultSettings.php is deprecated and will be removed. Use the ConfigSchema service object instead. [Called from require in /home/starsh2/public_html/fangs/LocalSettings.php at line 25] in /home/starsh2/public_html/fangs/includes/debug/MWDebug.php on line 381
[ZbqxwxOtUUq1GOtjB5KJmAAAAJI] /fangs/mw-config/?page=ExistingWiki   Exception: Unable to open file /MonoBook/skin.json: filemtime(): stat failed for /MonoBook/skin.json
Backtrace:
from /home/starsh2/public_html/fangs/includes/registration/ExtensionRegistry.php(199)
 #0 /home/starsh2/public_html/fangs/includes/GlobalFunctions.php(86): ExtensionRegistry->queue()
 #1 /home/starsh2/public_html/fangs/LocalSettings.php(172): wfLoadSkin()
 #2 /home/starsh2/public_html/fangs/includes/installer/Installer.php(707): require(string)
 #3 /home/starsh2/public_html/fangs/includes/installer/WebInstallerExistingWiki.php(29): Installer::getExistingLocalSettings()
 #4 /home/starsh2/public_htm

I'm flummoxed...it wasn't the lack of the MonoBook skin after-all. LeyteWolfer (talk) 20:49, 31 January 2024 (UTC)

@Bawolff: I found this topic with your involvement.

You suggested that person look at $wgStyleDirectory. My LocalSettings.pho does not have that as an entry at all. So, I went to Manual:$wgStyleDirectory for guidance. It says that this particular "path"(?) is ignored when the wfLoadSkin function has a direct address path stated for a particular skin.

Should I change my wfLoadSkin( 'MonoBook' ); by adding such a path? And if so, to save a lot of time working this, could you provide the exact way this should be provided, please?

Ex: wfLoadSkin( 'MonoBook', 'http://mypersonaldomain.com/fangs/skins/MonoBook' );? LeyteWolfer (talk) 00:34, 1 February 2024 (UTC)

First off, do you have a line like require_once( "$IP/includes/DefaultSettings.php" ) or something like that, in LocalSettings.php ? If so remove it, and see if it changes the error message. Bawolff (talk) 12:34, 1 February 2024 (UTC)

Yep, it was there. I've commented it out (will delete it later). And the error message is changed. Now it's "missing" Vector:

[ZbuzCZd7W8oz0n8K8PHStQAAAFE] /fangs/mw-config/?page=ExistingWiki   Exception: Unable to open file /home/starsh2/public_html/fangs/skins/Vector/skin.json: filemtime(): stat failed for /home/starsh2/public_html/fangs/skins/Vector/skin.json
Backtrace:
from /home/starsh2/public_html/fangs/includes/registration/ExtensionRegistry.php(199)
 #0 /home/starsh2/public_html/fangs/includes/GlobalFunctions.php(86): ExtensionRegistry->queue()
 #1 /home/starsh2/public_html/fangs/LocalSettings.php(175): wfLoadSkin()
 #2 /home/starsh2/public_html/fangs/includes/installer/Installer.php(707): require(string)
 #3 /home/starsh2/public_html/fangs/includes/installer/WebInstallerExistingWiki.php(29): Installer::getExistingLocalSettings()
 #4 /home/starsh2/public_html/fangs/includes/installer/WebInstaller.php(270): WebInstallerExistingWiki->execute()
 #5 /home/starsh2/public_html/fangs/mw-config/index.php(82): WebInstaller->execute()
 #6 /home/starsh2/public_html/fangs/mw-config/index.php(40): wfInstallerMain()
 #7 {main}

I didn't have Vector in /skins, so—after uploading it and ensuring it's in LocalSettings.php (Narrator: "it was"), I was able to get to the 2nd page (Existing wiki) and thru to "try out your wiki". However, that led to this error on the /index.php page:

 Warning:  Trying to access array offset on value of type bool in /home/starsh2/public_html/fangs/includes/Setup.php on line 331
 MediaWiki internal error.
 
 Original exception: [Zbu03fkMuzIRamb0JH4bsAAAAM4] /fangs/index.php   BadMethodCallException: Cannot call expand() if the appropriate SERVER/CANONICAL_SERVER/INTERNAL_SERVER option was not passed to the constructor
 Backtrace:
 from /home/starsh2/public_html/fangs/includes/utils/UrlUtils.php(132)
 #0 /home/starsh2/public_html/fangs/includes/GlobalFunctions.php(508): MediaWiki\Utils\UrlUtils->expand()
 #1 /home/starsh2/public_html/fangs/includes/MediaWiki.php(943): wfExpandUrl()
 #2 /home/starsh2/public_html/fangs/includes/MediaWiki.php(972): MediaWiki->shouldDoHttpRedirect()
 #3 /home/starsh2/public_html/fangs/includes/MediaWiki.php(874): MediaWiki->maybeDoHttpsRedirect()
 #4 /home/starsh2/public_html/fangs/includes/MediaWiki.php(562): MediaWiki->main()
 #5 /home/starsh2/public_html/fangs/index.php(50): MediaWiki->run()
 #6 /home/starsh2/public_html/fangs/index.php(46): wfIndexMain()
 #7 {main}
 
 Exception caught inside exception handler: [Zbu03fkMuzIRamb0JH4bsAAAAM4] /fangs/index.php   BadMethodCallException: Cannot call expand() if the appropriate SERVER/CANONICAL_SERVER/INTERNAL_SERVER option was not passed to the constructor
 Backtrace:
 from /home/starsh2/public_html/fangs/includes/utils/UrlUtils.php(132)
 #0 /home/starsh2/public_html/fangs/includes/GlobalFunctions.php(508): MediaWiki\Utils\UrlUtils->expand()
 #1 /home/starsh2/public_html/fangs/includes/OutputPage.php(3875): wfExpandUrl()
 #2 /home/starsh2/public_html/fangs/includes/OutputPage.php(3371): OutputPage->getHeadLinksArray()
 #3 /home/starsh2/public_html/fangs/includes/skins/SkinMustache.php(63): OutputPage->headElement()
 #4 /home/starsh2/public_html/fangs/includes/skins/SkinTemplate.php(177): SkinMustache->generateHTML()
 #5 /home/starsh2/public_html/fangs/includes/OutputPage.php(2876): SkinTemplate->outputPage()
 #6 /home/starsh2/public_html/fangs/includes/exception/MWExceptionRenderer.php(183): OutputPage->output()
 #7 /home/starsh2/public_html/fangs/includes/exception/MWExceptionRenderer.php(102): MWExceptionRenderer::reportHTML()
 #8 /home/starsh2/public_html/fangs/includes/exception/MWExceptionHandler.php(131): MWExceptionRenderer::output()
 #9 /home/starsh2/public_html/fangs/includes/exception/MWExceptionHandler.php(248): MWExceptionHandler::report()
 #10 /home/starsh2/public_html/fangs/includes/MediaWiki.php(581): MWExceptionHandler::handleException()
 #11

BTW, line 331 of Setup.php reads: $wgServerName = $serverParts['host']; Line 332 seems related: unset( $serverParts );

So, considerable progress on this. I suspect you're going to tell me there is something I have to do with the host server next. I'm all ears. LeyteWolfer (talk) 15:15, 1 February 2024 (UTC)

What is $wgServer set to in LocalSettings.php ? Bawolff (talk) 19:27, 1 February 2024 (UTC)

$wgServer = `http://mypersonaldomain.com`;

LeyteWolfer (talk) 19:32, 1 February 2024 (UTC)

That's odd. Normally that error message would mean $wgServer is not set. Could you post your LocalSettings.php file (minus any passwords) Bawolff (talk) 20:05, 2 February 2024 (UTC)

Gladly. The pound symbol was used to indicate where I changed out personal information.

<?php error_reporting( -1 ); ini_set( 'display_errors', 1 );
# This file was automatically generated by the MediaWiki installer.
# If you make manual changes, please keep track in case you need to
# recreate them later.
#
# See includes/DefaultSettings.php for all configurable settings
# and their default values, but don't forget to make changes in _this_
# file, not there.
#
# Further documentation for configuration settings may be found at:
# http://www.mediawiki.org/wiki/Manual:Configuration_settings
# If you customize your file layout, set $IP to the directory that contains
# the other MediaWiki files. It will be used as a base to locate files.
if( defined( 'MW_INSTALL_PATH' ) ) {
	$IP = MW_INSTALL_PATH;
} else {
	$IP = dirname( __FILE__ );
}
$path = array( $IP, "$IP/includes", "$IP/languages" );
set_include_path( implode( PATH_SEPARATOR, $path ) . PATH_SEPARATOR . get_include_path() );
#require_once( "$IP/includes/DefaultSettings.php" );
# If PHP's memory limit is very low, some operations may fail.
# ini_set( 'memory_limit', '20M' );
$wgServer = `http://#mypersonaldomain.com`;
#if ( $wgCommandLineMode ) {
#	if ( isset( $_SERVER ) && array_key_exists( 'REQUEST_METHOD', $_SERVER ) ) {
#		die( "This script must be run from the command line\n" );
#	}
#}
## Uncomment this to disable output compression
# $wgDisableOutputCompression = true;
$wgSitename         = "Fanah's Fangs";
## The URL base path to the directory containing the wiki;
## defaults for all runtime URL paths are based off of this.
## For more information on customizing the URLs please see:
## http://www.mediawiki.org/wiki/Manual:Short_URL
$wgScriptPath       = "/fangs";
$wgScriptExtension  = ".php";
## UPO means: this is also a user preference option
$wgEnableEmail      = true;
$wgEnableUserEmail  = true; # UPO
$wgEmergencyContact = "#mainstreet@gmail.com";
$wgPasswordSender = "#mainstreet@gmail.com";
s
$wgEnotifUserTalk = true; # UPO
$wgEnotifWatchlist = true; # UPO
$wgEmailAuthentication = true;s
## Database settings
$wgDBtype           = "mysql";
$wgDBserver         = "127.0.0.1";
$wgDBname           = "starsh2_fangs";
$wgDBuser           = "starsh2_fangs";
$wgDBpassword       = "#WARMACHINEROXsd";
# MySQL specific settings
$wgDBprefix         = "";
# MySQL table options to use during installation or update
$wgDBTableOptions   = "ENGINE=InnoDB, DEFAULT CHARSET=binary";
# Experimental charset support for MySQL 4.1/5.0.
$wgDBmysql5 = true;
## Shared memory settings
$wgMainCacheType = CACHE_NONE;
$wgMemCachedServers = array();
## To enable image uploads, make sure the 'images' directory
## is writable, then set this to true:
$wgEnableUploads       = false;
# $wgUseImageMagick = true;
# $wgImageMagickConvertCommand = "/usr/bin/convert";
## If you want to use image uploads under safe mode,
## create the directories images/archive, images/thumb and
## images/temp, and make them all writable. Then uncomment
## this, if it's not already uncommented:
# $wgHashedUploadDirectory = false;
## If you have the appropriate support software installed
## you can enable inline LaTeX equations:
$wgUseTeX           = false;
$wgLocalInterwiki   = $wgSitename;
$wgLanguageCode = "en";
$wgProxyKey = "289b71ab630977773ada9c723684c98471d1c13c67a389a3302e73eb3b907e49";
## Default skin: you can change the default skin. Use the internal symbolic
## names, ie 'standard', 'nostalgia', 'cologneblue', 'monobook':
$wgDefaultSkin = 'MonoBook';
## For attaching licensing metadata to pages, and displaying an
## appropriate copyright notice / icon. GNU Free Documentation
## License and Creative Commons licenses are supported so far.
# $wgEnableCreativeCommonsRdf = true;
$wgRightsPage = ""; # Set to the title of a wiki page that describes your license/copyright
$wgRightsUrl = "";
$wgRightsText = "";
$wgRightsIcon = "";
# $wgRightsCode = ""; # Not yet used
$wgDiff3 = "";
# When you make changes to this configuration file, this will make
# sure that cached pages are cleared.
$wgCacheEpoch = max( $wgCacheEpoch, gmdate( 'YmdHis', @filemtime( __FILE__ ) ) );
$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'ppt', 'pdf', 'doc', 'psd', 'mp3','xls', 'ogg', 'zip','swf', 'doc', 'ico', 'svg', 'pdn', 'bmp'); 
    
$wgEnableUploads = true; 
    
$wgStrictFileExtensions = false; 
    
$wgCheckFileExtensions = false; 
$wgMaxUploadSize = 125000000;
    
$wgUploadSizeWarning = 125000000; 
    
$wgAllowCopyUploads = true; 
    
$wgGroupPermissions['*']['read'] = false; 
    
$wgGroupPermissions['*']['edit'] = false; 
    
$wgWhitelistRead = array ("Special:Userlogin"); 
    
$wgGroupPermissions['*']['createaccount'] = false; 
$wgShowSQLErrors = true;
$wgLogo = 'http://#mypersonaldomain.com/fangs/images/FF2.PNG';
$wgUpgradeKey = '#upgradekey';
$wgTmpDirectory = "/home/starsh2/tmp_inbs4m";
$wgJobRunRate = 50;
$wgShowExceptionDetails = true;
$wgShowDBErrorBacktrace = true;
#wfLoadExtension( 'CategoryTree' );
#wfLoadExtension( 'Cite' );
#wfLoadExtension( 'CiteThisPage' );
#wfLoadExtension( 'ParserFunctions' );
#wfLoadExtension( 'SpamBlacklist' );
#wfLoadExtension( 'WikiEditor' );
#wfLoadSkin( 'Modern' );
#wfLoadSkin( 'MonoBook' );
#wfLoadSkin( 'MonoBook', 'http://#mypssersonaldomain.com/fangs/skins/MonoBook' );
wfLoadSkin( 'Vector' );
#wfLoadExtension( 'FlexDiagrams' );
$wgActorTableSchemaMigrationStage = MIGRATION_WRITE_NEW ;

LeyteWolfer (talk) 21:36, 2 February 2024 (UTC)

@Bawolff, have you had a chance to error-check this? LeyteWolfer (talk) 23:57, 3 February 2024 (UTC)

For the $wgServer, are the type of quotes used just a copy and paste issue, or are you actually using ` ?

Using ` instead of ' or " would likely cause this issue.

[The rest of the file looks fine. There are some configs in it that don't do anything anymore, like $wgShowSQLErrors or the stuff with include_path, but they won't hurt anything. The setting for $wgDiff3 will make you more likely to have edit conflicts (If you have diff3 installed on your server, set $wgDiff3 = 'diff3'; but only do it if the diff3 command is installed on your webserver. On debian/ubuntu you can install with apt install diffutils). There is an extra s after the end of $wgEmailAuthentication, which would cause problem but i assume that is a copy paste error. Your job run rate is very high, which might occasionally make it feel like the site hangs on views where lots of jobs are run. I'd recommend reducing it to 5 unless you are having problems with jobs never getting run. Setting $wgMainCacheType to CACHE_NONE, can make your wiki very slow. If possible, I recommend installing the php apcu extension (on debian/ubuntu apt get install php-apcu) and then setting $wgMainCacheType = CACHE_ACCEL;. As the performance improvement can be significant). Bawolff (talk) 13:57, 4 February 2024 (UTC)

Thank you very much for that detailed reply, with very helpful guidance. I wanted to say that even before attempting these changes, because I really do appreciate the time you've given me over the last 2 weeks.

And...i will be laughing maniacally if most of my problems are down to my use of ` instead of '. LeyteWolfer (talk) 16:16, 4 February 2024 (UTC)

Update: maniacal laughter was heard.

Again, thank you for the guidance and the complete review of my settings. I'm moving on to conduct the final upgrade here shortly, before doing it all again for the older two wikis. LeyteWolfer (talk) 16:44, 4 February 2024 (UTC)

For reference, in php ` means to run a program and take the output, which is why it caused enough problems to not work eventually, but not enough problems to error out immediately. Bawolff (talk) 16:47, 4 February 2024 (UTC)

Localisation not working on an Extension

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Hey Everyone,

I'm looking into: Extension:DataDump which does have localisation.

I've got it installed and running, however the page itself has no localisation. Instead the locale message keys are rendered.

You can see the special page here: https://wiki.resonite.com/Special:DataDump

I've also re-generated the locale cache but nothing changed. Perhaps its my Mediawiki Version? You can check that here: https://wiki.resonite.com/Special:Version

I'd love to know where to go from here for debugging.

Thank you! ProbablePrime (talk) 03:23, 30 January 2024 (UTC)

Sometimes it helps to remove and readd an extension to force l14n cache clear. Bawolff (talk) 16:23, 30 January 2024 (UTC)

Sometimes rebuildLocalisationCache.php does nothing unless you provide the --force parameter. Ciencia Al Poder (talk) 22:09, 31 January 2024 (UTC)

--force worked, thank you everyone. ProbablePrime (talk) 22:21, 31 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Pywikibot

Hello I need help please if I'm trying to run "pip install -r requirements.txt" this error showing "bash: pip command not found if I'm trying to run sudo apt update this error is showing "sorry tools.mytoolname is not allowed to excute '/use/bin/apt update' as root on tools.sgebastion-10.tools.eqiad1.wikimedia.cloud.tools.mytoolname@tools-sgebastion-10:~$" How fix this please I need help Kaleem Bhatti (talk) 08:48, 30 January 2024 (UTC)

You are in a shared environment, on a login server, you cannot just install your own packages there. Python needs to run within jobs on toolforge. Please read https://wikitech.wikimedia.org/wiki/Help:Toolforge/Python —TheDJ (Not WMF) (talk • contribs) 09:17, 30 January 2024 (UTC)

Search in Home Page

Hello

I'd like to put the special Search page on the home page. I've found the following code :

/* Remplacez l'URL de la page d'accueil utilisée dans les éléments tels que le logo, par l'URL d'une autre page du wiki. */ $wgHooks['SkinTemplateOutputPageBeforeExec'][] = 'lfChangeMainPageURL'; function lfChangeMainPageURL( $sk, &$tpl ) { $tpl->data['nav_urls']['mainpage']['href'] = Title::newFromText('LaPage')->getLocalURL(); // Faites pointer l'URL de la page d'accueil vers l'URL d'une page du wiki return true; }

But I can't find what to indicate in place of 'The Page' in this code.

Thank you very much for your help 2A01:CB0C:A65:7500:A146:6F7:7159:B4AE (talk) 09:55, 30 January 2024 (UTC)

that code does not seem to do what you want or be related to what you want.

What do you mean by put search on main page? Does extension:InputBox help? Bawolff (talk) 16:20, 30 January 2024 (UTC)

Modification not taken into account

Hello,

I'm translating a page from French into English. My problem is that I should modify something in the translated version but the modification is not taken into account. What should I do?

Thank you 147.161.163.100 (talk) 12:54, 30 January 2024 (UTC)

Maybe your edit is triggering an edit or spam filter that doesn't let you save. You should provide more details, including what page/url are you trying to edit. Ciencia Al Poder (talk) 22:11, 31 January 2024 (UTC)

Changes are traced in the history but not displayed on the page. I can't add a screenshot here Nambinina55 (talk) 08:56, 1 February 2024 (UTC)

where can I see the modification or spam filter? Nambinina55 (talk) 09:03, 1 February 2024 (UTC)

If your wiki is public, post a link to the page. Otherwise, explain how are translating things, which extension are you using to translate, etc. Ciencia Al Poder (talk) 22:25, 1 February 2024 (UTC)

How to create a wikipedia page

How do I create a wikipedia page? 216.54.20.98 (talk) 14:42, 30 January 2024 (UTC)

Please ask at w:WP:TEAHOUSE Bawolff (talk) 16:18, 30 January 2024 (UTC)

Visitors counter

How do I install a visitors counter in a wiki page? 201.217.129.242 (talk) 15:58, 30 January 2024 (UTC)

There is a "page view" extension Extension:HitCounters. Please check the instructions on the linked page.

If you want to have a more detailed analysis, consider using a tool like Matomo. There are extension to integrate this too: Extension:Matomo, Extension:MatomoAnalytics Osnard (talk) 09:08, 31 January 2024 (UTC)

Change permissions' descriptions

All permissions (per user group) are displayed on Special:ListGroupRights, with their respective descriptions, such as Create new user accounts (createaccount)and Delete pages (delete)

How can I change those descriptions? I guess they're located on the MediaWiki namespace, but couldn't find them. 190.219.189.83 (talk) 02:02, 31 January 2024 (UTC)

They use the format '$x-$y' where $x is a fixed string 'right' and and $y is a name of particular userright.

For instance createaccount description is at MediaWiki:right-createaccount while the one for delete is at MediaWiki:right-delete and so on. You can use the pseudo-language code qqx to find message keys. – Ammarpad (talk) 20:15, 31 January 2024 (UTC)

Thank you 190.219.189.83 (talk) 01:06, 1 February 2024 (UTC)

Find all pages that do not meet the template inclusion policy

Hello!

I adopted a wiki and I would like to make some structural changes to it. The wiki is particularly well-organized and may require (some) efforts to make it work nicely. And to gain one of the results I planned, I need to find pages that deal with the designed templates incorrectly.

Say, I have user talk pages in the User_talk namespace and I have two templates Template:Welcome and Template:Talkheader (IMPORTANT: where the latter template is included to the former one).

The user talk pages are considered:

- OK when a User_talk: page includes Template:Welcome directly

- BAD when a User_talk: page includes Template:Talkheader directly (it only should include Template:Welcome)

- BAD when a User_talk: page includes both Template:Welcome and Template:Header causing content doubling (Template:Welcome is a wrapper for Template:header)

How do I find user talk pages that have bad template inclusions? Thank you! 91.201.234.159 (talk) 17:07, 31 January 2024 (UTC)

One note: I'm open to use MediaWiki built-in web facilities, maintenance scripts and Pywikibot. 91.201.234.159 (talk) 17:09, 31 January 2024 (UTC)

One more note: using SQL is also a very good option to me. 91.201.234.159 (talk) 09:51, 1 February 2024 (UTC)

Find my account

I have been using Wiki for years but don't sign in I guess. I decided to sign in and cannot remember user or password. It says I can get help if I enter my email but don't know my password. Help! 2605:59C8:31A4:CD10:10A:B5FD:6D16:3BDC (talk) 18:18, 31 January 2024 (UTC)

Use Special:PasswordReset and provide the email. – Ammarpad (talk) 20:04, 31 January 2024 (UTC)

MediaWiki docker container behind NGINX Proxy Manager (also a docker container) works but can't use edit button

As described in the title, managed to getting working with this but if I try to use the "edit" in the main page I get:

"Error contacting the Parsoid/RESTBase server: (curl error: 60) SSL peer certificate or SSH remote key was not OK"

I can edit if I enter the URL manually, like"/index.php?title=Main_page&action=edit"

It does allow me to open the code editor, just not the normal editor, and I have no Idea where to go from here.

Both docker containers are running rootless in the same Debian host, I have the company DNS pointing at the docker host for "mywiki.ourdomain.com" and I have our certs loaded in NPM so for the lan this web is seen as secure by all browsers, this is an internal wiki and it will always be only in the lan.

Thank you all in advance. ScarUY (talk) 20:19, 31 January 2024 (UTC)

The server needs to connect to itself. As documented on the Parsoid page, you have to configure $wgVirtualRestConfig['modules']['parsoid'], so that it knows to connect internally, instead of externally to itself. —TheDJ (Not WMF) (talk • contribs) 23:08, 31 January 2024 (UTC)

Thank you for your answer, although it seems way over my head, the $wg you're referring to is under the title "Linking a developer checkout of Parsoid", and I'm no programmer so I don't understand how to begin to adapt that to my situation, as far as I understand, I don't have a Parsoid instance other than the one included in the mediawiki docker, I have no idea what modules it refers to, and thus I've advanced very little (at least I know the general direction of where the problem lies), care to elaborate a bit on how I should solve my problem, or point me to somewhere where this is a bit more plainly explained or has more examples?

I don't want to sound bad, but putting a wiki behind a reverse proxy seems to me a pretty common thing, so perhaps I missed something in the documentation or the documentation is missing something about the config necessary behind reverse proxies? ScarUY (talk) 03:40, 1 February 2024 (UTC)

On the bright side, i think this requirement is going away in a future version of MediaWiki. The following only applies if using the VisualEditor extension.

So if from within the container your web server is accessible at 127.0.0.1 on port 8080 on plain http you would do something like:

$wgVirtualRestConfig['modules']['parsoid'] = [ 'url' => 'http://127.0.0.1:8080' ];

Bawolff (talk) 19:49, 2 February 2024 (UTC)

I jumped to the LocalSettings.php the moment I saw your message...

I didn't willingly installed parsoid, I only found about its existence when reading TheDJ's answer, I think I just marked the option "VisualEditor" in the initial setup, had I known that, or had I read some kind of warning, I wouldn't have marked it, I didn't expected it'll cause me (and you reading this) so mucho trouble.

In any case since my docker-compose states "ports: - 8280:80" I'm assuming I have to change the 'http://127.0.0.1:8080' for 'http://127.0.0.1:80', but neither worked (I rebuilt the container after each change) , naturally I also uncommented "wfLoadExtension( 'VisualEditor' );" before trying your suggestion.

Since we're using this wiki with the "classic" editor, I'll just leave it commented and as soon as I can I'll spin up another identical container to try some more, (if I keep taking this one down I'll be in trouble).

Thank you for your time, and a humble suggestion, while this is neccesary (you said it's going away in future versions) shouldn't be a note somewhere about it? There's no way I would have linked the "VisualEditor" and "Parsoid" without TheDJ's comment, even after I enabled some more verbose errors! The proxy section in the help/manual ($wgCdnServers) says nothing about the VisualEditor or Parsoid, thet could use some improvement! ScarUY (talk) 20:30, 2 February 2024 (UTC)

> says nothing about the VisualEditor or Parsoid, that could use some improvement!

well this is a wiki, so…. Go right ahead ! —TheDJ (Not WMF) (talk • contribs) 21:15, 4 February 2024 (UTC)

Gladly! As soon as I know what to put there, I still don't know much more than "be carefull when first time boioting mediawiki as a docker container, if you mark the "VisualEditor" option you'll require aditional configuration in your localsettings.php otherwise you won't be able to edit behind a reverse proxy with https" and I don't think that'll be of much help to anyone but to scare or discourage new users, it'll be just warning about a (I hope) solvable problem without offering a solution, and as far as I've read here, that's not the spirit of this project. ScarUY (talk) 12:50, 5 February 2024 (UTC)