Wikipedia:Village pump (technical)

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.

view · edit

Frequently asked questions (see also: Wikipedia:FAQ/Technical)

Click "[show]" next to each point to see more details.

If something looks wrong, purge the server's cache, then bypass your browser's cache.
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 have problems making your fancy signature work, check Help:How to fix your signature.

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.

For server or network status, please see Wikimedia Status. If you cannot reach Wikipedia services, see Reporting a connectivity issue.

« Archives, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216

Search autocomplete selects random results when arrowing down

Tracked in Phabricator
Task T379983
Resolved

I've recently tried to search a few things, and noticed that if I press arrow down on the autocomplete results, it selects a random result, rather than the expected outcome of it selecting the first in the list (then going down one if pressed again, etcetera). For example, to test this, I typed in "AS" into the search bar, which displayed "AS", "Association football", "Associated Press", "Assassination of John F. Kennedy", among others. I pressed the arrow down, and it highlighted the last result, "ASEAN". I pressed it again, and it highlighted "Asperger syndrome", which is the 6th result in the list, and 4 results up from "ASEAN". This continues for some time, but it generally jumps through the list at random intervals. I checked that I had safemode on before trying this, and I am on the latest version of 64-bit Chrome, version 131.0.6778.70. EggRoll97 ^(talk) 01:11, 15 November 2024 (UTC)[reply]

Given the day, by the way, it may be WP:THURSDAY, but I'm not necessarily sure if that indeed is the case. EggRoll97 ^(talk) 01:13, 15 November 2024 (UTC)[reply]

Me too, Windows 10 version 22H2, Firefox 132.0.2 (recent upgrade), all skins except Vector-2022 and Minerva Neue, logged in and logged out. The main symptom seems to be that in the search box, the functions of the up and down arrows are exchanged. Also affects commons:. --Redrose64 🌹 (talk) 01:22, 15 November 2024 (UTC)[reply]

This is probably related to phab:T379983 though of course you can report a separate task. Izno (talk) 01:33, 15 November 2024 (UTC)[reply]

Looks like it, and it appears a change has been merged so this should (hopefully) resolve itself fairly soon. EggRoll97 ^(talk) 01:38, 15 November 2024 (UTC)[reply]

I'm facing the same issue, on Vivaldi (7.0.3495.11 (64-bit)) on Windows 11 Home 23H2. Are you on Wikipedia's 2010 Vector legacy skin (the old default GUI) by any chance? I have this issue on that skin but not on Wikipedia's new Vector skin. Tube·of·Light 11:21, 15 November 2024 (UTC)[reply]

I'm having the same issue on Firefox 128.4.0 with Vector 2010 on macOS 12.7.6. – dudhhr^talk_contribs^she_her 22:57, 15 November 2024 (UTC)[reply]

I don’t see anyone mentioning it anywhere, but I am also having the same issue on Timeless. win8x (talking | spying) 14:46, 16 November 2024 (UTC)[reply]

@Win8x: As I wrote above, all skins except Vector-2022 and Minerva Neue. --Redrose64 🌹 (talk) 16:52, 16 November 2024 (UTC)[reply]

Oops I didn't properly read. Glad a change has been merged though. win8x (talk) 16:53, 16 November 2024 (UTC)[reply]

Resolved

Now working as expected. --Redrose64 🌹 (talk) 18:05, 20 November 2024 (UTC)[reply]

Does Pending Changes disable edit conflict checking?

I haven't found any documentation about this at Wikipedia:Pending Changes, mw:Help:Extension:FlaggedRevs, mw:Extension:FlaggedRevs, or phab:T185664. (I am an idiot though, and frequently miss obvious information.)

