Jump to content

Wikipedia:Village pump (technical)

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 5.64.158.190 (talk) at 05:13, 27 November 2023 (→New Lua module replacement for {{Name in official languages}}). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

 Policy Technical Proposals Idea lab WMF Miscellaneous 
Shortcuts
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.

Purge API seems to still be broken

This is a followup to Wikipedia:Village pump (technical)/Archive 208#Purge API broken? It's still broken for me. I was hoping that T349348, which has been closed as "resolved", would fix it. The code review says the "Change has been successfully merged" and the "Post-merge build succeeded" November 01. But I can't find the MediaWiki release that deployed this patch. Can someone figure out and explain the current status of this? Thanks, wbm1058 (talk) 13:13, 20 November 2023 (UTC)[reply]

Can you clarify what is still broken for you? The bug and the patch you linked are for the Pywikibot framework, but later you talk about MediaWiki, so I am a bit confused. The previous thread you linked is pretty long and also confusing. Matma Rex talk 13:44, 20 November 2023 (UTC)[reply]
Just tried purging a page with forcelinkupdate=1 via ApiSandbox. I can see the page_links_updated value in database is updated. I don't think anything is wrong in MediaWiki; it could be an issue with the client code used. – SD0001 (talk) 13:52, 20 November 2023 (UTC)[reply]
THIS and THIS is the code for my BRFA-approved bot which is running on the Toolforge. It was working fine in August, when I pretty-much wrapped up my project to install this automated process. I've not made any (breaking) code changes since then, as I thought I was done tweaking the code to the point where it just ran itself and no longer needed close supervision. The first page it is attempting to refresh links for is Soygu (which is a redirect). The bot is stuck repeatedly attempting to purge this page, and no error code is returned to indicate there was any problem. Quarry query shows that the date is not being updated. Likely it was last updated by my bot on August 17, 2023. – wbm1058 (talk) 16:48, 20 November 2023 (UTC)[reply]
It seems to me that your bot has successfully purged that page with recursive links update about 50 times per day for the last couple of days (and completed 750,000 other purges every day – I'm surprised we have the logs for this, but we do: [1]). It's interesting that page_links_updated is not being updated, I will try to find out if that's expected or when it changed. It seems like a different issue than the last time (and it seems like the purges are working). Matma Rex talk 18:26, 20 November 2023 (UTC)[reply]
When viewing a Gerrit patch, if you click on the three dots at the top-right and select "Included in", it tells which branches the patch has been merged into. If it were a MediaWiki patch, you can then cross-reference with toolforge:versions to determine if it has been deployed yet. Here however, the patch is to Pywikibot. I see it is included in the 8.5.0 and 8.5.1 releases, so you'll want to make sure your Pywikibot is updated to one of those versions in order for the change to take effect. — MusikAnimal talk 18:46, 20 November 2023 (UTC)[reply]
Thanks for the helpful information. I realize now that I incorrectly assumed it was a MediaWiki patch. I don't think I have access to the Logstash, which would have helped me verify my bot's actions. I guess I could apply for nda group access for researchers and volunteers, if I sign an NDA for access to confidential data?
page_links_updated was definitely getting updated until sometime after August, so answering the question "why did it stop getting updated?" should hopefully lead to the solution. wbm1058 (talk) 19:50, 20 November 2023 (UTC)[reply]
(Logstash is indeed not public, and you could apply to get access, but you're not missing much in this case – I just linked to log messages that indicate that your API requests reach this point in the code: [2]) Matma Rex talk 20:41, 20 November 2023 (UTC)[reply]
I've looked for any recent changes to MediaWiki that would affect this, and I didn't find any. Then I tried doing a similar request using Special:ApiSandbox, and it worked for me – the page_links_updated field got bumped. So I tried running your code, and… it worked too. I'm definitely confused.
My current theory is that your bot is successfully scheduling the links update (as indicated by the log messages), but they are not actually happening for some reason.
In order to test that theory, I'd like to ask you to do two things, and run the script just once with these changes:
  • Uncomment print_r($result); in refreshmainlinks.php line 106
  • Change curl_setopt($this->ch, CURLOPT_HTTPHEADER, array('Expect:'));
    to curl_setopt($this->ch, CURLOPT_HTTPHEADER, array('Expect:', 'X-Wikimedia-Debug: backend=mwdebug2001.codfw.wmnet; log'));
    in botclasses.php line 109
The first will show you the API result, just in case it contains some interesting warnings. The second will enable debug logging on the WMF servers for these requests (wikitech:WikimediaDebug), I'll be able to view the results in Logstash and perhaps we'll find out what is happening.
Matma Rex talk 20:41, 20 November 2023 (UTC)[reply]
OK, I've shut down my bots while we debug this, since they weren't working right anyway... toolforge jobs delete refreshlinks and toolforge jobs delete refreshmainlinks
I started testing this by doing the purges at a slower rate, and then ramped up the speed, figuring I would refresh-links as fast as I could, until the system couldn't keep up... I think the problem may be that the system doesn't have a good way of telling me that it's not keeping up. Now I'll make the code changes and run the test that you requested. – wbm1058 (talk) 21:41, 20 November 2023 (UTC)[reply]
I also commented out the last line of refreshmainlinks.php so that it wouldn't run forever: #goto doit_again;
toolforge-jobs run refreshmainlinks --command "php ./php/refreshmainlinks.php" --image php8.2 -o ./logs/refreshmainlinks.log -e ./logs/refreshmainlinks.log
Running now... wbm1058 (talk) 21:57, 20 November 2023 (UTC)[reply]
console log
PHP version: 8.2.7

Logging in...
GET: https://en.wikipedia.org/w/api.php?action=query&meta=tokens&type=login&format=json (0.175213098526 s) (100 b)
POST: https://en.wikipedia.org/w/api.php?action=login&format=json (0.79974794387817 s) (73 b)
...done.

Days ago to refresh: 95
Current time: 1700517512 (2023-11-20 21:58:32)
Refresh time: 1692309512 (2023-08-17 21:58:32) ==> 20230817215832

Connected to database
mysqli_result Object
(
    [current_field] => 0
    [field_count] => 1
    [lengths] => 
    [num_rows] => 10000
    [type] => 0
)

0> Soygu
POST: https://en.wikipedia.org/w/api.php?action=purge&format=json&assert=user&forcerecursivelinkupdate=1 (3.1107079982758 s) (2223 b)
Array
(
    [batchcomplete] => 
    [purge] => Array
        (
            [0] => Array
                (
                    [ns] => 0
                    [title] => Soygu
                    [purged] => 
                    [linkupdate] => 
                )

            [1] => Array
                (
                    [ns] => 0
                    [title] => Soyinka, Wole
                    [purged] => 
                    [linkupdate] => 
                )

            [2] => Array
                (
                    [ns] => 0
                    [title] => Soynuts
                    [purged] => 
                    [linkupdate] => 
                )

            [3] => Array
                (
                    [ns] => 0
                    [title] => Soyode
                    [purged] => 
                    [linkupdate] => 
                )

            [4] => Array
                (
                    [ns] => 0
                    [title] => Soyons Libres
                    [purged] => 
                    [linkupdate] => 
                )

            [5] => Array
                (
                    [ns] => 0
                    [title] => Soyul
                    [purged] => 
                    [linkupdate] => 
                )

            [6] => Array
                (
                    [ns] => 0
                    [title] => Soyun Kasum oglu Sadykov
                    [purged] => 
                    [linkupdate] => 
                )

            [7] => Array
                (
                    [ns] => 0
                    [title] => Soyuz-7 (rocket)
                    [purged] => 
                    [linkupdate] => 
                )

            [8] => Array
                (
                    [ns] => 0
                    [title] => Soyuz 7K-L1E No.1
                    [purged] => 
                    [linkupdate] => 
                )

            [9] => Array
                (
                    [ns] => 0
                    [title] => Soyuz 7K-LOK No.1
                    [purged] => 
                    [linkupdate] => 
                )

            [10] => Array
                (
                    [ns] => 0
                    [title] => Soyuz 7K-LOK No.2
                    [purged] => 
                    [linkupdate] => 
                )

            [11] => Array
                (
                    [ns] => 0
                    [title] => Sozuza
                    [purged] => 
                    [linkupdate] => 
                )

            [12] => Array
                (
                    [ns] => 0
                    [title] => Soñer, Javier
                    [purged] => 
                    [linkupdate] => 
                )

            [13] => Array
                (
                    [ns] => 0
                    [title] => Soñora, Joel
                    [purged] => 
                    [linkupdate] => 
                )

            [14] => Array
                (
                    [ns] => 0
                    [title] => Soči
                    [purged] => 
                    [linkupdate] => 
                )

            [15] => Array
                (
                    [ns] => 0
                    [title] => Soʻx District
                    [purged] => 
                    [linkupdate] => 
                )

            [16] => Array
                (
                    [ns] => 0
                    [title] => So’a language
                    [purged] => 
                    [linkupdate] => 
                )

            [17] => Array
                (
                    [ns] => 0
                    [title] => Sp1 transcription factor
                    [purged] => 
                    [linkupdate] => 
                )

            [18] => Array
                (
                    [ns] => 0
                    [title] => Sp6likevirus
                    [purged] => 
                    [linkupdate] => 
                )

            [19] => Array
                (
                    [ns] => 0
                    [title] => SpAd
                    [purged] => 
                    [linkupdate] => 
                )

        )

    [normalized] => Array
        (
            [0] => Array
                (
                    [from] => :Soygu
                    [to] => Soygu
                )

            [1] => Array
                (
                    [from] => :Soyinka,_Wole
                    [to] => Soyinka, Wole
                )

            [2] => Array
                (
                    [from] => :Soynuts
                    [to] => Soynuts
                )

            [3] => Array
                (
                    [from] => :Soyode
                    [to] => Soyode
                )

            [4] => Array
                (
                    [from] => :Soyons_Libres
                    [to] => Soyons Libres
                )

            [5] => Array
                (
                    [from] => :Soyul
                    [to] => Soyul
                )

            [6] => Array
                (
                    [from] => :Soyun_Kasum_oglu_Sadykov
                    [to] => Soyun Kasum oglu Sadykov
                )

            [7] => Array
                (
                    [from] => :Soyuz-7_(rocket)
                    [to] => Soyuz-7 (rocket)
                )

            [8] => Array
                (
                    [from] => :Soyuz_7K-L1E_No.1
                    [to] => Soyuz 7K-L1E No.1
                )

            [9] => Array
                (
                    [from] => :Soyuz_7K-LOK_No.1
                    [to] => Soyuz 7K-LOK No.1
                )

            [10] => Array
                (
                    [from] => :Soyuz_7K-LOK_No.2
                    [to] => Soyuz 7K-LOK No.2
                )

            [11] => Array
                (
                    [from] => :Sozuza
                    [to] => Sozuza
                )

            [12] => Array
                (
                    [from] => :Soñer,_Javier
                    [to] => Soñer, Javier
                )

            [13] => Array
                (
                    [from] => :Soñora,_Joel
                    [to] => Soñora, Joel
                )

            [14] => Array
                (
                    [from] => :Soči
                    [to] => Soči
                )

            [15] => Array
                (
                    [from] => :Soʻx_District
                    [to] => Soʻx District
                )

            [16] => Array
                (
                    [from] => :So’a_language
                    [to] => So’a language
                )

            [17] => Array
                (
                    [from] => :Sp1_transcription_factor
                    [to] => Sp1 transcription factor
                )

            [18] => Array
                (
                    [from] => :Sp6likevirus
                    [to] => Sp6likevirus
                )

            [19] => Array
                (
                    [from] => :SpAd
                    [to] => SpAd
                )

        )

)
That's the beginning of my log. I don't think it shows anything abnormal. – wbm1058 (talk) 22:15, 20 November 2023 (UTC)[reply]
OK, it's refreshed 10,000 links in 34 1⁄2 minutes, so you should have plenty of X-Wikimedia-Debug stuff to examine in the logs now. – wbm1058 (talk) 22:47, 20 November 2023 (UTC)[reply]
Yep, I see them, I will have a look. Thanks. Matma Rex talk 23:04, 20 November 2023 (UTC)[reply]
Well, I don't know why this is happening. I filed a task about it, so that someone else from my team might have a look with fresh eyes, feel free to follow along: T351729. It might take us a few days to get around to this (it's the holiday and flu season), I hope the problem is not urgent. Matma Rex talk 15:24, 21 November 2023 (UTC)[reply]
Perhaps there's one more thing we could try: could you try to run your bot script once using another account, and check if it succeeds? And also, could you try to perform the purge using Special:ApiSandbox#action=purge&forcerecursivelinkupdate=1&titles=... while logged into your bot account, and check if it succeeds? If one of these methods works, that might help us guess where the problem lies. Matma Rex talk 15:28, 21 November 2023 (UTC)[reply]
I picked two random pages with August "links-updated" dates (verified by a Quarry query), then logged into the Bot1058 account (using the normal password, not the BotPasswords password) and performed the API sandbox purge. It worked!
Bot1058 API sandbox results
    "batchcomplete": true,
    "purge": [
        {
            "ns": 0,
            "title": "Speciestaler",
            "purged": true,
            "linkupdate": true
        },
        {
            "ns": 0,
            "title": "Specific State Memory Recall",
            "purged": true,
            "linkupdate": true
        }
    ],
    "normalized": [
        {
            "fromencoded": false,
            "from": "Specific_State_Memory_Recall",
            "to": "Specific State Memory Recall"
        }
    ]
Noting one difference, in the API sandbox results, "purged": true, and "linkupdate": true which in the console log they are null: [purged] => and [linkupdate] =>
I'm not sure whether that's a significant difference. – wbm1058 (talk) 20:01, 21 November 2023 (UTC)[reply]
The difference is because ApiSandbox applies formatversion=2 param. – SD0001 (talk) 06:12, 22 November 2023 (UTC)[reply]
Right, thanks. I added &formatversion=2 to the API call and ran the test again. Returned "1" rather than "true" but I suppose that's just a matter of variable-type declarations.
console log, with &format=json&formatversion=2
Array
(
    [batchcomplete] => 1
    [purge] => Array
        (
            [0] => Array
                (
                    [ns] => 0
                    [title] => Soyinka, Wole
                    [purged] => 1
                    [linkupdate] => 1
                )

            [1] => Array
                (
                    [ns] => 0
                    [title] => Soynuts
                    [purged] => 1
                    [linkupdate] => 1
                )
Checking the Quarry query, still failed to update page_links_updated. – wbm1058 (talk) 17:00, 22 November 2023 (UTC)[reply]
Finished another 10K edits run with X-Wikimedia-Debug stuff, under a different bot account of mine. Checking with Quarry for a couple of the pages that it was supposed to have purged, they still show page_links_updated August 17. So it still fails when running under a different account. Hmm, wbm1058 (talk) 22:43, 21 November 2023 (UTC)[reply]

Zoom messed up on iOS 17

I recently updated my phone from iOS 16 to iOS 17.1.1. When I access Wikipedia’s desktop site on my phone, every page I load starts out zoomed in about 200%. I can pinch to fully zoom out, but it’s annoying that I have to do that on every page. Also the width of the search bar is messed up. Are these known bugs, or is this because of some sort of browser setting on my end? —pythoncoder (talk | contribs) 20:16, 21 November 2023 (UTC)[reply]

Might be a setting, because i'd expect a lot of people to report about such a problem if it were widespread. Have you checked the fontsize option (under the Aa button) in the browser ? It's persisted per website, so if you accidentally change it, you are stuck with it until you reset it to 100%. —TheDJ (talk • contribs) 23:10, 21 November 2023 (UTC)[reply]
Just noticed this thread and realized it's the same for me, I updated a 12 mini to iOS 17.1.1 and have the same result. Home Lander (talk) 16:58, 23 November 2023 (UTC)[reply]

Email Problem

Hello! Recently, I sent emails directly to an @wikipedia.org address and emailed a user via Special:EmailUser founction. However, both got no response. Is there any technique issues or am I blacklisted? How do I fix it? Thanks.--Whisper of the heart 03:03, 22 November 2023 (UTC)[reply]

@Whisper of the heart: Your Wikipedia mail should be working. Have anyone said they don't receive mails from you or are you merely wondering why they haven't replied? That's not a technical issue but you can mail yourself or me as a test if you want. PrimeHunter (talk) 20:20, 22 November 2023 (UTC)[reply]
OK, I will send a test email to you. Whisper of the heart 20:47, 22 November 2023 (UTC)[reply]
@Whisper of the heart: I got the mail. PrimeHunter (talk) 20:50, 22 November 2023 (UTC)[reply]
Great! It seems that my email is working, but receivers haven't replied for some reason. Thanks a lot--Whisper of the heart 21:10, 22 November 2023 (UTC)[reply]
@Whisper of the heart: If you email somebody via Special:EmailUser, the recipient is not obliged to respond. Indeed, over the last fourteen years about twenty people have sent emails via Special:EmailUser/Redrose64 and IIRC I only replied to one of them, and that was concerning when this RfA should be filed. You might wonder why I have email set up if I have no intention of responding: it's in case I forget my password (this has actually happened). --Redrose64 🌹 (talk) 22:37, 22 November 2023 (UTC)[reply]
@Redrose64: Make that at least two; you responded to mine :-) ... I do intend on following up on that one properly (by making my way to your neck of the woods) within the next year ... this is not a threat. :-) Graham87 (talk) 10:11, 23 November 2023 (UTC)[reply]
The boilerplate appended to mail sent through Special:EmailUser actually warns against responding, at some length. —Cryptic 22:46, 22 November 2023 (UTC)[reply]
@Redrose64 FYI, in Special:Preferences you can turn of "allow users to email me", while keeping your email for password recovery. — xaosflux Talk 22:48, 22 November 2023 (UTC)[reply]
You people are right, actually I also set up rules to filter emails including Wikipedia's robot messages to another folder...--Whisper of the heart 11:32, 23 November 2023 (UTC)[reply]
You also mentioned a direct email to a @wikipedia.org address. I don't know about other addresses, but if that was emergency@wikipedia.org, you should definitely have received a reply, probably within about 10 minutes or so. If you didn't, don't assume your message has been read. Suffusion of Yellow (talk) 23:41, 23 November 2023 (UTC)[reply]
I'll add that the emergency email seems to have been having problems with emails being directed to the spam folder. This may or may not be the same with whichever wikipedia email address Whisper of the heart was directing their email towards. EggRoll97 (talk) 01:31, 25 November 2023 (UTC)[reply]

So, I've been using one-click archiving on my talk page for years. I realized it was a little cluttered today so I went to archive some stuff, only to find the links on the section headers are gone. Checked a few other pages that I know use one-click and I'm not seeing them there either. Beeblebrox (talk) 23:56, 22 November 2023 (UTC)[reply]

@Beeblebrox: the script you're using, User:Technical 13/Scripts/OneClickArchiver.js, was blanked due to it being broken. Using a fork such as User:Evad37/OneClickArchiver.js should work. Elli (talk | contribs) 00:01, 23 November 2023 (UTC)[reply]
Oddly, it tried to stop from saving the code, saying it contains errors, but I just confirmed it is working just fine. Thanks! Beeblebrox (talk) 00:22, 23 November 2023 (UTC)[reply]
Resolved
–Novem Linguae (talk) 18:39, 24 November 2023 (UTC)[reply]

Readability improvements: prototype testing results and next steps

Hi everyone,

In the past few months, the Web team from the Wikimedia Foundation has started working on the project Accessibility for reading. Our goal is to improve the typography on the desktop and mobile sites, and build an easy way for logged-in and logged-out users to set their preferred typography.

Cohorts of designs sent by editors

In October and November, we shared a prototype with 13 Wikipedia language communities and received feedback from more than 600 editors and other logged-in users. The prototype allowed them to experiment with different font sizes, line height, and paragraph spacing, and report which configuration was most comfortable for them.

The majority preferred a slightly larger font size and line height than the current default (around 15 – 17px). A large group showed a strong preference for the current default (14 px), while a smaller group preferred significantly larger font sizes (20–24px). See the full results of the testing.

First version of the new Theme menu when the Tools menu is hidden

We learned that editors who decided to take part in the test are interested in changes. We hope that small, medium, and large options to choose between will be received positively.

In the first half of December, on all wikis, we will launch a new beta feature which allows to select the preferred typography. The feature will be opt-in and available in your user preferences. Turning it on will display a new collapsible menu in the right sidebar, which will appear under the Tools menu.

We invite you to look out for it, try it out when it becomes available, and tell us what you think. In the meantime, if you have time - read over the report linked above and take a look at the mock.

(If you're curious about tiny details, there's a small error on the mock, the Tools menu should be next to the "View history" link and the watch star. Also, we may choose the wording "Night mode" instead of "Dark mode". The "hide" button doesn't have brackets and the word "Theme" is bolded out because this mock is built upon visual changes which we're rolling out next week, and which we mentioned in Tech News: 2023-47 - learn more about that here).

Thank you! SGrabarczuk (WMF) (talk) 01:17, 24 November 2023 (UTC)[reply]

"Night mode" risks confusion with things like windows Night Light and its reduced blue.©Geni (talk) 01:30, 24 November 2023 (UTC)[reply]

Greetings, Hoping the following is not "off-topic", as I thought to share my Monobook skin Font and Color changes for readability.

Recently, I downloaded and installed Font Inter from Github here. Inter a trademark of Rasmus Andersson (DBA: RSMS) This font IMO is very readable and "easy-on-the-eyes"; and contains many foreign language glyphs.

Within my fav Skin (monobook.css), I made these changes:

  1. Content (font-family) = "Inter Medium" - very readable
  2. Content color = 800000 (Maroon) - a dark font color choice
  3. Content background = ffe4e1 (Misty Rose) - contrast color for maroon
  4. Wikilink font = "Inter" - slightly lighter than Inter Medium
  5. Wikilink color = 348781 (Aquamarine Stone) - tones down Blue default

Since computer displays show colors and contrasts differently, these settings can be changed for individual needs. I am certain these choices may not be for everyone but I am hoping this example is helpful, especially for editors with visual difficulty , and those with many hours of Wikipedia updates. Regards, JoeNMLC (talk) 16:00, 24 November 2023 (UTC)[reply]

Template:Copyvio

Hi. Could someone with some technical expertise have a quick look at Template talk:Copyvio/core#Requested move 14 November 2023. It is sitting in the RM backlog and has been unopposed for over a week but I worry that carrying out the move as proposed could break things. Jenks24 (talk) 08:32, 24 November 2023 (UTC)[reply]

I've taken care of this — Martin (MSGJ · talk) 13:10, 24 November 2023 (UTC)[reply]
Resolved
–Novem Linguae (talk) 18:38, 24 November 2023 (UTC)[reply]

Mass revert moves

Hello! Is there a way for mass-reverting moves? In my homewiki we're in a situation where we need to mass-revert some hundred pages moved recently (together with their talk pages). Any way to achieve that without needing to manually move each one? I thought I'd ask here for help, maybe you can point me into a tool or a native way to achieve that. - Klein Muçi (talk) 11:57, 24 November 2023 (UTC)[reply]

User:SD0001/massMoveRevert.js. – SD0001 (talk) 12:43, 24 November 2023 (UTC)[reply]
SD0001, thank you very much! — Klein Muçi (talk) 13:19, 24 November 2023 (UTC)[reply]
Resolved
–Novem Linguae (talk) 18:38, 24 November 2023 (UTC)[reply]

Adjust video thumbnails

Not a good thumbnail
Good thumbnail but no longer opens the video player

I uploaded a video but was not blessed with a good thumbnail. So I uploaded File:Ubisoft Quebec office in 2013 thumb.jpg, this worked but now the video player doesn't open anymore.
How do I adjust the thumbnail for a video? — Alexis Jazz (talk or ping me) 16:56, 24 November 2023 (UTC)[reply]

This probably got broken in the figure element rewrite. You can also use the thumbtime parameter to get the thumb of an offset in the video. Ill file a ticket later tonight. —TheDJ (talk • contribs) 17:13, 24 November 2023 (UTC)[reply]
TheDJ, thanks, that's exactly what I was looking for! Somehow thumbtime wasn't documented on mw:Help:Images. I had already filed phab:T351937, I changed it from a feature request to a bug report. — Alexis Jazz (talk or ping me) 18:45, 24 November 2023 (UTC)[reply]
It’s documented at mediawikiwiki:Extension:TimedMediaHandler#Syntax_synopsis and probably also somewhere at Commons. —TheDJ (talk • contribs) 19:08, 24 November 2023 (UTC)[reply]
Also at WP:EIS#Video files. --Redrose64 🌹 (talk) 13:53, 26 November 2023 (UTC)[reply]

Check completeness of transclusions

{{Check completeness of transclusions}}

The tool doesn't work. Again.

504 Gateway Time-out. HandsomeFella (talk) 07:59, 25 November 2023 (UTC)[reply]

And the error page gives the name of the people who maintain it. —TheDJ (talk • contribs) 09:38, 25 November 2023 (UTC)[reply]

Pages using infobox boxer (amateur) with conflicting parameters

The latest run of Special:WantedCategories features a redlink for an infobox-generated (hence unremovable) maintenance category that I don't know what to do with, Category:Pages using infobox boxer (amateur) with conflicting parameters. I don't know if this is a category we want, or if it's one that should just be banished into the ether — and even if we want it I have absolutely no idea where it would belong in the category tree, while if we don't want it then I have no idea how to make it go away.

So could somebody with more knowledge about infobox maintenance categories either create the category if it's wanted, or kill it off so that it's never generated at all anymore if it isn't? Thanks. Bearcat (talk) 15:21, 25 November 2023 (UTC)[reply]

I have created the category. * Pppery * it has begun... 16:39, 25 November 2023 (UTC)[reply]
@Bearcat: The template {{Infobox boxer (amateur)}} has this code 
{{#invoke:Check for clobbered parameters|check
| template = [[Template:Infobox boxer (amateur)|infobox boxer (amateur)]]
| cat = {{main other|Category:Pages using infobox boxer (amateur) with conflicting parameters}}
| nicknames; nickname
| weight class; weight_class
| medals; medaltemplates
}}
and as long as that code is present, Category:Pages using infobox boxer (amateur) with conflicting parameters should exist.
When there are pages listed in that cat, the thing to do is to visit the page (e.g. Luke Jackson (boxer)), and edit the lead section. Then, without altering anything, click Show preview. This will yield a message like this:
Preview warning: Using more than one of the following parameters in infobox boxer (amateur): medals, medaltemplates.
Return to the point where you were editing the lead section, locate the parameters concerned - in this case |medals=2006 Commonwealth Games and |medaltemplates=
{{MedalCompetition|[[Boxing at the Commonwealth Games|Commonwealth Games]]}}
{{MedalBronze| [[2006 Commonwealth Games|2006 Melbourne]] | [[Boxing at the 2006 Commonwealth Games|Featherweight]]}}. Decide whether they should be combined, or one of them simply removed. Amend and save, the page should drop out of the category. --Redrose64 🌹 (talk) 16:31, 26 November 2023 (UTC)[reply]

Section size

WP:SIZE#If you have problems editing a long article says Often you can edit the article one section at a time by using the "Edit" links you see next to each header in the article. This should work as long as none of the sections are longer than 32 kB Is this limit still correct? Hawkeye7 (discuss) 20:09, 25 November 2023 (UTC)[reply]

I don't really understand why that number is there. There is no particular limit in either section or full page editing (well, there is for full pages, but it takes a lot of text to get there and the engine will tell you it's at the limit).
I would recommend changing it to something along the lines of "if the section also isn't large" or similar. Izno (talk) 23:19, 25 November 2023 (UTC)[reply]
The hard 32 kB limit was there because Netscape Navigator 4.76 and Opera 6.04 had problems with edit fields larger than that size. Per the Netscape Navigator and History of the Opera web browser, those web browser versions were released in the late 1990s and 2001, respectively. I wouldn't be surprised if these browsers are now unable to read Wikipedia pages, much less edit them, so I've edited the guideline accordingly. Graham87 (talk) 06:12, 26 November 2023 (UTC)[reply]

