Wikipedia:Village pump (technical)

The technical section of the village pump is used to discuss technical issues about Wikipedia. Bug reports and feature requests should be made in Phabricator (see how to report a bug). Bugs with security implications should be reported differently (see how to report security bugs).

If you want to report a JavaScript error, please follow this guideline. Questions about MediaWiki in general should be posted at the MediaWiki support desk. Discussions are automatically archived after remaining inactive for five days.

view · edit

Frequently asked questions (see also: Wikipedia:FAQ/Technical)

Click "[show]" next to each point to see more details.

If something looks wrong, purge the server's cache, then bypass your browser's cache.
This tends to solve most issues, including improper display of images, user-preferences not loading, and old versions of pages being shown.

No, we will not use JavaScript to set focus on the search box.
This would interfere with usability, accessibility, keyboard navigation and standard forms. See task 3864. There is an `accesskey` property on it (default to `accesskey="f"` in English). Logged-in users can enable the "Focus the cursor in the search bar on loading the Main Page" gadget in their preferences.

No, we will not add a spell-checker, or spell-checking bot.
You can use a web browser such as Firefox, which has a spell checker.

If you have problems making your fancy signature work, check Help:How to fix your signature.

If you changed to another skin and cannot change back, use this link.
Alternatively, you can press Tab until the "Save" button is highlighted, and press Enter. Using Mozilla Firefox also seems to solve the problem.

If an image thumbnail is not showing, try purging its image description page.
If the image is from Wikimedia Commons, you might have to purge there too. If it doesn't work, try again before doing anything else. Some ad blockers, proxies, or firewalls block URLs containing /ad/ or ending in common executable suffixes. This can cause some images or articles to not appear.

For server or network status, please see Wikimedia Status. If you cannot reach Wikipedia services, see Reporting a connectivity issue.

« Archives, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218

Parent categories

An editor has requested a change to the way we display categories in the Category: namespace. The existing system, which looks approximately like this:

Categories: Category name 1, Category name 2, etc.

does not seem intuitive. @PrimeHunter figured out how to change the existing category footer to something that makes the meaning more obvious:

Parent categories: Category name 1, Category name 2, etc.

and to have this only appear in the Category: namespace (i.e., will not change/screw up any articles).

Could we please get this change implemented here? It would only require copying the contents of testwiki:MediaWiki:Pagecategories to MediaWiki:Pagecategories.

WhatamIdoing (talk) 20:18, 22 January 2025 (UTC)[reply]

This sort of sounds like it would be an overall general improvement - that is not something special for only the English Wikipedia, and for only users with their interface language in en. If so, this should be requested upstream. — xaosflux ^Talk 01:56, 23 January 2025 (UTC)[reply]

I think it'd be better to do this locally, where it's been requested. If it seems to be a net improvement, we could always suggest it for widespread use (which would require re-translation of the string for all 300+ languages – not something that can happen quickly). WhatamIdoing (talk) 03:44, 23 January 2025 (UTC)[reply]

