Wikipedia:Village pump (technical)

 Policy Technical Proposals Idea lab WMF Miscellaneous 

• Table of contents
• First discussion
• End of page
• New post

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.

« Archives, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213

Keyboard navigation to page bottom

In Chrome on Windows 10, on Wikipedia, not only is Ctrl-End not taking me to the bottom of a page, but it's taking me to the top. I think this is recent, perhaps with the latest big skin update? Largoplazo (talk) 11:28, 4 February 2024 (UTC)

 Works for me try an incognito tab on a page to rule out if it is one of your personal settings or extensions. — xaosflux ^Talk 12:29, 4 February 2024 (UTC)

When the focus is on what? Plus, I don't know when you have to use Ctrl+End, and not just End, to go to the bottom of a page. Ctrl+End gets you to the end of the textbox when the focus is inside one but that still doesn't take you to the bottom of the page. Nardog (talk) 04:31, 5 February 2024 (UTC)

Neither End nor Ctrl-End works. This is both when I have just arrived at a page and haven't interacted with it and when I've clicked somewhere within the body text first. Ctrl-End is typically how I get to the bottom of the page, standard keyboard navigation. Though I just now went to random pages I pulled up from a Google search and some of them presented the same failure to react to Ctrl-End. Wait, here's what Google says: [1]. It says End alone is the way to do it. But End doesn't seem to work for me anywhere. Now I'm thinking that modern page layout has thwarted the browser's built-in shortcuts. For example, on the pages (different sites) I tried, End took the cursor to the end of the first link on the page, sometimes a "Skip navigation" link that then was made visible. OK, so it isn't a Wikipedia-specific problem. Largoplazo (talk) 12:22, 5 February 2024 (UTC)

You could try checking if you've accidentally switched on Caret Browsing. Press F7 or find Caret Browsing in the settings. —⁠andrybak (talk) 11:35, 10 February 2024 (UTC)

Issues with font color used on mobile for clicked links

Tracked in Phabricator
Task T356928

I'm not sure if this is the way that it has always been or if this changed recently, but I just noticed a bit of an accessibility issue when it comes to links using the mobile version of Wikipedia: Clickable links to other articles, after they've been clicked on once, changed to a color that is the same color as the rest of the text on the page. In other words, after clicking on the link once, since the link is indistinguishable from the rest of the text on the page, it is unclear that it is still a link. I know on most of the desktop skins, a clicked link goes from blue to purple in color, whereas a link on mobile goes from blue to black in color. Steel1943 (talk) 22:14, 8 February 2024 (UTC)

I'm seeing it too. It definitely wasn't like that before. Looks like it's WP: THURSDAY? --rchard2scout (talk) 22:31, 8 February 2024 (UTC)

I think it's been a while since a WP:THURSDAY broke something. Wonder how many weeks that was. Steel1943 (talk) 22:44, 8 February 2024 (UTC)

"0.5" is the answer. Or "two", if you want to be pedantic. – Jonesey95 (talk) 00:38, 9 February 2024 (UTC)

Ah-ha! That proves that ... I'm not on here regularly enough! 😂 Steel1943 (talk) 00:46, 9 February 2024 (UTC)

Same thing happening on my end, i noticed it immediately. Wasn’t like that this morning! Elvisisalive95 (talk) 23:49, 8 February 2024 (UTC)

I'm having the same issue on mobile. It doesn't seem to be isolated to just English Wikipedia either. RajanD100 (talk) 00:51, 9 February 2024 (UTC)

@Nardog: Thanks for knowing about and posting the phab. Steel1943 (talk) 00:55, 9 February 2024 (UTC)

Just noticed this too. Glad to see I'm not the only one! Loytra (talk) 01:38, 9 February 2024 (UTC)

It's awful. Please fix! Masterhatch (talk) 03:48, 9 February 2024 (UTC)

Links is blacked