Insert and Delete Tags

This question is about the ins and /ins tags, and presumably the del and /del tags. If I omit the / in the closing tag, and so have an extra ins, and then have another insertion, it appears that its end tag does not turn off the underscoring. My inference is that the extra insert tag not only fails to turn off the insertion (of course), but specifies two levels of insertion, so that multiple turn-off tags are also required.

Also, is there a way that I can display the tags with the angle brackets rather than having them actually do their thing? Robert McClenon (talk) 22:17, 25 November 2023 (UTC)[reply]

You can use nowiki tags to disable tags. For a shorthand you can also use < as the opening bracket and that will display the tag. Or you can use {{tag}}.
Your understanding is correct. Open a tag and forget to close it, you now simply have two open tags which both need closing. Izno (talk) 23:16, 25 November 2023 (UTC)[reply]
{{Tag}} is very nice. Like this: <ins>...</ins>. It also has fun options for showing just one kind of tag, like this: </ins>. – Jonesey95 (talk) 00:40, 26 November 2023 (UTC)[reply]

CodeMirror button for wikitext syntax highlighting is gone

I'm using source editor with editor toolbar ("2010 wikitext editor"). But the button for syntax highlighting is gone. It's called "Activate highlighting in wikitext" at Help:Edit toolbar. It is supposed to be between dropdown "Advanced" and puzzle-piece icon button . Instead, I see button called "Reference" .

