Used by ShoutWiki which is another trustworthy wiki farm, so shouldn’t be any security issues per se. However, I will note that the MediaWiki documentation page indicates that the latest version was released back in 2015 for MediaWiki 1.23, so if there haven’t been any substantial core updates since then, the code will need to be examined closely to see if there are any major bugs or flaws that would block installation.

The extension is not currently installed and needs security review. However, the fact that the extension documention has This extension stores its source code on a wiki page. Please be aware that this code may be unreviewed or maliciously altered. They may contain security holes, outdated interfaces that are no longer compatible etc. on the top of its page, this may prove to be a blocker from a security/privacy standpoint.

When I log into my wiki with my Miraheze account it says, "Auto-creation of a local account failed: Automatic account creation temporarily disabled due to prior errors."

In T3787#72689, @Tiger wrote:

OK. Then I have nothing to change.

Security review is needed. Although I will note that the message on the top of the doc page which reads This extension stores its source code on a wiki page. Please be aware that this code may be unreviewed or maliciously altered. may be a blocker.

Hmm... am I missing something here? I haven’t seen anything on the mw mailing list about a new version release, and the version lifecycle on MediaWiki.org still displays 1.31 as the latest version. To make things even stranger the lifecycle timeline jumps from 1.31 to 1.33 (skipping 1.32 altogether). Anyone have any insight?

I’m not sure if this is possible as it is not a standard MediaWiki skin but rather a custom skin that an individual wiki created manually for themselves. As it does not appear to be maintained upstream, it likely is incompatible with Miraheze, but I’ll let the security reviewers have the final say @labster @Samwilson

Okay, status update: The code is definitely workable. It needs to be updated for the latest version(s) of MediaWiki, but that’s the largest issue that I could find. The only other thing that I’ll note is that the current code doesn’t give users with the checkuser-limited permission access to Special:CheckUserLog, which is one of the key elements of the CU extension. I’ll look into adding code to allow a restricted log access where one can only see log entries of checks they have run, and since they will have only run checks on themselves, no PII will be divulged.

@shaunakchak please do not assign tasks to people without their consent, unless its an issue that can only be handled by one person. Thanks.

Unfortunately as the extension is not being actively maintained and the latest version was released for MediaWiki 1.23, we cannot be sure that the extension will work on Miraheze.

Infboxes are not an extension, but rather are a serious of content modules that need to be imported. To add an Infobox from, say, Wikipedia, go to Special:Export on Wikipedia, enter the name of the Infobox (including the “Template:”) prefix, and make sure to check the “include templates” checkbox. Then import the file to your wiki.

This appears to be an issue with the Cargo extension. (Note to self: Why do I feel like that I’ve seen this issue before?)

Security review required.

High priority as it is affecting a critical feature of MediaWiki.

High priority as it is affecting a critical feature of MediaWiki.

In T3665#72178, @MacFan4000 wrote:

@AmandaCath we can't change the extension files, so this would have to be reported upstream.

If I change ...->addModuleScripts... to ...->addModules... on line 378 of Tabs.body.php then the tabs do work as expected again (MW 1.31, PHP 7.2.8, Tabs 1.3.2).... sounds like something that needs to be done sysadmin-wise @John @Paladox

Might be an extension you need to enable.. not sure @Paladox

This was declined at least twice somewhere else (want to say on-wiki), although I don’t remember the exact reason.

This isn’t a design issue... sounds like an issue with one or more skins (which is categorized as extensions here).

High priority as this is blocking another task.

This is a feature that you can specifiy yourself when importing pages. When you go to Special:Import there is a checkbox that says “assign edits to local users where the user exists locally” or something like that.

Any updates on this?

No response, and therefore this task cannot proceed. Reopen if can provide a more detailed explanation on what is being requested here.

You may need to create MediaWiki:Rottenlinks-showbad on your wiki to whatever the default value should be, or whatever value you want. Sometimes messages defined by custom extensions or recently installed/enabled extensions don’t always show up in Special:AllMessages just from my experience.

IMHO this should be either a user preference option or a local wiki ManageWiki option - shouldn’t be hard coded in the extension and be “mandatory” for say.

This can be done through Special:ManageWikiPermissions on your wiki.

In T3716#71330, @Blakegriplingph wrote:

Any ETA on this one?

@Psiconauta I am unable to reproduce this on my wiki.

Hmm.. I’m investigating. Please stand by.

Database changes done per MacFan and Paladox.

Great to hear.

@Paladox I believe that this would be approved for installation and addition to ManageWikiExtensions.

@Paladox @Rob_Kam any updates?

@Gloop I’m sorry, but it’s not exactly clear what you are asking. Can you please clarify/explain? Thanks.