Wikipedia:Village pump (technical)

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
 Policy Technical Proposals Idea lab WMF Miscellaneous 
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.

This Mournable Body[edit]

I have done mistakes in this page by adding citations before the punctuations so can anyone fix it by using this bot User:Erutuon/scripts/footnoteCleanup.js. ​​​​​​​𝐋𝐨𝐫𝐝𝐕𝐨𝐥𝐝𝐞𝐦𝐨𝐫𝐭𝟕𝟐𝟖🧙‍♂️ 10:22, 21 November 2022 (UTC)Reply[reply]

@LordVoldemort728, you can fix it (manually or with the script). It will be fixed by User:WikiCleanerBot eventually anyway. — Qwerfjkltalk 23:17, 25 November 2022 (UTC)Reply[reply]

Downloads for Wikipedia:Wikipedia Signpost very broken[edit]

On the Wikipedia:Wikipedia Signpost page, there are download links for each item. However, the downloads are very broken, since I am getting 10 MB PDFs with 20-30k blank pages inside of them. I don't think that should happen. RPI2026F1 (talk) 22:35, 21 November 2022 (UTC)Reply[reply]

Display:inline-table not working[edit]

The style parameter "display:inline-table" is not working on Current tennis players rankings for some reason. I tried everything but to no avail. Any ideas as to why? Qwerty284651 (talk) 20:48, 22 November 2022 (UTC)Reply[reply]

Addendum: And worse yet: when I transcluded the sections to my subpage, the tables' column headers's borders were cut off. Qwerty284651 (talk) 21:46, 22 November 2022 (UTC) @Izno:, I see you intervened on the rankings page. The thing is, the column headers should stay as they are, not be converted to table captions. Qwerty284651 (talk) 21:52, 22 November 2022 (UTC)Reply[reply]

Those are correctly table captions and it is incorrect to represent them as table headers. See WP:Accessibility. Izno (talk) 21:56, 22 November 2022 (UTC)Reply[reply]
Okay, but that still doesn't explain the fact as to why the tables using the "display:inline-table" style param aren't displaying inline but below each other. Qwerty284651 (talk) 22:04, 22 November 2022 (UTC)Reply[reply]
I see that they are functioning as expected in Vector; the keys are inline with the tables.
What I think you want is for each of the sections' tables to inline with each other. That doesn't work because you have headings between each, which are block display. Izno (talk) 22:12, 22 November 2022 (UTC)Reply[reply]
This appears to be resolved now. The OP has structured the sections using the {{col-begin}} family of templates, which appears to produce the desired result. – Jonesey95 (talk) 22:21, 22 November 2022 (UTC)Reply[reply]
I removed the subsection headings and col-begin, leaving only display:inline table, thinking the headers were the issue, as you pointed out, but they are still one below each other. Display:inline should work like it does in this old version of the page. {{col-begin}} is the easy way out. Was hoping the style param would get the job done, so it's easier to edit the tables in VE, while also keeping both tables in each section inline. Qwerty284651 (talk) 22:26, 22 November 2022 (UTC)Reply[reply]
Will this work for you? – Jonesey95 (talk) 23:05, 22 November 2022 (UTC)Reply[reply]
Found a workaround. Should have know the legend templates between the tables were the cause of the problem. I relocated them to the bottom of the section. Works as intended. Thanks. Qwerty284651 (talk) 00:09, 23 November 2022 (UTC)Reply[reply]
Line break was the issue all along. Qwerty284651 (talk) 01:47, 23 November 2022 (UTC)Reply[reply]

New comments[edit]

It all works great on desktop, but on mobile the table's caption is confined within the first column (skewing up the table, in the process) instead of spanning across the entire table. Qwerty284651 (talk) 02:34, 23 November 2022 (UTC)Reply[reply]

