Cannabis Ruderalis

 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.

Talk page font size[edit]

On mobile edition, the first post in a talk page section (or anywhere else that uses the same tool for topics, including this page) has a larger font size than normal. This does not apply to the title, subsequent posts in the section, or desktop edition. Is this supposed to happen? QuicoleJR (talk) 19:43, 15 February 2024 (UTC)Reply[reply]

It also applies to Meta-Wiki, so it seems to be a MediaWiki thing. QuicoleJR (talk) 19:47, 15 February 2024 (UTC)Reply[reply]
Actually, upon looking at mainspace, it seems like talk page replies and section titles are some of the only things not affected. Can someone with a bit more technical knowledge please explain why the font size went up? Thanks, QuicoleJR (talk) 19:49, 15 February 2024 (UTC)Reply[reply]
This is probably related to phab:T349303, by Jon (WMF). You should be able to change the font size at Special:MobileOptions. It seems like indentation size has increased drastically on mobile too. Sdrqaz (talk) 20:03, 15 February 2024 (UTC)Reply[reply]
Weird, seems like setting it to small and then back to the default it was on fixed the problem. QuicoleJR (talk) 21:18, 15 February 2024 (UTC)Reply[reply]
Actually, that only fixed it for this specific page, and not any of the others. QuicoleJR (talk) 21:21, 15 February 2024 (UTC)Reply[reply]
The indentation issue is now tracked in a separate ticket . Jdlrobson (talk) 01:58, 16 February 2024 (UTC)Reply[reply]
Really hope this isn’t the intended design 70.23.34.176 (talk) 20:05, 15 February 2024 (UTC)Reply[reply]
I'm noticing the font size is drastically differing between articles in the mainspace on mobile. It is quite disorienting. Y2Kcrazyjoker4 (talk • contributions) 21:37, 15 February 2024 (UTC)Reply[reply]
Came here to ask about it too. Not happy with the change at all. Would appreciate any help in how to revert it back if possible. Thriley (talk) 21:40, 15 February 2024 (UTC)Reply[reply]
Quite literally made an account about this. Looks awful and is just way too big of a font. Not everyone that uses wikipedia is my 97 year old grandmother. Also would like a way to revert this. Someguyfromminnesota (talk) 23:36, 15 February 2024 (UTC)Reply[reply]
Click the hamburger button at the top, "Settings", and then "Small". Nardog (talk) 23:41, 15 February 2024 (UTC)Reply[reply]
There are two issues here. For logged in users as Nardog suggests change your font size to small. It is mislabelled but this is meant to be default.
For anonymous users we have an issue with cache. It should fix itself over the next 24 hours. Jdlrobson (talk) 00:14, 16 February 2024 (UTC)Reply[reply]
Hi Jon, is the line spacing supposed to remain close together or as it was before? Victor Grigas (talk) 02:05, 16 February 2024 (UTC)Reply[reply]
According to phab:T356339#9510249, this is an intentional change. — The Earwig (talk) 02:24, 16 February 2024 (UTC)Reply[reply]
It shouldn't be. QuicoleJR (talk) 14:40, 16 February 2024 (UTC)Reply[reply]
I’d echo the complaints about the font size/line spacing change, as it’s actually creating an accessibility issue for me- I have vision issues that make it difficult to follow lines of closely-vertically spaced text, and it is genuinely difficult to read the mobile wiki right now. Setting it to “regular” helps but it makes everything look stupidly large (because it is). I’d also advocate for a revert. Padgriffin Griffin's Nest 01:13, 16 February 2024 (UTC)Reply[reply]
It looks awful. Left alignment instead of justified? Are they insane? --2800:AC:4010:C67:1:0:28ED:3368 (talk) 13:44, 16 February 2024 (UTC)Reply[reply]
Justified text is generally a bad idea on the web. The technology isn't advanced enough to match print typesetting [1] and W3C advise against it for accessibility reasons [2]. the wub "?!" 14:30, 20 February 2024 (UTC)Reply[reply]
At one time we had a user preference "Justify paragraphs", which IIRC was in Preferences → Appearance somewhere near to "Show hidden categories". It was removed a little over ten years ago as part of a general clearout of little-used preferences (every preference, whether enabled or not, adds a little to the overhead of every page). For those who complained about the loss, a gadget was provided instead, to achieve the same effect. It's still there, at Preferences → Gadgets, under the "Appearance" heading. --Redrose64 🌹 (talk) 23:53, 20 February 2024 (UTC)Reply[reply]

Mobile font line spacing[edit]

This update in my opinion is hard to read, it’s harder to tap hyperlinks, I looked at the New York Times app and for every 10 lines on New York Times now Wikipedia has 11. Victor Grigas (talk) 02:58, 16 February 2024 (UTC)Reply[reply]

A comment was posted about this at Wikipedia talk:WikiProject Accessibility; I've copied it below. Graham87 (talk) 07:37, 16 February 2024 (UTC)Reply[reply]

I can't use Vector Wikipedia due to migraines, and redirect to Mobile Wikipedia.

I also switch fonts and increase font sizes due to eye strain. Now Mobile Wikipedia limits many lines to 24 px to 27 px. Which can be awfully cramped. I think Mobile Wikipedia should either revert the change or use a multiple of the users' specified font size. 173.66.17.86 (talk) 02:27, 16 February 2024 (UTC)Reply[reply]

New text size / format issue[edit]

Is there a way I can revert back to the old mobile version? I really don’t like the new format. Hurts my eyes. Thriley (talk) 06:46, 16 February 2024 (UTC)Reply[reply]

I agree. Spent the last hour trying to track this. It’s also on WikiMedia too. The rendering of inline styles is affected too with content bleeding over each other. I can’t believe this was by design, feels more like a gaff/malicious event hopefully to be changed soon. 109.151.12.170 (talk) 07:17, 16 February 2024 (UTC)Reply[reply]

Mobile line spacing[edit]

This new mobile spacing, which I see was an intentional change, is just unreadable for me. Everything is hard to read and cluttered. Is there any way to revert it on my end? And I think it should be reverted altogether; this is awful. Zanahary (talk) 11:13, 16 February 2024 (UTC)Reply[reply]

Ok, I found this custom CSS that works:
.mw-body p,
	.content p { line-height: 26.4px !important;}