As far as I know, this button comes from Extension:CodeMirror, which is still enabled according to Special:Version. In preferences, I have:

  • Preferences → Editing → Tick Enable the editing toolbar This is sometimes called the '2010 wikitext editor'.
  • Preferences → Editing → Empty Enable the visual editor
  • Preferences → Editing → Empty Use the wikitext mode inside the visual editor, instead of a different wikitext editor
  • Preferences → Editing → Tick Enable editing tools in source mode
  • Preferences → Gadgets → Editing → Tick (S) Syntax highlighter: Alternative to the default coloring of wiki syntax in the edit box (works best in Firefox and works almost all of the time in Chrome and Opera)
  • Preferences → Gadgets → Editing → Empty Enable the legacy (2006) editing toolbar. This will be overridden by the "Enable the editing toolbar" option in the Editing tab.

There was a discussion ~ten ago about CodeMirror, which also mentioned tweaking the UI, but I'm not sure it is related. How do I get the button back? —⁠andrybak (talk) 22:45, 25 November 2023 (UTC)[reply]

Check an edit page in safe mode e.g. https://en.wikipedia.org/wiki/WoW?action=edit&safemode=1 . If it works there, you have a conflicting gadget or script enabled and will need to identify which. Izno (talk) 23:12, 25 November 2023 (UTC)[reply]
Thank you, Izno. I've tried safe mode, and unfortunately it is still "Insert a template Reference Advanced" for me. —⁠andrybak (talk) 23:16, 25 November 2023 (UTC)[reply]
@Andrybak: You need to disable the syntax highlighter gadget; this is unrelated to the CodeMirror extension. If you're wondering how it could possibly interfere while in safe mode, CodeMirror apparently checks for for this gadget (and also WikEd), and won't load if it's enabled. Suffusion of Yellow (talk) 18:54, 26 November 2023 (UTC)[reply]
Suffusion of Yellow, thank you. That's it, I got button again.
This is a recent change, introduced in commit c0b0100 (Add $wgCodeMirrorConflictingGadgets instead of checking wikEd directly, 2023-10-10). The change seems to come from phab:T178348, quote Investigation: CodeMirror and WikEd gadget (and maybe other syntax highlighting gadgets) don't get along well
I couldn't find any mention of DotsSyntaxHighlighter in any related tickets or commits. So it seems, that the combination CodeMirror+DotsSyntaxHighlighter is only hypothetically causing problems? The combination works fine for me. I used DotsSyntaxHighlighter most of the time, and enabled CodeMirror on a case-by-case basis for complicated template edits.
Thankfully, I found a workaround on mw:User:Remember the dot/Syntax highlighter. Add the following to common.js to load DotsSyntaxHighlighter without it being detected by CodeMirror:
mw.loader.load('//www.mediawiki.org/w/index.php?title=MediaWiki:Gadget-DotsSyntaxHighlighter.js&action=raw&ctype=text/javascript');
@MusikAnimal FYI this whole section. —⁠andrybak (talk) 02:01, 27 November 2023 (UTC)[reply]