This is operating as expected for captions (besides that it's left aligned rather than centered). Izno (talk) 02:39, 23 November 2022 (UTC)Reply[reply]
But why does it only expand within the first column and is not sort of like colspan-ed across the entire table's width? It looks bad on mobile. And, if that's the default operation for captions, can it be fixed so it's stretched across the whole table? Qwerty284651 (talk) 02:45, 23 November 2022 (UTC)Reply[reply]
You're going to need to provide an image of what you see. The behavior you claim to exist is not the behavior I am seeing, and I know what I'm seeing is also correct behavior. :) Izno (talk) 02:55, 23 November 2022 (UTC)Reply[reply]
Here is the screenshot on mobile. Qwerty284651 (talk) 03:16, 23 November 2022 (UTC)Reply[reply]
I'm seeing the same thing in Safari on iOS. Here's a simplified test case. The second example is the same as the first, but without display:inline-table;. – Jonesey95 (talk) 04:08, 23 November 2022 (UTC)Reply[reply]
Yes, I see it too in Firefox now that I look at the correct resolution.
This appears to be how browsers react to CSS which sets the display of the <caption> to display: block (which is what Minerva and/or MobileFrontend is doing below 720px) when a <table> is display: table-inline.
I don't really understand why the <caption> has that CSS being applied to it since it always "display: block" in the ways that matter for mobile. That's probably a reasonable bug report. Izno (talk) 04:30, 23 November 2022 (UTC)Reply[reply]
Well, I looked at it. If the table is display block (IDK why Minerva sets tables to display block though I've known it's how it is) and the caption is not display: block and also has more content than the table algorithm identifies, then the caption becomes wider than the table. I'm not sure if that's sufficient cause to make it display: block. Izno (talk) 04:39, 23 November 2022 (UTC)Reply[reply]
@Izno, this bug should be reported on Phabricator to get it fixed. Qwerty284651 (talk) 16:14, 23 November 2022 (UTC)Reply[reply]
In the absence of any other setting for the display property, the caption element is display:table-caption; by default. --Redrose64 🌹 (talk) 19:52, 23 November 2022 (UTC)Reply[reply]

Bug in MediaWiki interface involving Template:URL[edit]

Your comment is requested at MediaWiki talk:Titleblacklist-custom-URL regarding a bug I found that breaks the link to the correct page. You can test it as a non-admin by attempting to create a forbidden URL-containing title, such as Https:// –LaundryPizza03 (d) 14:07, 23 November 2022 (UTC)Reply[reply]

Special:Log not remembering the target page[edit]

Right now if you go to Special:Log via "View logs for this page" on page history, e.g. [1], the Target field is empty, so if you modify the form to filter the results and click Show, it shows logs for all pages, unless you fill in Target yourself. And if you do fill in, now the special page remembers the input in that field; this appears to be dependent on whether the URL query includes &wpFormIdentifier=logeventslist. I'm pretty sure it didn't use to be this way and it's annoying. Is this a bug or a (misguided yet) deliberate decision? Nardog (talk) 16:23, 23 November 2022 (UTC)Reply[reply]

Looks like it breaks when wpFormIdentifier isn't passed along. I'll open a bug. — xaosflux Talk 16:36, 23 November 2022 (UTC)Reply[reply]

Why promise 100, 250, 500 when there may not be that many?[edit]

When someone clicks on the View history tab to see Revision history there are clickable numbers that are presented as (newest | oldest) View (newer 50 | older 50) (20 | 50 | 100 | 250 | 500) even when there are fewer than 500, or 250 or perhaps even 100. Is this false advertising? Isn't such a presentation, suggesting that an article that now has say 67 edits, including the initial article, has more edits than advertised? Is this a bug or a misfeature? Nuts240 (talk) 02:40, 24 November 2022‎ (UTC)Reply[reply]