` — Preceding unsigned comment added by Zanahary (talk • contribs) 11:21, 16 February 2024 (UTC)Reply[reply]
If you already increase font sizes, that may still be too cramped. 173.66.17.86 (talk) 17:17, 16 February 2024 (UTC)Reply[reply]

Font change on mobile view[edit]

Hello there, Wiki changed the font on Thursday night but is there any way you are able to revert it back to the original font before the changes on Thursday. The new font changes on mobile looks very ugly and I personally would much prefer the original font design. VileName8089289 (talk) 18:16, 18 February 2024 (UTC)Reply[reply]

VileName8089289, you can personally change it back, as described above. — Qwerfjkltalk 20:54, 18 February 2024 (UTC)Reply[reply]
Could you help direct me to this please. VileName8089289 (talk) 21:18, 18 February 2024 (UTC)Reply[reply]
  • Hello there, Wiki changed the font on Thursday night but is there any way you are able to revert it back to the original font before the changes on Thursday. The new font changes on mobile looks very ugly and I personally would much prefer the original font design before Thursday night. Could anyone help send me the instructions to revert it back to the original font design on mobile please. VileName8089289 (talk) 13:09, 19 February 2024 (UTC)Reply[reply]
    • VileName8089289, Click the hamburger button at the top, "Settings", and then "Small".— Qwerfjkltalk 16:59, 19 February 2024 (UTC)Reply[reply]
      I meant the fonts used before Thursday night not the current ones in use now. Even when I click on settings it comes out with the current font designs I.e. Small, Standard and Large as opposed to the prior four options of Very Small, Small, Medium and Large. Is there any way of going back to the original font designs on Wikipedia before they changed everything. VileName8089289 (talk) 17:48, 19 February 2024 (UTC)Reply[reply]
      No. — Qwerfjkltalk 17:49, 19 February 2024 (UTC)Reply[reply]

The new font size on mobile is awful and half-baked[edit]

The larger font ("standard") for paragraph texts looks awful. The ability to switch font size is appreciated, but it's hidden behind a hamburger menu and then a settings page on mobile site, which few, if any, persons will notice. It took myself days to realise that it is a personalisation option, and not shoved down the throats. And personally, I believe that the "standard" font size is way too large than it needs to be, considering that most mobile sites like news articles, etc. uses a font size comparable to the "small" size on Wikipedia, to which my (and other people's) eyes have been accustomed over the years. Furthermore, the <li> items, infobox items, image captions, etc. do not respect the personalisation choice, which is bad, they are always "small". If someone does choose "large" or "standard" font, they should have the entire article in that font, not just the paragraph text. Thanks! CX Zoom[he/him] (let's talk • {C•X}) 17:22, 20 February 2024 (UTC)Reply[reply]

There is currently a typo in the interface. The small is meant to be standard (default) and standard is meant to be "medium" but some logged in users are getting the incorrectly labelled "Standard" as default. This will be corrected soon. Jdlrobson (talk) 02:18, 21 February 2024 (UTC)Reply[reply]

Change font text design[edit]

Is there any way Wikipedia are able to revert back to the original font text design on mobile before they changed it on the 15th February? I'm having difficulty reading and using the new font and Wikipedia were fortunately able to revert back the font used for tables on pages relating to constituency seats for general election pages. Torres2000X (talk) 12:40, 26 February 2024 (UTC)Reply[reply]


What if there is an error in a headline?[edit]

The cite news template won't let me do sic.— Vchimpanzee • talk • contributions • 19:07, 19 February 2024 (UTC)Reply[reply]

@Vchimpanzee Generally leave it as is or use {{not a typo}}, but this is more of a question for Help talk:Citation Style 1. --Ahecht (TALK
PAGE
) 19:52, 19 February 2024 (UTC)Reply[reply]
I asked there.— Vchimpanzee • talk • contributions • 20:59, 19 February 2024 (UTC)Reply[reply]
You can put [sic] in plain text, or if it is just an obvious typo, you can correct it (However, insignificant spelling and typographic errors should simply be silently corrected). – Jonesey95 (talk) 21:09, 19 February 2024 (UTC)Reply[reply]
I did that. I was advised to use the template for a similar situation but I have no idea where I asked.— Vchimpanzee • talk • contributions • 23:23, 19 February 2024 (UTC)Reply[reply]
Use sic template like this: {{sic|nolink=y|reason=error in source|errror txet}}. But check the original publication, as sometimes the indexing web site makes an error, but the original was correct. And Wikipedia editors have also made errors too. Graeme Bartlett (talk) 11:06, 20 February 2024 (UTC)Reply[reply]
{{sic}} can't be used within citation templates as the italic text it outputs breaks the COinS metadata. --Ahecht (TALK
PAGE
) 15:14, 20 February 2024 (UTC)Reply[reply]
@Vchimpanzee, you can use {{as written|error t|xet [sic]}} which is using the {{Not a typo}} template however is more indicative of a misspelling. Not a good idea to correct titles as this can make searches for titles problematic. The template supports obfuscation as well which means that these items don't have to appear in search lists (once flagged). Neils51 (talk) 07:44, 25 February 2024 (UTC)Reply[reply]

Strange bug causing crashing /refreshing[edit]

Hello all, I have been experiencing a strange bug as of recently, where sometimes, seemingly completely random as of now, the Wikipedia site only allows me to delete or add 1 single character at a time when editing, and if I try to add or delete more, the site seemingly crashes and reloads automatically, undoing my edits and thus erasing any progress I made. Same thing also can happen when editing my own user page. Very, very frustrating. Any tips would be greatly appreciated. I am using a mobile Android phone. I was told to post here after posting this same request on the help desk. LoneWolf803 (talk) 20:14, 22 February 2024 (UTC)Reply[reply]

Judging from the tags, I assume you're talking about the mobile web site (en.m.wikipedia.org), not the app, correct? What version of what browser are you using? What keyboard app (e.g. Gboard) are you using to add and delete characters?
Does it typically happen after the editing page has been open for a while, or as soon as you start editing? Nardog (talk) 22:46, 22 February 2024 (UTC)Reply[reply]
Thanks for your reply, correct, I am using the website not the app. I’m using the latest version (121.0.6167.178) (as far as I know, I’m 99% sure but I’ll double check and update this reply if otherwise) of Google Chrome. I tried using Firefox as well and had the exact same issue. And yes I am using the latest version of Gboard (again I’ll double check but I’m almost positive I updated to the latest). Never had an issue with Gboard before either. I also tried clearing cache to no avail. It happens seemingly randomly like I said. Sometimes it’s when I just start editing a page (for the first time even), sometimes when I’ve had it open for a while. Seems to be no pattern to speak of from what I’ve seen. Should I try deleting and re downloading my browser apps? Thanks again. LoneWolf803 (talk) 00:54, 23 February 2024 (UTC)Reply[reply]
Hello, are you still available? LoneWolf803 (talk) 20:45, 24 February 2024 (UTC)Reply[reply]
If it's only happening on Wikipedia, I doubt reinstalling the apps would help you. With no one else corroborating it's difficult to pin down what's happening, but you can report it on Phabricator.
What do you mean, by the way, to try to add or delete more [than one character at a time]? AFAIK you can't add or delete more than one character at a time with mobile keyboards, unless you're pasting something from the clipboard or you've selected a string. Exactly what action causes the page to reload? Nardog (talk) 23:25, 24 February 2024 (UTC)Reply[reply]
Sorry, I didn’t get the notification for this reply until today for some reason. And what I mean by being only able to add or delete one character at a time (I should’ve been more clear about this) is that I can only add or delete one character at a time and then have to publish the edit or else it will crash and automatically reload the page. It just happened again. LoneWolf803 (talk) 06:50, 28 February 2024 (UTC)Reply[reply]
@LoneWolf803 bug or not, please don't power through such a problem, it makes (as you've pointed out) dozens of edits - a quick ctrl+f search of your last 500 contributions shows that 292 were +1 or -1 length changes, if all of those were for this reason then that's way too many edits.
It also, along with the other 254 edits you have done to your own user page (the other 206 user page edits were +1 or -1, so presumably this bug), breaks the intended way that the automatic extended confirmed access right is supposed to work. – 2804:F14:80E5:6B01:F969:B861:B7FB:B942 (talk) 08:40, 28 February 2024 (UTC)Reply[reply]
I am sorry. Yes of course all my +1 and -1 edits are due to this infuriating bug. I can’t help it. I am doing my best to get this bug resolved and was trying to demonstrate here what it is to try and attain a fix for it faster. Going forward, I will not make anymore edits if the bug occurs (like right now of course it is not) and will just have to wait it out I suppose. As I said, when I have time I will post on the other help page that was suggested. Thanks. LoneWolf803 (talk) 08:42, 28 February 2024 (UTC)Reply[reply]

Span style problem in signature[edit]

I may be asking in the wrong place, but take a look at this. I went to the edit screen and saw <span style="color:silver">[[User:Wikiwow1102|Wikiwow is just W0W!! ]] ([[User talk:Wikiwow1102|talk]]) 19:21, 29 November 2022 (UTC)</span>. Now this has been archived, so there's no point in asking the person to change their signature, unless it's still happening. — Vchimpanzee • talk • contributions • 22:28, 22 February 2024 (UTC)Reply[reply]

Diff. They probably didn't sign with four ~~~~ but either wrote the whole signature manually or signed with three ~~~. This omits a time stamp which can be faked by being part of the stored signature, using subst on code which produces the current time. It's confusing and I would ask an active user to change it but they haven't edited since January 2023. PrimeHunter (talk) 22:47, 22 February 2024 (UTC)Reply[reply]
I have to wonder why the span style didn't do anything to the actual signature, though.— Vchimpanzee • talk • contributions • 23:16, 22 February 2024 (UTC)Reply[reply]
Links are colored to clearly identify them as links. It can only be overwritten by setting a color inside a piped link. [[User:Wikiwow1102|<span style="color:silver">Wikiwow is just W0W!!</span>]] ([[User talk:Wikiwow1102|<span style="color:silver">talk</span>]]) produces: Wikiwow is just W0W!! (talk). Silver text on white background has awful contrast but that's another matter. PrimeHunter (talk) 23:25, 22 February 2024 (UTC)Reply[reply]
In my years of fixing Linter errors, I have seen a few signatures in which people have applied formatting to the time stamp as well as their signature. I suspect that it involves some trickery and that it confuses bots. If the signature also has Linter syntax errors, I will sometimes move the formatting so that it leaves the time stamp alone. – Jonesey95 (talk) 01:52, 23 February 2024 (UTC)Reply[reply]
No trickery, it can be done manually: <span style="color:silver">~~~~</span>Redrose64 🌹 (talk) 18:06, 23 February 2024 (UTC)Reply[reply]
@PrimeHunter: You can get just the timestamp part of the signature by typing ~~~~~, 5 instead of 4. – 2804:F14:80C5:3C01:95F6:953B:7E66:6B4C (talk) 23:45, 23 February 2024 (UTC)Reply[reply]

Weird issue where Vector 2022 is being forced on a single page.[edit]

So I use desktop Vector 2010 on mobile, and have a global preference set to enforce it. But when I go to Wikipedia:Sockpuppet investigations/PaullyMatthews (I was checking back on a report I made) I get Vector 2022 forced.

I can't find any reason why this page is forcing Vector 2022 (it's archive is doing the same). No other pages are effected, not even other SPI pages. -- LCU ActivelyDisinterested «@» °∆t° 22:40, 22 February 2024 (UTC)Reply[reply]

I also saw that, and also on some other SPI pages. I'll bet it was a WP:THURSDAY feature. I've refreshed and purged a few times and it seems to have now gone (for me anyway). -- zzuuzz (talk) 22:50, 22 February 2024 (UTC)Reply[reply]
Probably not, this has been happening to pages translcuding special pages (PrefixIndex in this case). See /Archive 210#One page looks like Wikipedia does now. Nardog (talk) 22:54, 22 February 2024 (UTC)Reply[reply]
Force-refreshing the SPI page has fixed it for me. This wasn't the first time; I recall some other time that an editor at VPT found Vector22 being forced and the link to it caused me to see it as well. SWinxy (talk) 04:53, 23 February 2024 (UTC)Reply[reply]
Happening on Module:RoundN too. SWinxy (talk) 02:50, 25 February 2024 (UTC)Reply[reply]
I get Vector 2022 instead of my preferred Monobook on Wikipedia:Featured article candidates/Dorothy Olsen/archive1, three times out of four reloads. —Kusma (talk) 23:00, 22 February 2024 (UTC)Reply[reply]
If I purge the archives and refresh I get the proper skin, but if I refresh again it's back to 2022. -- LCU ActivelyDisinterested «@» °∆t° 23:10, 22 February 2024 (UTC)Reply[reply]
I'll just add that I've seen the same thing RoySmith (talk) 23:44, 22 February 2024 (UTC)Reply[reply]
@STei (WMF) I'm guessing this may be related to the Edit Recovery feature you rolled out earlier today. RoySmith (talk) 00:36, 23 February 2024 (UTC)Reply[reply]
I also have it on Wikipedia:Sockpuppet investigations/PaullyMatthews (my default skin in Vector2010). But a hard refresh fixed it, and presumably hardest refresh would do the trick too. 🌺 Cremastra (talk) 00:57, 23 February 2024 (UTC)Reply[reply]
I've purged and refreshed the page, still the same problem. I'm using the desktop site on mobile, so the hardest refresh isn't an option (and why Vector 2022 is so very thoroughly broken for my purposes). -- LCU ActivelyDisinterested «@» °∆t° 02:25, 23 February 2024 (UTC)Reply[reply]
Wow, this is bizarre. I'm now getting V22 on Wikipedia:Sockpuppet investigations/PaullyMatthews and Wikipedia:Featured article candidates/Dorothy Olsen/archive1! Looks like it's somehow sticky to those pages. RoySmith (talk) 02:34, 23 February 2024 (UTC)Reply[reply]
I'm working my way through all the FAC pages listed at WP:FAC. So far, it's pretty repeatable that each /archive1 page I open up, it opens in V22. Doesn't seem to matter if it's a FAC I've ever looked at or not. Some unreproducible number of page reloads eventually gets me to the non-V22 version. RoySmith (talk) 02:57, 23 February 2024 (UTC)Reply[reply]
I noticed this at Wikipedia:Articles for deletion/¡Tchkung! (2nd nomination). Extraordinary Writ (talk) 06:52, 23 February 2024 (UTC)Reply[reply]
I likewise have the issue on this page: https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletion/Log/2024_February_24 Cortador (talk) 19:08, 24 February 2024 (UTC)Reply[reply]
Can confirm I'm having this problem on certain random pages, all under the Wikipedia namespace (mostly AFDs and SPIs), and it usually goes away when I refresh. I also have Vector 2010 as default. LilianaUwU (talk / contributions) 02:44, 25 February 2024 (UTC)Reply[reply]

Wrong skin on just one page[edit]

I use the "Vector legacy (2010)" skin and all pages display as they should. Except one: Wikipedia:WikiProject Canoeing and Kayaking. This page displays using the new Vector skin. Why? — GhostInTheMachine talk to me 09:49, 23 February 2024 (UTC)Reply[reply]

Yep, I see it — GhostInTheMachine talk to me 09:52, 23 February 2024 (UTC)Reply[reply]
It's a bunch of pages, upstream regression. — xaosflux Talk 15:35, 23 February 2024 (UTC)Reply[reply]
Yeah, but this one doesn't fit the pattern of transcluding Special:Prefixindex (which typically happens on sub-pages to create the back-link header). @GhostInTheMachine is this reproducible for you? RoySmith (talk) 15:50, 23 February 2024 (UTC)Reply[reply]
@RoySmith that page does indeed transclude prefixindex, it is in the navbox. — xaosflux Talk 15:56, 23 February 2024 (UTC)Reply[reply]
Ah, interesting. So now I'm wondering why I can't reproduce the problem on that page :-) RoySmith (talk) 16:11, 23 February 2024 (UTC)Reply[reply]
Oh, now I just got it in V2022. Weird. RoySmith (talk) 16:16, 23 February 2024 (UTC)Reply[reply]
The page is still being evil ... — Preceding unsigned comment added by GhostInTheMachine (talk • contribs) 17:00, 23 February 2024 (UTC)Reply[reply]
I get the wrong skin on a number of module pages, but not all. Ones with the wrong skin include Module:Clade, Module:Biota infobox and Module:Goalscorers, but Module:Taxonbar and Module:Autotaxobox shows with the skin in my preferences (MonoBook). —  Jts1882 | talk  17:37, 23 February 2024 (UTC)Reply[reply]
For me the first three also appear in the wrong skin, but the last two don't. It will be interesting to learn what's causing this. -- LCU ActivelyDisinterested «@» °∆t° 18:45, 23 February 2024 (UTC)Reply[reply]

I've got the same issues as the people above but also with Wikipedia:Articles for deletion/Log/2024 February 23. It seems to resolve for a bit if I changed to the new skin and back in a different tab and refresh, but it reverts to the issue later. Shaws username . talk . 22:00, 23 February 2024 (UTC)Reply[reply]

  • I also stumbled across this - a random selection of AfD date pages appear in Vector 2022 for me. This RfA is in V2022, but this one appears in V2010. Bizarre! —Ganesha811 (talk) 15:48, 24 February 2024 (UTC)Reply[reply]
Same, but some logs don't have the issue. Glad it's not my system. Star Mississippi 18:09, 24 February 2024 (UTC)Reply[reply]

Shifting "skins"[edit]

Sorry if this has been brought up already but I do a lot of work on AFD daily log pages and they keep shifting skins. The layout can even change when I refresh the page. The view I don't want is a small middle column and two wide columns on either side. I'm used to the old view with a large middle column that has the majority of content and a top menu and only a right-hand side columns. There was a message at the top of a page that mentioned XFD discussion so I uninstalled that feature but it hasn't changed things for me. I have a week of AFD daily logs open in tabs and about 5 pages have the old view and 3 pages have the alternate view. Refreshing the page helped this morning (the view would switch back) but that doesn't work any longer. I've looked at my Preferences but nothing has changed there, still Vector Legacy.

It's strange how the layout of content really affects how I work and I find this new view, with tons of white space, off-putting. Any ideas how I can return things to normal for all AFD daily log pages? Thanks for any suggestions. Liz Read! Talk! 05:19, 24 February 2024 (UTC)Reply[reply]

@Liz: Sounds like the same problem as Wikipedia:Village_pump_(technical)#Weird_issue_where_Vector_2022_is_being_forced_on_a_single_page. Where there are some cases where a page will use the new skin instead of the user's preferred skin. Or is this a different problem you are seeing? RudolfRed (talk) 06:02, 24 February 2024 (UTC)Reply[reply]
Well, Wikipedia:Articles for deletion/Log/2024 February 17 was one particular page that just kept showing the alternate, white space skin (I should really learn their names). I did find I could hide the right-hand side menu which helped. But I just refreshed this page and got the old style came back so who knows? But this time, I was running into this phenomena on AFD daily log pages (as mentioned in the message below this one). I should have known it was a system bug, not just me, so thanks for moving my message to join others that mention similar problems. Liz Read! Talk! 20:07, 24 February 2024 (UTC)Reply[reply]

Technical summary[edit]

Where Special:PrefixIndex is typically used

To summarize what's going on in a non-technical way, this appears to be a bug related to Special:PrefixIndex, which is used to generate the back-link header that's seen on subpages. A subpage is basically any page that has a slash in its title in certain namespaces (possibly all spaces except mainspace?). And what I'm calling the "back-link header" is the collection of links that take you back to the parent page. This is commonly seen in process pages such as WP:AfD, WP:SPI and WP:FAC. If you're seeing this on one of those kinds of pages, that explains it. If you're seeing this on a page that's not a subpage, that's a lot more interesting, and please post your exmples here. RoySmith (talk) 19:28, 24 February 2024 (UTC)Reply[reply]

That is incorrect. The breadcrumb links have nothing to do with this. It's happening on pages where Special:PrefixIndex is transcluded, usually via templates like {{Featured article tools}} and {{SPI archive notice}}. Nardog (talk) 19:43, 24 February 2024 (UTC)Reply[reply]
Oh, I thought the back links also called PrefixIndex. In any case, thank you for the correction. RoySmith (talk) 19:49, 24 February 2024 (UTC)Reply[reply]

Theme switching back and forth[edit]

I use the Vector 2010 theme, but have noticed that on a few AfD pages it switches to some sort of different, worse, minimalist theme. When I click "switch to old look" it takes me to the user page where it shows I am using the old look. Most pages are fine including this one. Is this a bug? SportingFlyer T·C 22:32, 24 February 2024 (UTC)Reply[reply]

Yes. See above. * Pppery * it has begun... 22:35, 24 February 2024 (UTC)Reply[reply]
Thanks! I absolutely detest Vector 2022 - anything I can do to help? SportingFlyer T·C 14:28, 25 February 2024 (UTC)Reply[reply]

Skin changing[edit]

Beginning yesterday, whenever I visit a page starting with the prefix Wikipedia:Featured article candidates/, the page is displayed in Vector 2022 (I think?). Every other page, and those pages in edit mode, display in the skin I have set, which is not that. Anyone know what is causing that? Nikkimaria (talk) 02:33, 26 February 2024 (UTC)Reply[reply]

Same issue for me and the FAC I have open at the moment. Very annoying - looks like it's a bug that will hopefully get fixed soon. PCN02WPS (talk | contribs) 05:01, 26 February 2024 (UTC)Reply[reply]

Status[edit]

I've just been chatting with some of the WMF RelEng folks on IRC. I don't want to speak for them, but I will say that they're aware of the problem and working on it. The best thing for most of us to do at this point is to let them do their thing and watch T336504 for status updates. It looks like doing a hard reload (hold down the shift key while reloading in Chrome; I assume soemthing similar on other browsers) gets you back to your configured skin, so in the meantime, that's a viable workaround. RoySmith (talk) 15:35, 26 February 2024 (UTC)Reply[reply]

Unfortunately such refresh options are not available on mobile, and even clearing all site data for Wikipedia doesn't clear the issue from all pages. -- LCU ActivelyDisinterested «@» °∆t° 22:35, 26 February 2024 (UTC)Reply[reply]
Sadness. RoySmith (talk) 22:39, 26 February 2024 (UTC)Reply[reply]

Resolved?[edit]

This is no longer happening for me, so I think it's been resolved. Can anyone else confirm? NW1223<Howl at meMy hunts> 18:56, 27 February 2024 (UTC)Reply[reply]

Yes, the fix has been deployed yesterday (or this morning, depending on your time zone: phab:T336504#9579650). Matma Rex talk 23:19, 27 February 2024 (UTC)Reply[reply]

everything is broken[edit]

I am confused

You Know on the main page."}]}" data-mw="{"caption":"This user helped get \"Frelinghuysen University\" listed at Did You Know on the main page."}">You Know on the main page." data-parsoid="{}">This user helped get "Frelinghuysen University" listed at Did <strong style=You Know on the main page." resource="//en.wikipedia.org/wiki/File:DYK_questionmark_icon.svg" src="//upload.wikimedia.org/wikipedia/commons/thumb/c/c6/DYK_questionmark_icon.svg/17px-DYK_questionmark_icon.svg.png" decoding="async" data-file-width="144" data-file-height="166" data-file-type="drawing" height="20" width="17" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/c/c6/DYK_questionmark_icon.svg/26px-DYK_questionmark_icon.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/c/c6/DYK_questionmark_icon.svg/35px-DYK_questionmark_icon.svg.png 2x" class="mw-file-element hide-images-handled" data-parsoid="{"a":{"resource":"./File:DYK_questionmark_icon.svg","height":"20","width":"17"},"sa":{"resource":"File:DYK questionmark icon.svg"}}">
You Know on the main page."}]}" data-mw="{"caption":"This user helped get \"Lisa Winter\" listed at Did You Know on the main page."}">You Know on the main page." data-parsoid="{}">This user helped get "Lisa Winter" listed at Did <strong style=You Know on the main page." resource="//en.wikipedia.org/wiki/File:DYK_questionmark_icon.svg" src="//upload.wikimedia.org/wikipedia/commons/thumb/c/c6/DYK_questionmark_icon.svg/17px-DYK_questionmark_icon.svg.png" decoding="async" data-file-width="144" data-file-height="166" data-file-type="drawing" height="20" width="17" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/c/c6/DYK_questionmark_icon.svg/26px-DYK_questionmark_icon.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/c/c6/DYK_questionmark_icon.svg/35px-DYK_questionmark_icon.svg.png 2x" class="mw-file-element hide-images-handled" data-parsoid="{"a":{"resource":"./File:DYK_questionmark_icon.svg","height":"20","width":"17"},"sa":{"resource":"File:DYK questionmark icon.svg"}}">
You Know on the main page."}]}" data-mw="{"caption":"This user helped get \"Shit flow diagram\" listed at Did You Know on the main page."}">You Know on the main page." data-parsoid="{}">This user helped get "Shit flow diagram" listed at Did <strong style=You Know on the main page." resource="//en.wikipedia.org/wiki/File:DYK_questionmark_icon.svg" src="//upload.wikimedia.org/wikipedia/commons/thumb/c/c6/DYK_questionmark_icon.svg/17px-DYK_questionmark_icon.svg.png" decoding="async" data-file-width="144" data-file-height="166" data-file-type="drawing" height="20" width="17" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/c/c6/DYK_questionmark_icon.svg/26px-DYK_questionmark_icon.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/c/c6/DYK_questionmark_icon.svg/35px-DYK_questionmark_icon.svg.png 2x" class="mw-file-element hide-images-handled" data-parsoid="{"a":{"resource":"./File:DYK_questionmark_icon.svg","height":"20","width":"17"},"sa":{"resource":"File:DYK questionmark icon.svg"}}">

every top badge on a proflie is breaking also it keeps forcing redlinks on actual things with pages

2601:5CC:8300:A7F0:1172:DF6B:3030:BF40?action=edit&redlink=1

•Cyberwolf•talk? 14:52, 23 February 2024 (UTC)Reply[reply]

Try to deactivate everything in User:Cyberwolf/common.js and meta:User:Cyberwolf/global.js, then reload. — xaosflux Talk 15:31, 23 February 2024 (UTC)Reply[reply]
Even simpler, try opening the page in an incognito window. RoySmith (talk) 16:27, 23 February 2024 (UTC)Reply[reply]
or with ?safemode=1 on your url. — xaosflux Talk 16:28, 23 February 2024 (UTC)Reply[reply]

Special:RecentChanges and "created automatically" accounts[edit]

Sorry if this has been asked before, couldn't find it, but it's something I only now noticed:
Recent changes only shows account creations that are listed as "was created" in Special:Log/newusers and doesn't show accounts that are listed as "was created automatically".
Am I just missing some obvious setting or is this actually intended? – 2804:F14:80C5:3C01:95F6:953B:7E66:6B4C (talk) 08:31, 24 February 2024 (UTC)Reply[reply]

This appears to be as designed (see phab:T24914 for a very old note). As you noted, the Special:Log is the place to look for these if you are interested. — xaosflux Talk 11:23, 27 February 2024 (UTC)Reply[reply]
That's fair enough. Thank you for looking into it. – 2804:F14:80E5:6B01:F969:B861:B7FB:B942 (talk) 23:06, 27 February 2024 (UTC)Reply[reply]

Category template mess[edit]

Is anyone able to work out why the redirect Category:Infobox road instances in has recently filled up with 273 entries when they should be in Category:Infobox road instances without location? I can't spot anything in the templates that shows why they're populating this one. Timrollpickering (talk) 09:55, 24 February 2024 (UTC)Reply[reply]

Following the chain of templates and modules used in {{Infobox road}}, it appears this change is causing {{Infobox road/meta/mask/category}} to return just the word "in" (at least for A21 road (England)). Whether this is an issue with the template usage or the module edit I don't know. Aidan9382 (talk) 10:30, 24 February 2024 (UTC)Reply[reply]
Changing country=ENG to country=GBR seems to solve the technical problem but the cost of altering the display on some entries. Timrollpickering (talk) 13:55, 24 February 2024 (UTC)Reply[reply]
Yeah it knocks out constituent country and the links for Northern Ireland are different. Timrollpickering (talk) 13:58, 24 February 2024 (UTC)Reply[reply]

Deleted Category Articles[edit]

I was directed here to ask my question about the “murderers for life insurance money” category. I’d like to know the list of articles under that category before it was deleted. I’m sure it’s under the contribution history of a user or bot, so I’m trying to find exactly which was responsible for it. If that’s not how I can find the list, I’d like to know how I can find that history. Reference me with “@“ so I may get an alert to your reply form the mention you leave. ContributingHelperOnTheSide (talk) 18:07, 24 February 2024 (UTC)Reply[reply]

@ContributingHelperOnTheSide: You can see the bot removing the category from articles here when it deleted it. Nardog (talk) 19:07, 24 February 2024 (UTC)Reply[reply]
And you can find the bot by clicking a link to the deleted page Category:Murderers for life insurance money, or enter the page name at Special:Log. PrimeHunter (talk) 19:17, 24 February 2024 (UTC)Reply[reply]
Thank you very much! ContributingHelperOnTheSide (talk) 20:28, 24 February 2024 (UTC)Reply[reply]
Thank you very much! ContributingHelperOnTheSide (talk) 20:28, 24 February 2024 (UTC)Reply[reply]

New articles from category by PetScan[edit]

Why some categories not load in PetScan? Eurohunter (talk) 19:47, 24 February 2024 (UTC)Reply[reply]

Try asking over at Wikipedia talk:PetScan. If you have a repeatable bug you may also report it here. — xaosflux Talk 11:14, 27 February 2024 (UTC)Reply[reply]

More contrib list trouble[edit]

Back here I had a problem with displaying editors' contributions lists because my filters were permanently set to "Hide probably good edits". Well, this has caused some problems lately. First of all, I'm getting tired of having to manually uncheck that box when I see someone's contributions list. But more importantly, I've been having some problems pressing the "Older 50/100/250/500" button. Here's what happens: 1) I uncheck the "Hide probably good edits" button (which, by the way, I've seen nothing pop up on vandalism-only accounts' contributions list because the programme thinks that they're "probably good edits") 2) I click "Older 50", although it could be for any other amount too 3) Nothing shows up. 4) I unclick "hide probably good edits" 5) I am shown only the first 50 contributions of the user. Nothing I've tried seems to work. Any advice? Cheers ‍ Relativity 23:03, 24 February 2024 (UTC)Reply[reply]

None of the options in the form get reflected unless and until you click "Search". So in order to see an unfiltered list of the 51st and older contributions, you have to uncheck the option, click Search, and then click "older 50". Nardog (talk) 23:09, 24 February 2024 (UTC)Reply[reply]
How are you accessing the contributions? "Hide probably good edits" isn't checked by default and I'm not aware of a user preference to make it so. Nardog (talk) 23:15, 24 February 2024 (UTC)Reply[reply]
Apparently checking "Show only likely problem edits (and hide probably good edits)" in Preferences -> Recent changes causes the option in Contributions to be checked by default. Nardog (talk) 23:29, 24 February 2024 (UTC)Reply[reply]
@Nardog Yes, unchecking that worked! Thank you! ‍ Relativity 01:32, 25 February 2024 (UTC)Reply[reply]

Harv and Sfn template errors[edit]

I have been using {{sfn}} pointing to {{cite gnis2}} citations, for example Denton Hills. This creates false no target errors, and {{sfn}} puts the articles into Category:Harv and Sfn template errors. DuncanHill has kindly been fixing the errors by adding {{sfn whitelist}} entries for each target. This seems daft. The point of using {{cite gnis2}} rather than {{cite gnis}} is to get support for {{sfn}} footnotes, but to avoid the errors we have to code e.g.

*{{cite gnis2 |type=antarid |id=17239 |name=Keble Hills}}{{sfn whitelist|CITEREFKeble_Hills_USGS}}

I started a crude alternative, {{Cite antgeo}}, which formats a citation as expected, does not result in a no target error, and the link seems to work but the citation is not higlighted when I click on the short footnote. E.g.

..some text{{sfn|Keble Hills USGS}}
{{reflist}}
*{{Cite antgeo |id=17239 |name=Keble Hills}}

generates

...some text[1]

Is this some trivial, fixable bug, or am I completely missing the point? Aymatth2 (talk) 14:43, 25 February 2024 (UTC)Reply[reply]

In your {{cite antgeo}} example, I see the Module:Footnotes-generated error message: sfn error: no target: CITEREFKeble_Hills_USGS. I also get the pale-blue highlight when I hover my mouse pointer over the superscripted [1] and also when I hover over the Keble Hills USGS link in the reference list. Clicking #CITEREFKeble Hills USGS in the reflist causes a page jump to the {{cite antgeo}} template in the 'bibliography' but there is no pale blue highlight.
If your primary complaint is the loss of the pale blue highlight, I can be of no help because I think that that is a function of mediawiki some place.
Trappist the monk (talk) 16:05, 25 February 2024 (UTC)Reply[reply]
My concern is that *{{cite gnis2 |type=antarid |id=17239 |name=Keble Hills}}{{sfn whitelist|CITEREFKeble_Hills_USGS}} is a very clumsy way to format a citation. There is surely some way for {{cite gnis2}} to make the target visible. My shot at it with {{Cite antgeo}} did not really work, but there must be some way to do it. Aymatth2 (talk) 17:09, 25 February 2024 (UTC)Reply[reply]
Here I have slightly mangled the parameter values assigned to {{harvnb}} and {{sfnref}} to avoid confusion with existing templates:
{{harvnb|KebleHills USGS}}KebleHills USGS
{{cite gnis2 |type=antarid |id=17239 |name=Keble Hills |ref={{sfnref|KebleHills USGS}}}}
"Keble Hills", Geographic Names Information System, United States Geological Survey, United States Department of the Interior
No error message; no need for {{sfn whitelist}}.
To avoid the false positive error message, Module:Footnotes must be able to construct a CITEREF id from information available in the article wikitext. To do that it looks for known author and date parameters and for known |ref= values (|ref={{sfnref|...}} and |ref={{harvid|...}} or plaintext |ref=CITEREF...). Without any of that, Module:Footnotes cannot construct a CITEREF id that matches the CITEREF id created by the long-form citation template.
Trappist the monk (talk) 17:53, 25 February 2024 (UTC)Reply[reply]
That seems an reasonable solution. I put it into Denton Hills and it works. It would be nice if syntax was a bit more compact, but this is o.k. The {{cite gnis2}} documentation needs to be updated. I can do that. Thanks, Aymatth2 (talk) 18:25, 25 February 2024 (UTC)Reply[reply]
@Aymatth2, DuncanHill, and Trappist the monk: {{sfn whitelist}} is a cop-out, it's just sweeping the problem under the carpet. If you feel that you need to add it to more than one page it's much easier to add an appropriate entry to Module:Footnotes/whitelist. --Redrose64 🌹 (talk) 19:15, 25 February 2024 (UTC)Reply[reply]
it's just sweeping the problem under the carpet Oh, I don't know about that. Module:Footnotes/whitelist is just a bigger broom. For me, single use CITEREF ids should not clutter the whitelist module.
Trappist the monk (talk) 20:08, 25 February 2024 (UTC)Reply[reply]
@Redrose64: A lot of the {{cite gnis}} targets will be used only on one or two pages, although the web source is the same for all of them. E.g.
https://web.archive.org/web/20210602235014/https://geonames.usgs.gov/apex/f?p=gnispq:5:::NO::P5_ANTAR_ID:12345
Adding a |ref= parameter like
*{{cite gnis2|id=12345|name=feature name|ref={{harvid|feature name USGS}}}}
is workable but clumsy. It would be better if Module:Footnotes understood that {{cite gnis}} creates a target like CITEREFfeature_name_USGS. Aymatth2 (talk) 20:12, 25 February 2024 (UTC)Reply[reply]
Best of all would be if Module:Footnotes could scan the generated code and see if the id was present. Aymatth2 (talk) 20:15, 25 February 2024 (UTC)Reply[reply]
Module:Footnotes is not going to understand {{cite gnis}} or {{cite gnis2}} or any of the other hundreds (thousands?) of wrapper templates because each wrapper seems to have its own proprietary way of creating short-format reference anchor ids. Generated html is not available to modules so Module:Footnotes will never scan it.
Trappist the monk (talk) 20:38, 25 February 2024 (UTC)Reply[reply]
The main whitelist doesn't check template and reference details. So if CITEREFKeble_Hills_USGS is listed with 'cite gnis' then CITEREFKeble_Hills_USGS is suppressed on all pages with any 'cite gnis' template, even if it's the wrong template and the correct one is missing.
Using 'sfn whitelist ' is a far superior option for templates that have many different CITEREFs. -- LCU ActivelyDisinterested «@» °∆t° 20:54, 25 February 2024 (UTC)Reply[reply]
Perhaps we should think about some sort of mapping table for the hundreds (thousands?) of wrapper templates. The entry for {{cite gnis2}} could be something like
Template:cite_gnis2 anchorid:"CITEREF{{{name|{{{2}}}}}} USGS"
Then Module:Footnotes could check the source code for templates in the mapping table and predict the anchor ids they would generate. We could populate the mapping table on demand. Aymatth2 (talk) 21:12, 25 February 2024 (UTC)Reply[reply]
The CITEREFs for some templates is anything the editor adds in the article, {{DBI}} for instance. There's no way of knowing beforehand what an editor might add. Getting mediwiki to suppress the error messages during page creation if the CITEREF does exist in the finished page would get rid of the issue altogether, but that's likely not possible. -- LCU ActivelyDisinterested «@» °∆t° 21:35, 25 February 2024 (UTC)Reply[reply]
See any of the edits that I made to Module:Footnotes/whitelist. All of them concern wrapper templates; for example, in this edit, the wrapper is Template:Quick-stations-5.05. --Redrose64 🌹 (talk) 22:08, 25 February 2024 (UTC)Reply[reply]
If we could eliminate most false errors that would be a big improvement. Perfection may be impossible. My guess is that a small number of cite wrappers cause most of the problems. The module can see the page source. It could scan until it found {{references}}, then start checking all the templates after that. If they were in the mapping table, it would work out what anchor id they would generate, and suppress error reporting for those anchor id's.
If a template takes whatever it is passed, that is not an issue. The table says Template:oddball anchorid:"{{{ref}}}". The module finds {{oddball |ref=whatever}} and puts CITEREFwhatever in the list of do-not-report anchor id's. Aymatth2 (talk) 23:19, 25 February 2024 (UTC)Reply[reply]

 Fixed I fixed the issue with {{cite gnis}} and {{cite gnis2}} here. — hike395 (talk) 11:31, 26 February 2024 (UTC)Reply[reply]

Sticky header template for tables. Need iphone and Android testers[edit]

Concerning sticky headers on tables. See this popular template, and new testcase styles discussion:

The opinions of more experts would be greatly appreciated concerning any possible improvements.

This is a template I started, and has been improved by Jroberson108. Some tests are being run, but I am the only iphone user doing the tests, and Jroberson108 is the only Android phone user doing the tests so far.

We need other cell phone users to look at the sandbox pages in their cell phones in both portrait and landscape orientation. The current template styles work very well now for iphone users (at least for me using iphone SE 2020 in mobile Safari, Firefox, Edge, Chrome, Opera) no matter the width of the table. In both portrait and landscape view. I do not need to zoom out, or change the font size.

I am worried that there may be less iphone users able to see sticky headers on tables with these new styles. Because some of the new styles are specific to my iphone SE 2020. So I would like some other iphone users to compare the results of the old and new styles:

I would also like some other Android phone users to look also. And tell us if the new styles are better or worse in portrait and landscape views. Specifically, one should not have to zoom or change font size to see sticky headers. But it may be required. Table widths shouldn't matter either. But they may. Be specific when comparing the old and new styles.

The main effect of the new styles is to allow non-sortable tables to have sticky headers on desktop and cell phones. But that was never a big problem because it is easy to add class=sortable to a table. And {{sort under}} if necessary.

If the new styles affect iphone and Android phone users positively, then the new styles should go live. But if they are negatively effected by the new styles, then the new styles need to be improved. And advice from experts is requested in any case. --Timeshifter (talk) 13:40, 26 February 2024 (UTC)Reply[reply]

I don't have time to read through the (extensive) discussion on the template pages, but here are my observations (appropriately displayed in a table):
sandbox244 (old) sandboxen243 & 245 (new)
Firefox Desktop Only sortable tables have sticky headers All headers are properly sticky
Firefox Android Only sticky if the table is sortable and
I (pinch) zoom out so the full width of all tables is visible
(because apparently those don't scroll horizontally?)
None sticky in portrait, all sticky in landscape
My viewport is 396px wide in portrait, and 760px wide in landscape. (...which is really weird scaling, because the physical display is 1080x2340. Huh.) Hopefully that's of some help. LittlePuppers (talk) 23:10, 26 February 2024 (UTC)Reply[reply]
@LittlePuppers: I have the same experience on my Android. Jroberson108 (talk) 23:32, 26 February 2024 (UTC)Reply[reply]

LittlePuppers. Thanks! Am I correct to assume that all table widths worked in Firefox Android landscape without zooming? Were any of the tables wider than landscape view? I just added some columns to a couple wide tables to make them into really wide 12 or 13-column tables. Here: User:Timeshifter/Sandbox243. --Timeshifter (talk) 00:23, 27 February 2024 (UTC)Reply[reply]

User:Timeshifter/Sandbox243#Test sticky-header (sortable) is the only one wider on my Android Chrome landscape where I have to zoom out to make it sticky. It pushes beyond the main content area making the whole page wider, but the text is still readable. Without zooming, the edge of the screen ends inside header 9. "Test sticky-header (no caption)" too, which the edge ends inside header 12. Jroberson108 (talk) 01:15, 27 February 2024 (UTC)Reply[reply]
Thanks. I just increased that one to 13 columns. I created some 12 or 13-column tables for the current styles too: User:Timeshifter/Sandbox244. Does the sortable table there require zooming to be sticky in landscape? --Timeshifter (talk) 01:47, 27 February 2024 (UTC)Reply[reply]
It appears that with either version of the template (old or new), if there is any table on the page wider than the default width, no headers will be sticky until the page is zoomed all the way out. LittlePuppers (talk) 02:03, 27 February 2024 (UTC)Reply[reply]
I agree, for User:Timeshifter/Sandbox243 in landscape you have to zoom all the way out for a table to be sticky. Also, if all the sections are open (all tables in view), then no tables are sticky unless you zoom all the way out.
For User:Timeshifter/Sandbox244, nothing is sticky except "Test sticky-header (sortable)", which requires zooming out to be sticky. Jroberson108 (talk) 02:24, 27 February 2024 (UTC)Reply[reply]

I am still looking for an iphone user to look at this. TheDJ, I vaguely remember you having an iphone. And you created the sticky header gadget:

--Timeshifter (talk) 14:32, 27 February 2024 (UTC)Reply[reply]

I have a very busy week, I can't make any promises until the weekend. —TheDJ (talk • contribs) 10:04, 28 February 2024 (UTC)Reply[reply]

Tech News: 2024-09[edit]

MediaWiki message delivery 19:21, 26 February 2024 (UTC)Reply[reply]

The reference list is not displayed![edit]

The reference list is not displayed!

On Hannibal Alkhas the Reference list does not appear. I have tried this on User:اربابی دوم/sandbox first and there everything works fine. What is the problem? Can anyone help? Arbabi second (talk) 20:23, 26 February 2024 (UTC)Reply[reply]

Don't use {{citation/fcite}}; it is no longer supported and will not render in article space. Why did you choose to use that template?
Trappist the monk (talk) 20:32, 26 February 2024 (UTC)Reply[reply]
@Trappist the monk
Thanks for the response. But what can be done now? Arbabi second (talk) 20:46, 26 February 2024 (UTC)Reply[reply]
As a quick fix I have changed each {{citation/fcite}} to {{citation}}.[7] Based on Special:WhatLinksHere/Template:Citation/fcite I wonder how you found {{citation/fcite}}. It should not be used. PrimeHunter (talk) 21:57, 26 February 2024 (UTC)Reply[reply]

Documentation for SSH[edit]

When I am on Toolforge, where I intend to work on a bot, it asks me to "Add your SSH public key". I am about to do that.
It continues "See the help documentation for more information on how to generate and upload your public SSH key." When I click the link the help documentation, it goes to https://wikitech.wikimedia.org/wiki/Obsolete:Toolforge/Access#Generating_and_uploading_an_SSH_key. Is that correct? Should it say "Obsolete"? --David Tornheim (talk) 22:18, 26 February 2024 (UTC)Reply[reply]

That's an outdated link. wikitech:Help:Toolforge/Quickstart#Connect_to_Toolforge_servers_using_SSH has the steps for SSH login. – SD0001 (talk) 18:07, 27 February 2024 (UTC)Reply[reply]
I think wikitech:Help:SSH is the correct updated link. --Ahecht (TALK
PAGE
) 19:48, 27 February 2024 (UTC)Reply[reply]
Ahecht, not sure why this would need a phab ticket? I've changed the redirect target. — Qwerfjkltalk 20:59, 27 February 2024 (UTC)Reply[reply]
Ignore that last comment, clearly I misread. — Qwerfjkltalk 21:00, 27 February 2024 (UTC)Reply[reply]
@Qwerfjkl: Thanks. For some reason, Ahecht changed it back. I am just as confused as when I first posted! --David Tornheim (talk) 00:40, 28 February 2024 (UTC)Reply[reply]
The redirect was correct before Qwerfjkl changed it. It's the link on the toolforge page itself that needs to be updated. --Ahecht (TALK
PAGE
) 01:32, 28 February 2024 (UTC)Reply[reply]
Okay. So should I just work under the assumption that the link should go to wikitech:Help:Toolforge/Quickstart#Connect_to_Toolforge_servers_using_SSH rather than to the obsolete page? --David Tornheim (talk) 02:32, 28 February 2024 (UTC)Reply[reply]

List of recent stubs in project[edit]

Any string manipulators in the house? I'm trying to create a report of articles recently assessed as a stub in a WikiProject. The best advice I've received is to base it on the existing Wikipedia:Version 1.0 Editorial Team/Anarchism articles by quality log report, but I'd like to process this page into just the names of the entries that were marked as stubs, i.e., any line that includes "Quality rating changed from <x>-Class to Stub-Class" or "Quality assessed as Stub-Class" (for new articles). Ideally it would just be a bulleted list of the eligible, wikilinked articles with all the other text ignored/deleted. I believe this is possible with some form of Module:String replace/match on {{#invoke:page|getContent|Wikipedia:Version 1.0 Editorial Team/Anarchism articles by quality log|as=raw}} similar to what is done in Template:WPVG announcements/shell but I'm not sure how to handle it without a regex lookahead. Can someone help, or have any tips? czar 23:22, 26 February 2024 (UTC)Reply[reply]

Czar, really, when you want to find multiple matches you should use a module and iterate over the matches. That said, you can do it in wikimarkup:
{{For nowiki||<nowiki>{{#invoke:string|match|pattern=[^{{truenewline}}]+Stub%-Class[^{{truenewline}}]+|s={{#invoke:page|getContent|Wikipedia:Version 1.0 Editorial Team/Anarchism articles by quality log|as=raw}}|match={{{1}}} }}</nowiki>|count={{#invoke:String|count|{{#invoke:page|getContent|Wikipedia:Version 1.0 Editorial Team/Anarchism articles by quality log|as=raw}}|[^{{truenewline}}]+Stub%-Class[^{{truenewline}}]+|plain=false}}
}}

Producing:

— Qwerfjkltalk 17:42, 27 February 2024 (UTC)Reply[reply]
What this does:
  • I've used the pattern [^{{truenewline}}]+Stub%-Class[^{{truenewline}}]+ to match any line containing "Stub-Class" (using {{truenewline}} because I couldn't find a better way to use newlines in sets).
  • Because there are multiple matches, I've used {{For nowiki}} to iterate over each match.
  • Then I've just used match on the string with the pattern, passing in the count from {{for nowiki}}
— Qwerfjkltalk 17:48, 27 February 2024 (UTC)Reply[reply]
Looking at Template:WPVG announcements/shell, it seems to just use patterns to remove the lines that don't match. I'm fairly sure that would require lookahead, as you say.
Here's an alternative approach, which splits the text into lines, and then only returns lines that match:
{{For nowiki||<nowiki>{{If string|source={{Array|get|{{#invoke:page|getContent|Wikipedia:Version 1.0 Editorial Team/Anarchism articles by quality log|as=raw}}|{{Truenewline}}|{{{1}}}}}|target=Stub-Class|plain=true}}</nowiki>|count={{Array|count|{{#invoke:page|getContent|Wikipedia:Version 1.0 Editorial Team/Anarchism articles by quality log|as=raw}}|{{truenewline}}}}}}
Qwerfjkltalk 19:17, 27 February 2024 (UTC)Reply[reply]
@Qwerfjkl, excellent—thank you! I threw together a template here (Template:Recent stubs) so others can use it too.
If there's a better way to get the intended result with using a module and iterating over the matches, open to that as well but I have yet to venture into Lua-land. Would that version be able to exclude stubs that have been reassessed as another class? Right now Ōsugi Sakae in the above example was formerly a stub but is no longer. czar 21:37, 27 February 2024 (UTC)Reply[reply]
Czar, you don't need a module for that, just a slightly more complicated pattern. I'm a tad busy right now, but I'll have a shot at it later today. — Qwerfjkltalk 07:13, 28 February 2024 (UTC)Reply[reply]

Finding non-redirect articles that have class=redirect on the talk page banner shell[edit]

I'd like to find articles under a specific category that have a wikiproject 'class' hard set to 'redirect' in the banner shell, but that are not actually redirects. Is there a tool to do this? I took at look at PetScan but I don't see a suitable combination of filters. Thanks. Praemonitus (talk) 04:33, 27 February 2024 (UTC)Reply[reply]

Praemonitus, I think ratings like that are automatically ignored. @Martin? — Qwerfjkltalk 07:21, 27 February 2024 (UTC)Reply[reply]
Yeah, redirects are detected automatically these days and any incorrect |class=redirect values are just ignored — Martin (MSGJ · talk) 08:53, 27 February 2024 (UTC)Reply[reply]
@Praemonitus: Please always give an example, in this case a category. Since a redirect category is not actually added by |class=redirect, I'm not sure which type of category and scenario you want. If I ignore part of your question and guess that you want pages which incorrectly have |class=redirect without being attached to a redirect then we can use that the category is not added with a search like hastemplate:"WikiProject Astronomy" insource:"class=redirect" -incategory:"Redirect-Class Astronomy articles". PrimeHunter (talk) 12:23, 27 February 2024 (UTC)Reply[reply]
@PrimeHunter: Okay, the scenario I have in mind is for a 'redirect' article that is correctly set to 'class=redirect'. At some point in the future, an editor converts the redirect into a normal article (which I have done myself). If the talk page banner shell is not suitably updated, it could continue to be perceived incorrectly by the WikiProject(s). In my case the particular category is Category:Astronomy and its various sub-categories, but this scenario could apply to any category maintained by a WikiProject. I don't have a good example of this because finding one would literally involve checking tens of thousands of redirect pages. Praemonitus (talk) 17:50, 27 February 2024 (UTC)Reply[reply]
@Praemonitus: It sounds like I guessed correctly. As mentioned, your scenario isn't really a problem since |class=redirect is ignored. You can try for yourself to preview Talk:Astronomy with {{WikiProject Astronomy}} or {{WikiProject Astronomy|class=redirect}}. It gives exactly the same result, both in the categories and WikiProject banner. I don't know any tools which look for |class=redirect in the source text. If there were any article examples of your issue for {{WikiProject Astronomy}} then they should appear in my above search but it only gives category talk pages. PrimeHunter (talk) 18:23, 27 February 2024 (UTC)Reply[reply]
Thank you, PrimeHunter. Praemonitus (talk) 18:26, 27 February 2024 (UTC)Reply[reply]

Visual Editor seems broken[edit]

Whenever I try to open Visual Editor, I get "Error: Unable to fetch Parsoid HTML". The editor fails to open. Zanahary (talk) 07:04, 27 February 2024 (UTC)Reply[reply]

 Works for me if this is still a problem, please try turning off your personal javascripts (User:Zanahary/common.js and meta:User:Zanahary/global.js) then try again. — xaosflux Talk 11:12, 27 February 2024 (UTC)Reply[reply]

See Wikipedia talk:Requested moves#Floating link (cc: SilverLocust). Whenever I try to save an edit to the Wikipedia:Requested moves page manually, it times out with an error of [eb5dac88-ace2-499b-816a-64cf82089c3f] 2024-02-28 04:17:33: Fatal exception of type "Wikimedia\Rdbms\DBQueryDisconnectedError". The console is complaining about deprecated ResourceLoader modules, with a link to this page. A brief search suggests this might be related to T354015. Any suggestions? Extraordinary Writ (talk) 04:43, 28 February 2024 (UTC)Reply[reply]

That certainly does look similar. There is some additional discussion at Template talk:COVID-19 pandemic data#Unorthodox edit request. I'd note that WP:RM has 69,677 revisions, and @HouseBlaster suspected that the template's bug is related to that page's ~90,000 revisions. SilverLocust 💬 05:43, 28 February 2024 (UTC)Reply[reply]
I looked up the error code, it's indeed the same problem as T354015. Matma Rex talk 05:52, 28 February 2024 (UTC)Reply[reply]

Yuuge page reader numbers[edit]

So, I was checking Wikipedia:WikiProject Volcanoes/Popular pages for any article I had written and noticed that Mount Takahe is the second-most popular article in the entire volcanoes project with about 10,000 readers per day. Given the not very active page history I kind of wonder if the reader numbers are wrong. @MusikAnimal, Kaldari, and Mforns (WMF): since you run the tool. Jo-Jo Eumerus (talk) 11:48, 28 February 2024 (UTC)Reply[reply]

Leave a Reply