Is this map/template fixable?

So while browing Wikipedia as a reader, I noted that Template:State historic sites of Louisiana map is being used at List of Louisiana state historic sites. If I'm reading the code right, this is created by taking an underlying map, and then overlaying the pins by hard-coding a pixel location in the template. This works at a standard presentation on a laptop, but at least on my mobile the way this code is written creates a warping of pin locations - everything is shifted to the west to the extent that Mansfield and Fort Jesup are showing up in Texas. Hardcoding pixel locations like this can't be a best practice. Is there any way to fix this within the current template, or does this just need replaced with something derived from Template:Location map? Hog Farm Talk 00:43, 26 November 2023 (UTC)[reply]

I'd start by replacing it with one of the few standard templates, yes. If that doesn't fix it, that's a bigger problem. (Memory says those aren't perfect but also aren't as broken at low resolution.) Izno (talk) 01:47, 26 November 2023 (UTC)[reply]
It works for me to remove text-align:center in the article.[3] PrimeHunter (talk) 10:21, 26 November 2023 (UTC)[reply]
With text-align:center the map was centered above the caption so if the caption has a longer line than the map width then the map is moved to the right. The pins were not moved so that's bad. In my desktop view the first caption line is slightly longer than the map so the pins also became slightly displaced for me in desktop. It was much more in mobile. PrimeHunter (talk) 00:22, 27 November 2023 (UTC)[reply]