Hello, why is Wikipedia like this? Why are the read links in the text of the article no longer purple? They are the color (Black) of the problem in the article and no different than the unlinked text in the article. By doing this, the users get extremely confused and cannot understand which part of the text of the article is a link, because when they click once on a link that is blue, the second time, that part is no longer purple, and the color of the text of the article is the same, it is black. Click on the black to find out (If you click on the black that has a link and then return to the this page, you will no longer notice that the black is linked). Ahilcaspian (talk) 22:19, 8 February 2024 (UTC)

This is an issue on your end. Amaury • 22:35, 8 February 2024 (UTC)

@Amaury: Per my section above, I don't think so. @Ahilcaspian: Looks like you are using mobile, so I will bundle this section with mine since it's the same problem. Steel1943 (talk) 22:37, 8 February 2024 (UTC)

@Amaury No, it's not about me, the same problem happened in the discussion above. Even when I log out of my Wikipedia account, the links are still the same color (black). Ahilcaspian (talk) 22:38, 8 February 2024 (UTC)

No, it's happening to me too, as of tonight. There's a reddit post about it too. Zanahary (talk) 01:38, 9 February 2024 (UTC)

I've also had this happen. CSS will always be Wikimedias mortal enemy. WiinterU (talk) 13:18, 9 February 2024 (UTC)

It only happens in the mobile vesion. For a fix, add the below to Special:MyPage/minerva.css.