+1 for doing it (it's an improvement), and +1 for doing it locally (no need to wait, and can easily undo the local change if and when upstream decides to do it). DMacks (talk) 19:55, 26 January 2025 (UTC)[reply]

Done The local customisation can be removed if/when a gerrit patch has been merged to change the message across all wikis. – SD0001 (talk) 05:35, 31 January 2025 (UTC)[reply]

Thank you WhatamIdoing (talk) 05:37, 31 January 2025 (UTC)[reply]

This had to be

Undone because it was pointed out that it creates a problem on VisualEditor – which shows the raw code. – SD0001 (talk) 04:08, 3 February 2025 (UTC)[reply]

@SD0001, what do you mean? WhatamIdoing (talk) 04:40, 3 February 2025 (UTC)[reply]

It was causing VisualEditor to display the page footer like this. A MediaWiki fix would be required to handle this properly. Suggest raising a phab ticket. – SD0001 (talk) 04:45, 3 February 2025 (UTC)[reply]

Tracked in Phabricator
Task T385405

I filed a Phab ticket. WhatamIdoing (talk) 04:55, 3 February 2025 (UTC)[reply]

Proposal: Move User:Enterprisey/easy-brfa.js to the MediaWiki namespace

This proposal is not necessarily to turn User:Enterprisey/easy-brfa.js into a gadget, but rather to simply move it to that namespace. The idea behind this is so that people can go to Wikipedia:Bots/Requests for approval/request and just click a button, which would redirect them to that same page plus a parameter such as withJS=MediaWiki:Easy-brfa.js, allowing them to use the tool straight away without having to install it, similar to what we have at DRN. Enterprisey has expressed no objection to this idea off-wiki. JJP_{Mas_ter} (she/they) 01:51, 29 January 2025 (UTC)[reply]

Are you offering to maintain the script? If so, I'll move it. There's a brief earlier discussion at Wikipedia:Bots/Noticeboard/Archive 19#easy-brfa, where there weren't really any objections. – SD0001 (talk) 15:17, 29 January 2025 (UTC)[reply]

@SD0001: I don't know how I would be able to maintain it as a non-interface-admin, but if I could, then I would agree to do so. JJP_{Mas_ter} (she/they) 14:40, 30 January 2025 (UTC)[reply]

@Enterprisey: any comment? — xaosflux ^Talk 19:20, 30 January 2025 (UTC)[reply]

Sounds good to me. I appreciate that it'll be maintained :) Enterprisey (talk!) 03:39, 2 February 2025 (UTC)[reply]

Creation of new citation template for the U.S. Gov Damage Assessment Toolkit (DAT)

The U.S. Government has a website called the Damage Assessment Toolkit (DAT). This website is an interactive map and database, where the National Oceanic and Atmospheric Administration uploads information regarding any tornado in the United States between roughly 2011 to 2025.

Note: This was directed to VPT by administrators after a decent discussion on the Wikipedia Discord Server.

Background of issue

The DAT (screenshot of it seen to the right; Image 1 & Image 2) is cited on hundreds of articles, including GAs and FAs. At several GANs/FACs, as well as on general article talk pages (and at the WikiProject Weather talk page), several users have expressed the desire for a separate citation template for the DAT. Why? Well, the screenshot to the right (Image 1) is a good example. The red line and subsequent triangles along the red line represent the U.S. government's information regarding the 2024 Greenfield tornado (92,000 page view article). The red line represents the track of the tornado and the triangles along the red line represent every "Damage Point" documented by the National Weather Service.

Each of these "Damage Point" triangles is clickable and by clicking the triangle, you can see it contains information. Image 3 to the right shows the information regarding a water tower hit by the 2023 Rolling Fork–Silver City tornado. This specific water tower is (1) actually discussed and mentioned directly in the Wikipedia article and (2) used as a photograph on the Tornadoes of 2023#March 24–27 (United States) article. In fact, that photograph is the photograph of it on the DAT. Since the DAT has photographs, the Commons has a stand-alone copyright-related template for it ({{PD-USGov-DAT}}). However, as seen in Image 3, the DAT does not just contain photographs. Specifically, information from the DAT is cited in the article including: The rating ("EF4") and the comments, "Collapsed water tower, bent just above near base, with anchoring pulled from concrete. Tank contained water, caused crater on ground impact. Potentially compromised by flying debris."

Now, why is this a problem? So, editors and readers alike have to manually change the date in the top right corner of the website (Image 1, Image 2) to match the date desired. The DAT is always being updated/changed, since hundreds of tornadoes occur in the U.S. every year. Because of this, the DAT automatically shows only the last week. Everything from more than a week ago is stored and accessible, by anyone, as long as the date is changed. For example, so see the DAT information for the 2013 Moore tornado (263,000-yearly viewed article), users need to change the date to May 19, 2013 to May 21, 2013. After the date is changed, users have to manually zoom into the area desired. The DAT shows the entire U.S. when it is first loaded up. Once loaded, users can zoom (just like on Google Maps) into the desired area.

To See this, I recommend setting the date from May 19, 2013 to May 21, 2013 and then zooming in on southern Oklahoma City, Oklahoma, to see the entire 2013 Moore tornado.

Due to the interactivity of the DAT, there is no "triangle-specific" or even "tornado-specific" URLs to cite; just the base DAT URL from above. This has led to some incidents of reviewers being unable to instantly verify the information and some other user having to explain how they can verify the information (Talk:2024 Greenfield tornado#Failed verification an example of this issue and subsequent discussion, where Sumanuil, a non-weather editor, was unable to verify the information in the article and another user (myself) had to explain how to verify the information).

What is being requested?

Since URL-specific citations are not able to be created, a citation template is being requested for it (even requested in the past at Wikipedia:Requested templates by Departure– in November 2024, which led nowhere).

The main things the DAT is used as a citation for on Wikipedia articles is the following items:

Tornado Tracks
- Tornado Length {how long was it on the ground for; distance}
- Tornado Width {how wide was the tornado; distance}
- Tornado Track comments {statements by the U.S. government on the tornado; press releases}
"Damage Points"
- The rating of the location(s) on the Enhanced Fujita scale
- Estimated wind speed at the location(s) {in miles-per-hour}
- Damage Point Comments {statements by the U.S. government on the tornado; press releases}

Is there a way for a template to be made which would allow users to cite the DAT-base URL and have options to specify the date, location, and then options for the different things above? The current citation for the DAT (as seen on the Tornadoes of 2024 article) is this: ^[1] The Weather Event Writer (Talk Page) 18:46, 30 January 2025 (UTC)[reply]

+1 - DAT is likely the most cited resource in the tornado editor community. Without the citation template, it will cause confusion. Wildfireupdateman :) (talk) 16:35, 31 January 2025 (UTC)[reply]

@WeatherWriter So the idea is that you'd have a citation template that includes these instructions, along the lines of -

Information on [track length and wind speed] sourced from the "Damage Assessment Toolkit" database, NOAA (2024). Retrieved 2024-01-20.
To access the DAT report, set the dates to cover [2013-05-19] to [2013-05-21], reload, and zoom in to the affected region. Information is available by clicking on the highlighted markers.

I'm not sure offhand of another one that has detailed instructions like this, but {{cite ODNB}} is an example of a wrapper to a standard citation template to add a standard note about access conditions, and that seems to work reasonably well.

I can see how you could knock together a citation template for this and call it along the lines of {{cite DAT|type=track length and wind speed|eventstart=2005-05-22|eventend=2013-05-21|year=2024|retrieved=2024-01-20}}. If that sounds suitable, I can draft you up something? Andrew Gray (talk) 23:18, 2 February 2025 (UTC)[reply]

Track length and wind speed aren't going to help much at all to anyone verifying. Filtering by starting latitude and longitude and including the event_id parameter if possible would be much more helpful. Departure– (talk) 23:30, 2 February 2025 (UTC)[reply]

One more thing: the DAT accepts selecting a single date, from my experience. Setting both the start and end dates to the same date will show all events from just that date. Departure– (talk) 23:32, 2 February 2025 (UTC)[reply]

@Departure– "Track length and wind speed" there is a placeholder - my assumption was you'd put some free text in there to say what details were being sourced. For lat and long - I can see why they'd be useful, but I also can't work out where a user would actually input them into the system, other than by using them to work out where to zoom in?

I've put together a scratch version at User:Andrew Gray/test - this takes an option for date (single or start/end), "sourcing" (ie what's being sourced here, free text), and lat/long (optional). Event ID is included if known, but it looks like a lot of entries don't have one so I've left it optional as well. Feel free to play around with it! It uses only one parser function (#if) and hopefully that should be reasonably self-explanatory. Andrew Gray (talk) 22:49, 3 February 2025 (UTC)[reply]

Honestly, the test version you made would probably work. Just a clarifying question Andrew Gray: Does the "sourcing" parameter show or not show to readers? In the two examples on User:Andrew Gray/test, the parameter is "| sourcing = damage". In the first example, it displays "Information on damage sourced..." and the second example, marked the same, it shows, "Information on this event sourced...". If I was choosing from the examples, the first option would be the best, since the key thing is for readers.

Also, a second question on the "sourcing" parameter: How exactly would that work? I.e. is there set words (like "Damage", "Wind speed", ect...) or is it free-choice? I'm just trying to figure out how that parameter would work exactly.

But yeah, that is more or less exactly what we are hoping for! I appreciate the work you are doing to help the tornado editors out! The Weather Event Writer (Talk Page) 23:21, 3 February 2025 (UTC)[reply]

It's free text - "Information on this event sourced from..." where this event is replaced by whatever you add to the |sourcing= ... element. If that element is blank, it just says "this event" (since that seems generic enough to cover most eventualities).

If you're happy with it then I think you can just go ahead and copy to something like {{cite DAT}} - we can sort out the documentation and so on once you've got a title. Andrew Gray (talk) 00:10, 4 February 2025 (UTC)[reply]

@Andrew Gray: I'm happy with the template! I am not super familiar with template creations, but I went ahead and copied it into {{cite DAT}}. Could you check it over to (1) make sure it works properly now and (2) do the documentation page? I'm trying to watch what you do so I would know how to do this in the future. There is a couple of other weather sources that are unique-enough for their own citation templates, so watching this one's process is teaching me about how to make them going forward. The Weather Event Writer (Talk Page) 02:42, 5 February 2025 (UTC)[reply]

Do you want me to quickly test it in an article, assuming you haven’t already? Either way, looks visually appealing. :) E_F⁵ 13:21, 5 February 2025 (UTC)[reply]