Emboldening a boundary in a table

Hi,
Will someone who knows table formatting please have a look at the table in this page. I wonder about making the association of the four source language headings with system variants more evident. Ie. "Source Texts in Oberon" should associate with the variants preceding "Source Texts in Oberon-2" and "Source Texts in Oberon-2" should associate with variants between that and "Source Texts in Active Oberon". Might be clear enough already but I imagine emboldening the line above each "Source Texts" heading. Thanks, ... PeterEasthope (talk) 14:50, 26 November 2023 (UTC)[reply]

@PeterEasthope: The column headers in the middle would be against MOS:COLHEAD in the English Wikipedia but I don't know Wikibooks. I have added style="border-top: solid 2px".[4] PrimeHunter (talk) 16:32, 26 November 2023 (UTC)[reply]
Single header alternative:
  1. Make source text the first column
  2. Use rowspan to make its cells multi row
  3. Apply background colour and bold to make it look like a heading.
  4. Rotate text 90 degrees so it consumes little horizontal space
Uwappa (talk) 16:41, 26 November 2023 (UTC)[reply]
Please don't Apply background colour and bold to make it look like a heading, it will create an accessibility problem. If it's supposed to be a header for the row, mark it up as a header cell (by using ! at the start of the line instead of |) and give it the attribute scope=row. --Redrose64 🌹 (talk) 16:50, 26 November 2023 (UTC)[reply]
If you want to rotate a header then Wikibooks has b:Template:Vertical header although it's only used in one page. PrimeHunter (talk) 17:12, 26 November 2023 (UTC)[reply]
Broken into multiple tables again, to avoid violation of MOS:COLHEAD. With multiple tables, the emboldened line is not required. I find the uniform column widths aesthetically preferable to distinct widths in each table.
Is a table heading better than the column spanning heading such as "Source Texts in Oberon"? Thx, ... PeterEasthope (talk) 02:33, 27 November 2023 (UTC)[reply]

