@Ahmsaqib you can also just use regular Special:Nuke to mass-delete pages created by any author in any namespace (assuming that the pages aren’t ancient). The Special:Nuke form has an option to limit pages to be deleted to certain namespaces.

In T4008#76774, @MacFan4000 wrote:

We removed the extension due to it causing other problems for us.

Security review is needed, although I will say from the beginning that the fact that the extension docs on MediaWiki.org says that its only compatible with the “master” version of MediaWIki (i.e. the latest development and WMF version which we aren’t running) is a red flag. However it does appear that there are versions of the extension available for older versions of MediaWiki, so I’d assume that would include the current stable and LTS versions.

High priority as blocking a critical feature of MediaWiki.

Hmm.. looks like some sort of parser or HTML issue to me.

Well, task 784... much before my time! Anyway, unless that missing server/element can be added, I don’t think this can be reinstalled.

In T3900#76804, @MacFan4000 wrote:

https://github.com/miraheze/mw-config/blob/master/extension-list#L33

It is installed

The extension is approved for install as it is being used by the Wikimedia Foundation, however I do not believe that it has actually been installed yet @Paladox

Hmm.. it appears that ContactPage needs to be enabled manually. I will do that for you.

The MediaWiki documentation page says that the extension was last updated in 2014, which is out-of-date for a production system like Miraheze that is concerned about security and bugs and the like. However, MediaWiki docs have a notorious reputation for being out of date themselves and thus reporting incorrect information, so I’ll let the reviewers take a look.

Yes, this is possible. You need a custom domain. See this page for more information.

Any updates on this?

@AleksanderTv see instructions here on how to install infoboxes in on your wiki

I’m not sure what you mean by “send zip file”

@AleksanderTv what do you mean by “it doesn’t work”? If you enabled it in Special:ManageWikiExtensions it is definitely installed. Are you getting an error message?

I’m not quite sure what you are asking. Can you please clarify a bit?

Security review of the skin is required. However, the fact that the MediaWiki documention page says “Status: Unkown” doesn’t inspire my confidence. Also it appears that this is a customized Wikia skin and so I don’t know if it would be compatible with Miraheze or not.

I would ask, why are we changing the default permissions anyway?

Unfortunately this is a known problem that has been reported many times before, with no solution able to be determined. Usually when you receive “this session has been cancelled due to suspected hijacking” you can simply refresh the page, or sometimes close your browser and start it up again, and then log back in, and you should be successful. Alternatively, if you don’t want to worry about it, next time you log in successfully, check the “keep me logged in” checkbox (assuming that you’re not using a shared device with other people).

@A_KLERK Hi, if you’re talking about https://www.mediawiki.org/wiki/Extension:EmailForm that extension can’t be installed on Miraheze at the moment as it hasn’t been updated recently and therefore will likely contain bugs or security risks.

Not yet - T3982

Unfortunately this is not something that Miraheze can do - Firefox and other web browsers should update their topicons, but you might need to delete the top site and re-add it etc.

Housekeeping note, appears that this will be done very soon per 7f8ee98cf628

Hmm.. not sure if this quite qualifies as an extension, but it will still need to pass security review due to it being something external from the MediaWiki core.

This is possible through Special:ManageWiki but I believe that it requires the managewiki-restricted userright, which only system administrators have. @Paladox

Yikes! Appears to possibly be a hijacking/compromised account issue. Although I’m familiar with session hijacking from an IT perspective, without technical data from the server logs (which I know can’t be shared) I can’t comment further.

You can now do this via Special:ManageWikiNamespaces on your wiki.

I’m not talking about enabling it globally. I’m talking about getting the code updated and working just for publictestwiki, and perhaps if I can make it available for individual wikis to enable upon request/need, I’ll go for that. However, I have never had any interest in trying to make it work globally.

Seconding MacFan that this still does occur. Appears to be an upstream issue.

I don’t think this is an ops task, judging by https://www.mediawiki.org/wiki/Citoid/Enabling_Citoid_on_your_wiki

@Sparr after Void’s change above, is the issue now resolved?

ManageWiki and all of its features are enabled on all wikis by default.

Blocked by upstream.

I don’t see the error anywhere on my wiki, but I do see it when accessing the Stewards noticeboard, although I don’t anywhere else on Meta.

See also the screenshot of TestWiki in T3942

And the 'problem' occurs on Wikipedia too when I edit there in Visual Editor mode.

Phab temporarily crashed while I was in the process of replying, so my reply got posted like six times. Sorry.

So the next thing we know, someone (whether it be us or upstream) will be saying that we should make all restricted special pages read-only to all users... which means that we’d be saying we should make pages like Special:Block and Special:DeletedContributions available to be read by anyone? No, that’s not good at all. And then, taking it to an extreme step, should we say that even the most restricted like Special:CheckUser should be readable by everyone? Making the pages readable to everyone only opens up more potential loopholes and security/privacy risks. If you are not authorized to use a feature than you are not authorized to use it - period. That includes viewing it.

@John no, what I’m not a fan of is making Special:ManageWiki and its associated pages viewable for all users. Whether or not the settings are editable or not, IMHO ManageWiki should still be a restricted special page.

@Kees_Langeveld is this still an issue?

No response to paladox. Reopen if still an issue.

No response to Revi in over a month. Reopen if still an issue.