.mw-body-content a:visited { color: #0B0080; } /* visited links */

PrimeHunter (talk) 03:43, 9 February 2024 (UTC)

Thank you for this, I couldn't stand having the links black ;-;

P.S. for those who use the Vector 2022 skin and think the colour looks off, replace "#0B0080" with "#795CB2" Loytra (talk) 07:16, 9 February 2024 (UTC)

Vector 2022 doesn't have the bug. I suggested to place the code in Special:MyPage/minerva.css which is only used in the mobile version. PrimeHunter (talk) 10:21, 9 February 2024 (UTC)

I'm not too well-versed in the technical intricacies of Wikipedia, but in that case the colour you suggested in the code was the wrong one. Mobile Wikipedia uses the Vector 2022 link colours. Loytra (talk) 10:54, 9 February 2024 (UTC)

I based it on Help:Link color#Standard colors which doesn't mention mobile but shows Vector 2022 as a special case. Visited links are currently black in mobile so I didn't know which color they were supposed to have. It may be #795CB2 as you say. When the right color is returned, I may update Help:Link color. PrimeHunter (talk) 15:16, 9 February 2024 (UTC)

The new CSS variable used is --color-link--visited and the old one is likely --color-visited, which is defined as #6b4ba1. Is there a chance that this was the color used before? It looks right to me. Kkuhlau (talk) 16:46, 9 February 2024 (UTC)

Thank you! My colours are back to normal. Masterhatch (talk) 14:49, 9 February 2024 (UTC)

Workaround added

I've added the manual css workaround site-wide via MediaWiki:Minerva.css; once deployed or if issues any int-admin should revert. — xaosflux ^Talk 10:34, 9 February 2024 (UTC)

The backport was deployed this morning, so I went ahead and reverted the local hotfix. This whole thread can be marked as

Resolved

I think –Novem Linguae (talk) 18:56, 9 February 2024 (UTC)

Notification bell icon changed color on mobile

Tracked in Phabricator
Task T356540

Another Mobile/Minerva skin issue that might or might not be related to the above. For logged-in users in the top right corner, there are two icons:

• "User menu" icon, which I can simply link. From SVG code, one can see that color #54595d is used
• and a notification bell icon to the left, which I can't link, because it's a data URI scheme file hardcoded in CSS. The SVG code uses fill="var(--color-subtle)". This CSS variable is supposed to be #54595d, but the icon shows up as #000 (black) both in Firefox and in Chrome.

The notification bell icon seems to be the only outlier. As an example, the settings icon is a regular SVG file with the correct color. —⁠andrybak (talk) 19:22, 9 February 2024 (UTC)

For reference, found a place in code related to the bell icon CSS. —⁠andrybak (talk) 19:30, 9 February 2024 (UTC)

Git blame suggests that this code was recently refactored in commit 59fd0cd (Convert all color related Less variables to CSS custom properties, 2024-02-01). I don't know how Less works, so I can't comment on the change itself, but the recency is conspicuous. —⁠andrybak (talk) 19:34, 9 February 2024 (UTC)

Jon (WMF), could you please take a look at the bug report in this subsection? —⁠andrybak (talk) 10:45, 11 February 2024 (UTC)

JDrewniak (WMF), could you please also take a look? —⁠andrybak (talk) 10:49, 11 February 2024 (UTC)

This is being tracked in https://phabricator.wikimedia.org/T356540. Jdlrobson (talk) 21:50, 12 February 2024 (UTC)

Is Toolforge down?

I have attempted to access two separate tools and both returned a 503. Is anyone else having issues? NW1223<Howl at me•My hunts> 03:35, 9 February 2024 (UTC)

Works for me. * Pppery * _{it has begun...} 03:41, 9 February 2024 (UTC)

And now it is working for me too. Must have been a temporary glitch. Oh well.

Resolved

NW1223<Howl at me•My hunts> 18:42, 9 February 2024 (UTC)

Page stats tool effects unclear

I installed the following editing tool in my common.js page and when I open VE or source editing I don't see any difference. It says it adds more links to the toolbox. What toolbox does it mean? Qwerty284651 (talk) 06:30, 9 February 2024 (UTC)

@Qwerty284651 Replicating the mw.util.addPortletLink(..) function call, it seems it adds them to the end of the "Tools" dropdown menu to the right of "View history" at the top right of the page. – 143.208.236.146 (talk) 07:14, 9 February 2024 (UTC)

Thanks. Qwerty284651 (talk) 03:46, 10 February 2024 (UTC)

It's also debatable if ten year old scripts still function well. Sjoerd de Bruin (talk) 09:07, 11 February 2024 (UTC)

Link behaving badly?

Pls see the infobox at Dave Sharma, specifically the link at Member of Parliament for Wentworth.

It should go to Division of Wentworth, an electorate in Sydney, Australia. Instead it links to Wentworth (UK Parliament constituency).

It seems to have worked correctly until the edit of 07:39, 30 November 2023 Special:Diff/1187603022. A change was made in that edit to the link's field but not to link itself which remained [[Division of Wentworth|Wentworth]]. Even mouseover at that stage starts showing "Wentworth (UK Parliament constituency)".

The links to Division of Wentworth in first para of lede and in navbox at foot of Sharma's article work properly. Likewise, in the iboxes of his predecessor Kerryn Phelps and his successor Allegra Spender, both link to Australia's Wentworth as they should.

Other editors have tried to fix to no avail. One tried by adding an (Australia) dab ie [[Division of Wentworth (Australia)|Wentworth]] but that didn't help - that page has apparently never existed? Sorry if it's something simple I'm missing. Any enlightenment gladly received. JennyOz (talk) 10:37, 9 February 2024 (UTC)

JennyOz, replacing | constituency_MP1 = with | constituency_MP = seems to fix it in preview. — Qwerfjkltalk 11:23, 9 February 2024 (UTC)

Fixed now.

Yeah, it's the infobox transclusion that's the problem, not the link per se. However it would be nice to know how it managed pluck "Wentworth" from the rest of the article. Martin Kealey (talk) 12:14, 9 February 2024 (UTC)

Martin Kealey, Wikidata perhaps. — Qwerfjkltalk 12:54, 9 February 2024 (UTC)

Thanks both! The "why" will remain a mystery but very relieved it now links correctly. JennyOz (talk) 01:02, 10 February 2024 (UTC)

Could we please get some feedback from Wikimedia boffins on how `|constituent_MP=Wentworth` was synthesized when neither label nor value was supplied? Martin Kealey (talk) 04:31, 11 February 2024 (UTC)

Wentworth was always supplied in the infobox. When it linked the wrong target, the infobox said | constituency_MP1 = [[Division of Wentworth|Wentworth]] | parliament = Australian. To match constituency and parliament parameters correctly, it should have said either | constituency_MP = ... | parliament = ... or | constituency_MP1 = ... | parliament1 = .... The wrong combination | constituency_MP1 = ... | parliament = ... meant that no parliament was associated with constituency_MP1. {{Infobox officeholder/office}} has UK as default. For UK it delinks constituency_MP1 to get "Wentworth" and then automatically links Wentworth (UK Parliament constituency) when that page exists. Maybe it should test whether the parameter is already linked and accept that instead of delinking and trying to add its own link, but it would require more code. PrimeHunter (talk) 16:18, 12 February 2024 (UTC)

PrimeHunter, thanks.

That explains how, at least partly.

I've started a discussion on the Template's talk page. Martin Kealey (talk) 07:59, 14 February 2024 (UTC)

Aligning {{shc}} and {{WikiProject Tennis}}

Can the templates below be aligned in the same row, for example, in WT:TENG's lead? Qwerty284651 (talk) 10:15, 10 February 2024 (UTC)

{{shc|WT:TENG|WT:TENNISG}}
{{WikiProject Tennis|category=no}}

They are aligned at the top if your window is wide enough. – Jonesey95 (talk) 14:44, 10 February 2024 (UTC)

So, it is a monitor size thing. Qwerty284651 (talk) 19:04, 11 February 2024 (UTC)

Weirdness with citation formatting

I'm doing some work on the Pitchfork (website) article and encountering some weirdness with citation formatting.

• When using the visual editor, all the mentions of "Pitchfork" in the citations (under work=) are bolded. I can't figure out why this is happening or if it matters, as it only seems to display like this when editing.
• I'm having trouble turning those mentions of "Pitchfork", in the citations, into wikilinks.

Does anyone know what's going on? Popcornfud (talk) 12:20, 10 February 2024 (UTC)

Edit: I'm being a moron. It's because I'm trying to link the Wikipedia page to itself and didn't even realise I was doing that. However, I'll leave this post here as it seems to me like the displaying in bold might be a Visual Editor bug, so it might be of interest to someone.

Links in a page to itself are displayed in bold by MediaWiki, so VisualEditor is accurately depicting the resulting appearance. isaacl (talk) 18:20, 10 February 2024 (UTC)

Interesting — why does it do that? If the purpose is to indicate a circular link, well, it didn't help me there, heh... Popcornfud (talk) 01:04, 11 February 2024 (UTC)

I don't know if this is why it is the way it is, but this is useful in navboxes: you can have the same list of links on each page but the one which would normally link to the page you're viewing is both not circular and is easy to distinguish. LittlePuppers (talk) 01:37, 11 February 2024 (UTC)

mw:Help:Self link#Utility gives navboxes as an example. I also find it very useful there. PrimeHunter (talk) 15:42, 12 February 2024 (UTC)

Error on Talk:Grand Duchy of Lithuania

There is an error on the bottom of Talk:Grand Duchy of Lithuania, a comment I made isn't rendering properly and is cutting off other comments. please help? Victor Grigas (talk) 16:55, 10 February 2024 (UTC)

I have closed a <ref> tag with </ref> which seems to have cleared things up. -- Verbarson  ^talk_edits 17:07, 10 February 2024 (UTC)

Schrodinger's redlink

The latest run of Special:WantedCategories includes a redlink for Category:Proposed deletion as of 1 February 2024, supposedly with two articles in it, yet if I actually click on the category it is empty at that level. Even a temporary undeletion failed to uncover any hidden contents, while redeleting it failed to resolve its "non-emptiness" on the WantedCategories report, so obviously there's some other kind of technical issue.

I've seen situations like this on occasion before, but I obviously don't know how to fix that myself — I've always had to bring these cases to VPT to get somebody with more expertise in the matter to look into them.

This may also be related to the other oddity I saw today. Last year, there was a spate of phantom draftspace redirects that would show up whenever I tried to do an incategory search for draft or userspace pages that were filed in Category:Living people, where the redirect didn't actually have any categories on it at all, and what had really happened was that somebody had added categories to the page while it was still in draft form and then moved it into mainspace a few moments afterward, so the system was somehow registering the resulting draftspace redirect as categorized because the categories had been added while the page was still technically in draftspace. That started out as a one-time thing about a year ago, and then didn't recur again for about a month, at which point it suddenly came back as an epidemic of dozens of pages — but after a while it got fixed by the bugfixer gurus, and then never recurred afterward.

Until today, when there was a new page exactly like that again.

For the time being I've solved the issue by applying the same workaround I started out with last year: move the page back into draftspace, wrap the categories in the {{draft categories}} wrapper, wait until the page drops from the search, and then move it back into mainspace again. But since the last time I saw this it turned into a carpet-bombing barrage of pages that needed special technical intervention to solve because it would have taken me the entire day to just apply that manual fix every time, I'm worried that that's going to happen again — so I wanted to bring it to VPT's attention now, in the hopes of solving it before it metastasizes again. Bearcat (talk) 18:09, 10 February 2024 (UTC)

 Fixed the first issue. I don't think the second is related to it. * Pppery * _{it has begun...} 19:02, 10 February 2024 (UTC)

And then Schrodinger took a trip to the Caribbean...

Separate issue, so separate header, but there were also two redlinks for Category:19th-century Dominica women and Category:19th-century Dominica writers, both of which were being autogenerated by the use of the bog-standard {{Women writers by nationality and century category header}} on Category:19th-century Dominican Republic women writers.

Now, as we well know, Dominica and the Dominican Republic are two different countries that each have their own separate literatures and their own separate citizenries and their own separate pools of women writers — but there's absolutely nothing out of the ordinary in that template to manually mix them up, meaning that the error is being imported from a module.

I've resolved the problem for the time being by reverting the recent addition of the category header template back to the category's prior form, but obviously this might happen again elsewhere if it isn't fixed.

So since I don't know what module it is that's doing this, could somebody figure that out and ensure that it's keeping Dominica and the Dominican Republic separate from each other since they are two different countries? Thanks. Bearcat (talk) 18:27, 10 February 2024 (UTC)

 Fixed in Module:Find demonym * Pppery * _{it has begun...} 18:56, 10 February 2024 (UTC)

Edit conflict

I've just lost a bunch of content which I've added to the Dangers of creationism in education article. I've clicked on the "Solve conflict" or something like that button and I've just saw a source code of the current version of the article and all my edits were lost. UA0Volodymyr (talk) 19:18, 10 February 2024 (UTC)

I've always gotten confused in that screen, it was only after seeing it multiple times that I realized that your original change is displayed underneath the source code of the current version in the edit conflict screen^{(link with a screenshot)}. That said, if you closed that tab it's unfortunately gone yes. – 143.208.236.146 (talk) 20:03, 10 February 2024 (UTC)

I didn't even see my edited version. I'll leave Wikipedia if it's not fixed. I've very angry and tired. UA0Volodymyr (talk) 04:10, 11 February 2024 (UTC)

@UA0Volodymyr: See Help:Edit conflict. Edit conflicts are not common, but when they do occur, you are presented with two big edit windows. The first one, as you note, shows the current page version. The second is a copy of the edit window that you were using prior to clicking Publish changes. Unless you have a very tall monitor, or a tiny font, this second edit window is always "below the fold", and you need to page down in order to see it. Between the two edit windows there are the usual publish/preview buttons plus a diff.

What I normally do is to locate my text in the second edit window and copy it to the clipboard; then back right out and try the "edit" link again, paste my text to the appropriate place, and save. --Redrose64 🌹 (talk) 16:37, 11 February 2024 (UTC)

Depending on your browser, reopening the tab (History→Recently Closed Tabs or similar) may or may not bring back the discarded text. Certes (talk) 20:19, 10 February 2024 (UTC)

Tried. Doesn't work. I use Firefox. UA0Volodymyr (talk) 04:08, 11 February 2024 (UTC)

The Firefox extension Form History Control by Stephan Mahieu got me out of some similar diabolical situations. -- Michael Bednarek (talk) 13:59, 11 February 2024 (UTC)

Creating a theme

I run Linux with a custom tiling window manager setup with the Catppuccin Mocha theme. The colors list is available at https://catppuccin.ryanccn.dev/palette; Mocha is the last one, so you'll have to scroll to the very bottom.

I've been theming the websites I use the most, and for most of them I have to install an extension. Wikipedia is nice and has theming functionality built in, but I'm struggling with the CSS classes it uses.

Ideally, my theme should work with both Vector 2010 and 2022.

Any guidance? Thanks in advance! —charmquark ^she/_they talk contribs 20:09, 10 February 2024 (UTC)

You may be able to use MediaWiki:Gadget-dark-mode.css as a template, that is most of what we style for the "dark mode" community gadget. — xaosflux ^Talk 16:27, 12 February 2024 (UTC)

Thanks! :) —charmquark ^she/_they talk contribs 19:56, 12 February 2024 (UTC)