This is a fairly cheap optimization that doesn't pose much of a user mismatch: A static number is cheap on the database and a non-static number is not. Izno (talk) 03:23, 24 November 2022 (UTC)Reply[reply]
Also, false advertising would require us to actually be advertising something.
(Buy edits today, for the low price of $0 per 100 edits!) mi1yT·C 07:21, 24 November 2022 (UTC)Reply[reply]
OK, not false advertising, and not even too misleading, but . . . can an hourly running bot store a count range, so that for "say 67 edits" the '250' and '500' numbers aren't displayed? Can this be put in a "suggested improvement" list? Nuts240 (talk) 19:53, 24 November 2022 (UTC)Reply[reply]
That would require the same changes as your suggestion, and to boot would be less efficient. This is not likely to be a task that will be worked on. Izno (talk) 20:01, 24 November 2022 (UTC)Reply[reply]
No. Read "500" as "up to 500". It's a constantly changing database so any promise, such as next 67 edits, cannot be accurate because pages might be added or deleted at the time you push the button. Johnuniq (talk) 23:33, 24 November 2022 (UTC)Reply[reply]
I don't think "promise" is the right word. What you're describing should really be interpreted as, "show that many revisions if they exist". Partofthemachine (talk) 23:52, 24 November 2022 (UTC)Reply[reply]

Incorrect article count on the Wikipedia landing page[edit]

Something seems to have broken on For some reason the article count for the English Wikipedia is displayed as 657,000+, it should be 6,579,000+. Does anyone know who is responsible for maintaining this page? (talk) 15:54, 25 November 2022 (UTC)Reply[reply]

T323731 * Pppery * it has begun... 16:35, 25 November 2022 (UTC)Reply[reply]
Thanks (talk) 17:25, 25 November 2022 (UTC)Reply[reply]

Mobile Wikipedia front page has wrong article count[edit]

