Spider Flower – Cleome

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

Heading markup changes

The HTML used to render all headings is being changed to improve accessibility. It will change on 22 May in some skins (Timeless, Modern, CologneBlue, Nostalgia, and Monobook). Please test gadgets on your wiki on these skins and report any related problems so that they can be resolved before this change is made in all other skins. The developers are also considering the introduction of a Gadget API for adding buttons to section titles if that would be helpful to tool creators, and would appreciate any input you have on that.

MediaWiki message delivery 23:01, 20 May 2024 (UTC)[reply]

Based on a quick search, it looks like the heading change will affect almost 300 scripts, many of which have inactive maintainers. Some arbitrary highlights from the top of the list include:

Plus many, many more. --Ahecht (TALK
PAGE) 19:22, 21 May 2024 (UTC)[reply]

A quick way to test these scripts right now, is to enable the Parsoid beta option (which already uses the new html structure) and to disable DiscussionTools, which uses a partial form of the new heading structure. —TheDJ (talk • contribs) 08:39, 22 May 2024 (UTC)[reply]

Indeed, you can already see it in Parsoid mode (but note that there are other differences – e.g. Parsoid output has <section> tags around each section, which may require a separate set of updates in some scripts).

Disabling DiscussionTools doesn't actually change anything though. The HTML structure is the same whether it's enabled or disabled, only the styles are different. Also, note that it uses a "hybrid" heading structure currently when using the default parser, as you say, but it uses the new structure when using Parsoid.

So in short, you can just use Parsoid mode to test these scripts today here on English Wikipedia, but beware that there may be extra issues. But if they work with Parsoid, they will work with the new headings too. Matma Rex talk 11:25, 22 May 2024 (UTC)[reply]

The technical 13 script was blanked, so we don't have to worry about that one.

Will the fact that they're rolling this out for only some wikimedia-deployed skins at this time make the patch more complicated? If I'm reading it right, the scripts may temporarily have to support both heading styles. –Novem Linguae (talk) 09:16, 22 May 2024 (UTC)[reply]

Yes, it does, and they have to. Matma Rex talk 11:20, 22 May 2024 (UTC)[reply]

At a glance, it seems that User:Mr. Stradivarius/gadgets/SignpostTagger.js already supports the new style, as it uses $( '#bodyContent h2:first' ).text() as a backup if $( '#bodyContent h2:first span.mw-headline' ) doesn't exist (line 291). — Mr. Stradivarius ^{♪ talk ♪} 13:09, 22 May 2024 (UTC)[reply]

Fixed RFUD-helper. Thanks for the ping. – SD0001 (talk) 18:33, 22 May 2024 (UTC)[reply]

This is going to break both my edit request scripts, I will try to fix them at the weekend. Terasail ^[✉️] 18:41, 22 May 2024 (UTC)[reply]

I've fixed my fork of the OneClickArchiver script (though now it only works with the new format; I don't care enough to get it working with both). Elli (talk | contribs) 02:09, 8 June 2024 (UTC)[reply]

And copy-section-link too (same caveat). Elli (talk | contribs) 02:16, 8 June 2024 (UTC)[reply]

Another one: User:Σ/Testing_facility/Archiver.js. Izno (talk) 00:45, 7 June 2024 (UTC)[reply]

And a couple other gadgets still remaining:

Izno (talk) 00:51, 7 June 2024 (UTC)[reply]

Gadget-teahouse is no longer used now that DiscussionTools has been rolled out. Pinging @Prtksxna and @TheDJ for the other two. --Ahecht (TALK
PAGE) 15:54, 12 June 2024 (UTC)[reply]

Σ's Archiver script has been superseded by forks. See subsection just below: #Tech News – User:Enterprisey/archiver.js. —⁠andrybak (talk) 01:19, 7 June 2024 (UTC)[reply]

I had no idea that one had gotten forked. Izno (talk) 01:24, 7 June 2024 (UTC)[reply]

Gadget-autonum (Auto-number headings)

I'm assuming ~ and feel free to correct me if i'm wrong ~ that something about this deployment is why headings no longer have numbers (for me)? Will it be possible to go back to that at some point? I find long pages almost impossible to navigate around without numbered headings, so will have to learn a new way of working if it won't be possible. Thanks, Happy days, ~ Lindsay^Hello 16:24, 27 May 2024 (UTC)[reply]

@LindsayH: No, that was removed a while ago. You may try the "Auto-number headings" gadget here. Nardog (talk) 19:31, 27 May 2024 (UTC)[reply]

If you're speaking about the table of contents, Vector 22 does not provide numbering. Vector, Monobook, and Modern do.

If you are speaking about each actual heading, then indeed the preference is gone and indeed there is a gadget for it now. You have correctly identified that gadget as needing to be updated for this change. It looks like the necessary change to the snippet (documentation) has already been made, so someone needs to port that here. Izno (talk) 19:59, 27 May 2024 (UTC)[reply]

Thank you, Izno, helpful. I'd assumed it was a script/gadget, as so many appeared to be affected above. I shall patiently wait in hope

Happy days, ~ Lindsay^Hello 11:51, 28 May 2024 (UTC)[reply]

@LindsayH. I think I fixed this gadget for monobook/timeless/modern with this update. But there is still a double number bug on some talk pages on vector/vector-2022. Will work on that next. –Novem Linguae (talk) 16:50, 1 June 2024 (UTC)[reply]

You star! Thanks for the notification (and, of course, for fixing it). Happy days, ~ Lindsay^Hello 06:14, 2 June 2024 (UTC)[reply]

Tech News – User:Enterprisey/archiver.js

I've been testing my fork of Enterprisey's script – User:Andrybak/Archiver. Example edits: 1226884323, 1227442551, 1227443165, 1227444165. So far, the script doesn't seem to be affected. —⁠andrybak (talk) 19:21, 5 June 2024 (UTC)[reply]

✅ Another successful test with random things (including cases, which were mentioned in bug reports): Special:Diff/1227451320. —⁠andrybak (talk) 21:33, 5 June 2024 (UTC)[reply]

Did you try all the old skins such as Timeless and Monobook? Vector isn't affected at all yet, and editing likely uses the API, but I can imagine the location of the header links this script places being possibly broken in old scripts. I fixed this kind of thing in 2 gadgets so far. –Novem Linguae (talk) 22:15, 5 June 2024 (UTC)[reply]

I know that Σ's User:Σ/Testing facility/Archiver supported at least Timeless: User talk:Σ/Archive/2021/January#Archy McArchface button caption in Timeless, so I expect Enterprisey's version to have remained compatible with other skins.

Good shout.

Checking... —⁠andrybak (talk) 22:28, 5 June 2024 (UTC)[reply]

Facepalm argh, I didn't read past the first sentence. My bad. Thank you, Novem Linguae, for pointing it out. —⁠andrybak (talk) 22:44, 5 June 2024 (UTC)[reply]

Novem Linguae, support for MonoBook and Timeless has been added: Special:Diff/1227543602. —⁠andrybak (talk) 11:22, 6 June 2024 (UTC)[reply]

Tests on real discussions: MonoBook, Timeless, Vector 2010, Vector 2022. —⁠andrybak (talk) 11:47, 6 June 2024 (UTC)[reply]

New h2 headings use serif font even when the "Vector classic typography" gadget is enabled

Vector classic typography is a gadget that forces all text to use sans-serif fonts, but even with the gadget enabled h2 headings on articles use a serif font. Incorrect behavior seen on both Firefox and Edge. TomatoFriesLAN (talk) 18:51, 6 June 2024 (UTC)[reply]

@TomatoFriesLAN Thanks for reporting, this is caused by the heading changes announced two weeks ago, which were deployed to legacy Vector as well this week. This edit should fix it: [1] – please try now. Matma Rex talk 20:27, 6 June 2024 (UTC)[reply]

Works, good job. TomatoFriesLAN (talk) 03:53, 7 June 2024 (UTC)[reply]

XFDcloser

I usually spend part of the day closing AFD discussions but none of the XFDcloser options are showing up. Not even the ability to relist. I've uninstalled every installation, unchecked the XFDcloser gadget, returned everything to normal but nothing works. Do I have to reboot my computer or something? Log out and log back in? This rarely happens so I'm not sure what happened today. I've posted a message on the XFDCloser talk page but it doesn't get much activity there. Liz ^{Read! Talk!} 23:26, 6 June 2024 (UTC)[reply]

It's not an XFDC issue, it's a THURSDAY issue. Primefac (talk) 00:35, 7 June 2024 (UTC)[reply]

Izno, I see you've moved this section, and it does appear to be mentioned in the original post of this threading, but why would it only appear now? I seem to recall closing discussions earlier this week (and I suspect Liz has as well). Primefac (talk) 01:17, 7 June 2024 (UTC)[reply]

I mean, it could not be this, and you're welcome to move it back, it just has the smell. Izno (talk) 01:24, 7 June 2024 (UTC)[reply]

I patched xfdcloser a couple days ago, so a new bug today is probably something else. Will take a look. –Novem Linguae (talk) 02:52, 7 June 2024 (UTC)[reply]

Well, I thought this thread was deleted until I found it reposted up here.

It's odd because XFDCloser was working fine this morning and then this afternoon, it just didn't load at all. But I see other editors closing discussions so I hope it isn't just me. I've had ongoing problems with XFDCloser not loading on CFD pages but it hasn't been a problem on AFD daily logs until today. Thanks for checking Novem Linguae, there are usually over 100 AFD discussions daily so if this is happening for other closers, they could pile up pretty quickly. If it matters, I use a laptop with Windows. Liz ^{Read! Talk!} 03:17, 7 June 2024 (UTC)[reply]

It's still working in Vector 2022, so changing your preferences temporarily is a workaround. Hopefully the issue will be fixed soon. Extraordinary Writ (talk) 03:39, 7 June 2024 (UTC)[reply]

I figured out the cause. I should have a fix deployed soon.

For the record, it looks like WMF deployed mw:Heading HTML changes to old skins (monobook, timeless, modern, cologneblue) last week, vector (2010) this week, and probably minerva and vector-2022 in the coming weeks. All breakages we see today will probably be vector (2010) only.

This staggered deployment has pros and cons. It means that if someone like me does fix a bunch of gadgets today, I'll just have to go fix them all again next week when they break on vector-2022.

It would be nice if there were an API for inserting header links. phab:T337286. APIs like mw.util.addPortlet(), mw.util.addPortletLink(), etc are great for multi-skin support and for keeping HTML changes from breaking gadgets and user scripts. –Novem Linguae (talk) 05:43, 7 June 2024 (UTC)[reply]

Yeah, I don't understand all of this jargon but I am FOREVER grateful that their are editors who do. Thanks for looking into this. Liz ^{Read! Talk!} 06:33, 7 June 2024 (UTC)[reply]

Fix deployed for XFDcloser. Should be fixed within the next 15 minutes (gadget code is cached for up to 15 minutes). –Novem Linguae (talk) 06:35, 7 June 2024 (UTC)[reply]

I see I did use Vector Legacy 2010. I don't like for page formatting and white space of the updated Vector 2022. Liz ^{Read! Talk!} 06:37, 7 June 2024 (UTC)[reply]

I also use Vector 2010. Best skin :) –Novem Linguae (talk) 06:38, 7 June 2024 (UTC)[reply]

I am looking forward to Vector 2034 — GhostInTheMachine ^{talk to me} 06:51, 7 June 2024 (UTC)[reply]

Yeah, and I don't like the left-side menu. But thanks Novem Linguae, it looks like things are now back to normal. I can go back to my old skin! Many thanks. Liz ^{Read! Talk!} 07:24, 7 June 2024 (UTC)[reply]

Novem Linguae, XFDCloser disappeared again! I think you said this might happen. It came back when I changed to Vector 2022 but, ugh! I guess I'll use that skin when working in AFDLand and then change back when doing regular editing. Liz ^{Read! Talk!} 22:15, 8 June 2024 (UTC)[reply]

I'm trying out Timeless. It's not as bad as Vector 2022. Liz ^{Read! Talk!} 22:32, 8 June 2024 (UTC)[reply]

But it doesn't work with Twinkle. Liz ^{Read! Talk!} 01:53, 9 June 2024 (UTC)[reply]

Well, XFDcloser returned to operational status. Thanks to whomever fixed that. Liz ^{Read! Talk!} 03:13, 9 June 2024 (UTC)[reply]

Very strange. I haven't done any work on XFDcloser since the last deploy on Thursday, and I don't see any relevant backport patches at wikitech:Server Admin Log that might have changed MediaWiki behavior this weekend. This is all quite mysterious. –Novem Linguae (talk) 08:56, 9 June 2024 (UTC)[reply]