But here's what happened (all these diffs are sequentially uninterrupted BTW): while WP:HD was under PC protection (LTA disruption), T=00 I reply to a thread. T+02 minutes, PrimeHunter replies. T+17 minutes, OP replies to my reply, removing PrimeHunter's reply with no edit summary (edit tagged as "2017 wikitext editor"). A bit later, I notice this and enter the source editor within Minerva to restore PrimeHunter's edit without automatically adding my sig. T+44 PrimeHunter restores the edit. T+46 I do too. Despite the edit summary of my immediate self-revert, I was never shown an edit conflict error (these do work in Minerva: I had three recently at heavily trafficked pages, all in ns4).

My interpretation of this sequence is that since FlaggedRevs are "automatically accepted" when the editor permissions allow, checking for edit conflicts is disabled or hampered in some way, at least in some editing interfaces. Can anyone confirm this? Folly Mox (talk) 18:13, 16 November 2024 (UTC)[reply]

Well, PrimeHunter restored text above the 2 lines :I think this was [...] and :: I haven't had this [...], while you restored it below those 2 lines, that's why there was no edit conflict. I actually don't know the exact logic, though something is mentioned at mw:Help:Edit conflict#Preventing edit conflicts - I've always assumed that it's the same logic that governs if you can still undo a revision after new revisions have been made (which from experience is when the diff of that revision would not have revealed lines that changed in later revisions). – 2804:F1...C6:3070 (::/32) (talk) 22:46, 16 November 2024 (UTC)[reply]

For clarity, here is a multi-revision diff of both of your restorations: Special:Diff/1257208774/1257214231. – 2804:F1...C6:3070 (::/32) (talk) 22:56, 16 November 2024 (UTC)[reply]

2804:F14:8085:6D01:BC4B:E524:C2C6:3070, I assume it's paragraph-based like the diffs. — Qwerfjkl talk 18:06, 17 November 2024 (UTC)[reply]

Huh, ok; I thought edit conflicts were partitioned by subheading, but the "same line" implementation makes sense here, while also making sense at the other three edit conflicts I did experience, since other editors and I were adding text to the same (empty) line. Thanks both for the information 🙏🏽 Folly Mox (talk) 13:47, 21 November 2024 (UTC)[reply]

Specify PDF page for thumbnail?

I have uploaded File:More Public Parks (booklet).pdf which I want to link into an article. The problem is, the first few pages of the PDF are boilerplate. I want the thumbnail to show page 6 Is that possible? RoySmith (talk) 18:29, 16 November 2024 (UTC)[reply]

@RoySmith: See WP:EIS#Page. --Redrose64 🌹 (talk) 19:29, 16 November 2024 (UTC)[reply]

Interesting. That certainly looks like what I need, but for some reason, this PDF isn't showing up as a thumbnail at all. See my original post in this thread and also Special:Diff/1257813566. In both of those, "File:More Public Parks (booklet).pdf" just gets run in with the text. RoySmith (talk) 19:41, 16 November 2024 (UTC)[reply]

Doing a quick Wikisource version, even if incomplete, sounds like what you want here. Could link directly to the one page / section you want, that way. (Or if you just want the image, then extracting the image to a separate file on Commons, and showing that.) SnowFire (talk) 20:14, 16 November 2024 (UTC)[reply]

For some reason, we're not properly picking it up from Commons. Compare File:More Public Parks (booklet).pdf, which shows a default PDF icon and says "0 × 0 pixels", with c:File:More Public Parks (booklet).pdf, which shows page 1 and says "810 × 1,350 pixels". --Redrose64 🌹 (talk) 20:17, 16 November 2024 (UTC)[reply]

Even more interesting. Is this the kind of thing that might just take a while to percolate through the system? Is it worth a phab ticket? RoySmith (talk) 20:26, 16 November 2024 (UTC)[reply]

Wikisource has the same issue - can't start a transcription there because the "local" version Wikisource sees is empty with 0 pages. Definitely something funky afoot here. SnowFire (talk) 20:46, 16 November 2024 (UTC)[reply]

