Jump to content

Wikipedia:Village pump (technical)

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Vitreology (talk | contribs) at 03:04, 26 October 2023. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

 Policy Technical Proposals Idea lab WMF Miscellaneous 
Shortcuts
The technical section of the village pump is used to discuss technical issues about Wikipedia. Bug reports and feature requests should be made in Phabricator (see how to report a bug). Bugs with security implications should be reported differently (see how to report security bugs).

If you want to report a JavaScript error, please follow this guideline. Questions about MediaWiki in general should be posted at the MediaWiki support desk. Discussions are automatically archived after remaining inactive for five days.

Purge API broken?

I noticed that sub categories in Category:AfC pending submissions by age were not being updated by the bot that normally periodically updates by purging. I could not remember which bot it was so just assumed it was down. I run a program I wrote to do a purge on drafts in the wrong cats as a temp fix but that also failed to make any difference. I then tried a manual purge from the More > Purge menu and again no update to the categories. note that doing an Edit+Publish does get the categories to update.

This appears to have happed in the last few days so I assume it was possibly broken by the mw:MediaWiki 1.41/wmf.30 update - possibly Git 964563. I havn't had time to dig deeper, but thought I would report. Cheers KylieTastic (talk) 11:24, 16 October 2023 (UTC)[reply]

@KylieTastic: Purge only updates the purged page itself, not category pages and link tables. That requires a null edit (Edit+Publish). They would automatically be updated at some point but it can take a really long time. The time varies. I don't know whether it has generally been slower lately. PrimeHunter (talk) 11:38, 16 October 2023 (UTC)[reply]
@PrimeHunter I was not sure if the menu purge was working before, I agree from the text in Help:Purge it looks like it never did. However the bot used to work and I know my own program worked but I do a purge setting forcelinkupdate as well that I found was required to fix these category issues. That was working a week ago when I used it to clear Category:Automatic taxobox cleanup that was showing hundreds of issues that were no longer valid. I'll investigate more when I have time. Cheers KylieTastic (talk) 11:50, 16 October 2023 (UTC)[reply]
Pretty sure the purge API updates categories with forcelinkupdate=1. Nardog (talk) 14:19, 16 October 2023 (UTC)[reply]
Out of interest, which bot normally does those purges? — TheresNoTime (talk • they/them) 11:52, 16 October 2023 (UTC)[reply]
@TheresNoTime it used to be HasteurBot for a long time, then after Hasteur passed someone else did take up the task but I can't remember who or what the bot was called, and I've failed to find the past discussion at WT:AFC. KylieTastic (talk) 12:32, 16 October 2023 (UTC)[reply]
@TheresNoTime doh I remembered that is was Joe's Null Bot for a while which led me to this discussion - so I think the answer is ProcBot run by ProcrastinatingReader. KylieTastic (talk) 12:38, 16 October 2023 (UTC)[reply]
Yeah, I think it's ProcBot. Category:AfC pending submissions by age is on the list located at User:ProcBot/PurgeList. I am not sure if the bot is still running though. Proc went inactive for awhile and the bot went down at least for awhile. The last time the AFC category stopped getting purged, I almost ended up writing a replacement bot. I forget what we did to fix it. –Novem Linguae (talk) 22:49, 21 October 2023 (UTC)[reply]

Quick clarification on how this should work now, from the person who wrote the patches in question:

  1. ActionPurge and ApiPurge should both enforce the rate limits for purge and linkpurge, which are both set to 30 purges per minute for each user (and each IP). But as far as I can tell this limit does not apply to bots, since the bot group has the noratelimit right set per default.
  2. purge is now an "implicite right" (like linkpurge already was). This means that the right cannot be denied, just rate-limited. A message like User does not have required user right "purge" should be impossible.

If this is not the case, please file a ticket on Phabricator and assign it to me. -- DKinzler (WMF) (talk) 20:56, 24 October 2023 (UTC)[reply]

Unfortunately this is not the case for #2, Pywikibot-based bots are still seeing that error message (phab:T349348). Shubinator (talk) 01:42, 25 October 2023 (UTC)[reply]
My bot is still spinning its wheels, repeatedly purging the same pages. I'm seeing no indication from the system reporting back to the bot that the pages were not successfully purged, and yet the page_links_updated value for these pages has not been updated, so my bots keep trying to update it... As I said, this behavior began around the end of September or the beginning of October, so you might look into what changed around that time. – wbm1058 (talk) 10:57, 25 October 2023 (UTC)[reply]
I see "Use Authority to check rate limits in the API." was submitted on September 28, that matches the time frame when my purge bots stopped working, so that code change is my suspect: "Rate limit checks are now performed implicitly by UserAuthority, see T310476." Even though my bots are not rate limited(?). – wbm1058 (talk) 11:13, 25 October 2023 (UTC)[reply]
That went in the the mw:MediaWiki 1.41/wmf.29 update, the update before the one reported at the top of this thread. – wbm1058 (talk) 11:24, 25 October 2023 (UTC)[reply]

My user page

I made some alternative user pages and redirected to my only active user page; i.e. I made user pages like User:Hamid.Hassani, User:Hamid Hassany, User:Hamid Hasany, and so on, with redirecting to the active one. Afterward, when I wanted to check my user page, I came accross this text: Hamidhassani1 is my former Wikipedia user. http://en.wikipedia.org/wiki/User:Hamid_Hassani, which I wrote ca. ten years ago. If I made a wrong action, please let me know to request deleting them via WP:SD request. Thank you. – Hamid Hassani (talk) 19:55, 16 October 2023 (UTC)[reply]
Additional note: apparently, this edit happened unintentionally through the creation of redirect user pages! – Hamid Hassani (talk) 20:10, 16 October 2023 (UTC)[reply]