There are specific pages for this, namely mw:Manual:How to make a MediaWiki skin and mw:Manual:Installing MediaWiki. Follow-up questions should go to mw:Project:Support desk. Snævar (talk) 20:23, 12 February 2024 (UTC)

Hey @Charmquark we are currently transitioning to CSS variables for Vector 2022 and Minerva (and aim to be done with that by the end of March). You may find it worthwhile for waiting for that to happen - as implementing a theme will then simply be a case of re-defining the CSS variables.

If you use developer tools and inspect the HTML/CSS of Minerva you will already see some of these colors. The same variables will soon be used in Vector 2022. Jdlrobson (talk) 21:46, 12 February 2024 (UTC)

Keyboard shortcut for my sandbox subpage

I would like to create a keyboard shortcut for my sandbox subpage with Alt + Shift + A. The letter A is one of a few letters of the keyboard shortcuts available for using the Alt+Shift + letter combination listed in WP:K). Any help would be much appreciated. Qwerty284651 (talk) 00:51, 11 February 2024 (UTC)

Add to your common.js:

$(function () {
	$('#pt-sandbox > a').attr('accesskey', 'a');
});

Nardog (talk) 04:15, 11 February 2024 (UTC)

Thanks. Qwerty284651 (talk) 20:56, 12 February 2024 (UTC)