@Andrew Gray: ~~Unless I'm doing something wrong, it appears to be broken.~~ E_F⁵ 13:50, 5 February 2025 (UTC)[reply]

Nevermind, seems to have just been a date issue. E_F⁵ 14:06, 5 February 2025 (UTC)[reply]

@EF5@WeatherWriter Looks good! I've set up a documentation subpage to tidy up the template a little, and I've tweaked it so it no longer has excess whitespace after the entry (it looked a bit odd on the Selma page). Andrew Gray (talk) 21:01, 5 February 2025 (UTC)[reply]

Support – The DAT is a highly useful repository of information for tornado events and their impacts. Having a template to more easily cite it, along with a way to cite where within the DAT information was found, would be highly beneficial for both editors inserting the source and readers looking for where the info was found. Chris ☁️^{(talk - contribs)} 04:23, 5 February 2025 (UTC)[reply]

+1, this would be extremely beneficial to the tornado-space as a whole. A few articles that use the Damage Assessment Toolkit as a reference:

2011 Cullman–Arab tornado (GA)
2015 Garland tornado (GA)
Tornado outbreak and derecho of April 1–3, 2024 (GA)
2011 Ringgold–Apison tornado (GA)

I could name several more, but my point is proven. E_F⁵ 13:37, 31 January 2025 (UTC)[reply]

+1 This came up in the FAC for Belvidere Apollo Theatre collapse - the DAT is a bit of a pain to work with, and it came up for sourcing an image in the aftermath. Ideally, an established reliable source wouldn't require this much explaining to FAC reviewers, so a template is definitely needed. The FAC passed, by the way, so now we've officially got a featured article to add to the articles that would benefit from this template. Departure– (talk) 16:07, 31 January 2025 (UTC)[reply]

References

^ Branches of the National Oceanic and Atmospheric Administration; National Weather Service; National Severe Storms Laboratory (2024). "Damage Assessment Toolkit". DAT. United States Department of Commerce. Archived from the original on 2020-04-23. Retrieved 2024-01-20.

New button in IP contrib page, dead link

Tracked in Phabricator
Task T385086

Hi, there's a new button in IP contributions page, labeled global contributions, that brings you to Special:GlobalContributions/whatever the IP is, that is broken (use Special:Contributions/127.0.0.1 as an example). I believe this is a new mw feature, as the special page does exist on meta wiki m:Special:GlobalContributions), but not yet on the English Wikipedia.

At mw:Trust and Safety Product/Temporary Accounts/Updates in section December it says