The mobile view home page of Wikipedia ( seems to be giving the wrong article count for the English version - 657k articles instead of 6.57 million. Not sure whether this is the right place to report it but it's been like it for at least a few days. YFB ¿ 00:22, 28 November 2022 (UTC)Reply[reply]

Already discussed at WP:HD#Error on the "" landing page - how to report?. tl;dr: It's not a bug that can be addressed on our (read:en.wp's) end. —Jéské Couriano v^_^v a little blue Bori 00:28, 28 November 2022 (UTC)Reply[reply]

Where did that come from[edit]

I used reftoolbar to cite this web[1] and it autofilled "Malak, Tony" which I can't find anywhere on the source page. Where did it come from and is it right? Gråbergs Gråa Sång (talk) 10:29, 26 November 2022 (UTC)Reply[reply]

It's listed multiple times in the hidden metadata of the page. It seems correct. —TheDJ (talkcontribs) 11:24, 26 November 2022 (UTC)Reply[reply]
Thanks! Gråbergs Gråa Sång (talk) 13:09, 26 November 2022 (UTC)Reply[reply]


  1. ^ Malak, Tony (23 June 2022). "Art in Protest at the 2022 Oslo Freedom Forum". Human Rights Foundation. Retrieved 26 November 2022.

bug in annotated link template[edit]

The annotated link template for Caricatures of Charles Darwin and his evolutionary theory in 19th-century England on Outline of evolution produces the confusing addition "– {{original research". Espoo (talk) 15:00, 26 November 2022 (UTC)Reply[reply]

@Espoo I fixed this. Terasail[✉️] 15:09, 26 November 2022 (UTC)Reply[reply]
Context of the error: The page that was linked (Caricatures of Charles Darwin and his evolutionary theory in 19th-century England) had an empty {{Short desc}} template which meant that {{Annotated link}} just got the first part of the article which was the original research notice. Terasail[✉️] 15:11, 26 November 2022 (UTC)Reply[reply]
Thanks, but deleting the empty short description is only a workaround. Could someone edit the annotated link template so that it adds nothing from an article if its {{Short desc}} template is empty? --Espoo (talk) 15:22, 26 November 2022 (UTC)Reply[reply]
@Espoo The whole point of the template is to add a short description, I added one to the article but if it isn't a good description then the best way to deal with this is to just wikilink it ([[Caricatures of Charles Darwin and his evolutionary theory in 19th-century England]]) Since there is no real point bypassing the core functionality of a template in order to just use the template. Terasail[✉️] 15:26, 26 November 2022 (UTC)Reply[reply]
OK, thanks. I guess we'll just have to live with this kind of confusing description sometimes existing for many months or years (like here since 2018) after being accidentally added when people change many wikilinks to annotated link templates without checking the results. --Espoo (talk) 15:37, 26 November 2022 (UTC)Reply[reply]
{{Short description}} should never be empty. I have submitted a proposed change to that template to check for empty |1=. – Jonesey95 (talk) 02:14, 27 November 2022 (UTC)Reply[reply]

Phantom image in infobox[edit]

Could anyone help me understand why the image Bgc3_logo.svg continues to appear on the page bgC3 after being removed from the code? I have purged the page cache every way I know of. (It is an outdated logo.) (talk) 16:37, 26 November 2022 (UTC)Reply[reply]

The infobox template pulls it automatically if in Wikidata. It needs to be updated (or deleted) there. MB 16:47, 26 November 2022 (UTC)Reply[reply]

Wikimedia error[edit]

Hello community!

I have noticed this error.

In the page there is this error:

“The time allocated for running scripts has expired.”

The Wikipedia languages list is no more available.

is there someone that can kindly fix it?

Many, many, and many thanks in advantage!!! (talk) 17:43, 27 November 2022 (UTC)Reply[reply]

  • This has nothing to do with the English Wikipedia; following the directions at the top of that page also appear to have resolved the problem. — xaosflux Talk 17:49, 27 November 2022 (UTC)Reply[reply]

Request to make a template[edit]


Can anyone make it? Masoud.h1368 (talk) 18:39, 27 November 2022 (UTC)Reply[reply]

Is there a problem with {{IPA-ca}}? Izno (talk) 19:44, 27 November 2022 (UTC)Reply[reply]
@Izno No, I prefer to use {{IPAc-ca}} Masoud.h1368 (talk) 22:10, 27 November 2022 (UTC)Reply[reply]
@Masoud.h1368 well to answer your technical question, yes anyone should be able to make it. (That doesn't mean it is a good idea). If you get an error when attempting, please let us know more details. — xaosflux Talk 22:45, 27 November 2022 (UTC)Reply[reply]

Character only exists in lowercase; blue link leads to nonexistent page[edit]

At Wikipedia:Redirects for discussion/Log/2022 November 24 I linked to ΐ, which is a blue link to a page that doesn't exist. The character has no capital equivalent so combining characters are used, and the link has the iota followed by two combining accents (U+0399 U+0308 U+0301), which is a redirect to Greek diacritics#Diaeresis. Click on the link and it leads to a title (U+03AA U+0301) where the separate iota and diaeresis are combined as "Greek capital letter iota with dialytika". Ϊ́ (U+0399 U+0308 U+0301, which is the redirect's title but actually links to U+03AA U+0301) is a red link. The redirect existed since 2005 and was at the lowercase title until 27 October when it was moved by User:Maintenance script. Is this a known bug? Also can this redirect (and others affected by this change[2]) be moved? Peter James (talk) 20:23, 27 November 2022 (UTC)Reply[reply]

  • @Peter James all title links are automatically capitalized, e.g. k becomes K; seems that the software thinks that ΐ is "lower case" and has an upper case equivalent. See meta:Unicode 11 case map migration for more details on this. It looks like this was a known case. If a new "bug" has been caused by this for a specific title, please open a bug report and link it to phab:T292552. — xaosflux Talk 20:44, 27 November 2022 (UTC)Reply[reply]
    Further on that, there is not a "redirect" (anymore than there is one from k to K) so no on-wiki process or request is going to be able to change that. — xaosflux Talk 20:46, 27 November 2022 (UTC)Reply[reply]

Date calculation error in the software template[edit]

There must be an error in the calculation of days in the software infobox. Please see this article. Notepad++. As of today November 28, the stable release date is November 8, so it should be '20 days ago', but it describes it as '12 days ago.'

This bug is found in various languuage versions. It says '3 days ago' in the Korean version ko:노트패드++, and '17 days ago' in the Chinese version zh:Notepad++. Regpath (talk) 04:28, 28 November 2022 (UTC)Reply[reply]