@Usernamekiran: Thank you for your comment. As I mentioned, I fixed the occurred problem to my user page. Now, do I need to request speedy deletions for the created redirects? — Hamid Hassani (talk) 12:53, 22 October 2023 (UTC)[reply]
@Hamid Hassani: that depends. you can go to Special:CreateAccount, and create the accounts for the three redirects above. If you do not wish create these accounts, then you can request for speedy deletion. A lot of editors create doppelganger accounts to avoid impersonation. It is totally up to you. But I don't think creating doppelganger accounts is really necessary, so I think requesting speedy deletions would be the best choice here. —usernamekiran (talk) 14:03, 22 October 2023 (UTC)[reply]
@Usernamekiran: Ok. I got the point. I will request WP:SD for some of them. — Hamid Hassani (talk) 17:21, 22 October 2023 (UTC)[reply]

Italicized title

Hi, while doing npp, I came across the article Horse symbolism, which has an italicized title. When I tried to fix it, I noticed there wasn't an {{italic title}} anywhere in the article, so I'm a bit confused as to why the title is italicized. Anyone know what happened and how to fix it? Thanks! ARandomName123 (talk)Ping me! 22:42, 16 October 2023 (UTC)[reply]

The several {{infobox artwork}}s in the page are doing so. I do not think those should be in there, especially since they seem to be serving as {{quote box}}s and not infoboxes. Izno (talk) 23:00, 16 October 2023 (UTC)[reply]
{{infobox artwork}} accepts |italic title=no but there are a lot and it's hard to know what future editors may do. Instead I have added {{DISPLAYTITLE:{{PAGENAME}}|noerror}} at the end to override whatever comes before it.[1] PrimeHunter (talk) 23:12, 16 October 2023 (UTC)[reply]
Thanks for the help! I'll take a shot at changing the infoboxes to quoteboxes. ARandomName123 (talk)Ping me! 23:18, 16 October 2023 (UTC)[reply]
Resolved
All infoboxes changed to other templates too. –Novem Linguae (talk) 22:41, 21 October 2023 (UTC)[reply]

Sticky header clips trailing f in page title

Tracked in Phabricator
Task T349436

While using Vector 2022, I saw that page titles ending with a lowercase f don't look right in the sticky header. This is really minor... but I thought I'd bring it up anyway and see if it's everyone or just me? I'm referring to titles like these:

It's much more noticeable on pages ending with italic f. By "sticky header", I mean the bar across the top of the screen when you've scrolled down the page a bit. It's the title as seen there that has the problem.

(Firefox 118) 3df (talk) 20:15, 17 October 2023 (UTC)[reply]

You are right. It's because .vector-sticky-header-context-bar-primary has overflow:hidden. Please file a bugreport in phabricator. —TheDJ (talk • contribs) 20:49, 17 October 2023 (UTC)[reply]
Yes Sent 3df (talk) 21:55, 21 October 2023 (UTC)[reply]

WP:1CA "undefined"

I stumbled across a page Wikipedia talk:WikiProject Articles for creation/undefined 2 obviously created in error. A quick search found that there are actually a few (maybe 30 or so) "undefined" pages created by 1CA. See archive intitle:undefined - Search results - Wikipedia. I bet the issue might be stale as the bug might have been fixed, but I wanted to raise the issue in case it has been noticed by other 1CA users. I am pretty sure all of these would be G6 eligible because these pages were created as a result of a malfunction of a user script. Awesome Aasim 23:15, 18 October 2023 (UTC)[reply]

Awesome Aasim. Looks like that page was created by User:Technical 13/Scripts/OneClickArchiver.js. I found out the hard way how buggy that script is, and I recommend that everyone upgrade to User:Evad37/OneClickArchiver.js, which is a forked version with lots of bug fixes. –Novem Linguae (talk) 22:12, 21 October 2023 (UTC)[reply]
@Novem Linguae Can you consider G6'ing the pages accidentally created by that script? Of course, after moving the text from the "undefined" archives. Also would consider commenting out the last part of the Technical 13 1CA. Awesome Aasim 13:33, 24 October 2023 (UTC)[reply]
Thanks for pointing this out. I think we should 1) prevent this problem from happening in the future by doing something to Technical13's script. I started a discussion on that at Wikipedia:Interface administrators' noticeboard#OneClickArchiver old version is creating a mess. 2) After #1, make a post at WP:AWBREQ to get some help cleaning up the 30 pages in your list. –Novem Linguae (talk) 15:05, 24 October 2023 (UTC)[reply]
#1 is now done. They ended up blanking the user script. I kicked off #2 by creating Wikipedia:AutoWikiBrowser/Tasks#Cleanup of 30 talk page archives with "undefined" in title. –Novem Linguae (talk) 17:04, 24 October 2023 (UTC)[reply]
#2 is now also complete.
Resolved
–Novem Linguae (talk) 09:54, 25 October 2023 (UTC)[reply]

Center babel box

Is there a way to center the {{babel}}’s box? I’ve tried |align=center but the lua module seems to only detect if the parameter exists and isn’t right. Also, how do I do the same for the #babel magic word? Aaron Liu (talk) 14:58, 20 October 2023 (UTC)[reply]

Try using <center> before, and then </center> after that. — Hamid Hassani (talk) 13:13, 22 October 2023 (UTC)[reply]
I've tried that, at least with the center template. It looks like this.
Aaron Liu (talk) 14:49, 22 October 2023 (UTC)[reply]
This is a hack, but it works (for now):
That's {{babel|extra-css=margin:auto;float:none}} – Jonesey95 (talk) 15:05, 22 October 2023 (UTC)[reply]
Great, thanks! I tried margin:unset but wow, I should've thought of that! Aaron Liu (talk) 15:17, 22 October 2023 (UTC)[reply]
Still, is this not possible for the #babel magic word? Aaron Liu (talk) 15:21, 22 October 2023 (UTC)[reply]