"Special:GlobalContributions will be able to display information about cross-wiki contributions from registered users, IP addresses, IP ranges, and temporary accounts in the near future. (T375632)".
Myrealnamm (💬Let's talk · 📜My work) 21:27, 30 January 2025 (UTC)[reply]

@Myrealnamm This is a known bug, see phab:T385086. The special page only exists on wikis with temporary accounts enabled. 86.23.109.101 (talk) 21:43, 30 January 2025 (UTC)[reply]

great… Thanks for the reference! Myrealnamm (💬Let's talk · 📜My work) 22:00, 30 January 2025 (UTC)[reply]

I have used MediaWiki:Nospecialpagetext to add a message to pages like Special:GlobalContributions/86.23.109.101 which is linked on Special:Contributions/86.23.109.101. PrimeHunter (talk) 00:30, 31 January 2025 (UTC)[reply]

The local page id:Special:GlobalContributions/Taylor_49 is broken since today on all wikis, it says "No such special page You have requested an invalid special page.". The global page m:Special:GlobalContributions/Taylor_49 shows something but says "Error loading data from some wikis. These results are incomplete. It may help to try again." and the displayed information is blatantly incorrect (huge increases in page size far above my merits). This is broken not only for IP but also for registered users. It used to work until ca yesterday thus this is NOT a new feature that "will be able to display information" but an old feature that recently stopped working. Taylor 49 (talk) 21:07, 2 February 2025 (UTC)[reply]

Special:GlobalContribs is a new feature. It is not completely developed even if it is deployed to some wikis. And by some I mean about a dozen. It is fine to say it is broken but it is by no means "old". Bugs should be expected in such a case. Izno (talk) 21:43, 2 February 2025 (UTC)[reply]

Well I confused the too prominently visible new id:Special:GlobalContributions/Taylor_49 with good old id:Special:CentralAuth/Taylor_49 that still works as it used to. Nothing is broken, just confusing. Taylor 49 (talk) 21:52, 2 February 2025 (UTC)[reply]

It is confusing Special:Contributions now has a link to Special:SpecialContributions even on wikis where it's not deployed though. Nardog (talk) 10:40, 3 February 2025 (UTC)[reply]

This mostly only works on the meta-wiki right now, it's being worked on in phab:T385086. — xaosflux ^Talk 13:43, 3 February 2025 (UTC)[reply]

Help with selective transclusion

Resolved

– Resolved. ⇌ Jake Wartenberg 18:09, 31 January 2025 (UTC)[reply]

As pointed out here, this template needs to be edited so that the floating link appears on Wikipedia:Requests for permissions, but not Template:Admin dashboard. Any takers? ⇌ Jake Wartenberg 16:00, 31 January 2025 (UTC)[reply]

Tool for listing template param usage

Is there any tool to list pages that transclude a specific template and use (i.e. do not leave it empty) a specific parameter of that template? Janhrach (talk) 19:41, 31 January 2025 (UTC)[reply]

For any template with a TemplateData section in the documentation, click the "monthly report" for this information. – Jonesey95 (talk) 20:44, 31 January 2025 (UTC)[reply]

Thank you, the tool does what I wanted, but unfortunately the template in question doesn't have TemplateData. Is there any other similar tool? Janhrach (talk) 19:56, 3 February 2025 (UTC)[reply]

@Janhrach Easiest way is to add TemplateData and wait until the next monthly report to run. If there is a particular parameter you're interested in, you can add a tracking category, e.g. {{#if:{{{FOO|}}}|[[Category:Pages using template BAR with parameter FOO]]}} You'll still need to wait a while (anywhere from hours to weeks) for all pages that use the template to update unless you force a null edit on each page using something like User:Ahecht/Scripts/refresh. --Ahecht (TALK
PAGE) 21:32, 3 February 2025 (UTC)[reply]

Next steps towards OWID visualization within MediaWiki

We at Wiki Project Med have built a method to visualize Our World in Data with all material coming from Commons. You can see it functional at mdwiki:WikiProjectMed:OWID#Way_3_(current_effort).

Wondering if we can get this and this copied to EN WP so we can begin testing here.

On MDWiki you should be able to:

scroll through the years of data,
if you put your cursor over a country it should highlight and give you the name,
if you put your cursor over the ranges bar, it should highlight all the countries in that range,
if you click on a country it should pull up a graph of how data has changed in that country over time
if you select a region of the world it will zoom into that region

It is built from about 500 seperate images. Doc James (talk · contribs · email) 05:06, 1 February 2025 (UTC)[reply]

We are working on improving functionality on mobile as currently this is poor. Just wanting to begin testing here, it is not ready for us in mainspace. Doc James (talk · contribs · email) 05:15, 1 February 2025 (UTC)[reply]

Global watchlist (for wikis in different languages)

Hi everyone,

I was wondering what the status of using the GlobalWatchlist extension on Wikipedia to have a unified watchlist across different wikis (all Wikipedia, but different languages)?

It seems like there is on-going development work on the extension itself, but I am not finding anything recent on its use for Wikipedia. Is there a trail of this somewhere?

Thanks a lot in advance!

Best, Julius Schwarz (talk) 08:39, 1 February 2025 (UTC)[reply]

It's on Meta-Wiki: m:Special:GlobalWatchlist. Nardog (talk) 09:29, 1 February 2025 (UTC)[reply]

Oh that's neat, thanks a lot! Julius Schwarz (talk) 15:21, 1 February 2025 (UTC)[reply]

unable to add maplink-road to map attribute in Template:Infobox_valley

I'm trying to replace the map attribute in Oak Creek Canyon's Template:Infobox valley with this:

|map = {{maplink-road|from=Oak Creek (AZ).map}}

Unfortunately, when I try I get this:

Lua error in Module:Location_map at line 526: "?'\"`UNIQ--mapframe-0000000D-QINU`\"'?" is not a valid name for a location map definition

It works fine with Template:Infobox river. Any ideas? TerraFrost (talk) 17:08, 1 February 2025 (UTC)[reply]

@TerraFrost The map parameter of {{Infobox valley}} is hardcoded to use {{Location map}}, the infobox fills in the inputs of the location map template with the data from various infobox fields. The map parameter of {{Infobox river}} is much more complex and can take an image, a location map, or a mapframe based map, and therefore it can handle a {{maplink road}} input.

The error you are seeing is due to the location map template having its parameters filled in with a half-parsed maplink-road, which causes the location map template to try to load a nonsense map title.

You need to check the template documentation - the infobox system is a bit of a mess and different templates can have the same parameter name doing different things or having different valid inputs. 86.23.109.101 (talk) 19:42, 2 February 2025 (UTC)[reply]

"this section could not be found" notifiactions

I've been getting those little pop-up notifications saying a section cannot be found when saving the creation of said section. That seems ....a little off. Beeblebrox ^Beebletalks 22:51, 1 February 2025 (UTC)[reply]

@Beeblebrox: It's because you're using templates in section headings. These are never a good idea. --Redrose64 🌹 (talk) 23:17, 1 February 2025 (UTC)[reply]

Huh. I knew you aren't supposed to do that in articles, but I guess I thought it was just an MOS thing, not a technical issue. Thanks for the reply. Beeblebrox ^Beebletalks 18:26, 2 February 2025 (UTC)[reply]

Unused categories script no longer functioning

Hi, I've been using the script User:Qwerfjkl/scripts/unusedCategories.js for almost three years without issue. A few days ago, the script suddenly stopped working, but only here on my laptop at home. At my work desktop, it functions perfectly fine. Any idea can could be causing an issue on my laptop? See also User talk:Qwerfjkl#Unused categories script. ✗plicit 00:51, 2 February 2025 (UTC)[reply]

Widespread background:transparent breaking dark mode

It appears that background:transparent ended up in many templates and other places, causing problems in dark mode. The text is illegibly gray-on-gray. Some examples I found are:

When background:transparent is removed, dark mode is fixed, and I do not see a difference after switching back to light mode and refreshing. It is not clear what it was originally added for, as the default background is already transparent. I propose that we go over all instances of insource:"background:transparent", and for each, either remove it or add a hidden comment why it is necessary. 173.206.40.108 (talk) 00:57, 3 February 2025 (UTC)[reply]

In many cases it simply didn't need to be added. In many others it was added as a default for a parameter, and much of the time before we had ParserFunctions, so there wasn't another option. Otherwise, simple inertia. Its uses can almost always be removed or rewritten to something like {{#if:{{{background|}}}|background: {{{background}}}}}. Izno (talk) 02:05, 3 February 2025 (UTC)[reply]

And in these few, I presume they were probably using NavFrame originally which had a default background that was being overridden. Izno (talk) 02:28, 3 February 2025 (UTC)[reply]

Thank you for accepting the ERs and providing the technical explanation! 173.206.40.108 (talk) 02:46, 3 February 2025 (UTC)[reply]

Please see this MediaWiki page for more detailed advice before proceeding with a bulk task. If you're going to bother doing these edits, please ensure that each instance of background: is accompanied by a color: – Jonesey95 (talk) 04:22, 3 February 2025 (UTC)[reply]

Also, the search link above understates the issue; searching all namespaces results in 152,000 pages, many of which are transcluded in other pages. – Jonesey95 (talk) 15:36, 3 February 2025 (UTC)[reply]

Compare similar discussion at Wikipedia talk:WikiProject Cricket#Interested in joining WP:Cricket (from America, even!), but asking for a favor first... Uncle G (talk) 10:36, 3 February 2025 (UTC)[reply]

Using a template from another wiki

Is there a way to use a template from another language wikipedia? It is a hassle to have to create a whole infobox just for one article. Hawkeye7 (discuss) 19:19, 3 February 2025 (UTC)[reply]

Well, some templates have templatedata that define how to change arguments from one template to another template linked on wikidata. ContentTranslate can then use this information and transfer the information automatically. You should still edit the data. Can not tell if that applies in your case since you did not specify which template it is. Snævar (talk) 19:36, 3 February 2025 (UTC)[reply]

The template I want is fr:Modèle:Infobox Quartier. Hawkeye7 (discuss) 20:03, 3 February 2025 (UTC)[reply]

Templates in one Wikipedia cannot be transcluded in another. Copying the Template code from one Wikipedia and fixing it to translate local namespaces/variables is often needed. The Lua code and magic variables itself should be the same regardless of language, but namespaces might be different. ~ 🦝 Shushugah (he/him • talk) 20:07, 3 February 2025 (UTC)[reply]

Why would the Lua code be the same? Hawkeye7 (discuss) 20:11, 3 February 2025 (UTC)[reply]

@Hawkeye7 Some of the syntax is same, not all; using ChatGPT and correcting it afterwards, came up with {{Infobox neighborhood quarter}}, does this work for you? Will add documentation now...I also noticed {{Infobox Settlement}} exists already ~ 🦝 Shushugah (he/him • talk) 20:20, 3 February 2025 (UTC)[reply]

Thank you! I know about {{Infobox Settlement}} but it is unsuitable. Hawkeye7 (discuss) 21:22, 3 February 2025 (UTC)[reply]

What the? {{Infobox neighborhood quarter}} gives {{Template:Infobox neighborhood quarter}} Hawkeye7 (discuss) 21:25, 3 February 2025 (UTC)[reply]

Why does searching for an exact phrase not work on a phone?

Take for example: [2] and [3]. If you search for a phrase like this on a desktop (either on the mobile or desktop site), you get the intended result immediately. Search for it using a cell phone (again, either on the mobile or desktop site), and it searches for all of the words individually, and your intended result is nowhere to be found. What gives? Home Lander (talk) 20:24, 3 February 2025 (UTC)[reply]

Interestingly, I just discovered that clicking directly on these links with my phone does load the results as intended. But if I manually type the phrase into the search, I get a list of random results containing all or some of the individual words I searched for. Home Lander (talk) 20:27, 3 February 2025 (UTC)[reply]

@Home Lander: If your problem is with phrases in quotes like your examples then I guess your phone uses special characters instead of straight quotation marks. Some special characters are ignored by search. iOS has such a feature called "Smart Punctuation". PrimeHunter (talk) 21:05, 3 February 2025 (UTC)[reply]

Sure enough, I have an iPhone and the quotation mark shown on the keyboard appears to be a standard one, but when entered into the search bar it looks to be curly. I suppose this probably affects all iPhones? If so, would there be a way to make search listen to curly quotes? Home Lander (talk) 21:11, 3 February 2025 (UTC)[reply]

Now filed as phab:T385525. I don't know if this is up to us or Apple to resolve though (i.e. it might have unwanted side-effects to automatically convert those characters back). Quiddity (talk) 21:20, 3 February 2025 (UTC)[reply]

@Home Lander: You can disable iOS "Smart Punctuation" under Settings, General, Keyboard. PrimeHunter (talk) 21:30, 3 February 2025 (UTC)[reply]

Thanks, that worked like a charm! Home Lander (talk) 00:46, 4 February 2025 (UTC)[reply]

It seems to work as expected for me, in both mobile Firefox (logged-in) and mobile Firefox Focus (anon). I have to include the quotation marks around the string of text, and specify the prefix, i.e. "immediate block of sockpuppet ip" prefix=Wikipedia:Administrators (or select the appropriate namespace checkbox) so that it goes beyond article-namespace.

My only guess is it might be due to curly marks, and testing confirms this doesn't work properly (I manually copied curly quotes from the infobox of Quotation mark) and PrimeHunter commented just as I was typing this with the same info! Quiddity (talk) 21:08, 3 February 2025 (UTC)[reply]

Tech News: 2025-06

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

Editors who use the "Special characters" editing-toolbar menu can now see the 32 special characters you have used most recently, across editing sessions on that wiki. This change should help make it easier to find the characters you use most often. The feature is in both the 2010 wikitext editor and VisualEditor. [4]
Editors using the 2010 wikitext editor can now create sublists with correct indentation by selecting the line(s) you want to indent and then clicking the toolbar buttons.[5] You can now also insert <code> tags using a new toolbar button.[6] Thanks to user stjn for these improvements.
Help is needed to ensure the citation generator works properly on each wiki.
- (1) Administrators should update the local versions of the page MediaWiki:Citoid-template-type-map.json to include entries for preprint, standard, and dataset; Here are example diffs to replicate for 'preprint' and for 'standard' and 'dataset'.
- (2.1) If the citoid map in the citation template used for these types of references is missing, one will need to be added. (2.2) If the citoid map does exist, the TemplateData will need to be updated to include new field names. Here are example updates for 'preprint' and for 'standard' and 'dataset'. The new fields that may need to be supported are archiveID, identifier, repository, organization, repositoryLocation, committee, and versionNumber. [7]
One new wiki has been created: a Wikipedia in Central Kanuri (w:knc:) [8]
View all 27 community-submitted tasks that were resolved last week. For example, the OCR (optical character recognition) tool used for Wikisource now supports a new language, Church Slavonic. [9]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 00:06, 4 February 2025 (UTC)[reply]

Should Wikipedia be generally internet-compliant?

There is an accessibility problem with several language templates on WP, which may display tofu for readers who don't use the most common browsers and OS's. There's often an easy fix, but the designers of the templates are not generally willing to implement them, and in fact may reverse them. The response I sometimes get, as here, is that it's not Wikipedia's responsibility to be accessible to users, but rather the user's responsibility to select an OS and browser that are compatible with the particular article that they're reading. Isn't it the philosophy of Wikipedia that it should be generally accessible? And that articles have similar accessibility to readers, rather than that depending on which templates happen to be used? — kwami (talk) 02:11, 4 February 2025 (UTC)[reply]

This is from Template talk:Korean#this template obscures hangul on Firefox. Can you make a short example, maybe in a sandbox. It would have a {{Korean}} example with some simple wikitext to demonstrate the problem. State what appears on your system. If there is an alternative method to display the same text in a way that works, post that as well. Johnuniq (talk) 04:33, 4 February 2025 (UTC)[reply]

Yes, the lead of the Hangul article has {{Korean|hangul=한글}}, which gives Korean: 한글.

As I see it, it displays 'Korean:' followed by two squares with the Unicode character codes D55C and AE00 inside.

I tried signing out, in case it was a problem with my preferences, but that didn't change the display.

This is the fix suggested on the talk page, with {{lang|ko-Hang| and {{lang|ko-Hani| replaced with {{lang|ko|. With that implemented, I saw 'Korean: 한글' with the hangul characters displaying properly, as had been the case the last time I'd visited the article.

I thought the problem was solved, but the fix was reverted with the explanation that it's not the responsibility of template creators to make their templates legible for everyone. — kwami (talk) 07:27, 4 February 2025 (UTC)[reply]

BTW, with my backup browser, Falkon, the template displays correctly whether I'm signed in or not. Thus it doesn't appear to be Mint that's incompatible with the template, but Firefox, or at least Firefox for Mint.

I did update my system/browser as well. No effect. — kwami (talk) 07:32, 4 February 2025 (UTC)[reply]

Yeah, this sounds like a bug in Firefox. Do you see tofu in this table?

	code	result
ko-Hang	`<span lang="ko-Hang">한글</span>`	한글
ko	`<span lang="ko">한글</span>`	한글

In that case, please report it to their bugtracker. --rchard2scout (talk) 08:50, 4 February 2025 (UTC)[reply]

Yes, tofu in row 1, hangul in row 2. Thanks. — kwami (talk) 09:20, 4 February 2025 (UTC)[reply]

As I replied at Template:Korean, the problem is with the user's settings for the Linux fontconfig-config package not Firefox or Wikipedia. 173.206.40.108 (talk) 10:06, 4 February 2025 (UTC)[reply]

How can it be my settings when I haven't personalized them? And why wouldn't they affect other browsers if it's not Firefox? — kwami (talk) 10:27, 4 February 2025 (UTC)[reply]

No tofu using the linuxmint-22.1-cinnamon-64bit.iso live cd. Please verify that you haven't personalized them. 173.206.40.108 (talk) 10:37, 4 February 2025 (UTC)[reply]

I wouldn't know how to personalize them. — kwami (talk) 10:46, 4 February 2025 (UTC)[reply]

Oh yeah, updating sometimes breaks things. I had to reinstall Linux after numbers and symbols started turning into emoji in the Wiktionary Reconstruction: namespace, also due to font problems with lang= set to values outside ISO 639-1. I recommend reinstalling, which would be a faster solution ~~than repeatedly having font problems resurface.~~ Actually, you do have a point about {{korean}} not being ISO 639-compliant as specified by Template:Lang#Syntax_and_usage. 173.206.40.108 (talk) 11:08, 4 February 2025 (UTC)[reply]

From that template documentation: The template also supports properly formatted IETF language tags using subtags that identify the language's script, region, and/or variant. [...] For an up-to-date list of available language, script, region, and variant codes, please refer to the IANA's language subtag registry. And right there in the subtag registry, "Subtag: Hang" is listed. So ko-Hang is a perfectly valid BCP 47 language tag. --rchard2scout (talk) 14:05, 4 February 2025 (UTC)[reply]

The sudo code had no effect, even after restarting my computer. — kwami (talk) 11:00, 4 February 2025 (UTC)[reply]

What is the exact version of your Mint and flavors? Same for Firefox? In Firefox's about:preferences#general > Fonts > Advanced > Fonts for > Korean, does yours has the same as below?

Proportional – Sans Serif
Serif – Default (Noto Serif)
Sans-serif – Default (Noto Sans)
Monospace – Default (DejaVu Sans Mono)
Allow pages to choose their own fonts, instead of your selections above – Checked

— 🧧🍊 Paper9oll 🍊🧧 (🔔 • 📝) 15:10, 4 February 2025 (UTC)[reply]

Thanks! That fixed the issue.

The defaults were different -- they were all DejaVu, not just the monospace -- though 'choose own font' was checked. I changed the defaults to Noto CJK Korean, and that fixed it. Though why Ko and Ko-Hani should be affected differently when 'choose own font' hasn't changed is beyond me. Nor why Korean should be a problem when Japanese isn't with the same generic font settings.

Changing 'other writing systems' from the system default ['serif', 'sans-serif', 'monospace'] to Noto also fixed Burmese, another tofu script in the lang templats that displayed correctly otherwise.

It still strikes me as odd that our language templates override the system default so that scripts no longer display correctly, when not templating text allows the system to display it properly. I would think a language template should improve accessibility, not compromise it. — kwami (talk) 23:07, 4 February 2025 (UTC)[reply]

Issue with The Wrong Move

Hi, I'm going to try to describe this the best I can. When looking up the movie The Wrong Move, using the search function of Wikipedia, you can see the article and below a small description. There is an issue with the description, it says 1975 West Germany film. But obviously the brackets ([[]]) should not be in the description, since that part is not a link. But I don't know where to update that, either on Wikipedia or Wikidata. Attaching a picture of the issue here, just to be sure I'm clear. Thank you in advance for the help, Cimoi (talk) 05:32, 4 February 2025 (UTC)[reply]

@Cimoi. Sorted (I hope). Someone was trying to use wikilinks in the WP:short description, but they don't work in those. Nthep (talk) 07:55, 4 February 2025 (UTC)[reply]

That's a good fix for this one article, but if there's an issue with {{Infobox film/short description}}, it could be affecting a large number of articles. -- John of Reading (talk) 07:58, 4 February 2025 (UTC)[reply]

It could use {{Delink}} instead of {{KillMarkers}}. Nardog (talk) 08:05, 4 February 2025 (UTC)[reply]

Yes, Delink works better. Part of the problem is that Template:Country2nationality does not track unrecognized country names. If someone familiar with Lua is able to add a tracking category to that template's module, that would be helpful. – Jonesey95 (talk) 15:23, 4 February 2025 (UTC)[reply]

Thank you everyone for the fix and the follow-ups to fix this more systematically. I'm happy to now know what this is called and how to look for it! Cimoi (talk) 15:30, 4 February 2025 (UTC)[reply]

"Lua error in Module:TFA_title at line 48: assign to undeclared variable 'today'."

As of today, editing any mainspace article (whole page or section), throws this error above the edit window:

Lua error in Module:TFA_title at line 48: assign to undeclared variable 'today'.

What has caused this? --Redrose64 🌹 (talk) 08:28, 4 February 2025 (UTC)[reply]

I am suddenly seeing the message "Lua error in Module:TFA_title at line 48: assign to undeclared variable 'today'." above the edit window when I edit pages in article space (e.g. Hindu Temple of Wisconsin). Module:TFA_title doesn't seem to have changed recently. William Avery (talk) 08:30, 4 February 2025 (UTC)[reply]

I'm seeing it for articles too, but not for this page. Nurg (talk) 08:38, 4 February 2025 (UTC)[reply]

@MSGJ: Does this have to do with your change here? S.A. Julio (talk) 08:50, 4 February 2025 (UTC)[reply]

The same message appears at Template:Editnotices/Namespace/Main without opening the edit window. Nurg (talk) 09:03, 4 February 2025 (UTC)[reply]

I edited Module:TFA title to remove an unintended global that was causing the above message. I don't know what triggered the error to occur now. Johnuniq (talk) 09:16, 4 February 2025 (UTC)[reply]

Apologies, that's to do with my recent edit request here, which added a require to a module that uses the strict mode, therefore making TFA title strict on accident too. Certainly not a potential error case I expected. Aidan9382 _(talk) 10:06, 4 February 2025 (UTC)[reply]

Module:TFA title had a bug which needed to be exposed before it could be fixed. It's good that your edit request unearthed it. Johnuniq (talk) 10:20, 4 February 2025 (UTC)[reply]

That said it's probably poor practice for modules used as transitive dependencies to require strict. * Pppery * _{it has begun...} 21:30, 4 February 2025 (UTC)[reply]

It's probably poorer practice for modules not to require strict. Izno (talk) 00:24, 5 February 2025 (UTC)[reply]

It's conceivable that a module could have a good reason to use a global variable, although I have not seen one. However, this module had a bug which was only found because strict was used. That's good. Johnuniq (talk) 01:06, 5 February 2025 (UTC)[reply]

Many Unicode scripts won't load

Many of the fonts at Help:Multilingual_support#Scripts won't render properly for me. I'm running the latest version of Microsoft Edge on the most recent update for Windows 10. I first noticed this when Linear B script wouldn't render. I even tried installing two different fonts that support Linear B onto my PC, and nothing changed.--3family6 (Talk to me|See what I have done) 12:43, 4 February 2025 (UTC)[reply]

Link to Edit count/Pie chart, no longer working

My Edit records link, no longer functions properly. GoodDay (talk) 13:36, 4 February 2025 (UTC)[reply]

Is that an old link? The url should look like this https://xtools.wmcloud.org/ec/en.wikipedia.org/X201. Alternatively, go to the bottom of your Contributions page and click Edit Count. - X201 (talk) 14:23, 4 February 2025 (UTC)[reply]

I was required to sign in but after that your link worked. There was a warning on replication lag, which could be causing issues. -- LCU ActivelyDisinterested «@» °∆t° 19:41, 4 February 2025 (UTC)[reply]

Huggle - default fonts and their sizes

Hi,I have modified the font and size settings in my Huggle and would like to revert to the original fonts (3 different fonts) and sizes. If anyone possesses this information, I would greatly appreciate your assistance. Thank you in advance. Cassiopeia talk 23:09, 4 February 2025 (UTC)[reply]

12pt "Helvetica, Arial, sans-serif" [10]. 173.206.40.108 (talk) 00:54, 5 February 2025 (UTC)[reply]

Firefox and Monobook

Does anyone else who's using the MonoBook skin notice that the text seems slightly...different on today's Firefox update (135)? Maybe a smidge smaller? I can't quite define it but there's a definite visual difference for me. I think. - The Bushranger _{One ping only} 23:52, 4 February 2025 (UTC)[reply]

Looked it up and apparently this is intentional. Guess I'll have to get used to it. - The Bushranger _{One ping only} 00:21, 5 February 2025 (UTC)[reply]

If I'm reading the patches in that bug correctly, it may be possible to restore the old behavior by editing Firefox config. Can you try to visit about:config (see https://support.mozilla.org/en-US/kb/about-config-editor-firefox), and create a preference with the name gfx.font_rendering.cleartype_params.force_gdi_classic_for_families and a value of type "String" and value Arial,Consolas,Courier New,Microsoft Sans Serif,Segoe UI,Tahoma,Trebuchet MS,Verdana? It may require reloading the pages or restarting Firefox afterwards. I don't actually see any difference on my computer when doing that, so maybe this option for text rendering has already been removed completely, but maybe I just have some other preferences that cause it to have to effect. Matma Rex talk 18:55, 5 February 2025 (UTC)[reply]

Another option I found by browsing related bugs is setting gfx.font_rendering.cleartype_params.rendering_mode to 2 (default is -1). This one has an effect for me, I took screenshots for anyone else who's curious:

Default (-1): https://phabricator.wikimedia.org/F58364666
GDI classic (2): https://phabricator.wikimedia.org/F58364667

The GDI classic mode seemingly applies much stronger font hinting (it tries to snap characters to pixel boundaries on your screen), which sometimes causes text to be significantly wider or narrower depending on the font size, and generally causes it to appear more crisp at the cost of bad kerning. In my screenshots, you can see this effect very clearly in some places, e.g. the "unwatch" tab, the "Download as PDF" link on the sidebar, or the "Symbolism" link in the table of contents.

Note that unlike the other option, this one will apply to all fonts, and may make some of them look terrible. Matma Rex talk 19:39, 5 February 2025 (UTC)[reply]

AfD Statistics for User

We need a little jump start for updating AfD Statistics for User. It was doing fine until recently. Thanks for any assistant you can give. — Maile (talk) 02:24, 5 February 2025 (UTC)[reply]

WP:REPLAG as usual. Probably due to T384592. This happens from time to time for a day or two and there's nothing anyone can do about it. * Pppery * _{it has begun...} 02:35, 5 February 2025 (UTC)[reply]

Thanks for the helpful info. — Maile (talk) 02:50, 5 February 2025 (UTC)[reply]

FYI - Stil no updates at all. — Maile (talk) 10:54, 5 February 2025 (UTC)[reply]

Interwiki linking to Moore Wikipedia

Is there a way to make an interwiki link to Moore Wikipedia? The standard way to do this would be [[mos:Soraogo]], but that links to the enwiki MOS. Best, House Blaster (talk • he/they) 02:51, 5 February 2025 (UTC)[reply]

{{#interwikilink:mos|Soraogo}} mos:Soraogo Or use #langlink: instead for an interwiki link of the sort Wikidata would produce. * Pppery * _{it has begun...} 03:05, 5 February 2025 (UTC)[reply]

Thank you! House Blaster (talk • he/they) 03:07, 5 February 2025 (UTC)[reply]

m:mos:Soraogo is shorter and recommended by Help:Interwiki_linking#Prefixes. 173.206.40.108 (talk) 03:15, 5 February 2025 (UTC)[reply]

My understanding from Help:Interwiki linking § Prefix codes for linking to Wikimedia sister projects is that w:mos: is the suggested prefix string. isaacl (talk) 04:24, 5 February 2025 (UTC)[reply]

MOS is a special case in which w:mos:foo doesn't actually work. * Pppery * _{it has begun...} 04:26, 5 February 2025 (UTC)[reply]

Redlinks are blue in mobile hatnotes

See Special:Permalink/1260322885 on mobile, where the bluelink in the hatnote actually goes to a non-existent article. Jon (WMF) said that this is intentional, which I think is baffling given that readers and editors have come to expect that bluelinks are supposed to go somewhere extant; they have refused to make any change, so the English Wikipedia will have to do so on its own. I'm therefore seeking thoughts on whether that would be a desirable change – they state that this can be done by either editing the styles CSS page for the module or by creating a skin-specific exemption to the WMF's default (interface administrator needed for the latter).

(Posting here because Module talk:Hatnote has a edit notice saying that I should consider using the village pump instead; will post note there pointing to this discussion). Sdrqaz (talk) 03:51, 5 February 2025 (UTC)[reply]

This is something of a continuation of Module talk:Hatnote#Mobile styling, but I've left a more pointed comment on that task. I would recommend having the discussion at the module talk page, not here. Izno (talk) 04:38, 5 February 2025 (UTC)[reply]

This also prevents visited links from having the right colour. As I don’t see any reason for this to exist, I re-opened that task and created a patch to remove that link colour override in Minerva. stjn 20:04, 5 February 2025 (UTC)[reply]

Bug with Media Viewer

Sometimes when I click on an image thumbnail, just a black screen appears instead of the Media Viewer, with no way to exit other than reloading the page without the #/media/ section. This happens most of the time, but sometimes it works as intended.

I am on Firefox 134.0.2 on Arch Linux. QuickQuokka ^{[⁠talk • contribs]} 11:51, 5 February 2025 (UTC)[reply]

This is probably phab:T385297. Izno (talk) 22:01, 5 February 2025 (UTC)[reply]

@Izno: I do have XTools enabled! And it works with ?safemode=true. QuickQuokka ^{[⁠talk • contribs]} 22:03, 5 February 2025 (UTC)[reply]

Font changed !?

Is anybody notice that the whole English Wikipedia's font got changed ?

Font size so small , narrow between words , lines and darker.

Did English Wikipedia's css or js changed recently ?

Did I missed something happened in community or Phabricator ?

How can I change that to last version ?Comrade John (talk) 13:14, 5 February 2025 (UTC)[reply]

There might be an option in appearance of your preferences. Some skins have different styles for text. APenguinThatIsSilly("talk") 18:45, 5 February 2025 (UTC)[reply]

There seems to have been a recent discussion about the wikis styles, but afiak it does not pertain to font size much other than infoboxes. APenguinThatIsSilly("talk") 18:49, 5 February 2025 (UTC)[reply]

What browser are you using? Maybe this is the same thing as #Firefox and Monobook above. Matma Rex talk 18:56, 5 February 2025 (UTC)[reply]

White space below navbox

Please see the navboxes at the foot of this page, where two or three line returns separate the two if they're in that order, but not if the order is inverted. I'm not clever enough to see what's happening here, hoping someone else will be. (note: I've just edited them to make them autocollapse, but the space was showing before I did so too). Many thanks, Justlettersandnumbers (talk) 18:52, 5 February 2025 (UTC)[reply]

@Justlettersandnumbers It's because there's a line break at the top of Template:Cattle breeds of Spain, the second navbox template. I've removed it now, should be fine now. Myrealnamm's Alternate Account (talk) 19:14, 5 February 2025 (UTC)[reply]

Thanks so much, Myrealnamm-alt! Even I should have been able to see that, but I didn't look in the right place. If only all of life's problems could be so easily resolved! Many thanks, Justlettersandnumbers (talk) 19:36, 5 February 2025 (UTC)[reply]

Created account without visiting the Wiki

Tracked in Phabricator
Task T385752

I'm not sure where to put this, but I went to m:Special:GlobalContributions/ClueBot NG (because I was bored), showed no results, and then closed it. Immediately after, I got the automatic Welcome message at w:ml:User talk:Myrealnamm-alt from the bot. I never visited the ML wiki directly. It might have to do with the fact that ClueBot NG has that Wiki attached (look for ml.wikipedia.org).

So GlobalContribs searches edits with the user account, not from the system directly, it seems? Something like that. Myrealnamm's Alternate Account (talk) 19:06, 5 February 2025 (UTC)[reply]

I tested it in my alternative account User:PrimeHunter2 and the same happened.[11] It's known that local accounts can be created by MediaWiki and attributed to the user without ever visiting a wiki if an edit is imported. Now it can probably also happen without ever editing any Wikimedia wiki. PrimeHunter (talk) 20:04, 5 February 2025 (UTC)[reply]

This seems odd. Now I'm gonna have to start searching if we've accidently linked some metawiki script to mlwiki. — xaosflux ^Talk 20:50, 5 February 2025 (UTC)[reply]

@Pcoombe (WMF): any chance work you've been doing on meta:MediaWiki:FundraisingBanners/LocalizeJS-2025.js could be causing a client to attach to mlwiki all of a sudden? — xaosflux ^Talk 21:02, 5 February 2025 (UTC)[reply]

OK it's not that. — xaosflux ^Talk 21:12, 5 February 2025 (UTC)[reply]

Other thought is that some central notice is providing a link, that some browsers may be opportunistically loading. — xaosflux ^Talk 21:09, 5 February 2025 (UTC)[reply]

Testing notes. Simply logging on to metawiki did not cause my Xaosflux2 user to attach to mlwiki. — xaosflux ^Talk 21:11, 5 February 2025 (UTC)[reply]
But using globalcontributions did. — xaosflux ^Talk 21:12, 5 February 2025 (UTC)[reply]
I've opened phab:T385752 on this. — xaosflux ^Talk 21:16, 5 February 2025 (UTC)[reply]

[DAT-1] Branches of the National Oceanic and Atmospheric Administration; National Weather Service; National Severe Storms Laboratory (2024). "Damage Assessment Toolkit". DAT. United States Department of Commerce. Archived from the original on 2020-04-23. Retrieved 2024-01-20.

[1]