In T7988#161562, @Compassnne wrote:

As said in that report, the admin-suggested CSS version of DarkVector (https://www.mediawiki.org/wiki/Skin:Vector/DarkCSS) is unmaintained and does not function properly when implemented on my wiki.

FYI, I asked an upstream maintainer about this.

This is declined per T6693#131704.

In T7899#160892, @Reception123 wrote:

GitHub's privacy policy covers all of our checklist and therefore would be approved. As far as I can see with shields.io there isn't any additional collection of information beyond what GitHub collects and "No tracking" is mentioned.

FYI, the version was bumped by @Universal_Omega seemingly because of replacing "DB_MASTER" with "DB_PRIMARY" which has been backported to 1.35.

What exactly "isn't working"? I tested it and the CSS worked.

I also got this error-
`Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at ‘https://snapdata.miraheze.org//w/api.php?action=query&format=json&origin=https%3A%2F%2Fsnapwiki.miraheze.org&meta=userinfo%7Ctokens’. (Reason: Credential is not supported if the CORS header ‘Access-Control-Allow-Origin’ is ‘*’).`

Could you please just make a new task instead of commenting on this closed task with unrelated discussion? You will have a better chance there, in my honest opinion.

In T7850#158190, @Ugochimobi wrote:

Well, I was about asking for this though,
@Redmin I think title blacklist is different from spam blacklist, one is for titles on-wiki the latter for links.

Same for spam "black"list, I hope?

Seems like this used to be available on Miraheze but was removed due to it leaking private information: 204da08f329f478f0ec7e9fdf9b819ed2fdf59dd.

In T7821#157905, @Protected wrote:

If you think it's not fixable I won't insist. Impressive that this feature isn't in core MediaWiki though. Thanks for checking.

In T7821#157843, @Protected wrote:

Could you explain why, please? Maybe we can fix the extension. If it's because of the extension schema I'm reading about a script that upgrades from the old to the new format, and if it's about the hook interface there is a procedure for upgrading that in the manual.

Apologies for the inconvenience but this extension is incompatible with MW 1.36 (the current MediaWiki version).

In T7798#157212, @Universal_Omega wrote:

https://github.com/miraheze/MatomoAnalytics/pull/50 is the only possible cause for this. It's the most recent change, and also touches the area that adds that. I can reproduce the issue as well.

I removed the ID just in case it is sensitive as it did not seem to change on each page load; let me know if it is needed.

In T7765#156831, @Universal_Omega wrote:

It is doubtful this would improve SEO at all. Nonetheless I guess it can be approved. Though I don't want to install anything redundant so I want to discuss with @Reception123 first.

Could you search with ?useskinversion=2 in the URL? I agree with RhinosF1 and as far as I am aware, this issue should not happen in the new Vector which uses a different API.

Does বিশেষ:ফ্লো_সক্রিয়করণ work?

Hello, both of them are globally enabled meaning you do not need to enable it yourself.

Link to an example page, please?

Both are already available in Special:ManageWiki/extensions. :)

Thank you so much!

Hello, you can do this by going to Special:ManageWiki/permissions and removing the "edit" right from the * user group.

Tagging with Test Me as I was not able to reproduce this and Lakelimbo also said on Discord that the update to MW works well for them.

A system administrator will have to do the import server side for you.

FYI, I have been receiving emails from Meta normally on my Outlook email address.

The "improvement" in #1 has actually made my life harder and I am pretty sure many others feel the same way. The types defined in extension registry are not useful at all to the end user; they make navigating ManageWiki harder. I suggest adding custom sections.

Hello, what exactly are you asking for? If you want to give another user access to your private wiki, you should go to Special:UserRights/<username> and add them to the member group. And we indeed do not have Bluespice.

Have you tried clearing your cookies for *.miraheze.org? Which browser are you using?

I intend to look into this task this weekend; claiming so I don't forget.

Will install as discussed with @Universal_Omega on Discord.