Α3IA

The correct title of this article is α3IA, and it is forced to upper case for technical reasons. Can someone tell me whether the first character is a capital Alpha or a capital A? Robert McClenon (talk) 07:17, 11 February 2024 (UTC)

@Robert McClenon I pasted the title (copied from the url) into https://www.babelstone.co.uk/Unicode/whatisit.html, it said the first character is "U+0391 : GREEK CAPITAL LETTER ALPHA", while the last character is "Latin capital letter A". – 143.208.236.146 (talk) 10:36, 11 February 2024 (UTC)

The title can also be pasted to the magic word {{lc:Α3IA}} (lc means lowercase) which produces α3ia. Somebody has added {{lowercase title}} which also works for Greek letters so the article displays α3IA now. PrimeHunter (talk) 15:35, 12 February 2024 (UTC)

A reverse twl2c

Need a param for {{twl2c}} that reverses the display for W/L followed by % without having to create a sister template with a swapped code? Qwerty284651 (talk) 20:55, 12 February 2024 (UTC)

@Qwerfjkl:, sorry for the edit conflict. Got the message and piped the tenplate instead. Qwerty284651 (talk) 21:02, 12 February 2024 (UTC)

Tech News: 2024-07

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

Recent changes

• The WDQS Graph Split experiment is working and loaded onto 3 test servers. The team in charge is testing the split's impact and requires feedback from WDQS users through the UI or programmatically in different channels. [2][3][4] Users' feedback will validate the impact of various use cases and workflows around the Wikidata Query service. [5][6]