The thumbnail generating slowly sounds like a thumbor issue to me. At the time of upload pdfs where generating thumbnails in 1.67 seconds. Images do consistently generate faster than pdfs, djvus and tiffs. Some thumbnail sizes are generated immediately, regardless of whether they are in use, 320px is one of those.

Not sure what causes enwiki showing 0pixels and commons showing a thumbnail, but it is definitely not thumbor. Snævar (talk) 00:15, 17 November 2024 (UTC)[reply]

The problem ended up being solved by purging the enwiki File page. And then purging the pages which included that File. RoySmith (talk) 00:29, 17 November 2024 (UTC)[reply]

Hmmm, I managed it alright using

[[File:Lewis Carroll - Alice's Adventures in Wonderland.djvu|page=117|thumb|Some of my friends, yesterday]]

at Wikipedia talk:Manual of Style/Archive 228#Indentation. --Redrose64 🌹 (talk) 20:32, 16 November 2024 (UTC)[reply]

Sortable table: "Short" text for merged cells?

This comes up from time to time - with merged cells there is often a huge size difference in the default-sort view (where they are merged) and after sorting (which unmerged all merged cells). This leads to the situation where you have to decide between either putting in a very terse / abbreviated, which avoids the table blowing up in size during sorting, but is less clear to readers and wastes the space you gain from merged cells in the first place; or you use the space provided by a merged cell, but then sorting the table might increase the size a lot.

My current exhibit A for this is this table: Nikon_Z-mount#Z-mount_cameras

In the default sort the "DX (APS-C)" and "FX (full frame)" provides useful information. But if you sort the table, this increases the row height a ton and it would be better to just make it say "DX" or "FX" (for example).

=> Is there a template or a similar solution for this? Phiarc (talk) 16:07, 17 November 2024 (UTC)[reply]

Your issue is caused by using tilted text in the far left column. The only solution is not to do that. Izno (talk) 16:37, 17 November 2024 (UTC)[reply]

Strip marker problem with template

It looks like 92 articles (possibly more) with {{election box candidate with party link}} templates are exposing strip markers (?UNIQ...QINU?). It seems like the issue is related to ref tags being used within the template. Example articles include Sussex East (European Parliament constituency), 1970 Florida Attorney General election, and Kocaeli (electoral district). I’m not sure how to resolve this, so I'm posting here. Daniel Quinlan (talk) 23:09, 17 November 2024 (UTC)[reply]

Probably has to do with the string replacement on the |change= parameter. Probably the easiest is to create a |change_note= parameter so it doesn't clash with that. Gonnym (talk) 23:27, 17 November 2024 (UTC)[reply]

{{Election box candidate with party link}} says {{#invoke:String|replace|source={{{change|}}}|-|−}} to change a hyphen to a minus sign in a negative number. If the parameter has a reference then its strip marker code has four hyphens which are also changed and this breaks the code. I suggest {{#invoke:String|replace|source={{{change|}}}|^-|−|plain=false}} to only change a hyphen if it's the first character. Then the articles don't need a new parameter for a note. Before editing a template used in 29,000 pages, does anyone have objections or a better solution? The bad cell in 1970 Florida Attorney General election#Results uses {{Election box winning candidate with party link}} which would need the same fix. PrimeHunter (talk) 00:08, 18 November 2024 (UTC)[reply]

Could it be further restricted to also require the hyphen to be followed by a digit? Daniel Quinlan (talk) 00:29, 18 November 2024 (UTC)[reply]

To elaborate, I was thinking something like {{#invoke:String|replace|source={{{change|}}}|^%s*-(%d)|−%1|plain=false}}. Daniel Quinlan (talk) 02:30, 18 November 2024 (UTC)[reply]

I see you also strip whitespace at the start. It should probably be done by a new template so complicated code doesn't have to be duplicated. This search finds 20 cases just in Category:Election and referendum infobox templates. PrimeHunter (talk) 21:40, 19 November 2024 (UTC)[reply]

Portal:Maldives/Selected articles template loop error

At Portal:Maldives/Selected articles the "Selected articles 12" section shows a template loop error. That error isn't shown at Portal:Maldives/Selected articles/12 or the article it transcludes (Ibrahim Nasir). Can't figure out where the error is from. Gonnym (talk) 00:44, 18 November 2024 (UTC)[reply]

Portal:Maldives/Selected articles uses {{For loop}} to run thorugh the 25 selected articles. Portal:Maldives/Selected articles/12 transcludes content from the lead of Ibrahim Nasir which uses {{post-nominals}} which uses {{For loop}}. That's enough to give a template loop error per WP:TEMPLATELOOP. One way to fix it is to replace the for loop in Portal:Maldives/Selected articles with 25 calls:

{{subpage|1|SPAN=true}}
...
{{subpage|25|SPAN=true}}

In particular, {{subpage|12|SPAN=true}} does not give an error. PrimeHunter (talk) 02:00, 18 November 2024 (UTC)[reply]

Technical glitch with the NPP page curation tool?

Hello my friends. I am a New Page Patroller and use the excellent page curation tool. Masterhatch kindly alerted me to the fact that, when I add an "uncategorised" or "improve categories" tag, the curation tool automatically adds a space at the top of the article above the SD. I am now having to manually close the space at the top. Is anyone else having this problem? Is there a solution? Apologies if I have brought this to the wrong discussion page. Best regards, BoyTheKingCanDance (talk) 06:16, 18 November 2024 (UTC)[reply]

Identifying duplicate named refs with identical body content

The current software does not flag duplicate named refs with identical body content, as this is not considered a significant problem. However:

It wastes wikitext space.
It adds visual clutter in an edit window.
If an editor changes the body content of one of the duplicates in any way, we now have a big red cite error that is visible to readers but may go unnoticed by editors for some time. Few editors have the time to frequently scan the entire References section for such errors.

Looking for a way to identify any such duplicates so they can be eliminated using <ref name="foo" />. ―Mandruss ☎ 07:26, 18 November 2024 (UTC)[reply]

Editors who are interested in identifying duplicate reference issues faster, can add the automatic Category:Pages with duplicate reference names to their watchlist. There's also a manual Category:All articles with duplicate citations which is added by template {{Duplicated citations}}. —⁠andrybak (talk) 10:14, 18 November 2024 (UTC)[reply]

Thanks. The first cat is for duplicate refs with different content. That's not what I'm talking about, hence my italics emphasis above. Regardless, no category is going to identify the duplicates. ―Mandruss ☎ 18:04, 18 November 2024 (UTC)[reply]

There is also the automatic toollabs:checkwiki/cgi-bin/checkwiki.cgi?project=enwiki&view=only&id=81. The bot tools AWB and WPCleaner can do this task. Snævar (talk) 11:45, 18 November 2024 (UTC)[reply]

I'm not looking for automated fix; I can do that manually and I actually prefer that. I just want to identify what I need to fix manually, within a single specific article—and without a big learning curve. ―Mandruss ☎ 18:04, 18 November 2024 (UTC)[reply]

The toollabs checkwiki tool does list what to fix, a code exerpt of the reference that is duplicated. It is just a matter of doing the edit manually and clicking the done link to the entry you fixed. The latter sentance in my first sentance on AWB is not what you are looking for. Snævar (talk) 21:19, 18 November 2024 (UTC)[reply]

@Mandruss: You'll need a script, and examine each article on a case-by-case basis. This is because if a suitable category did exist, it would contain many of these articles - the {{sfn}} template relies on the fact that it is not an error (or even a warning) for two refs to have the same content. --Redrose64 🌹 (talk) 09:05, 19 November 2024 (UTC)[reply]

Thanks.

You'll need a script - I assumed as much. I was hoping:
- Such a script already existed. Or,
- A script-qualified editor could be persuaded to create such a script with a barnstar and personal satisfaction as their rewards. Obviously the script would then benefit others in the same way, forever. That would be a significant contribution to the project, probably more than spending the same amount of time editing articles. (I'd certainly do it if I were script-qualified.)
I'm only interested in one article at this point, so I have no need for categories.
I neglected to mention: Said article is nearing its WP:PEIS limit, and the elimination of these duplicates would also help address that. ―Mandruss ☎ 12:13, 19 November 2024 (UTC)[reply]

Page history link in Watchlist email

Hey people,

Wouldn't it be helpful if the email received when a page on our watchlist is updated, to have a link to the page history as well?

Current it shows the following:

Dear Bunnypranav
The Wikipedia page Wikipedia:Articles for creation/Redirects has been
changed on 18 November 2024 by anonymous user 122.43.189.14, see
<https://en.wikipedia.org/wiki/Wikipedia:Articles_for_creation/Redirects>
for the current revision. 

To view this change, see
https://en.wikipedia.org/w/index.php?title=Wikipedia:Articles_for_creation/Redirects&diff=next&oldid=1258162746

For all changes since your last visit, see 
https://en.wikipedia.org/w/index.php?title=Wikipedia:Articles_for_creation/Redirects&diff=0&oldid=1258162746

~/Bunnypranav:<ping> 13:25, 18 November 2024 (UTC)[reply]

Weird CSS making pages more narrow?

Can an interface admin please remove this weird css that seemingly makes my pages narrow (even on old vector)? I want to read in full width instead TheWikipede^talk 19:58, 18 November 2024 (UTC)[reply]

Wikipedia talk:Article titles#Request for comment on the relationship between WP:CRITERIA and WP:TITLEFORMAT

Please see subject RfC. Cinderella157 (talk) 22:21, 18 November 2024 (UTC)[reply]

Tech News: 2024-47

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

Updates for editors

Users of Wikimedia sites will now be warned when they create a redirect to a page that doesn't exist. This will reduce the number of broken redirects to red links in our projects. [1]
View all 42 community-submitted tasks that were resolved last week. For example, Pywikibot, which automates work on MediaWiki sites, was upgraded to 9.5.0 on Toolforge. [2]

Updates for technical contributors

On wikis that use the FlaggedRevs extension, pages created or moved by users with the appropriate permissions are marked as flagged automatically. This feature has not been working recently, and changes fixing it should be deployed this week. Thanks to Daniel and Wargo for working on this. [3][4]

In depth

There is a new Diff post about Temporary Accounts, available in more than 15 languages. Read it to learn about what Temporary Accounts are, their impact on different groups of users, and the plan to introduce the change on all wikis.

Meetings and events

Technical volunteers can now register for the 2025 Wikimedia Hackathon, which will take place in Istanbul, Turkey. Application for travel and accommodation scholarships is open from November 12 to December 10 2024. The registration for the event will close in mid-April 2025. The Wikimedia Hackathon is an annual gathering that unites the global technical community to collaborate on existing projects and explore new ideas.
Join the Wikimedia Commons community calls this week to help prioritize support for Commons which will be planned for 2025–2026. The theme will be how content should be organised on Wikimedia Commons. This is an opportunity for volunteers who work on different things to come together and talk about what matters for the future of the project. The calls will take place November 21, 2024, 8:00 UTC and 16:00 UTC.
A Language community meeting will take place November 29, 16:00 UTC to discuss updates and technical problem-solving.

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

MediaWiki message delivery 01:57, 19 November 2024 (UTC)[reply]

Unexpercted change in Diff format

As of yesterday, I am seeing an unexpected much more compact format in Diffs that is much more difficult than the traditional one for me to work from. Is there any way to get back to the old format? I am using "Vector legacy (2010)" skin. Wtmitchell (talk) (earlier Boracay Bill) 02:01, 19 November 2024 (UTC)[reply]

If this is what I think it is, there should be a toggle labeled 'inline' that you can switch off. Izno (talk) 02:23, 19 November 2024 (UTC)[reply]

That toggle is on the top right, below the right end of "Browse history interactively". There is also a triangle in the middle of the page (slightly left and above the right-side "Line X" statement) which turns on/off a similar smaller preview. CMD (talk) 03:03, 19 November 2024 (UTC)[reply]

The triangle is a gadget or script that you have installed. It is not a native feature. Izno (talk) 03:10, 19 November 2024 (UTC)[reply]

Thanks, looks like it's the wikEdDiff gadget. (I do find it hard to describe the toggleable gadgets as non-native features though.) CMD (talk) 08:12, 19 November 2024 (UTC)[reply]

Lockout script misbehaving

I have a forked version of User:Anomie/lockout.js in my common.js which only blocks editing, not viewing. However, if the edit page is opened by DraftCleaner, the edit page isn't blocked and I can edit as usual, including if other scripts refresh the page. Why does this happen, and is there a way to block the edit page in this case? Suntooooth, it/he (talk/contribs) 03:31, 19 November 2024 (UTC)[reply]

Social media post template

There's a discussion over at Template talk:Tweet#Post template about creating a new social media post template, that would look an act the same as the current {{Tweet}} template but extended for other social sites. A result of this was {{SocialMediaPost}}, but this seems like a very manual solution, liable to breaking and inconsistencies. I was wondering if something could be created which could, given a "website" param, automatically select the correct "site logo", "article Link", "reference format" and "prefix", similar to the way {{Political party}}s or {{Infobox legislation}} are done. Or if I'm other thinking it and the manual method is fine. Cakelot1 ☞️ talk 09:50, 19 November 2024 (UTC)[reply]

It is possible, sure. It will require some work. Izno (talk) 17:16, 19 November 2024 (UTC)[reply]

Hi! Sorry for kind of jumping the gun on moving this to the template space. I'm not the best at templates, but I'll definitely take a look at those ones you linked and see if i can do anything to automate the process. It's been a bit since I've actually used Lua, but I'll try. Generating that information off of a 'website' parameter seems doable, and i'll let y'all know if i manage to make progress. Tantomile (talk) 19:41, 19 November 2024 (UTC)[reply]

In-line citation tag

Helo! I have spent way too much time trying to find the template which askes for more in-line citations in the sourcing of an article. Wading through page after page hasn't done the trick. Can anyone here please help me find it? SergeWoodzing (talk) 13:09, 19 November 2024 (UTC)[reply]

{{No footnotes}}? DMacks (talk) 13:14, 19 November 2024 (UTC)[reply]

Thank you! --SergeWoodzing (talk) 13:19, 19 November 2024 (UTC)[reply]

If it has some inline cites but could use more there's {{more footnotes needed}}. -- LCU ActivelyDisinterested «@» °∆t° 23:40, 19 November 2024 (UTC)[reply]

I'm not sure if you were already aware of it, but just in case you're not: WP:TC is a very useful list for this sort of thing. Suntooooth, it/he (talk/contribs) 18:23, 19 November 2024 (UTC)[reply]

Lua errors

Can someone explain what's wrong here? si:විකිපීඩියා:Templates for discussion VihirLak007^hmu!/_duh. 15:31, 19 November 2024 (UTC)[reply]

It looks like Lee imported a load of templates and modules from the English wikipedia which are designed to take English language inputs. The "time errors" for example, are because si:Module:YMD to ISO converts English date strings to an ISO formatted date, but you are giving it Sinhala month names (because the output of {{#time: depends upon the language of your wiki). You either need to go through and localise all the templates that were imported, or make new ones for your wiki. 86.23.109.101 (talk) 17:49, 19 November 2024 (UTC)[reply]

Thanks. Sounds like it gonna take a while to solve the issues tho VihirLak007^hmu!/_duh. 18:37, 19 November 2024 (UTC)[reply]

Any idea how to localize and what templates/modules to localize? VihirLak007^hmu!/_duh. 19:02, 19 November 2024 (UTC)[reply]

@VihirLak007 It would probably be amount the same amount of work to start from scratch rather than getting that module to work. The module takes input in the form 19 November 2024 or 19 Nov 2024, i.e. two numbers followed by the month name or abbreviation, followed by four numbers. The output of {{#time: on your wiki seems to be 2 Sinhala numerals (I think? I don't speak Sinhala) followed by the month in Sinhala, and the year. At a minimum you would need to translate the month names, add new logic to convert the Sinhala numerals to Arabic numerals, re-write all the input checks to account for the difference in format, possibly remove the logic for the month name abbreviations ... 86.23.109.101 (talk) 19:02, 19 November 2024 (UTC)[reply]

in sinhala, the numerals are same, arabic numerals. i think if i add sinhala month names alongside where it takes english names, it might work? The thing is i've no idea where to edit VihirLak007^hmu!/_duh. 19:05, 19 November 2024 (UTC)[reply]

@VihirLak007 In that case you would need to add the Sinhala names alongside the English ones, and also change the pattern matching checks at the bottom (the bit that goes arg1:match('^%d%d%d%d %a%a%a%a?%.?%a?%a?%a?%a?%a?%a? *%d%d?$')) to allow the new date formats. 86.23.109.101 (talk) 19:09, 19 November 2024 (UTC)[reply]

Sorry for being lost minded here. Where should i add the sinhala names? i know how to add but not sure where. VihirLak007^hmu!/_duh. 19:15, 19 November 2024 (UTC)[reply]

The Sinhala names would just replace the English ones in the months_full variable. I'm not sure what you'd need to do to update the pattern matching, sorry. 86.23.109.101 (talk) 19:20, 19 November 2024 (UTC)[reply]

Any idea where to find the place that controls the output of {{#time on Sinhala wiki? VihirLak007^hmu!/_duh. 20:11, 19 November 2024 (UTC)[reply]

@VihirLak007 See MW:help:parserfunctions##time. 86.23.109.101 (talk) 20:40, 19 November 2024 (UTC)[reply]

{{#time:...|en}} will format the output in English at any wiki. PrimeHunter (talk) 21:26, 19 November 2024 (UTC)[reply]

RFC references in Further Reading

@Neko-chan: Recent edits to § Further Reading by Neko-chan have changed some, but not all,RFC references to {{IETF RFC}}. Should this not be consistent?

I was going to suggest ussing {{Ref RFC}}, but it is still a stub, e.g., {{Ref RFC|5321}} produces "^[1]". -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 09:41, 20 November 2024 (UTC)[reply]

~~Thank you for pointing out some things I missed, can you link to exactly which article? That further reading link doesn't go anywhere. ~ฅ(ↀωↀ=)neko-chan^nyan 16:14, 20 November 2024 (UTC)~~[reply]

Oh, it's still pretty early in my time zone and I misread. Maybe I should get some coffee.

If this is Email_address#Further_reading, then they're not references, they're inline links which is what {{IETF RFC}} is for. It's not inconsistent, they have different purposes. I also didn't swap the {{cite IETF}} citations because {{ref RFC}} doesn't handle section cites properly. ~ฅ(ↀωↀ=)neko-chan^nyan 16:26, 20 November 2024 (UTC)[reply]

Sorry, the template I used, {{alink|Further Reading}}, is only valid in Talk:Email address; I should have used {{slink|Email address|Further Reading}}yielding Email address § Further Reading.

The inconsistency I referred to is the one that you corrected with permalink/1258604111. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 16:49, 20 November 2024 (UTC)[reply]

References

^ J. Klensin (October 2008). Simple Mail Transfer Protocol. Network Working Group. doi:10.17487/RFC5321. RFC 5321. Draft Standard. Updated by RFC 7504. Obsoletes RFC 2821. Updates RFC 1123.

RfC notice: Log the use of the HistMerge tool at both the merge target and merge source

There is currently a discussion at Wikipedia:Village pump (proposals) regarding the logging functionality of the Special:MergeHistory tool. The thread is RfC: Log the use of the HistMerge tool at both the merge target and merge source. Thank you. — Red-tailed hawk _(nest) 16:00, 20 November 2024 (UTC)[reply]

Special:Badtitle in pending changes notice

Tracked in Phabricator
Task T380519

Over at Silk Road (marketplace) where there was a pending changes notice on the history tab, the links in it were all broken with Special:Badtitle being used. Looking at Special:PendingChanges this seems to affect other article titles as well. It seems to be an issue with mw-fr-revision-tag-edit:

<div id="mw-fr-revision-tag-edit" class="cdx-message mw-fr-message-box cdx-message--block cdx-message--notice flaggedrevs_notice plainlinks"><span class="cdx-message__icon"></span><div class="cdx-message__content">The <a class="external text" href="https://en.wikipedia.org/w/index.php?title=Special:Badtitle/Message&amp;stable=1">latest accepted version</a> was <a class="external text" href="https://en.wikipedia.org/w/index.php?title=Special:Log&amp;type=review&amp;page=Special:Badtitle/Message">reviewed</a> on <i>20 November 2024</i>. There is <a class="external text" href="https://en.wikipedia.org/w/index.php?title=Special:Badtitle/Message&amp;oldid=1258565930&amp;diff=cur&amp;diffonly=0">1 pending revision</a> awaiting review.</div></div>

SmartSE (talk) 12:22, 21 November 2024 (UTC)[reply]

Pisco is currently listed at Special:PendingChanges so https://en.wikipedia.org/w/index.php?title=Pisco&action=history shows the issue right now. The message is made by MediaWiki:Revreview-pending-basic. We have customized it but the links are generated in the same way as the default message and the problem is also seen for an uncostumized message with uselang=de (German). The message uses {{FULLPAGENAMEE}} which apparently returns Special:Badtitle/Message in that message. The same history page uses MediaWiki:Histlegend where {{FULLPAGENAMEE}} works correctly. MediaWiki:Revreview-pending-basic is from an extension. Maybe that causes the difference. We got 1.44.0-wmf.4 today. If the issue started today then it sounds like WP:ITSTHURSDAY with a problem in something at mw:MediaWiki 1.44/wmf.4. PrimeHunter (talk) 13:15, 21 November 2024 (UTC)[reply]

Here is a quick and dirty fix for your common JavaScript:

document.body.innerHTML = document.body.innerHTML.replace(/Special:Badtitle\/Message/g, mw.config.get('wgPageName'));

It changes Special:Badtitle/Message everywhere (maybe the bug affects other messages) including in the edit window for this section, so don't edit it if you add the fix. PrimeHunter (talk) 13:56, 21 November 2024 (UTC)[reply]

I don't see a phabricator ticket. PrimeHunter, do you want to write something up? I'm wondering if this has something to do with * git #016644c4 - Do not pre-parse MessageValue arguments (T380045) by Isabelle Hurbain-Palatin? I did do a quick test to confirm that {{FULLPAGENAMEE}} (or {{FULLPAGENAME}}) are directly producing the Special:Badtitle/Message text, it's not just happening when passed through {{fullurl:}} or when linked.--Ahecht (TALK
PAGE) 15:06, 21 November 2024 (UTC)[reply]

I have created phab:T380519. PrimeHunter (talk) 18:13, 21 November 2024 (UTC)[reply]

I have made a partial fix [5]. It fixes the third and most important link in the message by omitting the bad title. A title is unnecessary in diff links. PrimeHunter (talk) 21:34, 21 November 2024 (UTC)[reply]

[rfc5321-1] J. Klensin (October 2008). Simple Mail Transfer Protocol. Network Working Group. doi:10.17487/RFC5321. RFC 5321. Draft Standard. Updated by RFC 7504. Obsoletes RFC 2821. Updates RFC 1123.

[1]