New Lua module replacement for {{Name in official languages}}

Hello, I've decided to make a Lua module to replace {{Name in official languages}}. I'd appreciate it if anyone could check whether the code has any issues.

At the moment I'm trying to figure out how to create wikilinks for the languages, which I'm having trouble with, due to Lua error at line 22: attempt to concatenate local 'display' (a nil value).

It's at: Module:User:A diehard editor/Name in various languages

- A diehard editor (talk | edits) 17:37, 26 November 2023 (UTC)[reply]

No templates in section headers.
Not at all clear to me what it is that you are trying to do. It appears that you are attempting to use Module:Lang/data to get language names from language tags. Your life might be easier if you use the functions built into Module:Lang that already do that. For example, your test template has 'en = English' so I presume that you want to fetch the language associated with en from Module:lang/data. You can do that with a template call that looks like this:
{{lang|fn=name_from_tag|en}} → English
You can require() Module:lang into your module to do the same thing: 
local lang_mod = require ('Module:Lang');
local language_name = lang_mod._name_from_tag ({'en'});
Or, because I suspect that the variety of languages needed is limited, you are probably better off using the MediaWiki magic work {{#language}} to get the name associated with a language tag:
{{#language:en|en}} → English
You can also do this in your module: 
local language_name = frame:callParserFunction ({name='#language', args={'en', 'en'}});
—Trappist the monk (talk) 20:00, 26 November 2023 (UTC)[reply]
Changing my mind. Better to require ('Module:Lang') because you will have to anyway to properly render the official name associated with the language tag.
Also, no need to construct language name links (as you are attempting in line 22. The call to Module:lang to get the language name can be tweaked to get a linked version: 
local lang_mod = require ('Module:Lang');
local language_name = lang_mod._name_from_tag ({'en', ['link'] = 'yes'});
The call to Module:lang to render the official name looks something like this: 
local official_name = lang_mod._lang ({'en', 'official name'});
—Trappist the monk (talk) 20:32, 26 November 2023 (UTC)[reply]
(If not covered above)
Hi,
So, basically you can't concatenate nil, yet display is indeed nil because you're feeding in values that aren't in language_names (Module:Language/data/iana_languages). This is because you're still iterating over the frame arguments including width, font_size & name as the frame object exposes its parameters via a metatable-provided interface, so your attempt to set these to nil has no effect. Because you intend to support multiple languages, and so multiple parameters, you'll need to filter out these other parameters in your iteration. However, you can't just exclude these three (width, font_size & name) because users may stuff in other random ones too, so you'll need to check the item exists within your language_names first. Due to the structure of your code, checking in ::resolve_language is too late, because you'll have already set up table lines by that point, so you'll need to check before constructing the row, e.g. in p.main.
Note too that Module:Language/data/iana_languages has entries with multiple ISO 639-1 names, e.g. "cu", so you may want to consider handling these. You should also consider users entering no languages at all, i.e. your template should not even begin to construct a table.
make_language_row can't expand the lang template directly in the Module. You should use the frame object's expandTemplate function to handle this.
I've put in some changes to your template as a demo. I'll let you sort out the styling & article links etc..
Regards,
J
5.64.158.190 (talk) 20:59, 26 November 2023 (UTC)[reply]
Thanks! Well, I was under the impression that my module wouldn't be able to call local functions in other modules.. but again I'm quite a newcomer to Lua, and Wikipedia's particular flavor of it. A diehard editor (talk | edits) 03:07, 27 November 2023 (UTC)[reply]
Here is a working example of one way to accomplish the rewrite: Module:User:Trappist the monk/Name in various languages
—Trappist the monk (talk) 04:00, 27 November 2023 (UTC)[reply]
Nice 5.64.158.190 (talk) 05:13, 27 November 2023 (UTC)[reply]

Definition of Local Project

Hi,

I read here that Wiktionary is not considered local to the Wikipedia project as far as Interwiki prefixes are concerned, yet a call to mw.site.interwikiMap("local") includes it. Should it be there?

Thanks,

J 5.64.158.190 (talk) 21:20, 26 November 2023 (UTC)[reply]

Audio files not showing on Timeless when viewed on mobile device in portrait

I think this has something to do with one of the stylesheets here, because safe mode does not result in this issue. There is a CSS line somewhere that has "height: auto;" and that is causing the height of the audio file player to get messed up. I isolated it to https://en.wikipedia.org/w/load.php?lang=en&modules=ext.gadget.Shortdesc-helper-pagestyles-vector%2CTwinkle-pagestyles%2CresponsiveContentBaseTimeless&only=styles&skin=timeless but cannot figure out which MediaWiki page I need to go to edit this. If an interface admin can fix this that would be great. Thank you. Awesome Aasim 21:55, 26 November 2023 (UTC)[reply]

On what specific page are you experiencing the issue? Izno (talk) 21:58, 26 November 2023 (UTC)[reply]
I added a file to Fire alarm notification appliance with a recording of the standard pattern used for fire alarms in North America, and while the file shows fine when in landscape, when viewing in portrait (first on my phone but later by using the F12 developer tools to test the page), it turns out that the "height: auto" might be interfering with the proper display of the player. Awesome Aasim 22:12, 26 November 2023 (UTC)[reply]
Ok I isolated the problem even further to MediaWiki:Gadget-responsiveContentBaseTimeless.css, line 71. I think that line needs to be removed or rethought out to allow the player to work on Timeless when so narrow. Awesome Aasim 22:20, 26 November 2023 (UTC)[reply]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(technical)&oldid=1187056260"