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 5 days.
This tends to solve most issues, including improper display of images, user-preferences not loading, and old versions of pages being shown.
No, we will not use JavaScript to set focus on the search box.
This would interfere with usability, accessibility, keyboard navigation and standard forms. See task 3864. There is an accesskey property on it (default to accesskey="f" in English). Logged-in users can enable the "Focus the cursor in the search bar on loading the Main Page" gadget in their preferences.
No, we will not add a spell-checker, or spell-checking bot.
You can use a web browser such as Firefox, which has a spell checker.
If you changed to another skin and cannot change back, use this link.
Alternatively, you can press Tab until the "Save" button is highlighted, and press Enter. Using Mozilla Firefox also seems to solve the problem.
If an image thumbnail is not showing, try purging its image description page.
If the image is from Wikimedia Commons, you might have to purge there too. If it doesn't work, try again before doing anything else. Some ad blockers, proxies, or firewalls block URLs containing /ad/ or ending in common executable suffixes. This can cause some images or articles to not appear.
When you attempt to create a double redirect you are shown a warning that includes a suggested fix (i.e. if Foo is a redirect to Bar and you attempt to create a redirect to Foo, MediaWiki shows a warning recommending you change the target of your new redirect to be Bar).
#TIL after an embarrassing amount of failing around and messing up syntax, that said warning doesn't apply to userspace. (i.e. creating User:Example/foo that redirects to User:Example/bar that's already a redirect to User:Example triggers no warning.) *sigh* Now I get to request user page deletions. FeRDNYC (talk) 20:41, 18 May 2025 (UTC)[reply]
See also links do not change with a subtopic name change
If there is a See also link in one article that read "[{See also|Radley_College#Rowing}]" and then the Rowing section had a name change to "Rowing Club", the See also link in the previous article breaks. This should be fixed. See also sections should look for name changes and adjust accordingly. NotQualified(talk)22:00, 14 May 2025 (UTC)[reply]
Broken anchors aren't fixed automatically and that can't be done because they can break for a variety of reasons. There's nothing magical about see also sections in the Wikipedia database. Graham87 (talk) 07:13, 15 May 2025 (UTC)[reply]
No. (not right now). They are also not unique, which is an additional challenge if you would ever want to do so (Think of repeating sub-sub-section names in an article for instance). —TheDJ (talk • contribs) 11:31, 15 May 2025 (UTC)[reply]
@NotQualified: By something that is anchor-able, do you mean content that could be given an anchor? Anchors are, in essence, the HTML id= attribute; and that attribute may be applied to all HTML elements (without exception). Since an HTML element of one type or another may be placed at any point in the content of a page, it follows that everything is anchorable. Such tagging would occur on every single edit, which would be impractical. --Redrose64 🌹 (talk) 21:00, 15 May 2025 (UTC)[reply]
Potentially, anything. Before I started to write this post, this section contained ten anchors. After saving, it will have eleven. --Redrose64 🌹 (talk) 21:54, 16 May 2025 (UTC)[reply]
Did the CSS just change on mobilein desktop view as seen on mobile? Page body text on my phone is a lot denser today. Chrome on a Galaxy phone. Largoplazo (talk) 14:59, 15 May 2025 (UTC)[reply]
Not on mobile, but on the usual Vector2022 view on a desktop I'm seeing text that appears a lot denser today as well. It's hard to tell because I don't have before and after screenshots, but my suspicion is that the leading (space between consecutive lines of text) has been reduced. I went into my custom css and increased the line-height (mine has a line ".vector-body {font-size: 115%; line-height: 150%;}" but you may not want such extreme values) and it looked a lot better again. —David Eppstein (talk) 18:28, 15 May 2025 (UTC)[reply]
Not sure if bigger... MonoBook here, and while I don't see that, I do see the pink box atop the editing window that - for instance - has the this-user-has-been-blocked-by-who-and-why looks to have larger text today. Or maybe it's always been this way and I'm losing my mind, that can't be ruled out? - The BushrangerOne ping only19:27, 15 May 2025 (UTC)[reply]
Aha. That would explain the larger text in the block notices. I also noticed the text in the box here looks odd (@Parsecboy: since I'm linking your page for an example!). And I'm going to guess that Wikimedia Commons got rolled out on Wednesday, which might explain the Metadata text looking bigger that I noticed there yesterday... - The BushrangerOne ping only22:48, 15 May 2025 (UTC)[reply]
and since it seems to be general for pink boxes, it also affects the pink box shown whn you visit the redlink of a deleted page. --Redrose64 🌹 (talk) 23:11, 16 May 2025 (UTC)[reply]
Are my eyes playing tricks on me, or ... is the font size in deletion summaries, such as the one posted at Yoshi Falls, bigger and/or has less space between lines than they previously did? And if so, was this intentional? (In case it is relevant, I'm using Vector legacy 2010.) Steel1943 (talk) 22:51, 16 May 2025 (UTC)[reply]
I removed it from Chrome checking whether any extensions were causing problems (it was bad memory). Replaced it and it no longer shows up in Tools. Windows 11. Than ks. Doug Wellertalk16:03, 15 May 2025 (UTC)[reply]
I didn't uninstall anything and it doesn't work for me either. I can see that it throws an error "TypeError: mw.Uri is not a constructor" in browser's (Firefox 138) console and doesn't load further. AstonishingTunesAdmirer➜16:21, 16 May 2025 (UTC)[reply]
Sorry about that! This is fixed in version 0.22.3, which is already live on the Firefox web store, and should go live on Chromium-based web stores soon. MusikAnimal (WMF) (talk) 22:47, 16 May 2025 (UTC)[reply]
I'm curious to know whether this module can be edited to format the team header to use Template:Diagonal_split_header or _2. When adding either template to an individual table using team_header={{diagonal split header 2|Home|Away}} the result only shows the class and style in plain text, presumably because the module creates the table using class="wikitable plainrowheaders"? StatmanIbrahimovic (talk) 18:24, 15 May 2025 (UTC)[reply]
@StatmanIbrahimovic:class="wikitable plainrowheaders" is unrelated. Special:ExpandTemplates can show the generated wikitext. It happens because the module adds scope="col" | with a pipe before team_header. {{diagonal split header}} includes cell formatting code which should be before a pipe so it adds its own pipe but everything just becomes cell content when there already is a pipe.
Updated to match(es) played on unknown. Source: [citation needed]
But don't do that. It's a bad hack. I don't know a good solution without modyfying the module to allow cell formatting by the caller. A pipe is needed somewhere after scope="col" so it wouldn't work to always omit the pipe. The normal solution is to add an extra optional parameter with code to insert before the pipe. PrimeHunter (talk) 08:14, 16 May 2025 (UTC)[reply]
Is that template accessible? Do screen readers read it correct with the entire table? If it doesn't work, then we shouldn't support it. Gonnym (talk) 16:48, 16 May 2025 (UTC)[reply]
invoke:cite causing harv and sfn no-target errors false positives
Neither of those 'fixes' should be pursued. The 'fix' is to fix Module:Footnotes so that it recognizes {{#invoke:Cite|xxxx|....}} and can then extract the necessary info from the invoke.
Editor Hike395 rewrote most of Module:Footnotes/anchor_id_list to the point where I no longer recognize the code so I am not the best person to say if what you have added was a good addition. I do notice that the 'template' names created from #invokes are not listed in template_list. Edit this version of my sandbox (don't change anything) and click Show preview. Then, in the Parser profiling data dropdown, click show under Lua logs. You should see something like this:
template_list=table#1{["Cite SSRN/new"]=1,["Template:Harvard citation no brackets/sandbox"]=1,}
In my sandbox page there are two {{#invoke:Cite|news|...}}. Change one of them to {{Cite news|...}}. Show preview; Show Lua logs. You should see something like this:
template_list=table#1{["Cite SSRN/new"]=1,["Cite news"]=1,["Template:Harvard citation no brackets/sandbox"]=1,}
The answer to Trappist's question is because the template_list variable is populated by template_list_add() here, and that function accepts the raw template string Module:Footnotes/anchor_id_list/sandbox#L-762 at line 762, not the hacked version produced by template_get_name Module:Footnotes/anchor_id_list/sandbox#L-762 at line 761. Is that right? It seems to me that template_list_add() at line 762 can be replaced by list_add(template_name, template_list). But I'm not 100% sure.
By the way, 95% of the code in Module:Footnotes/anchor_id_list is still Trappist's code. You can see my diff here. I changed the way the global variables were updated (for caching and to handle errors correctly), rewrote a little code for efficiency, handled "fascicles", and added citeref_patterns_make(), but that was it.
To answer Ahect's question -- I'm a bit nervous about turning all invokes into fake-o templates, because I don't know if that will generate any false positives or negatives. You may want to only turn {{#invoke:cite|XYZ}} into {{cite XYZ}}, because that seems safer and more predictable. — hike395 (talk) 02:54, 16 May 2025 (UTC)[reply]
@Hike395 My impression from the code is that template_params_get() only looked for named parameters, so it should automatically ignore lua function names, and similarly date_get() only looks for parameters starting with date=() (or an alias). sfnreg_get(), anchor_id_make_harvc(), and anchor_id_make_anchor() don't look at citation templates, so it doesn't matter there. The only other function that might potentially be impacted is template_list_add, which despite a comment saying that it handles case differently than template_params_get() is functionally identical as far as I can tell, so I just refactored it to use template_params_get()here. @Trappist the monk can correct me if my assumptions are wrong. --Ahecht (TALK PAGE)20:34, 18 May 2025 (UTC)[reply]
This version (permalink) of Gaza genocide directly precedes the edit that converted Module:Cite web and others to Module:Cite. Note that that §References section in that older version also has lots of harv errors. From that, I conclude that the change to Module:Citedid not cause any new problems. It appears that these errors began appearing 2025-05-03 at this edit (permalink). Since that time no one has bothered to notice or if they noticed, did not say anything. Of course, that harv error message is hidden so that might explain why the silence. No doubt, there are other articles where these sorts of error messages have not been noticed.
For those interested, Module:Cite web, Module:Cite news, and a few others are soon to be deleted so look now before their deletion prevents you from confirming what I have written.
The edit on the 3rd May marked the use of #invoke, so it seems to be #invoke that is causing the problem. As for not raising it earlier, I am sorry but I have a life. DuncanHill (talk) 21:45, 15 May 2025 (UTC)[reply]
A report at ANI (permalink) shows a troll with two external links in their signature. In this case, the links (which have been replaced) are apparently offensive but in general could be an attack on people who click the invisible external link. I can't find a report in Phab on this topic which makes me suspect I don't have the necessary skills so I'm hoping someone more familiar with that process will investigate and, if necessary, open a case. It's a shockingly bad weakness. Come to think of it, I believe this was reported many months ago in relation to how it could evade the black list. Johnuniq (talk) 11:28, 16 May 2025 (UTC)[reply]
@Matma Rex: I don’t think it’s really different per se, but it seems more insidious in this case as a signature link is the easiest way to get to a users user page or talk page, which were both spoofed in this case. It looks like the user intentionally hid the link using {{plainlink}} because the external link icon wasn’t present in his signature. Also, if using this method bypasses the blacklist, it makes the blacklist pointless to would be vandals. I can’t think of any legitimate reason an external URL would need to be in a signature to justify allowing them. cyberdog958Talk18:09, 16 May 2025 (UTC)[reply]
(edit conflict) It isn't, really, except that it violates WP:SIG#EL: Do not include links to external websites in your signature, which is both explicit and clear. ELs in sigs - whether to offensive websites or not - are a crime. --Redrose64 🌹 (talk) 18:10, 16 May 2025 (UTC)[reply]
Template-generated redlinked category on userspace page
But I can't justify going through the whole page to wrap all 145 invocations of the calculator template in {{suppress categories}} to make the redlink go away (both because that would be an excessive timesink and because it's a tracking category where userspace content isn't considered a problem), and I don't know how to figure out what the other problem is — so could somebody take a look at this and figure out how to fix whatever's causing the template to transclude a nonsense corruption of its tracking category? Thanks. Bearcat (talk) 15:33, 16 May 2025 (UTC)[reply]
Done. It's not the template's fault, it's that it's input was wrapped in a string replace op. I've just fixed that by suppressing categories for the problematic two uses. * Pppery *it has begun...15:38, 16 May 2025 (UTC)[reply]
Hi! I've been a regular patroller of CAT:MISSFILE for a number of years. In the past week or so, I've consistently noticed pages with missing images showing up in the category that aren't appearing as redlinks. The file names just appear as plain text, despite the image not appearing properly in the article. An example of this would be on this diff of Kladno Formation with Noeggerathia expansa.png. I always check the deletion history on Wikipedia, Commons and Wiki File Helper, but in all cases, no deletion history appears for these non-redlinked files despite that they aren't appearing properly in the article. I've noticed quite a few instances of this in the past week or so, but prior to that, any missing images in articles always appeared as redlinks. Is anyone aware of the technical reason for this change happening in the past week or two? Just asking so myself and the other patrollers of the category can have a better idea of the difference between those types of files and redlinked files. Cheers, KatnissMay the odds be ever in your favor ♥19:23, 16 May 2025 (UTC)[reply]
It appears that thumbs for missing files no longer display the file name in red. [[File:No such file.jpg]] produces File:No such file.jpg which is red for me. [[File:No such file.jpg|thumb]] produces the box to the right where I see the file name in black. PrimeHunter (talk) 08:16, 17 May 2025 (UTC)[reply]
Looks like it was probably I3846a15d4. Apparently someone overlooked that the .mw-file-element might be inside an a when doing more styling for dark more. Anomie⚔12:18, 17 May 2025 (UTC)[reply]
Ever since yesterday, when I use the desktop version on my mobile phone, the first item in my watchlist is a long column of text with 1-2 characters per line, and partially obscured by the "List of abbrevations" box. If you don't know what I mean, it's similar to how it looks on mobile with desktop view when discussions get too indented. Only happens when reading phone in portrait mode, not in landscape mode, I assume because there is more width available in landscape. The rest of the entries look normal, except maybe (not sure) the margin is wider than it used to be?
Is this something I just need to get used to, or is it something about to be fixed? Or am I the only person on the planet it is happening to? Is this somehow related to the "Font change in desktop view on mobile" thread above? Have I explained it so poorly that no one knows what I mean?
This is one of those things that's only a minor annoyance, except I see it every time I look at the watchlist, so the annoyance kind of accumulates after a while.... Floquenbeam (talk) 19:34, 16 May 2025 (UTC)[reply]
Seems unrelated to the other font changes. T331086 changed how line breaking of text works on the watchlist, and this seems to be an unintended consequence of that. I proposed a patch to improve it: [2]Matma Rextalk22:50, 16 May 2025 (UTC)[reply]
... and I guess the corollary is that maybe it would make sense to allow special pages to tell the skin (or vice versa, idk which way) whether they support mobile friendliness, as we work toward e.g. Vector being available as a 'mobile' skin rather than something which phones have to guess at what's important and what's not. Izno (talk) 05:24, 18 May 2025 (UTC)[reply]
The list of languages in the sidebar (I use legacy Vector 2010) seems to have disappeared, and been replaced by a single link to Wikidata. Testing it under the default V2022, it remains under the list of languages at the top. Why has this been changed for V2010? I deal with cross-wiki stuff all the time, and this is a huge productivity hit for me as it requires multiple steps and additional time to get to my destination. Please, how do I get the language list back again in the left sidebar? Mathglot (talk) 19:51, 16 May 2025 (UTC)[reply]
Quiddity, thanks for your reply. Your Example page works with the safe mode url suffix (and shows six languages in the sidebar) but it fails without the suffix. I hit Random article until I found three more pages with language links, they are: Ninzic languages, European turtle dove, and MILGEM project, and they all display [[Wikidata item]] under small-font heading, 'In other projects', and none of the individual languages. In each case, if I add ?useskin=vector&safemode=1 to the url, the language links in the sidebar come back again.
My most recent changes to commons.js was 4 April 2025 (and .css = 17 March). It occurred to me that perhaps one of the scripts I load may have changed recently, so I blanked my commons.js, bypassed my cache, and tried the three articles listed again, same thing: no links, but they come back in safemode. The only other thing that occurs to me, is that I believe there is a Preference setting somewhere to list my languages in the sidebar in English, not in the local language (i.e, I normally see: "German, French, Spanish", not "Deutsch, Français, Español"); should I hunt that down and disable that as well to see what happens? My common.js remains blanked for the moment. Mathglot (talk) 21:35, 16 May 2025 (UTC)[reply]
I have some clues: the languages are still there, but they are hidden, as if the list were toggled to 'hide'. It used to be, that when languages were listed, there was a down-pointing triangle and if you clicked it, it turned into a right-pointing triangle with the languages hidden. Now, the triangles act differently depending what browser you are on. Chrome, Vivaldi, Edge, Firefox, iOS desktop mode: no triangles at all, but if you click where the triangle ought to be, it toggles the list back and forth; Opera: down triangle is visible, right-pointing is invisible, toggling works if you click where it ought to be. There is also the question of why the language list got hidden in the first place, as I always keep them in 'show' mode. Mathglot (talk) 22:34, 16 May 2025 (UTC)[reply]
Is the toggle to hide/show a specific script you have? Mine have never done that, and on Ninzic languages I see the 3 interwikis displayed normally above the "Edit links" wikidata link. CMD (talk) 09:53, 17 May 2025 (UTC)[reply]
Hi, Chipmunkdavis. No, the behavior is the same even after I have blanked all my scripts, both in my common.js as well as global.js on meta. But the toggle behavior does go away at Ninzic languages in safemode. But are you sure you do not have that behavior? What happens when you click the header 'Language' above the language list, nothing? I'm not sure what it means that the language list toggling doesn't work in safe mode even though it does work in normal mode with all my scripts blanked. (I do not have a vector.js.) Sounds like I will have to try turning off gadgets next. Mathglot (talk) 03:26, 18 May 2025 (UTC)[reply]
I don't have an arrow, and there is nothing for me to click, it's just a h3 tag: <h3 id="p-lang-label" class="vector-menu-heading "><span class="vector-menu-heading-label">Languages</span></h3>. CMD (talk) 03:33, 18 May 2025 (UTC)[reply]
Found the culprit, finally: it is gadget 'Allow navigation menus to be collapsed', which I never would have suspected. Whew, what a pain! Now I can restore my js files. But, I still need to report a problem with that gadget not displaying the toggle triangles anymore, as it used to (see screenshot). Adding Quiddity, who may be curious to discover how it all shook out. (edit conflict) Mathglot (talk) 03:36, 18 May 2025 (UTC)[reply]
Nobody has an arrow (except Opera users); that is part of the problem, the triangle used to be there as in the image. I have the identical Html for the H3, but it is embedded in some code starting <nav id="p-lang" class="mw-portlet mw-portlet-lang vector-menu-portal portal vector-menu" aria-labelledby="p-lang-label"> which I suspect is the target of some js somewhere that does the show/hide operation. Mathglot (talk) 03:43, 18 May 2025 (UTC)[reply]
I have that wrapper too, presumably the arrow is coded within that separately. I also have a cogwheel with a link to Language settings not in the screenshot, so perhaps there were a couple of changes since that 2011 image was made. CMD (talk) 03:50, 18 May 2025 (UTC)[reply]
That gadget is basically ancient and based on a prototype version of Vector and so I would hesitate to call it maintained. Ignoring that, the arrow disappearing is due to an upstream skin change which now renders the triangles without loading separate images. I don't know which specific change it was and when I went to hunt I couldn't find it. I couldn't puzzle out a trivial change to fix another script with the same issue, User:Bradv/Scripts/ExpandDiffs.js (cc Bradv in case you're around or want to fix it when you are). (The spans that represent the triangles in question are still rendered in Bradv's script which means that script isn't dead to me, just looks kind of silly to click in white space.) Izno (talk) 05:12, 18 May 2025 (UTC)[reply]
Thanks, and that's what I was doing, too, namely clicking in the white space where the triangle isn't but ought to be. I discovered by accident that the whole 'Language' header adjacent to the missing triangle (a nongle? or is that a missing dongle?) is also clickable for hide/show but I don't know if that is an artifact of the missing triangle issue and will go away if that is fixed, or if it was always supposed to be clickable. Anyway, for the time being it is, and offers a bigger target. Will be interested what Bradv might have to say about the topic. Mathglot (talk) 07:41, 19 May 2025 (UTC)[reply]
I don't think it's that gadget ("SidebarTranslate"). I turned that gadget on, and set my skin to Vector2010, and the gadget works as expected on a regular pageview of Example. If the problem is not originating in your common.js, then I think it must be either another gadget, or one of the m:User:Mathglot/global.js userscripts. Try turning off various gadgets, or blanking your global.js. HTH. Quiddity (WMF) (talk) 22:36, 16 May 2025 (UTC)[reply]
Hi, can anyone tell me the link/ discussion thread for the patrol's new user page? As you can see below, there are two editor user pages with the "mark this page as patrol" tag. [3] and [4] . Thank you. Cassiopeiatalk23:46, 16 May 2025 (UTC)[reply]
The second page was deleted, so I can't comment on that. The first page was patrolled by you.
Andrybak} Thank you and I know. The second page I nominated for user name violation and that is the reason it was deleted. Stay safe and thank you. Cassiopeiatalk
Pages in any namespace can be patrolled, and the "Mark this page as patrolled" option is not new. You don't see it on mainspace pages because the Page curation toolbar hides it. Patrolling a page with this option is the same as marking it reviewed through the Page curation toolbar. The toolbar is easier to use and offers more features, which is why NPRs prefer that. You can mark userspace pages as patrolled, but we usually review only mainspace pages because patrolling other namespaces isn't necessary and is a waste of time. – DreamRimmer■16:28, 17 May 2025 (UTC)[reply]
DreamRimmer I have been patrolling for both NPR for many years and this is the first time I saw the in new user page. To me it doesn't make sense as we can mark patrol if all content added by the new user is adhere to the Wikipedia user page guidelines but we can guarantee the new user add something out the guidelines the next day or in the future. Thank you and stay safe. Cassiopeiatalk23:20, 17 May 2025 (UTC)[reply]
Patrol marking are about new pages, not about every revision, it is the same as new articles - if they get vandalized later they don't become unpatrolled. — xaosfluxTalk10:53, 20 May 2025 (UTC)[reply]
Immediately after this sentence, I want <references group="Names"/> to be displayed. However, this reference list is empty, and the footnote appears in Wikipedia:Manual of Style/Lead section#Special explanatory note instead of being displayed by itself(←primary goal) inside the table(←secondary goal).
@WhatamIdoing: The {{efn}} family of templates do accept a "group" parameter, but only with the specific values listed in the documentation. An arbitrary choice such as "Names" only gets you the default behaviour. -- John of Reading (talk) 07:42, 17 May 2025 (UTC)[reply]
@Alien333 Thanks for letting me know you could access it. That helped me figure out the issue. It turns out it was something on my end, not Gerrit's. Looks like it was a browser compatibility thing. Even after clearing the cache, it still wouldn’t work, but it loaded fine on other browsers like Firefox and Chrome for iOS. On my desktop I use Chrome, and apparently I was stuck on version 122.0.6261.129 because auto-updates weren’t working. I manually updated to version 136.0.7103.114, and now Gerrit works just fine. Dragoniez (talk)11:21, 17 May 2025 (UTC)[reply]
Now the section opens with the word "Show / Hide". This decision was justified at the dawn of the Internet 30 years ago, when HTML was version 1.0.
Now there are tags <details>, <summary>.
Probably, there are more beautiful solutions with an arrow (left, down).
In Wiki there are enough arrows as it is, even this topic, which I opened, has arrow (on mobile). But at the top of the page, the main sections are still opened using «Show/Hide». Seregadu (talk) 19:55, 17 May 2025 (UTC)[reply]
It would be a massive amount of work to transition literally every use of mw-collapsible, and that's even ignoring that I have had to yank teeth and still haven't 'won' the yanking to get these whitelisted. See phab:T25932 for the general discussion (and teeth yanking) and phab:T31118 for the specific. Izno (talk) 05:18, 18 May 2025 (UTC)[reply]
But then there is also no effective benefit to it. Additionally, mw-collapsible does more than what details/summary can do, so no matter what, you have to do both, in which case the original mw-collapsible is more maintainable. —TheDJ (talk • contribs) 19:23, 18 May 2025 (UTC)[reply]
I can’t analyze the page in DevTools, in terms of external scripts (it’s easier to look at clean code). But I will assume that the old implementation from the 2000s (as now) Show/Hide with (addEventListener("click", (event) => { })) is much more complex than the modern <details>, <summary>.
Sorry! This site is experiencing technical difficulties.
Try waiting a few minutes and reloading.
(Cannot access the database: Cannot access the database: Database servers in extension1 are overloaded. In order to protect application servers, the circuit breaking to databases of this section have been activated. Please try again a few seconds.)
It would be good for new, and dormant but returning editors (two groups) to have the notice as they may not be aware that they have to modify their blocking tools (extensions, firewall, etc) that they may have to allow requests to the auth domain. The first can be easily settled with assuming that new editors are not auto-confirmed editors and use the CSS class to show the text to them, the second group is harder without enabling some form of last login tracking.
At the very least, the wording of the notice can be tweaked or simplified given that the enhancement is no longer 'recent' (2 months or more ago?), i.e. "All logins are processed on auth.wikimedia.org. If you are using blocking software, you will need to allow access to this domain to log in. (technical details)" – robertsky (talk) 05:34, 18 May 2025 (UTC)[reply]
This message appears before you log in, so you can't know whether the account they are going to log in to is new. And even if you could CSS classes like "autoconfirmed-show" don't work on the login page. * Pppery *it has begun...13:46, 18 May 2025 (UTC)[reply]
In theory sessions can last for up to a year if you select the "remember me" option. So it seems likely that there are active editors who're going to log in using the new workflow for the first time in about 10 months' time. taavi (talk!) 15:26, 18 May 2025 (UTC)[reply]
To explain a little more, the English Wiipedia is part of a unified login system for around 1000 wikis run by the Wikimedia Foundation. Most user groups are local and only apply to one wiki where they are assigned and listed. The steward group is global and applies to all wikis. It is only assigned and listed at the central Meta wiki. It's admittedly confusing that Special:Statistics says Stewards 0. Maybe it should be explained in MediaWiki:Statistics-footer. PrimeHunter (talk) 09:39, 19 May 2025 (UTC)[reply]
For some time now, since the introduction of the dark-mode skin, this is how navboxes like Template:Seinfeld episodes appear in Vector 2022 when using dark mode.
(I've applied various tools and hand-edits to inline all of the styles and remove all CSS classes and element IDs, such that this should appear the same regardless what skin you're using, or what color-mode (if applicable). The only thing I can't control is the link coloring, since there's no way to inline-style a wikilink.)
This appears to simply be a mistake in the dark-mode CSS. One of the applicable rules — I'm not sure exactly where it comes from, but it's loaded with the page according to ny browser's development tools — is this one (warning: brain-melting CSS ahead)...
Why were odd-numbered navbox rows left out of the dark-mode border styling?
but also, perhaps even more fundamentally,
Why is dark-mode implemented like this, as a set of forced (!important, ugh), centralized style overrides?
Why were the applicable navbox TemplateStyles (Module:Navbox/styles.css) not updated with dark-mode support, either instead of or in addition to the central changes?
Why do we even bother with TemplateStyles when the skin is going to force them to be ignored?
Triple batch of questions is probably best answered as "WMF wanted to get things done at 900 wiki scale" and no real other reason. We can take these styles upon ourselves when phab:T365330 is done and then applying mw:Extension:WikimediaMessages#Site admin helper to the corresponding navbox-dark option. (Doing it before that task is done requires you or anyone else to work on the night mode related items at MediaWiki talk:Common.css/to do, though that may or may not be up to date in so far as there may be more to sort out.)
I can't explain why navbox-odd was forgotten. You could submit a patch upstream if you want. I haven't bothered because when the Phab ticket is done we can fix it directly ourselves, and it's not seriously impeding anything. It's a double thickness line of a slightly wrong color, but obscures no text from a contrast perspective, which was the priority. Izno (talk) 22:43, 18 May 2025 (UTC)[reply]
We at Wiki Project Med have been working on decreasing bandwidth usage since this was raised as a significant concern during the last discussion. We have succeeded in dropping usage from 36 Mb down to 498KB. See MDWiki:WikiProjectMed:OWID
The scrolling is honestly is somehow more confusing than before. Scrolling on the image (where my cursor is most likely positioned after clicking the images) moves, not the scrollbar, but a slider off screen, making me wonder what is going on. The initial concerns about unselectable text have also not bee addressed. This still feels a bit half-baked and probably needs more iteration before being considered as a default-on template gadget. Sohom (talk) 04:41, 21 May 2025 (UTC)[reply]
The latest run of Special:WantedCategories once again features two redlinks being autogenerated by modules I can't edit, which I can't figure out what to do with:
Category:Sweden by county category navigation with 6–15 links, autogenerated by the use of {{Sweden by county category navigation}} on various Swedish "by county" categories. While I can find evidence that this template generates numerous other categories tracking grey links, including the already-existing Category:Sweden by county category navigation with 6–15 grey links, I can't find any evidence of any other categories existing for any other number of just plain "links" without the "grey" modifier — so I can't figure out why this exists for the 6-15 range, but not for any other number, and thus can't create it if it isn't expected and doesn't have any other siblings. So could somebody with module-editing privileges figure out how to make it go away?
Category:Pages using old style mw-ui-constructive, autogenerated by the use of {{Clickable button/sandbox}} on various userspace pages. I could probably just wrap the template invocations in {{suppress categories}}, but I note that these invocations aren't new ones — they've all been on the pages for a long time without ever generating this category until now, meaning the category results from a new module edit within the past couple of days, and thus possibly could recur in the future if it isn't addressed some other way. So if this is a tracking category we would want, then could somebody who knows what they're doing create it — and if it isn't desired, then again, I need somebody with module-editing privileges to make it go away.
Never mind on the Sweden one, it turns out I was able to clear that out just by null-editing it, because it was just one of those "category not actually on the pages despite nominally appearing to have pages in it, because it had already been corrected but failed to purge" things. Bearcat (talk) 14:36, 19 May 2025 (UTC)[reply]
I remember seeing a template that let me combine two images into one placement. Anyone remember what that template is named?
Also, I have a bunch of templates on my user page that put images down the left edge of the page. If I want to put them horizontally is there an easy way to do it?
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
The Editing Team and the Machine Learning Team are working on a new check for newcomers: Peacock check. Using a prediction model, this check will encourage editors to improve the tone of their edits, using artificial intelligence. We invite volunteers to review the first version of the Peacock language model for the following languages: Arabic, Spanish, Portuguese, English, and Japanese. Users from these wikis interested in reviewing this model are invited to sign up at MediaWiki.org. The deadline to sign up is on May 23, which will be the start date of the test.
Updates for editors
From May 20, 2025, oversighters and checkusers will need to have their accounts secured with two-factor authentication (2FA) to be able to use their advanced rights. All users who belong to these two groups and do not have 2FA enabled have been informed. In the future, this requirement may be extended to other users with advanced rights. Learn more.
Multiblocks will begin mass deployment by the end of the month: all non-Wikipedia projects plus Catalan Wikipedia will adopt Multiblocks in the week of May 26, while all other Wikipedias will adopt it in the week of June 2. Please contact the team if you have concerns. Administrators can test the new user interface now on your own wiki by browsing to Special:Block?usecodex=1, and can test the full multiblocks functionality on testwiki. Multiblocks is the feature that makes it possible for administrators to impose different types of blocks on the same user at the same time. See the help page for more information. [5]
Later this week, the Special:SpecialPages listing of almost all special pages will be updated with a new design. This page has been redesigned to improve the user experience in a few ways, including: The ability to search for names and aliases of the special pages, sorting, more visible marking of restricted special pages, and a more mobile-friendly look. The new version can be previewed at Beta Cluster now, and feedback shared in the task. [6]
The Chart extension is being enabled on more wikis. For a detailed list of when the extension will be enabled on your wiki, please read the deployment timeline.
Wikifunctions will be deployed on May 27 on five Wiktionaries: Hausa, Igbo, Bengali, Malayalam, and Dhivehi/Maldivian. This is the second batch of deployment planned for the project. After deployment, the projects will be able to call functions from Wikifunctions and integrate them in their pages. A function is something that takes one or more inputs and transforms them into a desired output, such as adding up two numbers, converting miles into metres, calculating how much time has passed since an event, or declining a word into a case. Wikifunctions will allow users to do that through a simple call of a stable and global function, rather than via a local template.
Later this week, the Wikimedia Foundation will publish a hub for experiments. This is to showcase and get user feedback on product experiments. The experiments help the Wikimedia movement understand new users, how they interact with the internet and how it could affect the Wikimedia movement. Some examples are generated video, the Wikipedia Roblox speedrun game and the Discord bot.
View all 29 community-submitted tasks that were resolved last week. For example, there was a bug with creating an account using the API, which has now been fixed. [7]
Updates for technical contributors
Gadgets and user scripts that interact with Special:Block may need to be updated to work with the new manage blocks interface. Please review the developer guide for more information. If you need help or are unable to adapt your script to the new interface, please let the team know on the talk page. [8]
The mw.title object allows you to get information about a specific wiki page in the Lua programming language. Starting this week, a new property will be added to the object, named isDisambiguationPage. This property allows you to check if a page is a disambiguation page, without the need to write a custom function. [9]
User script developers can use a new reverse proxy tool to load javascript and css from gitlab.wikimedia.org with mw.loader.load. The tool's author hopes this will enable collaborative development workflows for user scripts including linting, unit tests, code generation, and code review on gitlab.wikimedia.org without a separate copy-and-paste step to publish scripts to a Wikimedia wiki for integration and acceptance testing. See Tool:Gitlab-content on Wikitech for more information.
The 12th edition of Wiki Workshop 2025, a forum that brings together researchers that explore all aspects of Wikimedia projects, will be held virtually on 21-22 May. Researchers can register now.
Hey, can you please ask an admin to fix the internal error with the RTS games list page?
Whenever I try to make a new small edit, this small error message always comes up after clicking to the next preview window in my mobile Wikipedia app on android phone.
It says:
"{"status":500,"type":"Internal error"}".
What is it? Is it a database upload problem with the page?
I don't use a VPN on phone.
Later on, someone suggested to me to edit and preview the page in a desktop PC browser. I did that and it worked. I haven't tested it in a mobile browser on the phone (but they should work the same way as the desktop PC browsers).
Recently, I'm noticing this different error message on the same page:
"{"status":413,"type":"Internal error"}".
I read about that online and it points to the payload data being too big for the server to handle. Can you fix these problems?
I'm also posting this topic here in a mobile browser (not the Wikipedia app) on my phone because the app didn't recognise me as logged in on this page. ObiKKa (talk) 23:31, 19 May 2025 (UTC)[reply]
This site shows geolocation data as well as proxy/VPN detection, whois, ISP/ASN, and abuse contacts all in one. It has no usage restrictions either. disclaimer: I'm the developer of the site in question Tally-IPLocate (talk) 09:57, 20 May 2025 (UTC)[reply]
Following the creation of a module grabbing specific specific data from Wikidata, I am in the process of ensuring its use "as is" across several wikis (to make it easier to maintain), and this requires adapting it to other wikis' local implementation of the {{Wikidata}} template.
For now, I have managed to do this for Portuguese (where the Wikidata module is more or less the same as here) and French (where it is noticeably different) -- see the current translation roadmap. But this is a lot of work and, in the case of the French version, it still results in some functionalities not working, which is disappointing.
@Trappist the monk, who has kindly provided very useful support for this project for some time, opined that it would be more efficient to develop an own implementation of calls to Wikidata, to make this language/wiki-independent. I still tried the other way because it seemed easier, but, now that the limitations appear more clearly, I think this is probably a better solution.
Hi everyone! I'm writing on behalf of the Web team. Over the past year, the team has been exploring ways to improve browsing for readers. We want to increase reader retention and create pathways for deepening reader connections with the wikis. We would like readers to use the wikis more frequently and potentially set towards the path of editing.
One of our experiments was to provide suggestions in the empty state of the search bar for logged-out users. The goal was to show suggestions to those who show interest in spending time on Wikipedia (by opening the search bar). We performed two experiments - showing the feature in a browser extension on desktop, and showing some readers the feature via an A/B test on mobile. It turned out that engagement with this feature is high when compared to other suggestion features, and readers who use the feature tend to read more articles overall. For more details, please check out the project page.
The next step is to make this feature available across wikis. We will begin rolling out the feature over the next month and a half. Catalan, Hebrew, and Italian Wikipedias, as well as a number of sister projects will see the change on desktop between May 21 and June 4, and on mobile June 4 and June 15. All other Wikipedias will see the change on desktop between June 4 and June 15, and on mobile – between June 15 and June 30. EBlackorby-WMF (talk) 18:55, 21 May 2025 (UTC)[reply]
I had raised this exact same issue on the Module talk:Political party. I was informed that this exact issue had been brought up at the Template talk:Party name with color, but no one has fixed this issue yet. User:CX Zoom suggested that I should try to bring this up here so that someone might be able fix this. I have described the exact situation below:
style="width: 2px; color:inherit; background-color: #f50222;" data-sort-value="Communist Party of India" | | scope="row" style="text-align: left;" | Communist Party of India
style="width: 2px; color:inherit; background-color: #cc0d0d;" data-sort-value="Communist Party of India (Marxist)" | | scope="row" style="text-align: left;" | Communist Party of India
Multiblocks will begin mass deployment by the end of the month: all non-Wikipedia projects plus Catalan Wikipedia will adopt Multiblocks in the week of May 26, while all other Wikipedias will adopt it in the week of June 2. Please contact the team if you have concerns. Administrators can test the new user interface now on your own wiki by browsing to Special:Block?usecodex=1, and can test the full multiblocks functionality on testwiki. Multiblocks is the feature that makes it possible for administrators to impose different types of blocks on the same user at the same time. See the help page for more information. [5]
View all 29 community-submitted tasks that were resolved last week. For example, there was a bug with creating an account using the API, which has now been fixed. [7]
User script developers can use a new reverse proxy tool to load javascript and css from gitlab.wikimedia.org with 