Problems

• There was a bug that affected the appearance of visited links when using mobile device to access wiki sites. It made the links appear black; this issue is fixed.

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 13 February. It will be on non-Wikipedia wikis and some Wikipedias from 14 February. It will be on all wikis from 15 February (calendar). [7][8]
• As work continues on the grid engine deprecation,[9] tools on the grid engine will be stopped starting on February 14th, 2024. If you have tools actively migrating you can ask for an extension so they are not stopped. [10]

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

MediaWiki message delivery 05:46, 13 February 2024 (UTC)

Module edit needed, again

Category:Equestrian at the Summer Olympics was recently renamed to Category:Equestrian events at the Summer Olympics, but five subcategories for individual Olympic Games were left behind in the old category because they were artificially transcluding it via a template instead of directly declaring it in text form. The implicated template is {{Sportname at the YYYY Summer Olympics category}}, but once again that template isn't actually generating the category itself, and instead it's just a pass-through from another module or template I can't identify.

For the moment, I've recreated the old category name as a redirect to the new one so that it isn't sitting red — but could somebody who knows a lot more about where the category generation is coming from update that to "equestrian events"? Thanks. Bearcat (talk) 21:19, 13 February 2024 (UTC)

I've listed the categories for speedy renaming, which will fix this when it's processed. * Pppery * _{it has begun...} 21:29, 13 February 2024 (UTC)

