I found EditCheck to also activate in Wikipedia: namespace on plwiki (apart from User: as flagged in the task description): https://pl.wikipedia.org/w/index.php?diff=74668368

For the record, EditCheck on plwiki has been just enabled in T373079: Enable EditCheck on Polish Wikipedia

EditCheck has been deployed and is now available for newcomers (<100 edits) without the URL flag.

I don't have a strong preference here – either delete those two buttons or make it a proper dialog that appears on click and that is modal.

Given that the patch has been reviewed, I'll go on with backporting it on Monday, 2 September.

In T373079#10106990, @ppelberg wrote:

However, we'd welcome you writing a patch provided someone on the Editing Engineering team can review it before you move forward with backporting.

In T373079#10089090, @ppelberg wrote:

Wonderful. Next Tuesday it is, Tufor!

I'll ping you here should that date need to change for any reason.

What's interesting, occurences of missing revisions seem to be correlated between wikis. Based on the @matej_suchanek query, I've checked bigger wikis from s2 (plwiki, itwiki, nlwiki, svwiki) and it turns out that often (especially during the severe windows) when there are missing RC entries on one wiki, there are also missing ones on another wikis within a few minutes.

In T71550#10069925, @Jdlrobson wrote:

I guess MediaWiki:Gadget-ReferenceTooltips.js, also has been moved into core, but I'm not sure what work is involved in removing it as a default gadget for anonymous users on en.wikipedia.org?

Even though the specific layout of the table could be indeed tweaked as mentioned above, I think that the alignment of the buttons and links in the same columns is beneficial overall and I second keeping this special page displayed as a table

As a plwiki admin and patroller I think that this change will be beneficial and helpful for people

I've prepared a patch for that.

The issue has been reported in plwiki tech village pump as well: https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne#X_zmian%28a%29_oczekuje_na_przejrzenie

I've browsed through the move log at plwiki and the issue started appearing between Wed, 2024-06-19 19:39 UTC (the last move that was automatically reviewed) and Thu, 2024-06-20 09:11 UTC (the first move that wasn't auto-reviewed but should be).

Here's screen recording of me reproducing the bug on plwiki: (I was doing it in Help: namespace but it's not significant for the problem)

In T361717#9882777, @DTorsani-WMF wrote:

Although the blue spectrum has a blue250 value, in order to be more visually balanced with the diff removed background color of yellow500, we use blue300 instead to address the goal mentioned above:

The task was also inspired by plwiki configuration changes to limit lint errors introduced by user signatures: T364769 and T362414 that for example stopped legacy <font> tags from being inserted.

Sure, no problem

The config change has been deployed.

For reference, here is some description of the script as well: https://meta.wikimedia.org/wiki/User:Msz2001/AbuseFilter_analyzer

In T362856#9749606, @Wargo wrote:

They had problems T363086 with deployment procedure and I don't know how they finalized it.

I can replicate those on Windows 11 + Edge 124, so the result seems to be independent from the OS newline convetions. Tested /tools on plwiki and both /tools and real filter on a local installation of MW 1.40.

In T363628#9750833, @suffusion_of_yellow wrote:

If that doesn't work, try using new_wikitext_pst.

I've just copied the content of Użytkownik:Swam_pl/brundopis3 to Użytkownik:Msz2001/brudnopis (examine) and the result is the same: the edit is recognized in an examine mode but not while saving.

In T362856#9749452, @Wargo wrote:

No, from 23 to 25. Last event was 18:20, deployments are on 20:00 (in Poland)

The patch that @KartikMistry mentioned was deployed on 22 April to plwiki, but it seems that it doesn't completely prevent unqualified users from publishing translations to mainspace. The edit filter for that caught two cases on 24.04. and 25.04.: https://pl.wikipedia.org/w/index.php?title=Specjalna:Rejestr_nadu%C5%BCy%C4%87&wpSearchFilter=38&uselang=en

I can confirm this on plwiki as well, as reported in https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne#Wyszukiwarka_si%C4%99_popsu%C5%82a (permalink).

In T362139#9724671, @matmarex wrote:

I'll be honest, I'm not sure how it's supposed to work. But I think I managed to restore how it worked.

I set up demo wikis to compare:
Before the bug: https://patchdemo.wmflabs.org/wikis/777f1587e8/w/index.php?title=Test1&action=edit&undoafter=152&undo=153
Current buggy version: https://patchdemo.wmflabs.org/wikis/1010d4fce1/w/index.php?title=Test1&action=edit&undoafter=152&undo=153
After the fix: https://patchdemo.wmflabs.org/wikis/83a92cb3f0/w/index.php?title=Test1&action=edit&undoafter=152&undo=153

If someone here feels like they understand it, I'd appreciate if you could test on those demo wikis as well.

Deployed to wiki

The change was deployed today.

Here are some direct URLs to the Undo page (the versions can get reviewed in a future, though):

• https://pl.wikipedia.org/w/index.php?title=Castel_del_Monte&action=edit&undoafter=67488563&undo=73325709&uselang=en
• https://pl.wikipedia.org/w/index.php?title=Stopa_cukrzycowa&action=edit&undoafter=73029306&undo=73325816&uselang=en
• https://pl.wikipedia.org/w/index.php?title=Polski_Kontyngent_Wojskowy_w_Rumunii&action=edit&undoafter=73004824&undo=73325826&uselang=en

It might be because of T343483: Change mechanism for altering links to Objects to not cache based on user page, and work with Parsoid

In T334940#9605163, @TheDJ wrote:

I would advise the community to look for solutions for graphs outside of the foundation (maybe through a grant or something). I personally still think that running something on toolforge and exporting to SVG which can then be uploaded, is the most flexible, easiest to realize and most usable short term way to enable rich creation tools. It creates a hard separation between security contexts and avoids any sort of fragile dependency on MediaWiki and Wikimedia. The uploading can even be automated, OAuth login and commons uploading are commonly implemented things in tools already.

@Urbanecm The SVGs are available on Commons now:

• icon: https://commons.wikimedia.org/wiki/File:Wikimania_2024_icon.svg
• wordmark: https://commons.wikimedia.org/wiki/File:Wikimania_2024_logo_black.svg
• old-style wiki logo: https://commons.wikimedia.org/wiki/File:Wikimania_2024_wiki_logo_(old_style).svg

I'll provide the SVG versions by tomorrow

The one that's used by the ResourceLoader to ensure users won't get syntactically incorrect code. The one in the editor flags no error (only some warnings and infos and none of them is around the problematic 910th line).

In T357580#9549180, @UOzurumba wrote:

There are changes to how user and site scripts load for Vector 2022 on specific wikis. The changes impacted the following Wikis: all projects with Vector legacy as the default skin, Wikivoyage, and Wikibooks.
Gadgets are not impacted, and the changes will last for the next three months. If you have been affected or want to minimize the impact on your project, see this ticket. Please coordinate and take action proactively.

There's a potentially highly visible regression for wikitables on mobile: T357589: [Regression] Wikitables has unwanted border spacing on mobile

I've just checked and it still persists:

Yeah, OpenSeaDragon looks for .prp-page-image img selector (source code) and as it cannot be found on the page in the task description, the error message is raised. (There's no <img> tag there).

In T340705#9493354, @Candalua wrote:

Some months ago I had applied many optimizations on it.wikisource using the |rights=purge syntax. However, right now the Special:Gadgets page is showing me this error: "The following right does not exist: purge". Did something change in user rights? Maybe the "purge" right does not exist anymore and I have to use something else?

In T334940#9480929, @Tim-moody wrote:

Can someone point me to the policy regarding JS gadgets?