Novem Linguae, it's just happened again, over the span of the past hour! This is getting annoying to have to keep changing skins. Liz ^{Read! Talk!} 23:31, 12 June 2024 (UTC)[reply]

@Liz. I deployed a fix related to the beta version of XFDcloser. Can you try Vector again and let me know if things are fixed? –Novem Linguae (talk) 00:48, 13 June 2024 (UTC)[reply]

User script that puts a ¶ symbol next to headings

What's the user script or gadget that puts a ¶ symbol next to headings, and when you click on it, it opens a modal with links to that section that you can copy/paste? It broke for me today and I want to fix it, but can't remember what it's called. Thanks. –Novem Linguae (talk) 03:35, 7 June 2024 (UTC)[reply]

Is it User:Enterprisey/copy-section-link? Sounds like what you described, but I don't see where you have it imported. – 2804:F14:809B:2701:19B4:583A:7C56:999F (talk) 04:22, 7 June 2024 (UTC)[reply]

Ah, it's in my global.js. No wonder I couldn't find it. Thank you very much for this link. –Novem Linguae (talk) 06:37, 7 June 2024 (UTC)[reply]

I wrote a script that provides links to user comments as well as headings, which I updated to support both the new and legacy methods of marking up headings. Its interface is a bit different though from the copy-section-link script. isaacl (talk) 06:23, 7 June 2024 (UTC)[reply]

I can't find where the script is putting the link(s) on Vector 2010. Any hints? –Novem Linguae (talk) 07:04, 7 June 2024 (UTC)[reply]

The function showCommentLinks() (starting on line 73) adds the links. The section of code starting at line 84 finds headings in the HTML document structure previously generated by MediaWiki (which I believe is the same across skins). The section of code starting at line 93 finds headings in the currently generated HTML document structure. isaacl (talk) 15:27, 7 June 2024 (UTC)[reply]

I was hoping you'd just tell me where the links are. lol. Anyway, I put a breakpoint on line 75 and the breakpoint is not getting hit when I refresh this page. I'm missing something. –Novem Linguae (talk) 20:33, 7 June 2024 (UTC)[reply]

