Btw, https://phabricator.wikimedia.org/T295830 indicates that GrowthExperiments shows errors if Suggested edits feature is enabled without CirrusSearch installed, so I guess it should also be disabled.

No worries.

I've investigated the problem: the reason for timeouts when using Wiki-Bot is because it asks for the whole list of extensions. Miraheze wikis respond to that specific request (https://meta.miraheze.org/w/api.php?action=query&meta=siteinfo&siprop=general|extensions with |extensions) too slowly, slower than most MediaWiki sites, and that is why the bot has problems. Asking simply for general is fine. If I had to guess, it's probably something to do with ManageWiki. (Leaving this here for people searching this in the future.)

Unless I am wrong about this, all those tasks concern occasional problems with autoreview. In our case right now, I have to review every single edit made by myself, so it is clearly a different thing from what they are describing in those tasks.

This causes errors for readers since any patrolled changes in modules don't automatically get to articles, see this example:

@Paladox, you didn't have to enable Popups as a beta feature, it was just cache for users since JavaScript loads a bit late compared to extension itself. Also enabling it as a beta feature turns it off for anonymous users.

Also would like to know about RelatedArticles issue.

It also would be beneficial to display a link to documentation and extension description somewhere.

Can't say for sure, the note I got from him is (translated):

The same user that have seen this problem also saw it when trying to move the page in some way (I don't know how exactly, he didn't tell, but probably with a hyphen), was it the same problem?

OK, thanks for quick answer.

Seems like without JavaScript the map is not being loaded, because the URL at Wikimedia Maps server reports this:

"Domain is not allowed"

I don't think the wiki of original requester exists, but if you would do mine, it's fine and welcome, yes.

Seems like Kartographer was installed and enabled on test1wiki.

@Reception123 or anyone else, just reminding that this task needs to be solved sometime soon since users keep getting those empty messages as of now.

Those edits can't be accessed via interface as far as I am concerned.

Recording progress:

1. Reception123 has helped me with running scripts that were needed for Flow, so that is done.
2. There needs to be Module talk added to list of Flow namespaces, hopefully someone can get to that.
3. There is a page that I screwed up that needs text retrieval from one of sysadmins. John told that he can do it.

Also, it seems like for Scribunto talk pages (Module talk) it needs to be added to LocalSettings or LocalExtensions file. I don't know how to do this myself, so I hope someone can help with this.

This shouldn't require security review since the extension is used in all Wikimedia projects for generating PDFs by default, so they should've done enough security checks on their own.

Seems that these problems have ended. I guess the issue is resolved (all special pages display the proper interface now instead of giving an error like before).

@John I did not think it is a duplicate exactly because the type of error is not the same (the other one at least displays a wiki page, in this case it is not displaying a page at all), but I guess I wasn't right.

You can also rename file that you have already uploaded.

Do you know that you can update logo at your wiki just by reuploading the file that is currently used? Not that it stops the task, but it is more easy to have a single file named "Logo.png" or "Wiki.png" that can be reuploaded if you need a logo change.

Forgot about this: yes, it is probably helpful to add a config option to disable it for people that encounter this problem in future (I have decided to not use those icons right now, but I would like the setting to be disabled).

Gadgets are enabled by default, you have to add them manually to your wiki, see this for help:
https://www.mediawiki.org/wiki/Extension:Gadgets#Usage

You can change link colours with CSS on your wiki (do it at https://enen.miraheze.org/wiki/MediaWiki:Common.css):

a {
	color: #56D83F;
}

Same problem with https://commons.wikimedia.org/wiki/File:Breezeicons-status-24-dialog-information.svg and a bunch of different files from Breeze 5.22.0 categories - they are in HTML format for some reason and can't be loaded on Miraheze. Seems like it is better to resume PNG thumbnails rather than support NativeSvgHandler.

Or maybe fork it? There doesn't seem to be like this extension has any alternatives.

In T1867#34892, @Reception123 wrote:

The weird thing is that it is not ALL SVG files, as a random one I found, https://meta.miraheze.org/wiki/File:Endomembrane_system_diagram_en.svg works perfectly fine. It is possible that there is an issue with that extension. I will investigate and make an issue there.

They have correct MIME type, so this is why other files are fine for that NativeSvgHandler extension. These icons do not.

Since it seems to be a problem with this extension: https://github.com/p12tic/NativeSvgHandler

This is really a bigger problem. Is there a way to display PNG thumbnails instead of SVG links on Miraheze? These files all return in plain/text content type, and while SVG converter from Commons converts them correctly into PNG thumbnails, Miraheze displays all SVG files as SVG files, so if file has incorrect content type, it isn't showing at all.

Same error with most of files here:
https://commons.wikimedia.org/wiki/Category:Antu_icons

On other wikis as well, yes (I’ve noticed it from mine).

Opening it again since I need to fix issues with statistics (I have already cleaned up everything not useful in main namespace so any help on the counter reset will be great, since right now wiki has "0 articles").

In T1825#33992, @Reception123 wrote:

Finished yesterday

Update: these pages are available when using links with index.php, for example https://isv.miraheze.org/w/index.php?title=Special:PendingChanges opens for me, https://isv.miraheze.org/wiki/Special:PendingChanges does not.