The inevitable new redlinked category problems

Latest problems at Special:WantedCategories that are beyond my ken to fix:

  1. Category:Proposed deletion as of 10 October 2023 is listed as a non-empty redlink with one member, even though the category itself is actually empty; I attempted a restore-and-redelete on it, but that failed to resolve the problem (or to reveal any contents).
  2. As part of the ongoing process of moving wikiproject "members" categories to "participants", Category:WikiProject Apple Inc. members has already been moved to participants and mostly emptied out; the one straggler still in the dead category is a css settings page that I can't edit. Can somebody with the necessary level of editing privileges move User:Jake01756/csstest.css from "members" to "participants"? Thanks. Bearcat (talk) 17:15, 20 October 2023 (UTC)[reply]
{{PAGESINCATEGORY:Proposed deletion as of 10 October 2023}} looks like it's going to stay broken (at 0) for the time being. The usual way I use to fix it didn't work, I suspect because another page had been moved to Lyceum (software) after the initial problematic deletion. phab:T85696 has the flawed fix that lets action=purge fix this about one time out of ten (ping Legoktm, on the off chance he wants to update it; some analysis here). phab:T311744 is an open bug showing the same symptoms. phab:T18603 asks for a script specifically to fix this and is closed as a duplicate, but I can't find what bug it's a duplicate of (it's not the one mentioned); I vaguely recall seeing mention of such a script and that it gets run monthly, though that might just be my brain playing mean tricks on me again. —Cryptic 20:23, 20 October 2023 (UTC)[reply]
phab:T18603 says "duplicate of bug 16112". Many old bugs were once renumbered by adding 2000 so it's now a duplicate of phab:T18112. I think it was caused by a merge of two numbered bug systems using the same numbers below 2000. PrimeHunter (talk) 21:10, 20 October 2023 (UTC)[reply]
That looks plausible, thanks. Wasn't any help in finding the modern iteration of the script, though, which is indeed run monthly. So Category:Proposed deletion as of 10 October 2023 should get fixed without further manual intervention... eventually. —Cryptic 21:21, 20 October 2023 (UTC)[reply]
Pretty much. When they switched from Bugzilla to Phabricator, people testing the latter started using it for real stuff pre-import and so when the bugs were later imported they had to be renumbered. Anomie⚔ 13:24, 21 October 2023 (UTC)[reply]
Bugzilla was the bug-tracking system used for just over ten years. The series of ticket numbers ran from bugzilla:1 (10 August 2004) up to bugzilla:73681 (21 November 2014). Some time before Bugzilla was dropped, it was decided to use Phabricator instead, and during the migration period tickets phab:T1 (5 February 2014) up to phab:T1391 (21 November 2014) were raised (mainly for issues connected with the migration) before all of the bugzilla tickets were imported over 21-22 November 2014, their numbers being increased by 2000 and prefixed with the letter T, hence phab:T2001 through phab:T75681 were all imported from Bugzilla. Tickets from phab:T75682 (22 November 2014) upwards were created directly in Phabricator. The numbers T1392 to T2000 inclusive were never issued. If links to Bugzilla tickets use the same format that I have used for the first two links in this post, an automatic redirection will occur, so there should be no beed for manual correction. Try out this link: bugzilla:16112. --Redrose64 🌹 (talk) 14:36, 22 October 2023 (UTC)[reply]
Should I say sorry for having done something unusual that inadvertently broke the system? And I can't even resolve the other redlinked category issue as pennance because another Iadmin beat me to it. * Pppery * it has begun... 23:22, 20 October 2023 (UTC)[reply]
Neener neener neeeeener Izno (talk) 23:25, 20 October 2023 (UTC)[reply]
Bearcat say relax, weren't aimed at you. Bearcat (talk) 01:14, 22 October 2023 (UTC)[reply]

updated since your last visit

The "updated since your last visit" I usually see when checking the history of a page I have watchlisted has changed to a migraine inducing vivid green, any idea how I can stop that so I can look at the page again? -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 18:48, 20 October 2023 (UTC)[reply]

Might be different rendering but its rather pleasant on my screen. In the short term if its causing a medical issue you could grayscale your display. Horse Eye's Back (talk) 18:55, 20 October 2023 (UTC)[reply]
There seems to be a move to the use of vivid colours, unfortunately not everyone finds them easy on the eye. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 18:59, 20 October 2023 (UTC)[reply]
I will say that when I turn my blue filter off it is a much less pleasant shade of green. I too would prefer something closer to a pastel (something which compliments our soft blues). Horse Eye's Back (talk) 19:06, 20 October 2023 (UTC)[reply]
@ActivelyDisinterested You could try 
.updatedmarker{color:somthing more appealing; background-color:white};
in your common.css. NW1223<Howl at me•My hunts> 20:30, 20 October 2023 (UTC)[reply]
Thanks I'll give it a try. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 20:43, 20 October 2023 (UTC)[reply]
Thanks, NightWolf1223. It would be helpful if devs added a prefs setting when they made changes like this, rather than our having to deal with CSS. This looks very like the watchlist preference Subtle update marker: Tone down the "Changed since last visit" indicator on history pages. (By default it renders as a green-filled bar, enabling this gadget changes it to green text.) BlackcurrantTea (talk) 06:22, 21 October 2023 (UTC)[reply]
Well, @BlackcurrantTea, I have that on, but it looks like they borked it. It renders as a a lime box rather than green text. I honestly have zero clue what is going on. Especially considering that my code is the exact same as the gadget. If anyone knows what is going on, please let me know. NW1223<Howl at me•My hunts> 06:32, 21 October 2023 (UTC)[reply]
It's the fault of this change to the gadget definition -- looks like some gadgets got limited to the Special namespace. I think it'd be reasonable to remove that change for this specific gadget, since it really is supposed to apply outside of that namespace. DLynch (WMF) (talk) 15:11, 21 October 2023 (UTC)[reply]
The issue seems to have been resolved by this edit[2]. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 16:58, 21 October 2023 (UTC)[reply]
Resolved
–Novem Linguae (talk) 21:45, 21 October 2023 (UTC)[reply]

History bullet points not working as they did

The History section bullet points no longer show as clear for unread versions, which was helpful, as they are near the "Compare selected revisions" radio buttons on the left side of my wide screen. The new messaging is off to the right, which makes it harder to determine which buttons to set. Why was that changed and can it be changed back? Dhtwiki (talk) 03:23, 21 October 2023 (UTC)[reply]

What "new messaging"? Nardog (talk) 07:45, 21 October 2023 (UTC)[reply]
I have seen the same thing as Dhtwiki, I think. The article history no longer shows different colored bullet points for unread versions (yesterday, it did). The new messaging is a text box which displays "updated since your last visit" in green at the end of the revision line. I saw this starting yesterday (I don't recall changing any preferences for this), but it is gone now. My watchlist does indicate which articles have changes I have not seen; it's just the article history that doesn't. --Spiffy sperry (talk) 17:49, 21 October 2023 (UTC)[reply]
@Izno: Remove |namespaces=-1 from WatchlistGreenIndicators and WatchlistGreenIndicatorsMono as well (or replace it with |actions=view,history). Nardog (talk) 18:00, 21 October 2023 (UTC)[reply]
Probably should consider splitting the gadget (at least the one loading on V22) if that makes sense since every line but one selector for one of those is specific to watchlist, and that's a lot of imagery loading. Izno (talk) 18:10, 21 October 2023 (UTC)[reply]
(And setting actions=view doesn't help in any great sense without also splitting.) Izno (talk) 18:12, 21 October 2023 (UTC)[reply]
Resolved
in this diff, I think. –Novem Linguae (talk) 21:47, 21 October 2023 (UTC)[reply]
It's back to the way it was for me (and the bullet points show as green, not clear, which is what I put before). Thank you. Dhtwiki (talk) 01:00, 22 October 2023 (UTC)[reply]
Firstly sorry for the unexpected breakage. I was investigating a small performance blip (increase in CSS bytes shipped on page) on Enwiki and that seemed liked an obvious optimization.
@Izno we could add 
namespaces=-1,actions=history
if this is being used on the history page as well as watchlist. What do you think? Jdlrobson (talk) 15:00, 23 October 2023 (UTC)[reply]
Wait, namespaces=-1,actions=history means "in the special namespace or on history pages"? If so the documentation needs updating, as that is contradictory to "only on the specified page actions"/"only on the specified namespaces". Nardog (talk) 17:01, 23 October 2023 (UTC)[reply]
Indeed, separate RL parameters demarcate logical AND, not OR. I made this comment at phab:T63007#9192636 also, which gifted us the namespaces parameter. There has been some chatter about more complex loading functions which might allow logical OR. That's phab:T342567. I don't see an existing open task which specifically requests logical OR, but given Krinkle's general stewardship of the Phabricator project, someone might be able to find such in the declined pile. (Or not.) (Logical OR would also be difficult to shoehorn into the current gadget definitions. It might be something that could be done on its own if/when Gadget definition namespace is used.)
I will take a look at splitting this like I suggested above. The other thing I'm thinking about is turning this off as a default. We had so few responses here when it disappeared for the few days it did. Izno (talk) 17:23, 23 October 2023 (UTC)[reply]
@Jdlrobson I was investigating a small performance blip (increase in CSS bytes shipped on page) on Enwiki
That must be due to https://gerrit.wikimedia.org/r/c/mediawiki/core/+/964878 - purge is now an implicit right available to IPs as well. This means cached page views now ship geonotice, watchlist-notice and other gadgets that were previously restricted to registered users (using the rights=purge hack). We can update the condition to rights=createpage. – SD0001 (talk) 13:04, 24 October 2023 (UTC)[reply]
I had been wondering about that patch and gadgets-definition. Probably worth saying something on task for that... Izno (talk) 16:58, 24 October 2023 (UTC)[reply]
Nice catch User:SD0001 - that would explain the increase in gadget bundle we were seeing!
on subject of logical OR I created phab:T349654. Jdlrobson (talk) 17:36, 24 October 2023 (UTC)[reply]

De & Fr WP articles to En

Two specimen print screens of the tool "tofawiki!"

I'm looking for a tool on the De & Fr WPs for the ease and reducing the time-consuming mechanical work in order to creating non-existent EnWP articles via translating articles, e.g., from the two mentioned WPs.
As far as I'm aware, there's a special tool in FaWP (named "tofawiki") that helps users to create a specific En article on the FaWiki. This tool, especially, helps transferring accordant references, categories, etc automatically in this regard. Is there any tool especially on the De and/or Fr Wiki(s) alike? Thanks in advance. — Hamid Hassani (talk) 04:44, 21 October 2023 (UTC)[reply]

There is Wikipedia:Requests for page importation which imports the markup and history. Then you can translate manually. Jo-Jo Eumerus (talk) 08:40, 21 October 2023 (UTC)[reply]
Importation can be done but isn't required here (I do most of the work on that page). I think you were looking for the Content translation tool. Graham87 (talk) 09:23, 21 October 2023 (UTC)[reply]
@Graham87: The WP page you mentioned is the nearest one to what I was seeking. Thank you indeed. — Hamid Hassani (talk) 05:37, 23 October 2023 (UTC)[reply]

Deletion of never created content

So, an interesting finding at Category talk:Railway stations in Allahabad district - the page is currently empty after the deletion of 107 bytes of text ... except that there is no edit showing the addition of these 107 bytes. Jo-Jo Eumerus (talk) 11:55, 21 October 2023 (UTC)[reply]

This was because of a history merge, see log. – SD0001 (talk) 13:35, 21 October 2023 (UTC)[reply]
Gah, why do I keep doing unusual things that cause queries at VPT? This is the second time in only a few days (the other one being #The inevitable new redlinked category problems) * Pppery * it has begun... 18:22, 21 October 2023 (UTC)[reply]
Tracked in Phabricator
Task T341760
I have a ticket to create an entry in the page's history when a history merge occurs. Could help prevent confusion like this. –Novem Linguae (talk) 21:43, 21 October 2023 (UTC)[reply]

Project tag adding script creates blank pages

Sometimes, MediaWiki:AFC-add-project-tags.js appears to screw up and make blank pages like e.g Draft talk:Anunay Films which I've now deleted. I don't know JavaScript; can the script be changed so that it doesn't fail in this fashion? Jo-Jo Eumerus (talk) 12:00, 21 October 2023 (UTC)[reply]

Sometimes it even deletes existing tags, e.g Draft talk:Nehza Elnaz Rayya Jo-Jo Eumerus (talk) 12:06, 21 October 2023 (UTC)[reply]
This edit was done via another script altogether – WP:AFCSW. The edit that removed the wikiproject tag was from a resubmission. During resubmission, the script shows the existing project tags in the UI and allows the user to remove existing ones or add new ones. In this case, the user must have chosen to remove the one tag that was there on the page. – SD0001 (talk) 13:31, 21 October 2023 (UTC)[reply]
If the user submits the form at Wikipedia:WikiProject Articles for creation/Add WikiProject tags without selecting any tags, then sure - it'll create a blank talk page. I wouldn't call that a screw-up; blank talk pages do no harm. – SD0001 (talk) 13:27, 21 October 2023 (UTC)[reply]

Janie Fricke

There's a stray right bracket at the very bottom of Janie Fricke that I can't seem to get rid of as I can't locate it on the page. Anyone able to get it for me? Ten Pound Hammer • (What did I screw up now?) 19:21, 21 October 2023 (UTC)[reply]

Yes, just a stray bracket.[3] Thincat (talk) 19:37, 21 October 2023 (UTC)[reply]
Resolved
–Novem Linguae (talk) 02:31, 23 October 2023 (UTC)[reply]

css problem with category renaming

Moved to WP:IANB § Retired user populating deleted categories

Izno (talk) 20:34, 22 October 2023 (UTC)[reply]

Adding a "death toll" in infobox of car models.

Hello, in United States, (and likely in other countries), there are statistics for death per million/miles, per 10 000 vehicules, or simply plain number aggregate numbers.

Once a vehicule reaches 20 accidents, official stats are made, on a vehicule.

I have tried to set up a parameter infobox [in the text editor] (in the sandbox), then to edit infoboxes, but it does not seem to change anything. I am very unsure, and the template tutorial didn't really feel so helpful. I tried as well editing by the graphical editor

The US road safety organisation has stats for several models.

I wanted to explore infobox options and death tolls in infoboxes, likely should not be limited to conflicts.

May anyone, please provide any guidance? Kamil Hasenfeller (talk) 10:39, 22 October 2023 (UTC)[reply]

Template:Infobox automobile/doc is the documentation, not the actual template. The edit would have to happen at Template:Infobox automobile ... and I think folks will ask whether this number is indeed important enough to be highlighted in the infobox. Jo-Jo Eumerus (talk) 10:59, 22 October 2023 (UTC)[reply]
I think it is because we have articles about road security, that security is major component of a car's design, and so. Yes, I do not think most would oppose so. Here is where I failed: Template:Infobox automobile/sandbox.
This number is indeed important, and there are yearly statistics made for car accidents and some vehicules are famous for their death toll. (F150 for example).
I try to set up a sandbox thing. But parameters when added stay as "Unknown" and do not change the display of the (sandbox) infobox. Kamil Hasenfeller (talk) 11:22, 22 October 2023 (UTC)[reply]
@Kamil Hasenfeller "Vehicule." Would that be a microscopically small car? You know, "vehiCLE" and "moleCULE"? Uporządnicki (talk) 11:14, 22 October 2023 (UTC)[reply]
My bad, here is a misspelling, I used too often. Kamil Hasenfeller (talk) 11:23, 22 October 2023 (UTC)[reply]
Consensus would need to be obtained for the proposed change - probably at Template talk:Infobox automobile. Good luck with that.Nigel Ish (talk) 11:25, 22 October 2023 (UTC)[reply]
Is consensus needed for attempting to edit the sandbox? I do not mean to change the template, just to try figure see HOW it is done. Later if included yes, it would need a policy consensus. Kamil Hasenfeller (talk) 11:30, 22 October 2023 (UTC)[reply]
Anyone can edit the sandbox. It's a good idea to check that a change is technically feasible before proposing it, and to have an example to illustrate what's being suggested. My view is that this change would be very easy technically but might not attract consensus, both because the figure is not a core property of the car and because it may be specific to the U.S. when most cars are used in other countries. Certes (talk) 13:15, 22 October 2023 (UTC)[reply]
How about models mostly found in the US? It actually might be hard I found the figures for only 4 models. Is not safety a core property? Kamil Hasenfeller (talk) 13:20, 22 October 2023 (UTC)[reply]

In my my own sandbox how must I proceed to add a new parameter?? (I have opened a sandbox). https://en.wikipedia.org/wiki/User:Kamil_Hasenfeller/sandbox — Preceding unsigned comment added by Kamil Hasenfeller (talk • contribs) 11:36, 22 October 2023 (UTC) [reply]

--Kamil Hasenfeller (talk) 12:59, 22 October 2023 (UTC)[reply]

{{Infobox automobile}} has no such parameter and it cannot be added in the call alone. It has to be supported by the template. For testing you could call your modified version at {{Infobox automobile/sandbox}}. This does not happen automatically just because the call is in a sandbox page. You have to include /sandbox when you make the call. PrimeHunter (talk) 14:56, 22 October 2023 (UTC)[reply]
I would like to make the template support a new parameter. Kamil Hasenfeller (talk) 13:22, 23 October 2023 (UTC)[reply]
In the sandbox. Kamil Hasenfeller (talk) 13:22, 23 October 2023 (UTC)[reply]
I told you to include /sandbox when you call {{Infobox automobile/sandbox}}. I have now done it for you [4] but if you cannot follow such a simple instruction then I suggest you don't try to edit infobox templates. PrimeHunter (talk) 19:40, 23 October 2023 (UTC)[reply]
There is more information at WP:TESTCASES. --Redrose64 🌹 (talk) 22:34, 22 October 2023 (UTC)[reply]
This page very few information about how to make a template. Kamil Hasenfeller (talk) 13:28, 23 October 2023 (UTC)[reply]
WP:TESTCASES is about testing templates, not making them. See Help:Template for general help on making templates, and Template:Infobox for help on making infobox templates. WP:TESTCASES gives an efficient test method for users who know how it works but it may be too complicated for you and it isn't required. Instead you can just manually make test calls of a template. Make sure you are really calling the wanted template by its precise name. PrimeHunter (talk) 19:57, 23 October 2023 (UTC)[reply]
It's also about creating and updating /sandbox pages. --Redrose64 🌹 (talk) 12:50, 24 October 2023 (UTC)[reply]

That's a pretty loaded number (implies deaths caused by the vehicle and who decides that?) and would probably need clarification / explanation and sourcing....i.e. (only) in the body because info boxes are bad at clarification / explanation and sourcing North8000 (talk) 19:45, 23 October 2023 (UTC)[reply]

Yes, both the weapon and the shooter are guilty. Well then it could be a list. Kamil Hasenfeller (talk) 16:58, 24 October 2023 (UTC)[reply]

En-dashes and em-dashes looking the same in the editor?

Let me know if this is just a me thing — but the en dash (–) and the em dash (—) look exactly the same to me in the edit window. They look obviously different in the preview, and they look different when I save the page, but the monospace font in the edit window (and the monospace font used with <code> tags) shows literally exactly the same glyph.

  • – (en)
  • — (em)

And I do mean exactly the same glyph. To the pixel. I'm using Firefox on Linux; is this just an implementation detail for me, or is this the case for everyone? If the latter, I would like to establish a petition, social movement, referendum, et cetera to slightly alter the monospace font we use to make them look slightly different. jp×g 00:40, 23 October 2023 (UTC)[reply]

What skin are you using? Are you using visual editor or wikitext editor? They look different to me on vector 2010, wikitext editor, Google Chrome for Windows. –Novem Linguae (talk) 02:30, 23 October 2023 (UTC)[reply]
Try different fonts.
There is no "monospace font we use". The CSS is just .mw-editfont-monospace { font-family: monospace, monospace; } (without the second monospace it becomes smaller) and it shows in whatever monospace font set in your browser. Nardog (talk) 04:35, 23 October 2023 (UTC)[reply]
They look different for me; I'm using the Consolas font. I tried a few other common fonts, and in DejaVu Sans Mono they look indistinguishable, so perhaps that's the one you're using. You can choose your preferred monospace font in Firefox settings: Fonts → Advanced… → Monospace. Matma Rex talk 16:36, 23 October 2023 (UTC)[reply]
@JPxG: As per Matma Rex; plus, when I installed Firefox on my present machine, the default monospace font was unsatisfactory - I'm now using Courier New 13pt but don't recall what I altered it from. --Redrose64 🌹 (talk) 10:51, 24 October 2023 (UTC)[reply]

Undo button not showing auto text

I am not able to replicate it, but recently, I was able to "undo"/revert someone's edit without the typical Undid revision X by X showing up in the edit summary. It was this edit, where it marked it as a "minor edit" (Button was not clicked to be a minor edit). I tried to replicate it briefly in my sandbox to no luck. I also checked and this was not a redwarn style revert, as the edit summary wouldn't have been blank if, which it was. I doubt there is a instant "You did this" or "I can fix that" solution to this, but on the 0.1% chance there was, I wanted to alert y'all here. I was on Edge Browser, so if others report some similar problem, y'all got a report from me on it. Cheers. The Weather Event Writer (Talk Page) 00:56, 23 October 2023 (UTC)[reply]

What is your point? It's always been possible to revert edits with no summary. Nardog (talk) 04:39, 23 October 2023 (UTC)[reply]
The default undo summary has never shown up when undoing multiple revisions, like that edit did. —Cryptic 04:49, 23 October 2023 (UTC)[reply]
Has it always been possible to undo multiple edits, or is that a new thing? Came here to report the blank edit summary and realized I was undoing two edits. Feels like it's a new feature, but I could be wrong. –Novem Linguae (talk) 20:50, 23 October 2023 (UTC)[reply]
@WeatherWriter and Novem Linguae: It has always (or at last since May 2009, when I started editing) been possible to revert multiple edits as a single revert, and where two or more edits are reverted as a single action, the default edit summary is always blank, but Twinkle does supply one.
Assuming that you're not using Twinkle, such single reverts of multiple edits are normally done from the page history, either (i) when you have used the "cur" link on the third row or below and then used the "undo" link at upper right; or (ii) when you have selected radiobuttons on non-consecutive rows, then used the Compare selected revisions feature and then used the "undo" link as above.
In this case, the edit under discussion reverted these six edits all at once, and since the very next edit was the one under discussion, I suspect that the "undo" was preceded by using the "cur" link on the row directly beneath the ones that I have listed. --Redrose64 🌹 (talk) 21:21, 23 October 2023 (UTC)[reply]
Undoing multiple edits was added to Help:Reverting in November 2009.[5] PrimeHunter (talk) 21:44, 23 October 2023 (UTC)[reply]
That's when the help page was updated; I'm certain that the feature existed long before. --Redrose64 🌹 (talk) 12:54, 24 October 2023 (UTC)[reply]

Global user page not showing in mobile app ( Android)

Hi,

I am using the global user page on all other languages except the English Wikipedia. When I view my user profile in another language via a browser, it correctly fetches the page from https://meta.wikimedia.org/wiki/User:Anoopspeaks. However, if I try the same from the mobile app (Android), I end up on the non-existing local user page link, causing a 404 error. Is there a way to fix this? Anoop Bhatia (talk) 17:22, 23 October 2023 (UTC)[reply]

Tech News: 2023-43

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

Recent changes

  • There is a new Language and internationalization newsletter, written quarterly. It contains updates on new feature development, improvements in various language-related technical projects, and related support work.
  • Source map support has been enabled on all wikis. When you open the debugger in your browser's developer tools, you should be able to see the unminified JavaScript source code. [6]

Changes later this week

  • The new version of MediaWiki will be on test wikis and MediaWiki.org from 24 October. It will be on non-Wikipedia wikis and some Wikipedias from 25 October. It will be on all wikis from 26 October (calendar).

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

MediaWiki message delivery 23:14, 23 October 2023 (UTC)[reply]

Blurry SVG render with "frame"

It seems that [[File:...|frame|...]] doesn't work properly on high-density screens (often misnamed "HiDPI") by not including srcset in the output HTML, so that at least for SVG files, the rendered PNG size is based on "logical pixels" instead of device pixels. For an example, see the image in Uncanny#Related theories. Removing |frame makes it properly sharp (and I do see srcset with higher-resolution 1.5x and 2x in the HTML). I don't know whether it's a general MediaWiki or a local problem... — Mikhail Ryazanov (talk) 23:53, 23 October 2023 (UTC)[reply]

Tracked in Phabricator
Task T133489
Well, apparently nobody cares, but I've found this error already reported (T133489) in 2016, so in fact nobody really cared about it for 7 years... I did some investigation and described my findings in that task, so if anybody having access to the code base can test the proposed solution, please do. — Mikhail Ryazanov (talk) 02:23, 26 October 2023 (UTC)[reply]

Citation clean up with bot

I recently started working with CSSP (Common_Symbiotic_Signaling_Pathway) but it requires referencing some references several times. I could not learn the "named reference" feature due to being obsessively focused on reading the journal articles (I am Autistic and immensely monotropic that makes it difficult for me to switch in between tasks). in this situation I have introduced several references with the citation button, and later on I am failing to visually scan the wall of text where I have introduced the duplicate/ redundant references. I apologise for this mistake. But is there any available wikipedia bot which can find duplicate references and can replace with appropriate named reference?

please help me out! RIT RAJARSHI (talk) 09:27, 24 October 2023 (UTC)[reply]

Resolved with wikimedia reFill tool https://refill.toolforge.org/ RIT RAJARSHI (talk) 11:05, 24 October 2023 (UTC)[reply]

Admin afdstats down?

I refer to: https://afdstats.toolforge.org/afdstats.py?name=Maile66&max=&startdate=&altname= When I try to open that today, it just goes on an endless loop, and nothing ever happens. I don't readily see any other issues elsewhere. — Maile (talk) 11:34, 24 October 2023 (UTC)[reply]

@Maile66, it doesn't open for me. It appears that problems with that external tool may be reported here. — xaosflux Talk 14:33, 24 October 2023 (UTC)[reply]
Thanks for the input and info. — Maile (talk) 14:51, 24 October 2023 (UTC)[reply]
Just saw this in passing and restarted the webservice — could you try again now Maile66? — TheresNoTime (talk • they/them) 15:11, 24 October 2023 (UTC)[reply]
Ta! Da! It works now. Thanks. — Maile (talk) 15:12, 24 October 2023 (UTC)[reply]

Kerem Shalom border crossing

Hello all - the Kerem Shalom border crossing is showing the correct geolocation, but as it stands the map only shows the city of Rafah, which has led some to confuse it with the Rafah Border Crossing (see talk page).

Not sure if anything can be done to remedy this or if this is the appropriate venue for this, but bringing this to editor attention. GnocchiFan (talk) 12:38, 24 October 2023 (UTC)[reply]

This is a point, and it's a bit hard sometimes to automatically determine an appropriate zoom level. I have set a different zoom level now. Map options could have been found in the template's documentation. —TheDJ (talk • contribs) 13:30, 24 October 2023 (UTC)[reply]
Thank you so much! That's much better now GnocchiFan (talk) 14:54, 24 October 2023 (UTC)[reply]

Pageviews from search query

What are the most-viewed articles with "born" in their titles (e.g. Oscar (footballer, born 1991))? (or generally, how can one turn search results into pageview analysis?) Hameltion (talk | contribs) 16:28, 24 October 2023 (UTC)[reply]

Someone could probably build a script that pulls interesting info.
The other alternative might be to see if pageviews can have another option titled "searchviews" or something. Or it could more gracefully integrate with e.g. Petscan or another one of our "big data comb" tools. Izno (talk) 16:55, 24 October 2023 (UTC)[reply]
https://pageviews.wmcloud.org/massviews/?project=en.wikipedia.org already has a "Search" option under "Source". It may have problems for searches with a huge number of results. intitle:born includes articles which only match on a redirect like George Bush (born 1946) to George W. Bush. I don't know whether such redirects can be excluded. PrimeHunter (talk) 21:25, 24 October 2023 (UTC)[reply]
> Me totally missing I could change the source of massviews. Izno (talk) 21:37, 24 October 2023 (UTC)[reply]
100% me too. Thanks PrimeHunter. Redirects aren't too much of an issue for this (can just Ctrl+F on the results) but massviews definitely tends to clunk out when processing big batches.
So of (partial) results, most viewed this year: Paul Mullin (footballer, born 1994), Rodri (footballer, born 1996), Jorginho (footballer, born December 1991). Of non-footballers: Princess Charlotte of Wales (born 2015), Peyton List (actress, born 1998), Samyuktha (actress, born 1995), Jung Kyung-ho (actor, born 1983), Jason Williams (basketball, born 1975). Others of note: Sophia Smith (soccer, born 2000), Alex Scott (footballer, born 1984), Chris Jones (defensive tackle, born 1994), Barbara Bush (born 1981). Hameltion (talk | contribs) 21:49, 24 October 2023 (UTC)[reply]

Template for discussion invitation

I am not sure if this is the right place to ask this question, but since I didn't where else to ask it, I am asking it here.

Instead of writing manual invitations at project's talk pages asking other project members for comments and feedback on XYZ subjects, is there a template, I am not aware of, that would automatically formulate an invitation by substituting it? Qwerty284651 (talk) 23:58, 24 October 2023 (UTC)[reply]

I personally make my notifications a one-liner. It just saves me time and dodges concerns of potential non-neutrality. I also use User:Newslinger/Notifier.js when I need to notify en masse. Izno (talk) 01:17, 25 October 2023 (UTC)[reply]
@Izno, would you say my invitation was non-neutral? Qwerty284651 (talk) 16:42, 25 October 2023 (UTC)[reply]
I personally. It was not a comment about notifications you may have made before. Izno (talk) 17:09, 25 October 2023 (UTC)[reply]
I know you were talking about in general. I was asking for feedback for my notification in the WT:TEN, whether it was worded as non-neutral. Qwerty284651 (talk) 22:05, 25 October 2023 (UTC)[reply]
It tends away from neutrality with to enable visitors and readers of tennis articles be given the best version of BLP's statistics that we possibly can. which is a common argument axis in many discussions. Izno (talk) 22:32, 25 October 2023 (UTC)[reply]
How do you propose I should reword it so it best fits the WP:NEUTRAL policy? Qwerty284651 (talk) 23:12, 25 October 2023 (UTC)[reply]

Grammarly issues

On several occasions, I have experienced issues when using the pop-up box editor with Grammarly. The corrections are made but with errors. For example, a comma is inserted in the middle of a word instead of the end of the word, or a correction is placed randomly in the sentence or in the middle of the word I was attempting to replace. The problem is that you cannot see how the edits are inserted from the editor box, so it is something that I have to catch in a final visual check. This issue happened one day, but everything worked as expected the next day. Only to have the problem show up again several weeks later. Unfortunately, I did not document every time I experienced this. But we know for sure it happened in August when I saved this colossal mess by mistake on the Lamar University article. It is so bizarre that am I having a hard time figuring out what was supposed to change. Rublamb (talk) 00:00, 25 October 2023 (UTC)[reply]

WP:Grammarly is a known issue. Izno (talk) 01:20, 25 October 2023 (UTC)[reply]
Thanks for sharing that link. Funny thing is, I came across it as a recommended tool for copyediting, as in Wikipedia:Spellchecking and Wikipedia:Basic copyediting. Rublamb (talk) 01:37, 25 October 2023 (UTC)[reply]
@Rublamb: Both of those pages say to use the tools carefully because they can introduce errors. RudolfRed (talk) 01:22, 26 October 2023 (UTC)[reply]

Edit conflicts with myself

Something annoying has started happening lately; this has happened to me multiple times in the last several days.

I click undo to undo another editor's edit, and check the diff, then when I click save I see:

"Someone else has changed this page since you started editing it, resulting in an edit conflict."

That someone else was me, and my edit was successfully saved, despite this message popping up telling me otherwise! wbm1058 (talk) 15:44, 25 October 2023 (UTC)[reply]

Do you have a cheap mouse that sometimes gives you two clicks when one would have been enough?
—Trappist the monk (talk) 17:20, 25 October 2023 (UTC)[reply]
Built in mouse on laptop; I guess that could happen although not to my knowledge or at any other time. Rublamb (talk) 02:06, 26 October 2023 (UTC)[reply]

I have a large page (https://en.wikipedia.org/wiki/History_of_Smooth_Island_(Tasmania) which I want to rewrite via Microsoft Word. I'll need to use a reference manager like EndNote or Zotero. How can I export the page, and it's reference list, to ensure the numbered inline citations don't become a complete mess once I start moving sections around in Microsoft Word?

I'd really love to be able to cleanly export the reflist from a wiki page into a RIS or BibTeX format.

Even better still, I'd love to be able to export a wikipedia page to a Word document, in such a way that the in-line citations hyperlinks are preserved and so that EndNote/Zotero etc can recognise them as true citations.

I'd be very grateful for any tools or solutions you could provide

Vitreology (talk) 03:04, 26 October 2023 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(technical)&oldid=1181934577"