Bearcat, the problematic wikicode is

{{#ifexist:Category:Olympic {{lcfirst:{{{fooing}}}}} tournaments|[[Category:Olympic {{lcfirst:{{{fooing}}}}} tournaments|{{{year}}}]]|[[Category:{{ucfirst:{{{fooing}}}}} at the Summer Olympics|{{{year}}}]]}}

in Template:Sportname at the YYYY Summer Olympics category/core.
This resolves to [[Category:Equestrian at the Summer Olympics|1900]]
The solution is probably to wrap a further ifexist in there.

How I found it:
It's obviously caused by {{Sportname at the YYYY Summer Olympics category}} on the page, which itself just calls the /core template Using Special:ExpandTemplates with "Category:Equestrian at the 1900 Summer Olympics" as the title and {{Sportname at the YYYY Summer Olympics category}} as the wikitext, and "Remove comments" off, a Ctrl+F for the category gives

[[Category:Equestrian at the Summer Olympics|1900]]
[[Category:1900 Summer Olympics events|Equestrian]] <!--

 # Next bit is a kludge to cope with any sport in which any of the title words is capitalised in running text

which matches up in the source template with the wikicode above. — Qwerfjkltalk 21:33, 13 February 2024 (UTC)

Correcting or changing a repeated word

How can I change a specific word, for example a name that appears many times in the same article? Is there a Gadget to help? Or do I have to do it manually? Anyway please kindly let me know as soon as possible so I can move forward with my project. Arbabi second (talk) 08:25, 14 February 2024 (UTC)

Probably the easiest way is to use VisualEditor's search and replace feature. Nardog (talk) 08:28, 14 February 2024 (UTC)

The desktop source editor also has search and replace. Click "Advanced" in the toolbar and then the magnifying glass icon at the far right. PrimeHunter (talk) 14:26, 14 February 2024 (UTC)

But that doesn't allow you to replace only the occurrences visible in the output. Nardog (talk) 07:11, 15 February 2024 (UTC)

REST API returning HTML that doesn't exist in standard page

I'm unable to upload screenshots of the HTML, so I'll do my best to explain. In the table for https://en.wikipedia.org/api/rest_v1/page/html/List_of_Chainsaw_Man_chapters, the second row is an empty table row element; . But on the normal page, https://en.wikipedia.org/wiki/List_of_Chainsaw_Man_chapters, this empty table row element does not exist. I looked at the source code for the table template, but I don't have much experience there, so I didn't see anything obvious that would explain it. Why does the REST API have this empty table row element? Tyephlosion (talk) 13:42, 14 February 2024 (UTC)

The output of the REST API is generated by a new wikitext parser called Parsoid, which will eventually also be used for normal page views. You can see the Parsoid output in the context of a normal page view like this: https://en.wikipedia.org/w/index.php?title=List_of_Chainsaw_Man_chapters&useparsoid=1 (there's also a preference to enable it: Special:Preferences#mw-prefsection-editing-developertools).

So the question now is, why is Parsoid output different from the old wikitext parser? I'm not sure, but we can make some guesses. You can paste the {{Graphic novel …}} templates into Special:ExpandTemplates to reveal the wikitext that is fed to both of the parsers, and there's a fragment that looks like this:

…
!width=24%|English release date
|-


<tr style="text-align: center;"><th scope="row" id="vol1" style="text-align: center; font-weight: normal; background-color: transparent;">1</th>…

I would guess that the |- markup preceding the <tr> generates the extra empty table row. I have no idea why that doesn't happen in the old parser. The |- doesn't seem necessary anyhow, and if you track down which template it comes from, you could probably remove it. Matma Rex talk 17:01, 14 February 2024 (UTC)

Tech tip: how to figure out which script did something

I have way too many scripts in my common.js and I often forget what they all do. TIL a trick to help with that. In Chrome (and I suspect most modern browsers), you can search all of your loaded scripts in a single operation. In my case, I was wondering what had added a blue or green background to various bits of text. In the element browser, I saw that the text in question had style="background-color: lightskyblue" So I searched all my loaded js for "lightskyblue" and out popped the script that added that style. RoySmith (talk) 16:41, 14 February 2024 (UTC)

Random timelines no longer appearing on pages after any edit

Tracked in Phabricator
Task T357268
Resolved

I think there's an issue with EasyTimeline but for the life of me I can't figure it out.

If you try to change anything whatsoever on a timeline (a person's date, color of an instrument, anything at all), such as here or here, it will display as if there's no image. There's no error message or anything.

However, on timelines such as here or here, it's perfectly fine and displays as normal when something is changed. But the latter two were created in the same way as the former two.

I have absolutely no idea why this is affecting some timelines but not others. I cannot find any major differences between the first two and second two examples, and I've even tried copying the attributes (timeline size, colors, etc.) of a working timeline into a broken one, and it still doesn't work. It's random and I don't know the cause of it. Xanarki (talk) 17:49, 14 February 2024 (UTC)

Default url-status fails

Hi, here's a reference that by default shows the archived URL, when it should show the live URL (if I'm correct that it defaults to "live"):

<ref name=Wilner>{{cite news |last1=Weaver |first1=Jay |last2=Wilner |first2=Michael |title=Trump-appointed judge at center of ex-president's FBI fight. Who is Aileen Cannon? |url=https://www.miamiherald.com/news/local/article265558746.html |access-date=December 11, 2022 |work=[[Miami Herald]] |date=September 12, 2022 |archive-url=https://archive.today/20220912222835/https://www.miamiherald.com/news/local/article265558746.html |archive-date=September 12, 2022}}</ref>

I've solved this by inserting and forcing "url-status=live", though I also note that I've seen editors (and a bot?) removing this parameter as redundant if live.

Am I missing something. Thanks, Esowteric + Talk + Breadcrumbs 20:15, 14 February 2024 (UTC)

References

Or maybe I'm just having a "senior moment"? Esowteric + Talk + Breadcrumbs 20:37, 14 February 2024 (UTC)

(edit conflict)

Nope. Default is dead. Module:Citation/CS1 (and the wikitext {{citation/core}} that preceded it) assume that the value in |url= is dead when |archive-url= has a value. To link |title= with |url= when the template has |archive-url= you must set |url-status=live.

When a template has |url= and |archive-url=, |url-status=dead is superfluous; when a template has |url= but does not have |archive-url=, |url-status=<any value> is also superfluous. In both cases, |url-status= should be removed because unnecessary clutter.

—Trappist the monk (talk) 20:39, 14 February 2024 (UTC)

Ah, thanks a lot. Esowteric + Talk + Breadcrumbs 21:20, 14 February 2024 (UTC)

Basic reproduction number page errors

Can't work out what's gone wrong here: My display, using Safari or Chrome, is unreadable, peppered with errors like Failed to parse (SVG (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "http://localhost:6011/en.wikipedia.org/v1/":): {\displaystyle R_0}. Shhhnotsoloud (talk) 22:01, 14 February 2024 (UTC)

That article works for me. Possibly a temporary server glitch. If it's still happening for you, try a null edit or a purge of the page. – Jonesey95 (talk) 22:23, 14 February 2024 (UTC)

I saw such an error message a single time after "The underlying matching differential equation is". It was this formula: $${\frac {dn_{E}(t)}{dt}}=n_{E}(t){\frac {\ln(R_{0})}{\tau }}.$$ It worked after a purge and it works here. PrimeHunter (talk) 23:26, 14 February 2024 (UTC)