I'm sorry, I didn't realize you were asking about the interface. As described in the documentation, you have to select the "Toggle link2clipboard" item in the tools menu (the location of the menu depends on your skin; for Vector 2010 it's in the left sidebar). </> is prepended to the start of each comment. For headings, <h/> is also prepended. Most of the time I don't want to see the links, so I chose to require an extra step to display them. Another difference from the other script is that for the major non-Safari browsers, the link text is automatically copied to the clipboard (always without surrounding square brackets; the other script can be configured not to do that if desired). isaacl (talk) 20:51, 7 June 2024 (UTC)[reply]

Nice, that worked. Thanks a lot. Feature idea: Add a way to copy it as an external link. I do this a lot when writing GitHub or Phabricator tickets, for example. –Novem Linguae (talk) 20:59, 7 June 2024 (UTC)[reply]

As my personal frequent use case is to link to comments or sections in wikitext, I wanted a way that would provide easy access to the link without underscores ;-) (And I chose to avoid square brackets as it's easier to add them when needed than delete them, and I like to use {{section link}} when feasible.) I'll take it under consideration, though; thanks for the feedback! isaacl (talk) 21:08, 7 June 2024 (UTC)[reply]

@Novem Linguae: I made a copy of Enterprisey's script with this fixed, if you'd like to switch to it: User:The Earwig/copy-section-link.js. — The Earwig (talk) 03:37, 20 June 2024 (UTC)[reply]

And I've just been informed that Enterprisey has replicated the fix to his version. — The Earwig (talk) 03:45, 20 June 2024 (UTC)[reply]

It seems that User:Enterprisey/copy-section-link.js and User:The Earwig/copy-section-link.js broke again after WP:THURSDAY. They put "undefined" after the hash (Wikipedia:Village pump (technical)#undefined instead of Wikipedia:Village pump (technical)#Heading markup changes), and don't work on headings other than ==second level== (<h2>). —⁠andrybak (talk) 10:20, 22 June 2024 (UTC)[reply]

To fix the issue I described above, I re-used similar code for finding the section headings from User:Andrybak/Archiver.js (as described just above in #Tech News – User:Enterprisey/archiver.js). Enterprisey and The Earwig, please see Special:Diff/1230446524/1230449212. —⁠andrybak (talk) 19:31, 22 June 2024 (UTC)[reply]

Section header typeface

I just noticed that section headers in articles are now using a serif typeface on both Vector and Vector legacy. Sorry I couldn't find information about this elsewhere but when and why was this change made? I do not like that it uses Oldstyle figures and would like to change it in my settings or .css page to be the same sans serif font used in other headers. Thanks! Reywas92^Talk 17:23, 7 June 2024 (UTC)[reply]

@Reywas92 Vector headers have actually been using serif fonts by default for a long time, but you have user CSS which was overriding that. It no longer works due to some changes to heading HTML. You can either change that part of your user CSS to:

h1, h2, .mw-heading1, .mw-heading2 {
    font-family: inherit !important;
}

Or alternatively just use the gadget "Vector classic typography" which has already been fixed. the wub "?!" 19:25, 7 June 2024 (UTC)[reply]

Thank you! Forgot they did that a decade ago, these numerals are awful. Reywas92^Talk 20:23, 7 June 2024 (UTC)[reply]

One click archiving not working?

I have been using User:Evad37/OneClickArchiver for some time, but I noticed the other day that the archiving links are no longer appearing for me. Anyone know why that might be? Just Step Sideways ^{from this world ..... today} 18:06, 9 June 2024 (UTC)[reply]

Just Step Sideways, see § Heading markup changes. I believe User:Andrybak/Archiver is a working ~~fork~~. — Qwerfjkl talk 18:08, 9 June 2024 (UTC)[reply]

Thanks for the pointer! I guess I'm off to install that. Just Step Sideways ^{from this world ..... today} 18:13, 9 June 2024 (UTC)[reply]

Well, that works, but it certainly isn't "one-click". Oh well. Just Step Sideways ^{from this world ..... today} 18:17, 9 June 2024 (UTC)[reply]

Just Step Sideways and Qwerfjkl, there are two kinds of scripts, which make semi-automatic archiving easier. Page Wikipedia:One click archiving lists User:Evad37/OneClickArchiver as the most recent script for "One click archiving". My User:Andrybak/Archiver is the latest for "Multi-section archiving". —⁠andrybak (talk) 18:28, 9 June 2024 (UTC)[reply]

I didn't mean to disparaige your script,it works just fine, while currently, the Evad one does not. Just Step Sideways ^{from this world ..... today} 18:44, 9 June 2024 (UTC)[reply]

No disparagement taken. From Qwerfjkl's reply it might seem like User:andrybak/Archiver is a fork of User:Evad37/OneClickArchiver, but it's not. I just wanted to ensure there's no confusion about that. —⁠andrybak (talk) 18:49, 9 June 2024 (UTC)[reply]

Apologies, my mistake. — Qwerfjkl talk 19:30, 9 June 2024 (UTC)[reply]

It looks like Elli and FlightTime have recently worked on their copies of OCA. Are yours functioning in the new structure? Izno (talk) 21:00, 9 June 2024 (UTC)[reply]

Yep, mine works :) Elli (talk | contribs) 21:05, 9 June 2024 (UTC)[reply]

Elli, please consider adding your script to Wikipedia:One click archiving and Wikipedia:User scripts/List#Discussions 3. —⁠andrybak (talk) 21:57, 9 June 2024 (UTC)[reply]

I've now done so. Elli (talk | contribs) 22:07, 9 June 2024 (UTC)[reply]

@Just Step Sideways ^ Izno (talk) 22:06, 9 June 2024 (UTC)[reply]

Nice, just installed it works great. Thanks all. Just Step Sideways ^{from this world ..... today} 17:19, 10 June 2024 (UTC)[reply]

Neat! I came to VPT just to browse, and not even 10 sections in, I learned of a script that deals with the new header markup. Rusty4321 ^{talk contribs} 01:34, 14 June 2024 (UTC)[reply]

OneClickArchiver disappeared...Answers found here

Very handy gadget for manual-archiving - User:Evad37/OneClickArchiver.js - but it isn't showing up today on any talk pages for me. Don't know why, the script is still sitting on my common.js page. Has it been disabled/usurped by a better gadget? Why isn't it showing up?... Help please & thanks, Shearonink (talk) 14:48, 15 June 2024 (UTC)[reply]

Ok so after posting the above query I have now read through some of the other threads about archiver scripts... Is there a present script or fork that works on individual sections/posts/threads like Evad37's used to do? Shearonink (talk) 14:54, 15 June 2024 (UTC)[reply]

Forgot to add...I am editing with Vector 2010 original/legacy if that make a difference. Shearonink (talk) 14:57, 15 June 2024 (UTC)[reply]

For anyone who is as much of a non-adept at code & tech stuff around here and has Evad37's one-click oneclick one click archive script installed, and wants the same functionality, do the following:

go to the Wikipedia:One click archiving page.
navigate to Wikipedia:One click archiving#One click archiving (1CA) section.
See User:Elli/OneClickArchiver listed there? It is an updated 2024 script that is maintained and fixes some issues with Evad37's script (having to do with the 'Heading markup changes' mentioned at the top of this page.
Follow the instructions at the User:Elli/OneClickArchiver page.
Yay! You made it. - Shearonink (talk) 15:49, 15 June 2024 (UTC)[reply]

Broken template in Vector 2010

It would appear that these recent changes have broken Evad37's WP:Highlight duplicate links script in Vector 2010, which now no longer distinguishes between repeated links in the lead section and repeated links in the article body. ‑‑Neveselbert (talk · contribs · email) 18:20, 14 June 2024 (UTC)[reply]

Script works for me. What kind of skin are you using ? —TheDJ (talk • contribs) 18:41, 14 June 2024 (UTC)[reply]

Oh lol, it was in the title :) Anyway. works with vector 2010 for me. —TheDJ (talk • contribs) 18:42, 14 June 2024 (UTC)[reply]

This seems unrelated. Should be moved out to its own section. Nothing has changed in Vector 2010 skin. 🐸 Jdlrobson (talk) 20:01, 14 June 2024 (UTC)[reply]

@TheDJ and Jdlrobson: On Elizabeth II, using Vector 2010, the script highlights links in the lead section which shouldn't be highlighted, as they're not repeated in the lead section, and highlights links (in red) that are the first instances of those links in the article body. This does not occur in Vector 2022. ‑‑Neveselbert (talk · contribs · email) 22:49, 14 June 2024 (UTC)[reply]

This is indeed caused by mw:Heading HTML changes. I think this needs to be fixed in User:Evad37/duplinks-alt.js. It should be sufficient to replace this line:

if (this.nodeName.toLowerCase() == 'h2') {

with this:

if ( $(this).is('h2, .mw-heading2') ) {

(cc @Evad37) Matma Rex talk 08:46, 15 June 2024 (UTC)[reply]

I made an edit request: User talk:Evad37/duplinks-alt.js#Update for mw:Heading HTML changes Matma Rex talk 17:03, 18 June 2024 (UTC)[reply]

help desired

Real life has kept me away for the better part of a fortnight; I really shouldn't be taking the time to write this...

I have a script User:Trappist the monk/HarvErrors.js that is a tweaked copy of User:Ucucha/HarvErrors.js. Some of those tweaks were my own to turn down the glare of the red error messages that Ucucha's script produced. At some point someone asked me for further tweaks. What I know about javascript can be put in a thimble so I had to rely on the expertise of other more javascript fluent editors.

My script may have become broken because of the mw:Heading HTML changes. I suspect that the broken code is at lines 46–48. The code is supposed to make three separate lists of references found in each of an article's §External links, §Further reading, and §Publications sections. The purpose of that is to suppress the error messaging that would occur if any reference in those sections duplicates or can be linked from a short-form reference ({{sfn}} and the like).

With my script installed for example, this version of Rudolf Roessler (permalink) shows Harv error: linked from CITEREF... for every reference in (§Bibliography (permalink)). Those were 'fixed' by renaming §Publications to §Works (diff).

Is there anyone out there who would be willing to show me how to fix the issue? Because I'm not really here for the time being, a post on my talk page will find me via an email notification from MediaWiki.

Thank you.

—Trappist the monk (talk) 17:05, 19 June 2024 (UTC)[reply]

@Trappist the monk I'm not sure if I understand exactly what the script should do, however, I think it may be enough to add .mw-heading2 to the selectors in those 3 lines, like this:

		var further_reading = $content.find('#Further_reading').parent().nextUntil('h2, .mw-heading2').find('.citation').get();	// get all cites inside a Further reading section
		var external_links = $content.find('#External_links').parent().nextUntil('h2, .mw-heading2').find('.citation').get();		// get all cites inside a External links section
		var publications = $content.find('#Publications').parent().nextUntil('h2, .mw-heading2').find('.citation').get();			// get all cites inside a Publications section

Matma Rex talk 17:25, 19 June 2024 (UTC)[reply]

@Matma Rex: Ding! Ding! Ding! That works though I don't understand why it works. Thank you.

—Trappist the monk (talk) 13:56, 21 June 2024 (UTC)[reply]

The HTML nesting of headings changed recently. The fix done above is to check for both the old and the new selector (h2, .mw-heading2), until all skins are switched over in a couple weeks, at which point just the new selector can be used. –Novem Linguae (talk) 21:02, 21 June 2024 (UTC)[reply]

Thursday 13 June style changes

Update: The images problem was resolved on Tuesday 19th, the changed styling of infoboxes and hatnotes was reverted on Fri 14th

Infobox problems

I am not seeing infobox borders anymore (at Walter Cronkite and Google for example). Is that a "me" issue, or is something broken? (I am on Debian/Firefox, so it might very well be a "me"/specific issue.)

On Android (both app and Firefox) everything seems normal. JackTheSecond (talk) 19:08, 13 June 2024 (UTC)[reply]

Same here. Also, my search box now disappeared! Martinevans123 (talk) 19:13, 13 June 2024 (UTC)[reply]

In My Preferences, Vector legacy (2010) restores my search box, Vector (2022) removes it. Perhaps coincidental/ unrelated. Martinevans123 (talk) 20:44, 13 June 2024 (UTC)[reply]

Consider starting a new section for that. I have no idea what could be causing it. Izno (talk) 20:51, 13 June 2024 (UTC)[reply]

Done Have started a new thread. Thanks. Martinevans123 (talk) 21:10, 13 June 2024 (UTC)[reply]

The infoboxes look different for me as well, starting recently. But I'm not sure it's a technical problem, it could be a recently released change? Simeon (talk) 19:14, 13 June 2024 (UTC)[reply]

I have the same thing. On further investigation, it only affects me on Vector 2022 and not on any other skins. If it's a change to the skin, it's also broken some images in infoboxes and sidebars. The images seem to have either shrunk considerably at their default size, stopped loading or completely disappeared. Examples include: Next Senedd election, 2024 United States presidential election, Template:Donald Trump series, Template:Joe Biden series, Template:Keir Starmer sidebar, Template: Rishi Sunak sidebar, Template:Elon Musk series, etc. I remember a similar change to infoboxes was made a few months ago but dropped within a day or two. Can anyone at Wikimedia provide some clarification? ThatRandomGuy1 (talk) 19:16, 13 June 2024 (UTC)[reply]

Images are the same cause. I'll file a separate task for them since it's not obvious to me what the best resolution is for them. Izno (talk) 20:07, 13 June 2024 (UTC)[reply]

Ok, this one was caused by phab:T113101 and I've filed phab:T367463 for resolution. Izno (talk) 20:23, 13 June 2024 (UTC)[reply]

On Monobook, I'm finding that certain infobox images are showing smaller than usual. Images in {{Infobox station}}, for example, are appearing at 272px for me rather than the 340px that I normally see that at. I assume this is related to this issue? Pi.1415926535 (talk) 03:03, 14 June 2024 (UTC)[reply]

Pi.1415926535, please see subsection #Infobox thumbnail-sized images are a few pixels too small. —⁠andrybak (talk) 09:40, 14 June 2024 (UTC)[reply]

@Andrybak: I'm not sure if the issue I'm seeing is that - I'm on Monobook rather than Vector, and I'm seeing them at ~80% size rather than just a few percent smaller. Regardless, hopefully it'll be sorted out by one of these Phabricator threads. Pi.1415926535 (talk) 20:16, 14 June 2024 (UTC)[reply]

For disappearing images in {{ombox}}, subsection #Ombox images sometimes not showing has been created below. —⁠andrybak (talk) 09:40, 14 June 2024 (UTC)[reply]

Same here on Firefox/Windows11. Don't remember seeing any discussion about this change anywhere before now. --JackFromWisconsin (talk | contribs) 19:23, 13 June 2024 (UTC)[reply]

It's affecting me on Windows 10 as well. ThatRandomGuy1 (talk) 19:26, 13 June 2024 (UTC)[reply]

This happened yesterday on commons with Wikidata Infobox when using Vector-22 so it seems to be a Wikimedia change. Cakelot1 ☞️ talk 19:33, 13 June 2024 (UTC)[reply]

Did looking around and the infoboxes now look like they do on the Minerva skin, and the hatnotes on the top of the article also look like Minerva now. Not sure if this is intentional or not. --JackFromWisconsin (talk | contribs) 19:40, 13 June 2024 (UTC)[reply]

I'm not surprised this happened, I will poke the relevant task. And yes, the relevant task also caused the hatnote differences below. Izno (talk) 19:45, 13 June 2024 (UTC)[reply]

So, these were caused by the work in phab:T361573 and elsewhere. I've filed phab:T367462 for a resolution. Izno (talk) 20:01, 13 June 2024 (UTC)[reply]

Please have a look at the infobox on 2024 European Parliament election in Ireland to see another issue this has caused. Why was it even changed in the first place? Was there a strong consensus for this change? The new format is causing many more problems than the old one ever did. Please ping me in your reply. Helper201 (talk) 05:26, 14 June 2024 (UTC)[reply]

I have reported this specific problem at T367462 just in case it is a separate problem from the other problems in this section. – Jonesey95 (talk) 06:05, 14 June 2024 (UTC)[reply]

Thanks. You can see another issue in this - Next Australian federal election - infobox as well. Helper201 (talk) 06:33, 14 June 2024 (UTC)[reply]

And another - 2017 United Kingdom general election. Helper201 (talk) 08:31, 14 June 2024 (UTC)[reply]

The latest post on "phabricator" says "We can either inverse the media queries for those hatnotes/infobox.less for now. (only apply at lower resolutions), or revert." I don't have an account on this platform but my vote in 100% revert this infobox change and return to how things were on Wednesday 12 June. Helper201 (talk) 09:25, 14 June 2024 (UTC)[reply]

I've been seeing issues with {{Infobox film}} which I assume are a result of this change. If no image is used in the infobox, then the width is set so low that even average-length names get split across two lines (see Normal Love for an example). hinnk (talk) 09:58, 14 June 2024 (UTC)[reply]

Multi-column tables in infoboxes aligned badly

split from the section above for tracking purposes

This seems to have broken a lot of infoboxes. The career history of every association football player is a misaligned mess; see the screenshot I've attached for an example. It seems like this change needs to be reverted until it's more polished. –IagoQnsi (talk) 20:12, 13 June 2024 (UTC)[reply]

Consider that your specific example is also how it displays on mobile and you should consider how best to remedy that regardless. This just made the issue visible for desktop as well. There probably needs to be some work done on the template to support small resolutions. Izno (talk) 20:25, 13 June 2024 (UTC)[reply]

The footballers infoboxes look nasty now it's true. CNC (talk) 21:48, 13 June 2024 (UTC)[reply]

A four-column table should be four columns. Not four items placed at seemingly-random horizontal alignments. I checked, and the HTML has the data as a table with several rows and four cells per row. Now, HTML tables go right back to HTML 3.2 (27 years ago), and it's always been the case that tables having multiple rows and multiple columns are presented in such a way that each cell is the same width as the other cells in the same column. How can this have been screwed up so badly? It looks as if all of the cells in a row have been merged into one, with proportionate spacing between the items. --Redrose64 🌹 (talk) 22:19, 13 June 2024 (UTC)[reply]

We have a chicken-egg problem. The issue here is that the infobox is currently a table element. Using the table for this element is bad, as it is difficult to consistently make tables friendly on a mobile device. For mobile devices, we currently resort to using display: flex.

Hopefully this GIF demonstrates the problem we are talking about here and how it impacts our mobile users (please click):

Some wikis have successfully moved away from using a table for this reason. For example fr:Pic_de_Guadeloupe. English hasn't been able to move away from a table so easily, as many infoboxes like this example rely heavily on the status quo that it is a table.

The correct solution here would be to insert a table inside the relevant infobox section and not rely on the fact it will always be a table.

I've applied a change to Module:Infobox3cols to restore the old behaviour for now - but I hope we can agree this is not a long term solution. 🐸 Jdlrobson (talk) 01:28, 14 June 2024 (UTC)[reply]

Thanks. That fixed the column alignment. The infobox is still incredibly wide, much wider than it used to be and much wider than on Vector legacy, and there is also far too much vertical padding. I hope that fixes to the tickets tracked here will undo those changes. Also, it is not clear to me that French Wikipedia uses something other than tables for infoboxes. fr:Diego Maradona's infobox definitely uses a table for its infobox layout. fr:Pic_de_Guadeloupe, which does not use an infobox, also uses tables for layout of its taxobox, inside of div tags. – Jonesey95 (talk) 01:56, 14 June 2024 (UTC)[reply]

Sorry I should have clarified - French Wikipedia still has legacy infoboxes that they are trying to migrate away from. If you inspect the newer ones tend to come from newer infobox templates! 🐸 Jdlrobson (talk) 03:45, 14 June 2024 (UTC)[reply]

Links to examples of post-migration French infoboxes would be magnifique. – Jonesey95 (talk) 06:06, 14 June 2024 (UTC)[reply]

fr:Projet:Infobox/V3 is probably the best entry point! 🐸 Jdlrobson (talk) 16:06, 14 June 2024 (UTC)[reply]

Font size change

split from the section above for tracking purposes

For me, at least, the font size in infoboxes has changed to 90% of the default size instead of 88%, which it has been forever. In Vector 2010, the font size in infoboxes is still 88%. I am looking at John Dalton, for example. I have the (formerly default) "small" font size selected as my prose body font preference in the new radio-button switcher on the right-side toolbar. – Jonesey95 (talk) 19:50, 13 June 2024 (UTC)[reply]

Is the small size also related to the massive line spacing as well? Is that visible for everyone else? microbiologyMarcus ^{[petri dish·growths]} 20:09, 13 June 2024 (UTC)[reply]

Line spacing inside infoboxes? Yes, that would be this change. Line spacing outside? Probably worth a different section Izno (talk) 20:52, 13 June 2024 (UTC)[reply]

Dear MediaWiki designers, dividers can be either gaps or lines – there is absolutely no need to use both approaches together, as this consumes valuable space and adds visual noise at the same time without producing any benefits. — Mikhail Ryazanov (talk) 06:23, 14 June 2024 (UTC)[reply]

And why .infobox td has that damn padding in hard-coded pixels instead of font units?! — Mikhail Ryazanov (talk) 07:24, 14 June 2024 (UTC)[reply]

A font size change this minor can have a significant impact, as in Louisville, Kentucky, two of the image descriptions in the montage went from two to three lines. I may have to change to a combined description as a cleanup, unless, of course, the font size is reverted back. Stefen Tower_{s among the rest!} ^{Gab • Gruntwerk} 06:56, 14 June 2024 (UTC)[reply]

I just changed a couple images to make the descriptions go back to two lines. Image widths make a difference in this case. And it so happens I was able to select images that focused more on the entities they represent. Stefen Tower_{s among the rest!} ^{Gab • Gruntwerk} 15:54, 14 June 2024 (UTC)[reply]

You should t be relying on fontsize to begin with. Ever. —TheDJ (talk • contribs) 17:11, 14 June 2024 (UTC)[reply]

I'm not "relying on fontsize". I never set any font size involved here. I just want to ensure things display well given the typical display settings and relative sizes of things. If anything, I have made the display less brittle due to underlying font size changes. And that's the point. Stefen Tower_{s among the rest!} ^{Gab • Gruntwerk} 19:50, 14 June 2024 (UTC)[reply]

I've noticed a significant decrease in font size across all text, not just infoboxes, while using the Vector 2010 skin on my iPad since the style changes. Here's a screenshot for reference. @Jonesey95: do you know if this is a separate issue? Thanks, ‑‑Neveselbert (talk · contribs · email) 17:53, 14 June 2024 (UTC)[reply]

Unrelated. This issue only applied to Vector 2022 skin. 🐸 Jdlrobson (talk) 19:55, 14 June 2024 (UTC)[reply]

Biographical infoboxes

Biographical infoboxes suddenly got much larger! Anybody know what is going on? Hawkeye7 (discuss) 21:55, 13 June 2024 (UTC)[reply]

Hawkeye7, please see section #Infobox problems above. —⁠andrybak (talk) 21:58, 13 June 2024 (UTC)[reply]

Hatnotes have Minerva-style background color?

Look at the documentation for {{hatnote}} under Vector 2022. A WP:THURSDAY just happened; is there some change in MediaWiki that would've caused this? The CSS indicates that the change is intended to apply to any responsive skin. Aaron Liu (talk) 19:21, 13 June 2024 (UTC)[reply]

~~Is it possibly related this change to Module:Message box/fmbox.css? Oops, that was a month ago, but the class seems to be affected.~~ With a bit more digging, that change seems unrelated. Probably something in the MediaWiki code itself, probably related to dark mode changes. – Jonesey95 (talk) 19:38, 13 June 2024 (UTC)[reply]

I've made some notes above. Regarding specifically hatnotes, you should also consider participating in Module talk:Hatnote#Mobile styling, which I started some time ago. Izno (talk) 20:01, 13 June 2024 (UTC)[reply]

Not keen on the new look at all, this is something that should have been agreed. Also, the font on the hatnotes looks smaller than it used to, it was a slight strain to read it on my laptop... this seems like a MOS:ACCESS issue if nothing else - small text is a huge no no. — Amakuru (talk) 08:51, 14 June 2024 (UTC)[reply]

Infobox madness

OK, does anyone know what is going on with infoboxes right now? The formatting is all askew as of the past 10 minutes or so. Stefen Tower_{s among the rest!} ^{Gab • Gruntwerk} 22:04, 13 June 2024 (UTC)[reply]

Came here to raise similar concerns. We have articles like SS United States with two infoboxes tucked inside one another having extraordinarily wiiiiide boxes, to the point that articles are hard to read. I've seen broken infoboxes thinner than the current ones.

Yesterday, I was set to the old 2010 display settings. Who's screwing with the new vector display? GGOTCC (talk) 22:21, 13 June 2024 (UTC)[reply]

Annnnd it's fixed! Check Thursday 13 June style changes above for more info. GGOTCC (talk) 22:23, 13 June 2024 (UTC)[reply]

The pages I'm looking at are not fixed. I work on pages for Star Wars characters and have done a lot of work to get infobox items to stay on one line. Now they're wrapping to a second line. Wafflewombat (talk) 22:26, 13 June 2024 (UTC)[reply]

Yes, the worst of it has apparently been corrected, but I'm still seeing things out of whack. Stefen Tower_{s among the rest!} ^{Gab • Gruntwerk} 22:27, 13 June 2024 (UTC)[reply]

Definitely not fixed yet in Vector 2022. The borders are still missing, and there are new, unnecessary borders between the rows, with excessive vertical spacing. The font size is also still at 90% instead of 88%, which is wrong. – Jonesey95 (talk) 23:37, 13 June 2024 (UTC)[reply]

Are the borders suppose to be missing? When I first saw it, I thought the change was to improve ascetics. GGOTCC (talk) 00:29, 14 June 2024 (UTC)[reply]

Yes, this appears to be an issue with the Vector (2022) skin. Infoboxes look fine on the old Vector. Stefen Tower_{s among the rest!} ^{Gab • Gruntwerk} 22:25, 13 June 2024 (UTC)[reply]

Others on this page are wondering the same thing. Some infoboxes now have far less space for content, which messes everything up. Wafflewombat (talk) 22:23, 13 June 2024 (UTC)[reply]

If I may summarize the key problem I'm seeing at this point, it's when you have a tabular presentation within the infobox, the first column is hogging up too much width. Stefen Tower_{s among the rest!} ^{Gab • Gruntwerk} 22:45, 13 June 2024 (UTC)[reply]

Perhaps, although the infoboxes seem thinner altogether, like there is simply less room for text overall. Or perhaps the text is just bigger than it was before? For me, changing the skin to 2010 doesn't fix the issue. Wafflewombat (talk) 22:47, 13 June 2024 (UTC)[reply]

From what I'm seeing, that is the appearance because first columns (usually data descriptions) are being given lots of extra width at the expense of second columns (the data). Stefen Tower_{s among the rest!} ^{Gab • Gruntwerk} 23:15, 13 June 2024 (UTC)[reply]

Just my 2¢ I'm working on Præsidenten fra Nordvest and the infobox looks so strange with the width being the size of the image. It looks inconsistent with other films like Batman (1989 film) (which I presume the width maxes out when there's a line break in one of the cells). The new infoboxes look the same as mobile-view, so it feels like a mobilificiation. Do style changes like this have a consensus discussion before changing? Svampesky (talk) 23:11, 13 June 2024 (UTC)[reply]

Infobox thumbnail-sized images are a few pixels too small

FWIW, thumb-sized images now show slightly smaller than my chosen preference (300px) in infoboxes in Vector 2022. A normal thumbnail or frameless image shows as 300px, and the same image in Template:Infobox person (which defaults to the "frameless" image size option) shows as 295px.

https://en.wikipedia.org/w/index.php?title=User:Jonesey95/sandbox&oldid=1228927316

When I force the view to Vector legacy, both images are the same, correct, size. Vector 2022's style sheets do not appear to be respecting users' (or at least my) preferred image thumbnail size. Maybe it's just me. I entered the above info into T367462, but it might be a separate bug. – Jonesey95 (talk) 00:00, 14 June 2024 (UTC)[reply]

~~See Izno's message above about T367463. —⁠andrybak (talk) 00:09, 14 June 2024 (UTC)~~[reply]

These images are not minuscule; they are just a little smaller than they should be, about 1.5% too small. – Jonesey95 (talk) 06:03, 14 June 2024 (UTC)[reply]

My mistake. I've struck link to the incorrect ticket. —⁠andrybak (talk) 10:04, 14 June 2024 (UTC)[reply]

Other images (which are not in infoboxes) have also shrunk. The images in the {{Public art row}} template in List of public art in the London Borough of Ealing § Acton are now minuscule, but the portrait-format images in List of public art in the London Borough of Ealing § Ealing are the size they ought to be. Ham II (talk) 06:56, 14 June 2024 (UTC)[reply]

Take a look at Wikipedia:Top 25 Report or any other page in Category:Wikipedia Top 25 Report; all of them them have images set to 100px inside a wikitable, but the displayed images are much smaller than what it should be... Vestrian24Bio (TALK) 14:29, 14 June 2024 (UTC)[reply]

How do I get these style changes on my local MW install?

I just noticed the new look of the infobox and am wondering how I can get this to my local MediaWiki install. I've already used Special:Export with Template:Infobox and Module:Infobox with Include templates on, but the changes have not applied. Anything I've forgotten to import? A diehard editor (talk | edits) 00:48, 14 June 2024 (UTC)[reply]

A diehard editor, because it is WP:THURSDAY, these changes are caused by the latest deployment of a new version of MediaWiki, which is 1.43.0-wmf.9 (see Special:Version). These changes are considered to be a bug. It was reported to the bug tracker at phab:T367462 and phab:T367463. —⁠andrybak (talk) 01:04, 14 June 2024 (UTC)[reply]

Oh, so it's not supposed to be like this on desktop, and I should not bring them over? I'm still on 1.42. A diehard editor (talk | edits) 01:07, 14 June 2024 (UTC)[reply]

Infoboxes

Who and what changed the infoboxs to their new format in the last 24 or 48 hours? It’s causing issues I'd to let them know about. Where do I do this? Helper201 (talk) 05:21, 14 June 2024 (UTC)[reply]

This was a change to the MediaWiki code. Nobody at the English Wikipedia caused it. See above. – Jonesey95 (talk) 06:03, 14 June 2024 (UTC)[reply]

Jonesey95 can you please give me the link to the MediaWiki page where this decision came about or where on MediaWiki to present the issues this change has caused? Helper201 (talk) 06:17, 14 June 2024 (UTC)[reply]

Ombox images sometimes not showing

Screenshot illustrating the problem.

Screenshot illustrating what it should look like.

Seems like there is a problem with {{ombox}} where sometimes images are not showing up, see e.g. {{sockpuppet}}. Mz7 (talk) 06:28, 14 June 2024 (UTC)[reply]

That's phab:T367463. Vector 2022 is now being affected by the same issues which affected Minerva (mobile) and Timeless skins for a long time (phab:T282588). —⁠andrybak (talk) 09:36, 14 June 2024 (UTC)[reply]

{{tmbox}} got a workaround applied in Special:Diff/1228936760. —⁠andrybak (talk) 09:40, 14 June 2024 (UTC)[reply]

I've submitted a request to apply the same workaround to {{ombox}}. —⁠andrybak (talk) 10:42, 14 June 2024 (UTC)[reply]

Workaround has been applied. —⁠andrybak (talk) 19:35, 14 June 2024 (UTC)[reply]

@Andrybak: Thank you so much for your help on that! Mz7 (talk) 10:09, 15 June 2024 (UTC)[reply]

Infobox & Hatnotes

What just happened? Infoboxes and Hatnotes on Vector 2022 looks similar to that on Minerva... Is it any of my scripts or is it the new MediaWiki software causing these madness??? Vestrian24Bio (TALK) 07:37, 14 June 2024 (UTC)[reply]

How hatnote looks like in Minerva

How hatnote now looks like in Vector 2022

How hatnote should look like (Vector)

Added screenshots for reference. Vestrian24Bio (TALK) 08:46, 14 June 2024 (UTC)[reply]

@Vestrian24Bio, you started this subsection "Infobox & Hatnotes" of the big section #Thursday 13 June style changes. Please see other subsections for details about infoboxes and hatnotes. All issues highlighted in your screenshots are already being discussed there. —⁠andrybak (talk) 09:13, 14 June 2024 (UTC)[reply]

Got it. Thanks! Vestrian24Bio (TALK) 09:16, 14 June 2024 (UTC)[reply]

It's not the skin; it's the parser

Earlier this week, Wikimedia newsletter stated this week they are making changes to the HTML parser; even though it was supposed to only effect the citations, looks like its effecting other things as well.

I just tried breaking the parsing process and the images, hatnotes and even the infoboxes looked just like how they were yesterday and had none of these problems other than broken rendering. (Same for the Parsoid and Legacy as well) Vestrian24Bio (TALK) 14:47, 14 June 2024 (UTC)[reply]

Blue background for section hatlinks making them almost illegible

Combination of tiny font and pale blue background is making section hatlinks almost illegible and major eyestrain on my laptop. The text size does not increase with selecting larger text from the appearance menu. This combination with excessively small text in edit boxes is untenable. I am now spending too much time zooming in and out when I could be actually improving content. · · · Peter Southwood ^(talk): 12:37, 14 June 2024 (UTC)[reply]

Is this part of Wikipedia:Village_pump_(technical)#Thursday_13_June_style_changes above or something different? Can you provide a link to an example, if you are on mobile or desktop, your skin, and your viewport size? — xaosflux ^Talk 13:17, 14 June 2024 (UTC)[reply]

It is part of #Thursday 13 June style changes. Vestrian24Bio (TALK) 14:22, 14 June 2024 (UTC)[reply]

Friday message from the Web team

Hey everyone, this is the Web team working on skins. We wanted to explain the situation, apologize, and share what will happen next. Thank you all for reporting and helping us fix things.

This week, we released styling changes to hatnotes, templates, and images. Some of these changes were not intended for rollout this week. Our focus was mostly on "Images should be responsive in Vector and restrained to a max-size" (T113101) and related tasks. We apologize for introducing bugs and making editors confused.

We read concerns shared on different wikis and on Discord, and went over our options. We decided to revert all changes to templates and hatnotes for the time being, and keep the changes to images. Next, we'll review the changes to templates and hatnotes, and bring them for discussion one by one prior to proceeding. If you notice any remaining issues with images, please report them in comments to this Phabricator ticket. We hope to have a fix for the remaining issue on Monday.

Thank you! SGrabarczuk (WMF) (talk) 17:24, 14 June 2024 (UTC)[reply]

@SGrabarczuk (WMF) thanks for addressing us here! These changes seem massively consequential. Was the mistake the rollout of these changes or were these changes not supposed to be as broken as they were, i.e. it wasn't properly tested but the changes where rolled out as planned? microbiologyMarcus ^{[petri dish·growths]} 18:52, 14 June 2024 (UTC)[reply]

Hey @MicrobiologyMarcus. The former - the mistake was the rollout of changes to hatnotes and infoboxes (and maybe other templates too). We only wanted to roll out the changes to images. SGrabarczuk (WMF) (talk) 19:09, 14 June 2024 (UTC)[reply]

@SGrabarczuk (WMF) Hi! I liked the design for infoboxes that was changed, will it be coming back? Interestingedits (talk) 20:03, 14 June 2024 (UTC)[reply]

@Interestingedits: It had better not be coming back, see #Multi-column tables in infoboxes aligned badly. --Redrose64 🌹 (talk) 21:46, 14 June 2024 (UTC)[reply]

Seconded. It caused way too much damage. Some articles had infobox images going off into the border whilst others had them shrinking or seemingly disappearing. Plenty other issues also emerged. They should fix those issues caused by the redesign first before considering whether to bring it back as an actual feature. ThatRandomGuy1 (talk) 21:58, 14 June 2024 (UTC)[reply]

Just FYI, it is the same infobox design as in the Minerva (mobile) skin. Just an idea if you wanted to switch over. JackFromWisconsin (talk | contribs) 07:46, 15 June 2024 (UTC)[reply]

Hey @Interestingedits - yes, we would like to bring the main ideas of the design back in the future! The issue was that it got batched together with some other changes before it was fully tested and ready for release. To bring it back we would need to do a bit more testing of the design and discussing on here and other wikis to make sure we can adapt everything in time before proceeding with the change. OVasileva (WMF) (talk) 08:12, 17 June 2024 (UTC)[reply]

Hi! Looking forward to it. Is there a way to keep track of the tests/discussions? Would love to be apart of it! Interestingedits (talk) 00:03, 18 June 2024 (UTC)[reply]

These changes/discussions are being tracked in phab:T367519 Jon (WMF) (talk) 21:13, 18 June 2024 (UTC)[reply]

Thanks for the update and your work. For me, there was a bright side to these events: It pushed me to fix display issues in two infoboxes that will make them appear less clunky on mobile. Stefen Tower_{s among the rest!} ^{Gab • Gruntwerk} 20:10, 14 June 2024 (UTC)[reply]

Tuesday 19th update

The problem with images was resolved on Tuesday 19th, the changed styling of infoboxes and hatnotes was reverted on Fri 14th. —TheDJ (talk • contribs) 07:58, 19 June 2024 (UTC)[reply]

U.S. county infobox display issue

See Template talk:Infobox U.S. county#"Location within the state" map broken?. This is a map display problem seemingly discovered just today. Stefen Tower_{s among the rest!} ^{Gab • Gruntwerk} 23:29, 16 June 2024 (UTC)[reply]

FYI, This doesn't seem to be related to the CSS changes. File:Map of Texas highlighting Liberty County.svg is not displaying correctly for me. Are others seeing this? I am using Vector 2022, logged in or logged out, mobile and desktop view. It also does not display in Timeless or Vector legacy. – Jonesey95 (talk) 05:35, 17 June 2024 (UTC)[reply]

I possibly assumed too quickly this connected to the infobox formatting. The problem exists in the Commons version too. SVG processing error, or some problem at the Commons source? Stefen Tower_{s among the rest!} ^{Gab • Gruntwerk} 06:22, 17 June 2024 (UTC)[reply]

Rendering of US county SVG files has changed and fixed replacements must be uploaded at Commons. See Wikipedia:Teahouse#Infobox probelem and Wikipedia:Teahouse#Us couties on article map. PrimeHunter (talk) 09:35, 17 June 2024 (UTC)[reply]

SVG file not displaying correctly - Microsoft Edge

Hi, it looks like SVG files and their PNG preview versions are not displaying correctly in Microsoft Edge browser Version 126.0.2592.56 (64-bit). For example, Cabell County, West Virginia shows the red outline of the county but no background map of the state in the infobox picture. It has the same appearance if "reloaded in Internet Explorer mode". Tsarivan613 (talk) 14:10, 17 June 2024 (UTC)[reply]

I just submitted a bug report to Phabricator site. Tsarivan613 (talk) 14:20, 17 June 2024 (UTC)[reply]

It's a problem with the SVG files that was revealed by last week's software update (see #Tech News: 2024-24) – it's already filed as T367645. Matma Rex talk 14:33, 17 June 2024 (UTC)[reply]

I've filed a BRFA over on Commons to sort these. Mdann52 (talk) 17:46, 19 June 2024 (UTC)[reply]

Lots of problems with Quarry

There have been problems with Quarry query for days now (and I opened a phab ticket but no action so far) and now the bots I rely on issue reports that are all out of whack, coming hours after they are regularly scheduled to be issued. I'm wondering if there is a bigger problem going on here with the database and since my phab ticket had has little response, I thought I'd inquire here in case anyone had any answers. It's frustrating and it's been going on days now. Liz ^{Read! Talk!} 06:03, 17 June 2024 (UTC)[reply]

According to the ticket, SD0001 wrote a patch to try to fix it and got it deployed. Sadly it didn't completely fix things though and more work is needed. Seems like a tricky bug. –Novem Linguae (talk) 01:06, 18 June 2024 (UTC)[reply]

(Un)subscribe JS error [Gadget?] (and many warnings)

(Skin Monobook) Example from this page:

Wikipedia:Village_pump_(technical):984 This page is using the deprecated ResourceLoader module "mediawiki.ui.input".
[1.41] Please use Codex. See migration guidelines: https://www.mediawiki.org/wiki/Codex/Migrating_from_MediaWiki_UI
Wikipedia:Village_pump_(technical):984 This page is using the deprecated ResourceLoader module "mediawiki.ui.checkbox".
[1.41] Please use Codex. See migration guidelines: https://www.mediawiki.org/wiki/Codex/Migrating_from_MediaWiki_UI
Wikipedia:Village_pump_(technical):984 This page is using the deprecated ResourceLoader module "mediawiki.ui.button".
[1.41] Please use Codex. See migration guidelines: https://www.mediawiki.org/wiki/Codex/Migrating_from_MediaWiki_UI
(anonymous)	@	Wikipedia:Village_pump_(technical):984
Wikipedia:Village_pump_(technical):984 This page is using the deprecated ResourceLoader module "codex-search-styles".
[1.43] Use a CodexModule with codexComponents to set your specific components used: https://www.mediawiki.org/wiki/Codex#Using_a_limited_subset_of_components
(anonymous)	@	Wikipedia:Village_pump_(technical):984
startup.js:1307 This page is using the deprecated ResourceLoader module "jquery.ui".
Please use Codex instead.
2
log.js:79 Use of "addPortletLink" is deprecated. Use mw.util.addPortletLink instead
maybeLog	@	log.js:79
index.php?title=User…=text/javascript:67 Reflinks: Loading messages from cache @ 1718487515832
index.php?title=User…text/javascript:185 Promoting reFill 2
log.js:79 Use of "addPortletLink" is deprecated. Use mw.util.addPortletLink instead
maybeLog	@	log.js:79
startup.js:1307 This page is using the deprecated ResourceLoader module "mediawiki.ui".
[1.41] Please use Codex. See migration guidelines: https://www.mediawiki.org/wiki/Codex/Migrating_from_MediaWiki_UI
execute	@	startup.js:1307
ext.gadget.Navigatio…ps-script-0.js:2997 Uncaught 
TypeError: Cannot read properties of null (reading 'indexOf')
    at Title.namespaceId (ext.gadget.Navigatio…script-0.js:2997:22)
    at isInStrippableNamespace (ext.gadget.Navigatio…script-0.js:3220:18)
    at navlinkTag.getPrintFunction (ext.gadget.Navigatio…script-0.js:7580:48)
    at navlinkTag.html (ext.gadget.Navigatio…-script-0.js:7360:8)
    at navlinkStringToHTML (ext.gadget.Navigatio…script-0.js:7347:19)
    at pg.structures.menus.popupTopLinks (ext.gadget.Navigatio…script-0.js:1146:10)
    at pg.structures.shortmenus.popupTopLinks (ext.gadget.Navigatio…script-0.js:1160:30)
    at fillEmptySpans (ext.gadget.Navigatio…script-0.js:3876:12)
    at simplePopupContent (ext.gadget.Navigatio…s-script-0.js:365:3)
    at mouseOverWikiLink2 (ext.gadget.Navigatio…s-script-0.js:331:4)

Error does not seem to be 100% consistent, but I've had it on other pages too.

What is Codex? Were we asked about it?

All the best: Rich Farmbrough 10:59, 17 June 2024 (UTC).[reply]

Codex is "described" here. All the best: Rich Farmbrough 11:20, 17 June 2024 (UTC).[reply]

Most of that isn’t relevant, just warnings. The part that matters is:

ext.gadget.Navigatio…ps-script-0.js:2997 Uncaught TypeError: Cannot read properties of null (reading 'indexOf') at Title.namespaceId (ext.gadget.Navigatio…script-0.js:2997:22) at isInStrippableNamespace (ext.gadget.Navigatio…script-0.js:3220:18)

so it was an error when rendering a Navigation popups of a specific link that you were hovering. —TheDJ (talk • contribs) 21:32, 17 June 2024 (UTC)[reply]

Any console warnings that talk about "deprecation" mean that there are plans to delete support for that in the future, so folks are encouraged to update their code before that happens. But they don't result in any errors yet, just noisy warnings. So deprecation stuff can be ignored when debugging. –Novem Linguae (talk) 01:00, 18 June 2024 (UTC)[reply]

Many thanks for the replies.

I know what deprecation is.
I sometimes raise issues solely because they are a problem for me, though I would probably do so ref desk.
Generally I will raise issues here because they are issues for the wiki. These are such.

Breakdown of issues

Warnings are important, including deprecations. They are a designed to enable us to prevent things from breaking rather than letting them break then (maybe) fixing them.
We have a whole new JS component infrastructure. It may well be that most people are already aware of this, on the other hand it may not. If not this is a series socio-technical issue that needs addressing. Which is the case?
We need to have a program to remove these deprecated items before they are no longer supported, or, a campaign to undeprecate them. This pf course applies to other wikis. Is such in place?
There is an issue with a popular gadget. Someone willing and competent should look at this. If that someone is reading this great, if not who is it?

I've added a question to each issue (to try and move things forward), except the first, which is really a matter of maintenance philosophy, though I hope most people agree with it. Hope this makes the issues clearer.

All the best: Rich Farmbrough 08:55, 18 June 2024 (UTC).[reply]

MediaWiki:Actionthrottledtext triggered for non-bot account

Hi. Using this account (which is not automated, albeit new), I tried to make a major edit to this page. Request got blocked by MediaWiki:Actionthrottledtext. I tried again roughly 14 hours later : same error message. The Help Desk told me to publish this technical difficulty here. You can found my original message here.
I did try to make the same edit with an older account : got hit by the MediaWiki:Actionthrottledtext too.
Thanks in advance. Alpiiiiiine (talk) 14:42, 17 June 2024 (UTC)[reply]

The help desk and Teahouse has recently got several posts from users reporting this message. None of them were autoconfirmed. We didn't get such reports before so something has probably changed. PrimeHunter (talk) 21:56, 17 June 2024 (UTC)[reply]

That older account, which is autoconfirmed, is also hit by the same restriction, even after waiting for a day. It's @Erwan789. I really don't understand why both accounts are receiving that message is one is years older and autoconfirmed, and the other one isn't. Alpiiiiiine (talk) 08:47, 18 June 2024 (UTC)[reply]

User:Erwan789 is not autoconfirmed. It requires both four days and ten edits at the English Wikipedia. Erwan789 only has seven edits here. Special:CentralAuth/Erwan789 shows edits at other wikis but that doesn't count. PrimeHunter (talk) 11:46, 18 June 2024 (UTC)[reply]

Oh OK I got it now, thanks for explaining, that really helped me. Erwan789 (talk) 22:49, 18 June 2024 (UTC)[reply]

@Alpiiiiiine: I know this happened because of this situation, but please read the policy on multiple accounts, you really aren't supposed to be using more than one account at once without it being for at least one of the valid reasons, and even then the accounts should usually be linked – 2804:F14:80D0:4F01:ECC5:CFE4:210D:21A8 (talk) 19:00, 18 June 2024 (UTC)[reply]

Do not worry : I will delete the newly (and useless) account, thanks for reminding me to do so. Erwan789 (talk) 22:50, 18 June 2024 (UTC)[reply]

@Alpiiiiiine:/@Erwan789: Did you get a CAPTCHA with your "major edit", and if so how many times did it take for you to get it right? In any case, can you try one more time, from the Alpiiiiiine account, please? Suffusion of Yellow (talk) 23:09, 18 June 2024 (UTC)[reply]

I did get CAPTCHA for them, and I got them right on the first trim except for one.

I tried again, this time i got not CAPTCHA, just the error message. Erwan789 (talk) 08:00, 19 June 2024 (UTC)[reply]

That post was the tenth edit by User:Erwan789, meaning the account is now autoconfirmed. Can you test whether it still fails for Alpiiiiiine but now works for Erwan789? PrimeHunter (talk) 11:27, 19 June 2024 (UTC)[reply]

The edit was blocked on Alpiiiiiine, but it (finally) went through for this account! Erwan789 (talk) 11:41, 19 June 2024 (UTC)[reply]

Thanks for the information. It may help somebody (not me) who tries to track down the cause. PrimeHunter (talk) 12:43, 19 June 2024 (UTC)[reply]

Sorting problem

Why it's impossible to sort properly "Monthly net minimum wage (EUR)" in this list. Eurohunter (talk) 21:14, 17 June 2024 (UTC)[reply]

The documentation for sortable tables is at Help:Sortable tables —TheDJ (talk • contribs) 21:34, 17 June 2024 (UTC)[reply]

@Eurohunter: I have added data-sort-type="currency" to all wage columns [2]. They now ignore the currency symbol and sort the numbers in numerical order. If you want to sort by value then see Help:Sortable tables#Specifying a sort key for a cell. You could add data-sort-value="€..." | with an approximate € value to numbers not given in €. The data-sort-value is not shown to readers so the conversion doesn't have to be precise. PrimeHunter (talk) 22:10, 17 June 2024 (UTC)[reply]

@PrimeHunter: Thanks. Eurohunter (talk) 16:54, 18 June 2024 (UTC)[reply]

New York City locator maps in Slovenian?

It appears that the locator maps for places in New York City are being displayed with labels in what appears to be Slovenian or another Slavic language. For example, see the screenshot I just took of the locator map in the Radio City Music Hall article: Lincoln Square is "Linkoln Skver", Columbus Circle is "Kolambus Serkl", Hell's Kitchen is "Hels Kičen", South Central Manhattan is "Južni Srednji Menhetn", etc. —Bkell (talk) 21:59, 17 June 2024 (UTC)[reply]

See Wikipedia:Village pump (technical)/Archive 212#Serbian place names displayed on Manhattan maps. It's being worked on. PrimeHunter (talk) 22:12, 17 June 2024 (UTC)[reply]

The priority of one ticket, T230013, was recently moved from "Backlog" to "Later". A second ticket, T195318, looks like it might actually have a patch available, but it needs to be moved forward. – Jonesey95 (talk) 22:22, 17 June 2024 (UTC)[reply]

In Wikipedia, language translates you! RoySmith (talk) 14:30, 18 June 2024 (UTC)[reply]

I have a similar issue but with the '2022 Russian invasion of Ukraine.svg' image used in Russian invasion of Ukraine. It's only visible one the original file option. -- LCU ActivelyDisinterested «@» °∆t° 19:23, 19 June 2024 (UTC)[reply]

Tech News: 2024-25

MediaWiki message delivery 23:46, 17 June 2024 (UTC)[reply]

Morebits

Hi. I recently created the AlertAssistant user script. Would it be possible to make the two radio buttons appear on the same line and display the {{Contentious topics/log}} template? Also, would it be possible to not be warned by filter 602? Thanks. '''[[User:CanonNi]]''' (talk • contribs) 00:19, 19 June 2024 (UTC)[reply]

This is not directly supported by Morebits, but can be achieved by custom CSS modifications. – SD0001 (talk) 04:51, 20 June 2024 (UTC)[reply]

Saving settings

Whenever I attempt to save my settings (both on mobile and laptop) it instantly resets as soon as I leave the settings page, regardless of whether I have clicked save. Has anyone else experienced this? The main issue for me is the email settings and I am considering just removing my email address so I am not constantly receiving emails, however it does mean that if I forgot my password I will be locked out of my account. Any help would be greatly appreciated. Longhorncowfish (talk) 00:25, 19 June 2024 (UTC)[reply]

@Longhorncowfish The options at Special:Preferences#mw-prefsection-echo include having one email per week with all your notifications, and check boxes to specify what these notifications should include. Are you saying you can't save changes to that set of preferences? Mike Turnbull (talk) 21:24, 19 June 2024 (UTC)[reply]

Accessibility of map pushpin in infobox

Hello,

On this page, Glover-Archbold Park, I noticed the red dot signifying coordinates on the map in the infobox is quite hard to see. The background has a lot of lines, etc., that make it hard to identify where on the map the red dot is at a glance. Are there more accessible ways to portray this within infobox? Namely, a red dot on a green line seems like a colorblindness nightmare. Cheers, --Engineerchange (talk) 01:17, 19 June 2024 (UTC)[reply]

@Engineerchange: Template:Location map#Parameters has mark to change File:Red pog.svg, but Glover-Archbold Park uses {{Infobox NRHP}} which doesn't pass on mark so this method doesn't currently work here. There is no pretty way to do it. An ugly way is wrapping the whole infobox call in {{replace}} to change the file name but it would make it hard to edit the infobox in VisualEditor, and it could fail later if the infobox changes a detail in its output. I don't recommend such a hack for a minor change like this. You could try a request at Template talk:Infobox NRHP to pass on mark. PrimeHunter (talk) 11:12, 19 June 2024 (UTC)[reply]

"Talk:" page locked

cannot reply on Talk:Anthony Fauci
CHANGE: Anthony Fauci
FROM: His paternal grandparents, Antonino Fauci and Calogera Guardino, were from Sciacca
TO: His paternal grandparents, Antonino Fauci and Calogera Guardino, were from Sciacca, Sicily

98.248.161.240 (talk) 03:53, 19 June 2024 (UTC)[reply]

This edit was also requested at Wikipedia:Teahouse#"Talk:" page locked. This request was implemented by User:RudolfRed in this and this edit. LightNightLights (talk • contribs) 09:44, 19 June 2024 (UTC)[reply]

Heads-up: Diff colour

Hey everyone,

On the topic of accessibility: As you might know, the Wikimedia Foundation Web team is working on a night mode, which is currently available on mobile but continues to be developed. As part of the accessability work around this, the developers made some slight changes to the colour in the diff text, which will be visible on the wikis this week but didn't make it into Tech News until next week. You can read more in phab:T361717.

As part of the Tech News crew, I wanted to let you know since it didn't make it into this week's issue. /Johan (WMF) (talk) 15:07, 19 June 2024 (UTC)[reply]

Is having different colours between different modes such a hard thing to add? The colour look much worse now on the default/white mode and are too pale. Traumnovelle (talk) 10:17, 20 June 2024 (UTC)[reply]

I'm using the old Vector style, and I want to switch back to old diff colors. This is hurting my eyes...can someone help me with the css code needed? Jonatan Svensson Glad (talk) 11:56, 20 June 2024 (UTC)[reply]

I came here to ask the same, particularly the new yellow is painfully vivid due to light sensitivity. -- LCU ActivelyDisinterested «@» °∆t° 14:23, 20 June 2024 (UTC)[reply]

This should restore the old colors:

.diff-deletedline {
  border-color: #ffe49c;
}
.diff-addedline {
  border-color: #a3d3ff;
}
.diff-deletedline .diffchange,
.mw-diff-inline-deleted del, .mw-diff-inline-changed del, .mw-diff-inline-moved del {
  background: #ffebad;
}
.diff-addedline .diffchange,
.mw-diff-inline-added ins, .mw-diff-inline-changed ins, .mw-diff-inline-moved ins {
  background: #a3d3ff;
}

-- hgzh 14:31, 20 June 2024 (UTC)[reply]

Thanks hgzh that works perfectly. -- LCU ActivelyDisinterested «@» °∆t° 15:36, 20 June 2024 (UTC)[reply]

Before too many people copy this over to their user CSS, I strongly advise instead that you use the CSS I recommended in T361717#9910664 instead as diff HTML (and thus associated selectors) is not covered by the mw:Stable_interface_policy/Frontend. Jon (WMF) (talk) 16:21, 20 June 2024 (UTC)[reply]

I used the selectors because they work in all skins, while the changes to css variables will have no effect in timeless and monobook skin (don't know how many people are using these over here, in dewiki I think we have quite a lot of people that still use monobook and are not very keen on a changing interface). If you are only on Vector/Minerva skins, the variable override is better. hgzh 17:41, 20 June 2024 (UTC)[reply]

Ack. I forgot the old skins are not getting CSS variables right now. I'll update my comment with clearer advice by the end of the day. Thanks for pointing this out. Jon (WMF) (talk) 21:11, 20 June 2024 (UTC)[reply]

@Johan (WMF), Tech News is distributed to 700+ communities. So it is extremely weird (and a bit disheartening) to see WMF people inform only the English-speaking community if something was not relayed there.

(Though I am of the opinion that this strange diff colour change should not have been made at all, or should’ve been made with more care to keep the colours closer to the original.) stjn 16:32, 20 June 2024 (UTC)[reply]

Stjn: I absolutely understand that perspective, and this is not a substitute for a Tech News update – there will be a Tech News update – but I'd like to point out didn't only update the English-speaking community. I also posted on a mailing list for people who have signed up to spread technical information to their home communities. Where this quick update ended up doesn't reflect Foundation priorities, but language limitations – it's also been posted on Swedish Wikipedia, for example. Johan (WMF) (talk) 17:05, 20 June 2024 (UTC)[reply]

Thanks for that hgzh! I think two of the colors are slightly off. I think this will restore the original colors:

/* restore old diff colors */
.diff-deletedline {
  border-color: #FFE49C;
}
.diff-addedline {
  border-color: #A3D3FF;
}
.diff-deletedline .diffchange,
.mw-diff-inline-deleted del, .mw-diff-inline-changed del, .mw-diff-inline-moved del {
  background: #FEEEC8;
}
.diff-addedline .diffchange,
.mw-diff-inline-added ins, .mw-diff-inline-changed ins, .mw-diff-inline-moved ins {
  background: #D8ECFF;
}

I did try the CSS that Jon (WMF) linked, but sadly it did not work. –Novem Linguae (talk) 16:59, 20 June 2024 (UTC)[reply]

What should be the previous colors can be found at Special:Permalink/1228175150 (old version of Help:Diff). The hex color codes in Novem Linguae's version look accurate to me. —⁠andrybak (talk) 22:38, 20 June 2024 (UTC)[reply]

The hex colour codes are correct and normally work fine; however, when one is comparing a diff with highlighted text such as [13] the colours are more bold and vivid than before.

Diffs where text is not highlighted such as [14] appear fine however. Traumnovelle (talk) 00:20, 21 June 2024 (UTC)[reply]

Just wanted to remark that the colours are interfering with the ability to highlight text (for example, for copying and pasting)—the highlight can't be seen against the purple colour. — SGconlaw (talk) 02:33, 21 June 2024 (UTC)[reply]

The colours used when marking text for copy and paste are a feature of your browser and/or operating system, we have no control over them. There aren't even any CSS pseudo-classes, CSS background properties or CSS color properties that might provide any means of selection or setting. --Redrose64 🌹 (talk) 07:07, 21 June 2024 (UTC)[reply]

Pseudo-element ::selection applies styles to the part of a document that has been highlighted by the user (such as clicking and dragging the mouse across text). —⁠andrybak (talk) 09:51, 21 June 2024 (UTC)[reply]

@Novem Linguae: thanks for that version. It worked with my monobook. I was fearing I'd have to stop editing here, it was that bad. My eyes hurt and watered. -- Valjean (talk) (PING me) 22:12, 21 June 2024 (UTC)[reply]

Thanks for this. The new colors are awful and non-intuitive. Some1 (talk) 22:30, 21 June 2024 (UTC)[reply]

Our interface admin switched our wiki back to the old colors, but on m.wikipedia I'm still seeing the new low-contrast backgrounds (purple and ochre). So there must be something else that needs to be fixed. Form over function - rarely a good thing! Ponor (talk) 14:36, 22 June 2024 (UTC)[reply]

Why isn't that a setting in preferences? I already have problems with my head hurting lately, and high contrast on my computer or phone screen doesn't help. LilianaUwU ^{(talk / contributions)} 03:07, 21 June 2024 (UTC)[reply]

Speaking of which, there already is a gadget called "Display diffs with the old yellow-and-green colors and design". Time for another one? lol Nardog (talk) 03:15, 21 June 2024 (UTC)[reply]

I mean... why not. LilianaUwU ^{(talk / contributions)} 03:19, 21 June 2024 (UTC)[reply]

Or you can paste the old diff color CSS code that NL made to your Meta global.css page. Codename Noreste 🤔 Talk 19:50, 21 June 2024 (UTC)[reply]

Novem Linguae's version worked for me. -- Valjean (talk) (PING me) 22:13, 21 June 2024 (UTC)[reply]

This should be some type of setting one can easily toggle. -- Valjean (talk) (PING me) 22:15, 21 June 2024 (UTC)[reply]

New color for added text in diffs?

Is it just me, or has --background-color-content-added changed to a lilac #afb6e9 from the previous blue? The color contrast's awful now. Aaron Liu (talk) 17:39, 21 June 2024 (UTC)[reply]

see #Heads-up: Diff colour above. Nthep (talk) 17:49, 21 June 2024 (UTC)[reply]

Recent change to colors in "Difference between revisions" window?

When I look at the "Difference between revisions", the colors have been changed. When did this happen? It is now more difficult for me to read the text. The previous version worked fine. -- Valjean (talk) (PING me) 21:47, 21 June 2024 (UTC)[reply]

Wikipedia:Village_pump_(technical)#Heads-up:_Diff_colour -- GreenC 21:51, 21 June 2024 (UTC)[reply]

Thank you! I'll check it out. I hope it isn't a permanent change, as it's really disturbing to my eyes. -- Valjean (talk) (PING me) 21:57, 21 June 2024 (UTC)[reply]

Watched pages at Wikidata

Is this possible to see which pages are already in watch list on Wikidata while on page at ENWP? Is there any icon to show it? Eurohunter (talk) 20:32, 19 June 2024 (UTC)[reply]

@Eurohunter: I don't know a way to see on a Wikipedia page whether the Wikidata item for the page is on your watchlist at Wikidata. It's not what you asked for but in case you don't know this, you may be interested in the option "Show Wikidata edits in your watchlist" at Special:Preferences#mw-prefsection-watchlist. PrimeHunter (talk) 21:44, 19 June 2024 (UTC)[reply]

@PrimeHunter: Yes, I have it but all the time I visit page at ENWP I don't know if I watch it already in WD. Eurohunter (talk) 15:47, 20 June 2024 (UTC)[reply]

Line of text at top of user page or user talk page with statistics

In the past when I was on a user page or user talk page I would see a line of text near the top with the age of the account, number of edits and most recent edit date or something like that. It disappeared a while ago. I've tried some things but couldn't figure out to bring it back. What's the deal? SchreiberBike | ⌨ 21:07, 19 June 2024 (UTC)[reply]

@SchreiberBike: Are you sure it wasn't just displayed when you hovered over a link and had Navigation popups enabled? PrimeHunter (talk) 21:57, 19 June 2024 (UTC)[reply]

Nope. I even tried turning on Navigation popups, but that didn't bring it back. I remember reading about the trick to see that line of text at VPT many years ago and I think I copied some code to one of my code pages, but it stopped some time in the last month or so. I then deleted all the code from the code pages so I could move forward with a clean slate. Thanks for the idea though. SchreiberBike | ⌨ 22:07, 19 June 2024 (UTC)[reply]

@SchreiberBike: This would be User:PleaseStand/User info, which you attempted to disable two weeks ago (but probably broke instead, hence the subsequent edit). Please note that the  tags only work on HTML pages, they are not valid Javascript for which the comment syntax is /* ... */. --Redrose64 🌹 (talk) 22:18, 19 June 2024 (UTC)[reply]

@Redrose64: That did the job. Thank you for your help. SchreiberBike | ⌨ 22:35, 19 June 2024 (UTC)[reply]

I think this is the XTools gadget. Izno (talk) 22:14, 19 June 2024 (UTC)[reply]

@Izno: Nope, but that's interesting too. Thank you. SchreiberBike | ⌨ 22:39, 19 June 2024 (UTC)[reply]

Delay after editing pages found by insource search

I Wikignome IMDb errors using this insource search. Tonight, I corrected about a dozen articles based on the hits (see my contributions for details). Usually, if I repeat the search, the hits are gone as soon as I've made the relevant correction but this time they only disappeared slowly: the search is still giving six hits despite, in reality, the articles currently not having the issue searched for! Is this a known behaviour? Mike Turnbull (talk) 21:13, 19 June 2024 (UTC)[reply]

I sometimes see delays in search results, not specific to insource. The time stamp at the search result shows the searched revision but doesn't reveal if there is a newer revision. I assume any search will be based on the same revision until the search index is updated with a newer revision. Navigation popups shows how long ago a page was edited when you hover over a link. This time should always be up to date. PrimeHunter (talk) 21:53, 19 June 2024 (UTC)[reply]

Thanks, I thought I was cracking up! I do use navigation popups and can see the discrepancy in the times: there are still six hits as I write and the oldest is now ~ 2 hours out-of-date. Mike Turnbull (talk) 22:01, 19 June 2024 (UTC)[reply]

In case you don't know how a search index works: It's far too slow for the software to actually search every page when a user performs a search. For efficiency reasons, a search index is built, e.g. listing all pages with "imdbtitle" in the wikitext. This search index has to be updated every time a page is saved. I remember years ago when the search index of all pages was always only updated once a day, and some days skipped the update. PrimeHunter (talk) 22:13, 19 June 2024 (UTC)[reply]

Yes, over the years I've had experience with Db2 and Oracle for large scientific databases. I just hadn't noticed such latency here on Wikipedia before. Mike Turnbull (talk) 09:09, 20 June 2024 (UTC)[reply]

They recently introduced such a latency, it would take 10 mins to process. Sjoerd de Bruin (talk) 16:02, 20 June 2024 (UTC)[reply]

Bugs persisting after last week

Hello! Ever since the infobox bugs last week, I've been experiencing some issues. Just wanted to let you know.

The search bar at the top of the page disappears if I zoom in on the page too far. I usually read and edit WP zoomed-in, and this doesn't usually happen.
On Talk pages, the WikiProject headers have lost their icons.
When I'm in the visual editor and I click the number for an inline citation, the full citation pops up in a box like usual, but sometimes I am unable to click links in the citation.

Thanks! Wafflewombat (talk) 16:19, 20 June 2024 (UTC)[reply]

@Wafflewombat: Regarding no. 1: the search bar does not disappear, it collapses into a magnifying glass icon - try clicking that. No. 2 doesn't happen for me. --Redrose64 🌹 (talk) 18:27, 20 June 2024 (UTC)[reply]

Do you know if the search bar is supposed to collapse, or if the collapsing is a glitch? Wafflewombat (talk) 21:16, 20 June 2024 (UTC)[reply]

@Wafflewombat Re: 1 - If you zoom-in far enough using your browser's settings, the page will eventually switch into the layout that it uses for everyone if their browser-window is less than 1120pixels wide (which doesn't use the sticky header)

Re: 2 - It might help if you could link to an example page, and describe what icons you used to see at that example, but no longer see. E.g. I don't see any missing icons at Talk:Cat. (It might also help if you clear your browser cache with a hard-refresh, cf. WP:REFRESH.)

Re: 3 - Matma Rex has covered below. Quiddity (WMF) (talk) 01:10, 21 June 2024 (UTC)[reply]

I figured out the icons issue, but I still find the search bar issue strange, because it's disappearing at a zoom level that I always use, and it didn't disappear at that zoom level before. Not a big deal, though. I can live with it, if it's not a problem for anyone else. Wafflewombat (talk) 01:22, 21 June 2024 (UTC)[reply]

When I'm in the visual editor and I click the number for an inline citation, the full citation pops up in a box like usual, but sometimes I am unable to click links in the citation.

This is now filed as T368119. Matma Rex talk 01:09, 21 June 2024 (UTC)[reply]

Just a heads-up, this clicking problem in the VE is now happening with other buttons in addition to the inline citations. Wafflewombat (talk) 06:22, 21 June 2024 (UTC)[reply]

@Wafflewombat Hi, please could you describe which specific other buttons you are experiencing problems with? (I tried opening an article in VE and clicking random things, but everything else worked as expected.) Thanks. Quiddity (WMF) (talk) 17:39, 21 June 2024 (UTC)[reply]

Thanks for the message. The other buttons are working properly now, but the links within citations I mentioned above are still not functioning. Wafflewombat (talk) 17:48, 21 June 2024 (UTC)[reply]

Category:Wikipedia requested photographs of

This page, which redirects and seems completely redundant to Category:Wikipedia requested photographs, has been created three times since November 2023 (twice so far this month). The first two creations were misplaced userspace drafts. As I type, it's slowly being populated with talk pages, with the corresponding redirect link being left behind on each talk page. I've just switched it from a "hard" to a soft redirect in line with WP:R#CATEGORY.

Does anyone know why this category is continuing to be populated? Also, considering its recreations, has there been some kind of template documentation change somewhere on en.wiki which keeps leading users to this page?

I'm not sure the category must be deleted, but seeing as the category title is longer than the one it redirects to, keeping it seems rather pointless to me.

I'm in half a mind to just G6-delete and re-salt on account of the technical issues from the category population, but I'm intrigued... SuperMarioMan (Talk) 20:51, 20 June 2024 (UTC)[reply]

I am pretty sure this is due to |image-needed= not being set up correctly or there being something not quite working in Module:WikiProject banner. @MSGJ? Izno (talk) 20:58, 20 June 2024 (UTC)[reply]

~~Soft-redirecting appears to have stopped the category population.~~ When it was a hard redirect, the category seemed to be accumulating talk pages at a rate of ~10 a minute. SuperMarioMan (Talk) 21:10, 20 June 2024 (UTC)[reply]

Correction: the category is still populating, but more slowly. SuperMarioMan (Talk) 21:57, 20 June 2024 (UTC)[reply]

The code is in Module:WikiProject banner/auxiliary. I see it looks whether a category of the form Category:Wikipedia requested photographs of {{{topic}}} exists. If it does then it uses that category, otherwise it will use the default, which for biographies is Category:Wikipedia requested photographs of people. So creating Category:Wikipedia requested photographs of has actually caused this problem. But I obviously need to update the code so that a blank topic parameter will be considered. — Martin (MSGJ · talk) 22:34, 20 June 2024 (UTC)[reply]

I posted a similar query at the module's talk page. – Jonesey95 (talk) 23:09, 20 June 2024 (UTC)[reply]

I think that the main problem is that Category:Wikipedia requested photographs of got created - this occurred yesterday, and was done by The Sharpest Lives (talk · contribs). The code in Module:WikiProject banner/auxiliary relies on the non-existence of that category page. We may need to delete it, and then WP:NULLEDIT every page in the category. --Redrose64 🌹 (talk) 07:16, 21 June 2024 (UTC)[reply]

I assume it got created because it already contained some pages, which I don't understand. But anyway I have updated the module code so this should no longer happen — Martin (MSGJ · talk) 07:31, 21 June 2024 (UTC)[reply]

Apologies – I created the redirect because I noticed it was on Special:WantedPages with thousands of links. I thought that making the category a redirect would "move" the pages into the correct category, but I'm sure now that that's not how all this works. Sorry for any trouble. – The Sharpest Lives (💬•✏️•ℹ️) 12:53, 21 June 2024 (UTC)[reply]

@The Sharpest Lives: If a page uses mw:Help:Extension:ParserFunctions##ifexist then it causes an entry in WhatLinksHere for the tested page, and probably also counts in Special:WantedPages. A template may make thousands of ifexist checks of the same page. It doesn't imply somebody wants the page to exist, or that anything actually links to the page. PrimeHunter (talk) 15:42, 21 June 2024 (UTC)[reply]

A null edit isn't needed, a purge with forcelinkupdate works. Eventually the job queue should get around to doing that due to the module edit, but I don't know how long that might take or if there's job queue breakage of some sort at the moment. Anomie ⚔ 14:57, 21 June 2024 (UTC)[reply]

Mysterious alteration of anchor

Resolved

I made two edits, to Template:Citation Style documentation/title and to Template:Citation Style documentation/quote. The second one works to allow a link like Template:Cite web#csdoc_trans-quote, but the first one doesn't work - the link Template:Cite web#csdoc_trans-title fails. Checking the HTML emitted by Template:Cite web, I find that the intended anchor id="csdoc_trans-title" is being silently altered to id="csdoc_trans_title" but id="csdoc_trans-quote" is left as intended. Does anybody know why the behaviour differs? --Redrose64 🌹 (talk) 21:37, 20 June 2024 (UTC)[reply]

csdoc_trans_title appears in Template:Citation Style documentation/web, could that have something to do with it? That's the extent I have looked at it, haven't perused around the code. – 2804:F14:80D0:4F01:D5D6:530:F7B:3C2A (talk) 21:45, 20 June 2024 (UTC)[reply]

The markup in Template:Citation Style documentation/web is transcluded from Template:Citation Style documentation/title, and the third entry in the search provided shows the correct markup. --Redrose64 🌹 (talk) 21:56, 20 June 2024 (UTC)[reply]

Maybe I'm just misunderstanding things, but neither /web nor /title appear to transclude each other, they're both manually written, even if it's the same content. /web is trancluded in Template:Cite web... personally I would just have tested if changing it in /web and purging the cache fixed Template:Cite web#csdoc_trans-title, but I don't know the reasons for the id being what it is and am afraid of messing things up. – 2804:F14:80D0:4F01:D5D6:530:F7B:3C2A (talk) 22:07, 20 June 2024 (UTC)[reply]

@Redrose64: Eh, I didn't see how changing it could break anything, so I did change it(diff) - Template:Cite web#csdoc_trans-title now works. – 2804:F14:80D0:4F01:D5D6:530:F7B:3C2A (talk) 22:29, 20 June 2024 (UTC)[reply]

This sounds like a MediaWiki parsing error, and if I had a suspicion of cause it would have to do with title being a valid HTML attribute. Izno (talk) 21:56, 20 June 2024 (UTC)[reply]

On that basis, Template:Citation Style documentation/title#csdoc_trans-title would also fail, but it works. --Redrose64 🌹 (talk) 22:03, 20 June 2024 (UTC)[reply]

Both of the links you gave, Template:Cite web#csdoc_trans-quote and Template:Cite web#csdoc_trans-title, work for me. Matma Rex talk 23:29, 20 June 2024 (UTC)[reply]

I fixed #csdoc_trans-title, as I mentioned above. – 2804:F14:80D0:4F01:D5D6:530:F7B:3C2A (talk) 23:56, 20 June 2024 (UTC)[reply]

Thanks. It totally missed me that Template:Citation Style documentation/web did things its own way. Late evening and sleepy, I guess. --Redrose64 🌹 (talk) 07:09, 21 June 2024 (UTC)[reply]

Getting a list/count of values of a parameter.

(not real example). Template Infobox:Guinea Pig has a parameter called "Tail color". I'd like to be able to see what values this parameter has over all articles that use the infobox. (I asked on the help desk and got no response)Naraht (talk) 21:46, 20 June 2024 (UTC)[reply]

Bambots TemplateParam supports it for templates that have TemplateData. Izno (talk) 00:14, 21 June 2024 (UTC)[reply]

Any template that has a TemplateData section filled out in its documentation should also have a {{TemplateData header}} template. That header template contains a link to a report, generated monthly, of parameter usage. If the template you are interested in does not have a TemplateData section yet, one will have to be added. After that, the bot runs sometime around the 10th of each month and generates a report. – Jonesey95 (talk) 01:42, 21 June 2024 (UTC)[reply]

thank you both very much. While only running monthly, the Bambots TemplateParam for Infobox Fraternity is proving very useful at Wikipedia:WikiProject Fraternities and Sororities.Naraht (talk) 03:18, 22 June 2024 (UTC)[reply]

"updated since your last visit" stopped working on WP:RSN

The "updated since your last visit" feature (where that text is displayed next to revisions in the edit history) has stopped displaying for me on Wikipedia:Reliable sources/Noticeboard. It still works on other pages. I suspect the issue is the extraordinary size of Wikipedia:Reliable sources/Noticeboard, currently 1,051,395 bytes. Is this a known issue, that this feature fails on large pages? It is not overly pressing, as it seems some big discussions are going to be archived off that page soon, bringing the size back down. -sche (talk) 00:20, 21 June 2024 (UTC)[reply]

Ensure Preferences -> Gadgets -> Watchlist -> Subtle update marker is checked. Separately, ensure you're watching that page still. Izno (talk) 00:23, 21 June 2024 (UTC)[reply]

Thanks. I checked and I still have it enabled, and still have the page watchlisted. And now it's showing up for me on that page again. It had always continued showing up for me on e.g. WP:AN, even when it wasn't showing up on RSN. I guess it was a temporary glitch. (If it stops showing up again, I'll report back.) -sche (talk) 01:22, 21 June 2024 (UTC)[reply]

The time allocated for running scripts has expired

Hello, appear to get red messages of "The time allocated for running scripts has expired." As an example there is 3 messages at end of Bridlington and The Wolds (UK Parliament constituency). The page does not display the templates at the end of the article. I have tried a dummy edit on page to see if that will clear the problem. The page is OK when viewed in edit preview, wikitext editor. Keith D (talk) 12:26, 21 June 2024 (UTC)[reply]

A purge seemes to have fixed it. — xaosflux ^Talk 13:20, 21 June 2024 (UTC)[reply]

@Keith D: This has been affecting random pages at random times for some weeks, all you need to do is WP:PURGE. --Redrose64 🌹 (talk) 16:06, 21 June 2024 (UTC)[reply]

Blue rectangle when clicking images

The glitch in Firefox on the page Wikipedia:Community portal

The glitch is more easily visible after middle-clicking any image, i.e. any <img> tag, but it also appears on the left mouse button down. All images are affected, e.g. it's also visible when clicking on the image on any file page, like File:Example.jpg. I think this started appearing yesterday.

Reproduced both logged in and logged out. Only Vector 2022 is affected. Monobook and Legacy Vector (2010) are not affected.

The issue is more prominent in Firefox, where the blue rectangle intersects the image.

In Chromium, the blue rectangle follows the border of the image, however, the blue border in Chromium seems to be less visible for <img> tags of smaller size. E.g. lynx image in Template:In the news (currently on the Main Page) only shows the border at the bottom of the image. —⁠andrybak (talk) 09:51, 22 June 2024 (UTC)[reply]

Any clickable object has a hotspot, the area within which a click will fire the associated event (for example, for a link in running text the hotspot is the word or phrase enclosed by the link, and the event is the browser taking you to the link target). In Firefox, if you click a link in text, come back to the same page, and then press the Tab ↹ key, the next link in sequence will gain a blue border - this indicates the extent of the hotspot. I first noticed this some jobs ago, waaaay back in 1998, when my browser at work was Netscape 4, so it's not really a new feature. Clickable images also have a hotspot, which normally corresponds to the image outline, but when you tab into a clickable image in Firefox 127, for some reason it draws the blue border smaller than the true extent of the hotspot. I think that you're seeing this border. In the days before style sheets, this border appeared by default, even when you weren't tabbing between links, but could be suppressed by using the border=0 attribute on the <img /> tag. --Redrose64 🌹 (talk) 12:59, 22 June 2024 (UTC)[reply]

It appears that the "focus ring" is appearing around the bounds of the <a> tag, which has the width of the image but the height of the line. At a quick check I'm not seeing any MediaWiki-specific styles for the :focus-visible pseudo-class, and a test HTML page with no styles has the same behavior, so this is coming from the browser's default behavior. Anomie ⚔ 21:07, 22 June 2024 (UTC)[reply]

This is probably worth a bug report. Izno (talk) 16:09, 22 June 2024 (UTC)[reply]

Created phab:T368205. —⁠andrybak (talk) 20:06, 22 June 2024 (UTC)[reply]

I'm experiencing a this same issue, and another not mentioned by OP. When I visit a page with a non-existent talk page, the talk page link is blue. When I click to confirm that the talk page does not exist and go back to the previous page, the link becomes red. This started three or four days ago for me. Could this be related? ✗plicit 00:23, 23 June 2024 (UTC)[reply]

Can reproduce – most noticeable for file pages on Commons, which rarely have talk pages. This seems like a separate bug to me. —⁠andrybak (talk) 06:59, 23 June 2024 (UTC)[reply]

Citing Wikipedia Library sources

Not sure where to ask this but a few times I've tried to cite a source found through the Wikipedia Library but all I get is this rather than the article I'm citing from. See Niccolò Paganini and Manuel de Falla for examples. Is this a technical issue with the cite tool? Or am I doing something wrong? — Iadmc♫^talk 10:36, 22 June 2024 (UTC)[reply]

Well you should not be pasting in the url that you use for the Wikipedia library to the cite tool. The tool will be asked to logon and that will be why you get the wrong link. You can use the doi or other permanent link that the pages show. Or the url that would be used if not using Wikipedia library. I get close to 100% success with dois. Graeme Bartlett (talk) 12:16, 22 June 2024 (UTC)[reply]

Ah that could be it! Thanks I'll try that next time. — Iadmc♫^talk 12:45, 22 June 2024 (UTC)[reply]

Feverfew – A new link checker tool

Hello everyone, today I'd like to introduce a tool that I've just finished developing called Feverfew. This application is designed to check links within an article and determine whether they are working or broken.

The idea for Feverfew stems from Dispenser's Checklinks tool, which has been intermittently accessible via IP and is now unreachable since 2020. With Dispenser's absence, Checklinks has had reliability issues, prompting the development of Feverfew in hopes of reviving some of Checklinks' functionality.

You can access the tool at this website: https://feverfew.toolforge.org/, and learn how to use it by visiting: User:Plantaest/Feverfew.

While I acknowledge that InternetArchiveBot has done a commendable job archiving links, I believe a tool similar to Dispenser's Checklinks remains valuable for certain needs. Further perspectives on this can be explored in the "Feverfew and InternetArchiveBot" section.

I plan to add a feature for previewing web pages via iframe, though this may take some time.

This tool has been open-sourced on GitHub: feverfew repo. You can star it to show support if you have a GitHub account.

You can leave comments, give feedback, or report bugs about this tool on the following page: User talk:Plantaest/Feverfew; or directly here. Thank you very much :D

Plantaest (talk) 16:58, 22 June 2024 (UTC)[reply]

You might want to take a look at a similar tool I wrote a while ago at https://link-dispenser.toolforge.org :) Sohom (talk) 17:15, 22 June 2024 (UTC)[reply]

Is this an appropriate place to plug these tools? I assume they are free? — Iadmc♫^talk 17:17, 22 June 2024 (UTC)[reply]

toolforge:link-dispenser is free and hosted completely on toolforge. I think feverfew is also free, but uses AWS infrastructure (which has it's own downsides and upsides imho). Sohom (talk) 17:20, 22 June 2024 (UTC)[reply]

@Sohom Datta: Good tool. I wasn't aware of it, probably because I don't frequent enwiki. Initially, I hosted the entire Feverfew on Toolforge, but realized that Toolforge IPs could potentially be blocked if there were too many requests from this tool to websites. Therefore, I moved a small portion of the code to an AWS Lambda Function to take advantage of their extensive IP pool. Overall, this tool is free, as the cost for AWS Lambda Function is negligible (I still have quite a long time left on their free tier). Plantaest (talk) 17:35, 22 June 2024 (UTC)[reply]

@Plantaest AFAIK, a lot more URLs are blocked from AWS/GCP/Hetzner like cloud providers than smaller ones like Toolforge https://gitlab.wikimedia.org/toolforge-repos/link-dispenser/-/blob/main/blocked.json?ref_type=heads is the entire list for my tool (along with archive.org). Btw, maybe you could add a check for spammy links? Sohom (talk) 17:48, 22 June 2024 (UTC)[reply]

@Sohom Datta: I think what you're saying is possible, but in reality, I don't see the blocking situation; the tool still accesses archive.org. The purpose of hiding Toolforge IP addresses is to avoid impacting tools developed by other developers, as Toolforge is a shared server. Regarding the issue of spam links, I have another project to handle (Citron), but it's only for Vietnamese Wikipedia because I think this issue requires significant infrastructure resources to address, which is not suitable for a large wiki like English Wikipedia. Plantaest (talk) 17:58, 22 June 2024 (UTC)[reply]

Internet Archive Reference Explorer is similar. Early public release. One development feature, not in this release, is the ability to switch the dead link checker method - currently the IABot method, or the Wayback Machine method - to be able to compare results. Neither method use machine learning like Feverfew, would be interesting to compare. The version posted here is using the IABot method. -- GreenC 00:39, 23 June 2024 (UTC)[reply]

@GreenC: A good tool with a bright UI. I noticed that the Internet Archive Reference Explorer allows for PDF file analysis, so it is a larger-scale project compared to Feverfew. I will share my machine learning model method when I have time, although this model is not entirely accurate, and I am not an expert in machine learning. However, I think this could be helpful for those interested in this topic in developing a better model in the future. Plantaest (talk) 01:49, 23 June 2024 (UTC)[reply]

Connexion problems

I've had a few "Original error: upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport failure reason: delayed connect error: 111" errors tonight, also one or two "unable to load your Twinkle preferences". DuncanHill (talk) 22:45, 22 June 2024 (UTC)[reply]

Probably related to the ongoing outage. —⁠andrybak (talk) 22:51, 22 June 2024 (UTC)[reply]

I had the same error message repeatedly, when trying to go from the Main Page (which loaded fine), to the login page. Seems to be getting back to normal now. --Tryptofish (talk) 23:16, 22 June 2024 (UTC)[reply]

Category problems

Using the template "{{Month events in country category header}}" it does not always generate the three categories needed see Category:June 1943 events in Australia it has not generated Category:June 1943 events in Oceania; likewise for Category:June 1943 events in the United States it has not generated Category:June 1943 events in North America

Hugo999 (talk) 23:11, 22 June 2024 (UTC)[reply]

@Hugo999: Most templates aren't supposed to add non-existing categories. It uses mw:Help:Extension:ParserFunctions##ifexist to test whether the category exists and only adds it in that case. PrimeHunter (talk) 23:44, 22 June 2024 (UTC)[reply]