Wikipedia:Village pump (technical)

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
 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.


Signature using ifeq, present on 800+ pages[edit]

The signature of editor Lambiam present on these 800+ pages contains #ifeq code that I think was supposed to be substed at the time of its insertion, but it apparently was not. It is IMO messy, and it is somehow generating a transclusion of the editor's User talk page on each page in which it is used. It looks like it needs careful replacement by someone with AWB and the knowledge of the right thing to replace it with. – Jonesey95 (talk) — Preceding undated comment added 23:41, 30 June 2022‎ (UTC)[reply]

That page jumped out at me in the query results too. —Cryptic 23:49, 30 June 2022 (UTC)[reply]
The call to Module:Redirect would cause the transclusion. Izno (talk) 23:59, 30 June 2022 (UTC)[reply]
This is what it should be replaced with (spaces cause no harm):
{{subst:#ifeq:{{subst:FULLPAGENAME}}|{{subst:#invoke:Redirect|main|User talk:Lambiam}}
|Lambiam
|
    {{subst:#if:Lambiam
    |[[User talk:Lambiam|Lambiam]]
    |[[User talk:Lambiam]]
    }}
}}
NguoiDungKhongDinhDanh 01:52, 1 July 2022 (UTC)[reply]
Please do not replace the broken signature with anything fancy such as the above. Just replace it with a standard signature. "Lambian ([[User talk:Lambian|talk]])" would be fine. Johnuniq (talk) 08:07, 1 July 2022 (UTC)[reply]
Because of the substitutions, I believe that would result in only [[User talk:Lambiam|Lambiam]] being actually saved to the page, but at that point, one might as well insert that directly. Rummskartoffel 19:17, 1 July 2022 (UTC)[reply]
OOjs UI icon check-constructive.svg Done. ― Qwerfjkltalk 06:07, 6 July 2022 (UTC)[reply]

Possibility to condense notifications of mass deletion discussions?[edit]

I was recently given no less than thirty notifications of deletion discussions at once, all related to a mass deletion discussion (see Wikipedia:Templates for discussion/Log/2022 July 2#Template:VR-K color) by User:Gonnym (ping intentionally left out as Gonnym is not really at fault here). This cluttered up my talk page and caused me to accidentally overlook a discussion I had not answered yet.

Might it somehow be possible that when such a mass deletion discussion is started, each editor involved in the discussion is only given one notice, possibly containing links to each of the pages (in this case, templates) nominated for discussion? JIP | Talk 00:19, 3 July 2022 (UTC)[reply]

There's a wider issue here: we need a tool to create a nomination for many related pages at once. Twinkle does an excellent job of creating each nomination individually but combining them is a pain, often hampered by multiple edit conflicts with early responders as they paste their response into each nomination in turn. Certes (talk) 00:36, 3 July 2022 (UTC)[reply]
I know I've personally asked for Twinkle to be updated to handle that. Doing mass template or category nominations is just a pain atm. AWB is an option, but can work but only if you know the same editor is the creator, however that requires you to manually check each page which makes AWB moot. Gonnym (talk) 08:42, 3 July 2022 (UTC)[reply]
It would be fairly easy to write a script. It would be better if it could be integrated into Twinkle or as an AWB plugin. ― Qwerfjkltalk 19:30, 3 July 2022 (UTC)[reply]
Something like VisualFileChange on commons? It gives a single notification for a bulk action, such as [1]. DMacks (talk) 17:07, 5 July 2022 (UTC)[reply]

Re-ordering a large table, possibly off-wiki[edit]

One-party state has a huge table which was created in Dec 2019 when 4 separate tables were combined. It makes sense to have them in one table, but the previous listings weren't merged, just added end-to-end, so it is now in 4 A-Z sequences. I thought I had a technique to sort the table by copying it out into csv and then into Excel, sorting, and replacing, but that technique lost all the links, flag images, and refs.

Obviously the table can be sorted in real time when looking at it, but it would be better if the code of the table, and thus the default display, were in a logical order.

So: Can someone please either:

  • Point me in the direction of simple tools to sort a large table, or
  • Do some clever editing on this table yourself, to sort it A-Z by country.

I've raised it on the article talk page, where I mentioned another couple of possible sort orders, but as the original tables were mostly sorted A-Z by country I don't think this is controversial. The article had a sudden peak in pageviews last week, as it was the target of "Redactle" puzzle.

Thanks. PamD 09:53, 3 July 2022 (UTC)[reply]

> "Obviously the table can be sorted in real time when looking at it": Mobile users don't have sort option. :( —CX Zoom[he/him] (let's talk • {C•X}) 10:32, 3 July 2022 (UTC)[reply]
They do since last week :) phab:T233340 the wub "?!" 11:26, 3 July 2022 (UTC)[reply]
Yay, they do! —CX Zoom[he/him] (let's talk • {C•X}) 20:10, 3 July 2022 (UTC)[reply]
I attempted this but it's not easy to automate. Presumably it should be sorted by country, so "Tinoquista Costa Rica" appears under C, but there's no easily extracted clue that in this case the second word determines the sort order. Certes (talk) 10:51, 3 July 2022 (UTC)[reply]
@PamD, @Certes, maybe D:WD:OpenRefine? ― Qwerfjkltalk 12:32, 3 July 2022 (UTC)[reply]
@Certes: If you could do the heavy lifting of sorting them by whatever is there, I could go through and upgrade the minority of countries which need a {{sort}} added to fix their alphabetisation. Ah, thinking about it, a better plan: if I go through and add those {{sort}}s anyway - they'd always be needed for re-sorting back to A-Z after sorting on any of the other fields - would you then be able to re-order the code? PamD 16:10, 3 July 2022 (UTC)[reply]
The more I look, the more puzzling it gets: I can't see what it's sorting on at the moment. Possibly the name of the "flagicon"? Puzzling.
If you sort the first column,
  • {{flagicon|Romania}}{{flagicon image|Flag of the Legionary Movement.png}} [[National Legionary State]] seems to sort as "Romania" (so presumably being picked up from the "flagicon" field, as the only mention)
  • {{flagicon image|Flag of Cameroon (1961-1975).svg}}{{flagicon image|Flag of Cameroon.svg}} [[Cameroon|Republic of Cameroon]] sorts as "Republic of Cameroon"
  • {{flagicon|Upper Volta}} [[Republic of Upper Volta|Upper Volta]] sorts as Republic of Upper Volta" (so UV and Cameroon differ: one filed by displayed title, and one by target article title)
  • [[Communist-controlled China (1927–1949)|Yan'an]] sorts as "Yan'an" despite not having a flagicon..
Can anyone explain how this sorting is working? I wonder whether it uses the country with which the flagicon is associated, and the displayed text if there is no flagicon? PamD 16:33, 3 July 2022 (UTC)[reply]
I tried sorting the table using some find-and-replace magic, but the columns do not have consistent sort keys. If someone adds consistently formatted |data-sort-value= entries to the cells in the first column of the table, I should be able to sort it manually. – Jonesey95 (talk) 16:38, 3 July 2022 (UTC)[reply]
I've had a go at adding data-sort-value using Wikidata and some manual fiddling. Anomalies like how to sort Benin/Dahomey and various Chinas remain. Certes (talk) 21:23, 3 July 2022 (UTC)[reply]

When trying to edit I see the left-hand menu covering the edit field[edit]

Making it impossible to edit. Latest version of Chrome. Doug Weller talk 11:22, 3 July 2022 (UTC)[reply]

Works for me. Does it help to reload the edit window with Ctrl+F5 (not F5 alone)? What is your skin at Special:Preferences#mw-prefsection-rendering? Does it happen if you log out? Does it happen in safemode? Please link an example edit url. PrimeHunter (talk) 14:32, 3 July 2022 (UTC)[reply]
@PrimeHunter Ctr5F5 doesn't help. Vector legacy skin. Doesn't happen logged out or in safemode. Example:[2] Doug Weller talk 14:49, 3 July 2022 (UTC)[reply]
It's Chrome specific, just tried Firefox where it works. Doug Weller talk 15:11, 3 July 2022 (UTC)[reply]
It may be a script issue with User:Doug Weller/common.js, User:Doug Weller/vector.js, or something enabled in preferences. Try previewing a blanked version of [3] or [4]. You don't have to save the blank version. My edit links enable safemode but safemode disappears when you preview. A previewed user js file only loads the previewed version. PrimeHunter (talk) 15:15, 3 July 2022 (UTC)[reply]
@PrimeHunter thought I'd solved it, but a preview of my common.js has the same problem. Ditto vector.js It's erratic, I just tried to edit 3 articles, 2 no problem, one the same issue. Doug Weller talk 15:20, 3 July 2022 (UTC)[reply]
@PrimeHunter Switching to Vector 2022 gets rid of the problem but I hate the wasted space. This is a new problem, something's changed somewhere, and I did nothing in the past few days. Doug Weller talk 16:25, 3 July 2022 (UTC)[reply]
And I found the problem. I'd added BitDefender's anti-tracking extension to Chrome. Remove that and no problem. Maybe they updated it recently. Doug Weller talk 15:16, 3 July 2022 (UTC)[reply]
Nope, see above. Doug Weller talk 15:32, 3 July 2022 (UTC)[reply]
And Mono breaks at least one script, the one that gives me details about an editor at the top of their talk page. It's too useful to give up. I really prefer the legacy version of Vector, does that make me a Luddite? Doug Weller talk 16:04, 5 July 2022 (UTC)[reply]
Have you smashed up any textile machinery lately? --Redrose64 🌹 (talk) 21:38, 5 July 2022 (UTC)[reply]
Not this month. Doug Weller talk 05:51, 6 July 2022 (UTC)[reply]

Just got the message "Error contacting the Parsoid/RESTBase server (HTTP 504)" when using reply[edit]

Why is that? Doug Weller talk 11:35, 3 July 2022 (UTC)[reply]

Some servers are down. Replying without the "reply" tool still works. —Kusma (talk) 12:23, 3 July 2022 (UTC)[reply]
This also includes the visual editor on desktop for me. When I tries to save the page, it takes forever to save and would timeout, saying "Error contacting the Parsoid/RESTBase server (HTTP 504)". It doesn't work even when I purged the cache (both "?action=purge" and browser), log out and back. CactiStaccingCrane (talk) 12:29, 3 July 2022 (UTC)[reply]
Error message CactiStaccingCrane (talk) 12:32, 3 July 2022 (UTC)[reply]
Anything that requires parsoid is broken; this includes the visual editor. —Kusma (talk) 12:35, 3 July 2022 (UTC)[reply]
Working now. Doug Weller talk 12:55, 3 July 2022 (UTC)[reply]
Amazing! CactiStaccingCrane (talk) 12:59, 3 July 2022 (UTC)[reply]
I found incident documentation for this outage: https://wikitech.wikimedia.org/wiki/Incidents/2022-07-03_shellbox_request_spike (unfortunately it has few details). My vague understanding is that something related to <score> handling overwhelmed the servers, causing failures in unrelated places. Matma Rex talk 16:01, 5 July 2022 (UTC)[reply]

SUL failing consistently[edit]

Ever since my Firefox upgraded itself recently (I'm now on FF 102), SUL is failing. I am logged in on English Wikipedia, but when I go to any other WMF site, such as meta or commons, I'm shown as logged out. I've tried explicitly logging out on en.wp, and logging in again to get a fresh login cookie, but no joy. Is this a Firefox bug, or MediaWiki? Is there a phab: ticket? --Redrose64 🌹 (talk) 19:00, 3 July 2022 (UTC)[reply]

This is phab:T226797. There is no simple solution. The Firefox team recommended rebuilding the auth system, which is being looked into in the Auth experiments 2022 project.--Snævar (talk) 19:40, 3 July 2022 (UTC)[reply]
You might be able to get it working again if you disable "Enhanced Tracking Protection" for SUL sites. To do that, click the shield icon at the left end of the URL bar while on the site, then click on the switch next to where it says "Enhanced Tracking Protection is ON for this site". The page should then reload and you should be logged in. Rummskartoffel 21:40, 3 July 2022 (UTC)[reply]
Do I do that when still on the en.wp page prior to following a link to commons, or after? --Redrose64 🌹 (talk) 22:07, 3 July 2022 (UTC)[reply]

How to draw a timeline?[edit]

I want to create a event timeline image. I see WP:EasyTimeline, but I get the impression that's not how people do these things these day. Are there better/newer tools? -- RoySmith (talk) 22:54, 3 July 2022 (UTC)[reply]

True. EasyTimeline will be removed eventually. Use either Extension:Graph or HTML based graphs. The largest and most feature rich templates are Module:Graph for Extension:Graph and Module:Chart for HTML. There are also smaller templates. It depends on your usecase which one is more suitable. Snævar (talk) 12:03, 4 July 2022 (UTC)[reply]

Submit an edit request[edit]

Could the big blue button at {{Submit an edit request}}, which is used in (I think) MediaWiki:Protectedpagetext, acquire a little extra text? I'd like it to say "Submit an edit request for changes to {{FULLPAGENAME}}". My hope is that this would discourage people from submitting requests to the wrong page. Or even something like "Submit an edit request (not for changes to articles)" for requests outside the mainspace. WhatamIdoing (talk) 00:23, 4 July 2022 (UTC)[reply]

There are very few misplaced edit requests, and generally the people making requests aren't reading any of the instructions anyway. That said, it doesn't hurt to add even more text. ScottishFinnishRadish (talk) 00:50, 4 July 2022 (UTC)[reply]
Very few in the mainspace, maybe. But see also [5][6][7][8][9][10][11][12], not to mention the apparently endless supply of empty requests. WhatamIdoing (talk) 03:40, 4 July 2022 (UTC)[reply]
Yeah, 8 out tens of thousands, and they all look to have been been appropriately handled. I don't think adding even more text will help the thousands of blank requests that are created despite the instruction text in the edit window and the pre edit request explanatory page. ScottishFinnishRadish (talk) 08:41, 4 July 2022 (UTC)[reply]
I don't think it will add anything since the page title will be shown at the top of the page, and it states "This page is..." quite clearly, implying that the edit request that would be submitted is specific to the open page. Longer text only adds more text for users not to read and could end up with a multi-line button on width limited smaller screens. Clear and concise is normally the best approach. There is no "Read {$pagename} article | Edit the {$pagename} article | View the history of the page {$pagename}" as the three main buttons at the top of a page for a reason. Terasail[✉️] 00:58, 4 July 2022 (UTC)[reply]
If someone does incorrectly place an edit request, a responder only has to notify the user of the error, either with {{EP|mis}} or a personalised reply. I am not sure that the problem is common enough to require this change where a responder can just guide the user to the correct place. Terasail[✉️] 01:05, 4 July 2022 (UTC)[reply]
AFAICT we usually just blank them, rather than notifying or explaining. WhatamIdoing (talk) 03:41, 4 July 2022 (UTC)[reply]
My understanding was that only empty edit requests or clear policy violations were blanked rather than simply misplaced requests. Terasail[✉️] 13:03, 4 July 2022 (UTC)[reply]
I'm sure that's the usual practice for articles, but consider, e.g., the first one I linked above, which was reverted three minutes after it was posted. This might not be the best practice, but it does not seem to be unusual, either. WhatamIdoing (talk) 18:31, 4 July 2022 (UTC)[reply]
Unambiguous self promotion normally is immediately reverted. ScottishFinnishRadish (talk) 21:45, 4 July 2022 (UTC)[reply]
Wikipedia:Autobiography does not say that you should revert a newbie who is trying (however misguidedly) to write an autobiography. I'd rather that this newbie, and all the others as well, had known up front that clicking this particular blue button would do them no good at all. WhatamIdoing (talk) 22:59, 4 July 2022 (UTC)[reply]
I know its annoying to deal with others' mistakes, but this expectation that we often put out there that people should not make mistakes (and that adding text will help them not to make mistakes) seems unachievable to me. Mistakes are how people learn. We need to give people the opportunity to learn, or they won't even be here at all. This is after all Wikipedia, not the paper version of Encyclopedia Brittanica. —TheDJ (talk • contribs) 11:02, 4 July 2022 (UTC)[reply]
As a general rule, I'd say that substantially reducing text would help. Most people probably look right past the oblong gray blur of text there, but if they read anything, they read the text on the button itself.
Another good approach would be offering options. Perhaps we need one button that says "Request a change to the {{FULBASEPAGENAME}} page" plus another button that says "Ask for help with another page or something else" (maybe pointing to the Teahouse). If you only give people one button, they'll use it for everything. WhatamIdoing (talk) 18:38, 4 July 2022 (UTC)[reply]
This is a good point. We also see that with uploading. Ppl primarily care about uploading and not about licenses etc. So they will choose whatever allows them to achieve their goal. —TheDJ (talk • contribs) 08:14, 5 July 2022 (UTC)[reply]
If there's a page getting hit particularly often, you can try changing the notice for just that page by creating an appropriate subpage of Template:Editnotices/Protection/. Anomie⚔ 10:59, 5 July 2022 (UTC)[reply]
WP:V brought me here, but the problem is more diffuse than that. Also, Template:Editnotices/Page/Wikipedia:Verifiability already exists. WP:Nobody reads the directions, so it probably doesn't do much good. It particularly won't do much good when the one bit that the person sees says "Submit an edit request", with no indication that this means "an edit request for this specific page, which is probably not the one that you want, and not for a generic queue that will ultimately get routed to the right place". WhatamIdoing (talk) 15:55, 5 July 2022 (UTC)[reply]

Need review of recent contents of a category[edit]

Could somebody who has the ability to work with past dumps run a scan and provide me with the contents of Category:Austro-Hungarian films as of the last available dump date before June 27, 2022? It's been erroneously emptied out, so I need to reconstruct it. The output can be saved to my sandbox at User:Bearcat/Random.

(I tried processing a dump myself this afternoon, and failed hard.)

Thanks. Bearcat (talk) 01:36, 4 July 2022 (UTC)[reply]

The Internet Archive has a snapshot from 30 April.[13] PrimeHunter (talk) 03:22, 4 July 2022 (UTC)[reply]
See also "Category membership" at Help:Watchlist#Limitations. In an alternative account with a small watchlist I can see around 80 removals by Qwerfjkl (bot) since 23 June. PrimeHunter (talk) 03:29, 4 July 2022 (UTC)[reply]
@Bearcat, I'm planning on mass reverting any edits by the bot that removed more than one category, and handling them separately, probably with a pywikibot script. It would be easier for me to handle these along with all the other pages, so could you hold off on reconstructing the category (unless it's too late)? ― Qwerfjkltalk 20:01, 4 July 2022 (UTC)[reply]
It's already been done Bearcat (talk) 20:01, 4 July 2022 (UTC)[reply]

Stray Brackett[edit]

I just created an article titled Battle of Punished Woman's Fork. (The article is still a stub, but I'm expanding it.) At the end of the summary paragraph is a stray bracket. In trying to edit the article, I can't find the bracket to delete it. Can somebody delete it? Thanks. Sorry to be so incompetent. Smallchief (talk) 11:06, 4 July 2022 (UTC)[reply]

  • Ignore the request. The stray bracket seems to have disappeared when I added more text. Another unexplained riddle of technology? Smallchief (talk) 11:13, 4 July 2022 (UTC)[reply]
It didn't disappear but remained at the end of the article which only consisted of the summary paragraph when you posted. Your added text just meant that the article ended later. I have removed the bracket.[14] PrimeHunter (talk) 11:46, 4 July 2022 (UTC)[reply]

How do I disable the new drop down box for Add Topic[edit]

This has to be one of the worst ideas ever. It keeps adding "no wiki" in the middle of sentences, and makes it a lot harder to just add a simple topic, because you have to go in and delete what it added that you didn't want. It's horrible. How do I disable it completely? — Maile (talk) 12:40, 4 July 2022 (UTC)[reply]

"go to Special:Preferences#mw-prefsection-editing-discussion and turn it off". DuncanHill (talk) 12:51, 4 July 2022 (UTC)[reply]
Thank you — Maile (talk) 13:13, 4 July 2022 (UTC)![reply]
You're right about the new drop down, btw. DuncanHill (talk) 13:16, 4 July 2022 (UTC)[reply]
Is there a way to switch default to "Source editor" in the Add topic/reply system? The "visual editor" is non-intuitive for anyone who understands the markup. Source editing also shows a live preview below, so new editors won't find it hard to use. And it's better for them to learn by doing too, as many templates all over Wikipedia still do not support visual editing. —CX Zoom[he/him] (let's talk • {C•X}) 13:46, 4 July 2022 (UTC)[reply]
@CX Zoom "default" - as in for all non-logged in users as well? I think you are overestimating the subclass of "new editors" that are brand-new editors. — xaosflux Talk 21:30, 4 July 2022 (UTC)[reply]
That is already the default, same as for article editing. Matma Rex talk 22:40, 4 July 2022 (UTC)[reply]
@Maile66, it looks like you made your first-ever edit in the Reply tool here at VPT, and were put into the wikitext source mode by default. Your next edit was also here, and it looks like you switched to the visual mode (maybe trying out all the buttons?). It looks like you never switched back. The Reply and New Topic tools use the same settings, so if you switch to the visual mode for Reply, you'll be in the visual mode for New Topics.
Fortunately, if you don't like it (or if you want to add templates to your comments), the switch is easy and sticky: Just click the "Source" tab, and it will automatically remember your choice until you change it again. Whatamidoing (WMF) (talk) 01:39, 5 July 2022 (UTC)[reply]
Thanks for looking into this. I'll try to remember to never use the Reply option again. — Maile (talk) 01:48, 5 July 2022 (UTC)[reply]
You can turn it off in prefs if you want, but you could also just switch it to source mode, and the other one will follow suit, too. Whatamidoing (WMF) (talk) 02:03, 5 July 2022 (UTC)[reply]
Yes! I've turned it off in prefs. Thanks. — Maile (talk) 02:13, 5 July 2022 (UTC)[reply]

Tech News: 2022-27[edit]

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

Changes later this week

  • The new version of MediaWiki will be on test wikis and MediaWiki.org from 5 July. It will be on non-Wikipedia wikis and some Wikipedias from 6 July. It will be on all wikis from 7 July (calendar).
  • Some wikis will be in read-only for a few minutes because of a switch of their main database. It will be performed on 5 July at 07:00 UTC (targeted wikis) and on 7 July at 7:00 UTC (targeted wikis).
  • The Beta Feature for DiscussionTools will be updated throughout July. Discussions will look different. You can see some of the proposed changes.
  • This change only affects pages in the main namespace in Wikisource. The Javascript config variable proofreadpage_source_href will be removed from mw.config and be replaced with the variable prpSourceIndexPage. [15]

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

19:30, 4 July 2022 (UTC)

Pending changes again[edit]

Tracked in Phabricator
Task T234743

Is it clear why this edit on a pending changes protected article was automatically accepted? The user is not autoconfirmed and has no flags. Thanks. Ymblanter (talk) 20:19, 4 July 2022 (UTC)[reply]

Not sure, however please note that phab:T234743 has been open for a few years about pendingchanges not working, sometimes. — xaosflux Talk 21:27, 4 July 2022 (UTC)[reply]
Are they not autoconfirmed? From what I see they have been since 2021. Terasail[✉️] 21:29, 4 July 2022 (UTC)[reply]
MySun is autoconfirmed, the edit prior to theirs was accepted - so yes, this appears to have worked properly this time. @Ymblanter: why do you think they are not AC? — xaosflux Talk 21:51, 4 July 2022 (UTC)[reply]
Note, that article is also SPP, so everyone editing it will be autoconfirmed, making the PC1 mostly moot. — xaosflux Talk 21:53, 4 July 2022 (UTC)[reply]
They have only made 14 edits in total, I thought they need more (30 or 50?) for an autoconfirmed. Thanks anyway, it is clear that PC1 is not really appropriate for this article, but this is not a technical question.--Ymblanter (talk) 05:28, 5 July 2022 (UTC)[reply]
It's only 10 edits and four days for autoconfirmed here. Graham87 09:19, 5 July 2022 (UTC)[reply]
I see, thanks. Ymblanter (talk) 10:27, 5 July 2022 (UTC)[reply]

Glitches on Featured and good articles when using scripts[edit]

See here about an odd glitch in the duplicate link checker, that is only affecting Featured and good articles. There is a similar glitch, also only on Featured articles best I can tell, in the prose size script installed in tools. It is also generating duplicate info, only on FAs. So perhaps the glitch is not coming from the scripts, but from something else in the FA or GA template? The writer of the dup link script hasn't edited since Jan and hasn't responded; maybe someone else can locate the issue. SandyGeorgia (Talk) 21:56, 4 July 2022 (UTC)[reply]

@SandyGeorgia: Line 17 currently is:
var $content = isVisualEditor ? $(".ve-ce-documentNode.ve-ce-branchNode") : $(".mw-parser-output")
It should have been:
var $content = isVisualEditor ? $(".ve-ce-documentNode.ve-ce-branchNode") : $($(".mw-parser-output", "#mw-content-text")[0])
I'm unsure how this will help you (other than forking the script yourself) if its author has been inactive for quite a while. NguoiDungKhongDinhDanh 02:09, 5 July 2022 (UTC)[reply]
I was hoping someone would find instead that the error was in one of the templates, in which case we could fix it. I guess we're stuck. Thanks for looking ! SandyGeorgia (Talk) 03:59, 5 July 2022 (UTC)[reply]
Interface admins will take bug fix edit protected requests. You should file one at the appropriate talk page. Izno (talk) 04:16, 5 July 2022 (UTC)[reply]
Thx, Izno, but it still makes no sense to me why both of these scripts are failing only on articles that have a GA or FA template? SandyGeorgia (Talk) 04:17, 5 July 2022 (UTC)[reply]
Basically, Evad was looking for a (supposed-to-be) single element that bears a class named .mw-parser-output (without the leading dot). This class marks the outputs of the wikitext parser, which is the content of the page, and, unfortunately, indicator templates (e.g. FA/GA star, {{pp}} etc.). NguoiDungKhongDinhDanh 04:49, 5 July 2022 (UTC)[reply]
Ah, thanks again. I do not know where or how to request these be fixed by "interface admins". SandyGeorgia (Talk) 04:55, 5 July 2022 (UTC)[reply]
I've made an edit request. Many thanks to all of you for taking a look at this! Extraordinary Writ (talk) 05:07, 5 July 2022 (UTC)[reply]
The change for indicators to output .mw-parser-output is also fairly recent, so that is why these scripts have had issues only lately. Izno (talk) 06:59, 5 July 2022 (UTC)[reply]
I have been unable to figure where to find the host of the prose size script that I have installed in tools on the left-hand side of screen ... sorry, techno-dummy ... but that needs similar attention. Over at WT:FAC, I am told any of these people can do the fixing:
Maybe this is it? Wikipedia:Prosesize ? I know I installed it way back when DrPda wrote it, so maybe I have an old version or something? SandyGeorgia (Talk) 16:02, 5 July 2022 (UTC)[reply]
$($(".mw-parser-output", "#mw-content-text")[0]) seems unnecessarily complicated. Wouldn't $("#mw-content-text .mw-parser-output").first() do the job? Nardog (talk) 07:03, 5 July 2022 (UTC)[reply]

aligning table right[edit]

I've tried and searched and tested but I cannot figure out how to align a table to the right margin. Does someone know how to do this? Thank you.

https://en.wikipedia.org/wiki/Talk:2021%E2%80%932022_inflation_surge#table

soibangla (talk) 10:37, 5 July 2022 (UTC)[reply]

Do you mean aligning the text in each cell (H:TABLE#Cell content indenting and padding recommends style="text-align:right") or moving the whole table to the right of the screen (like H:TABLE#Float table left or right)? DMacks (talk) 10:56, 5 July 2022 (UTC)[reply]
floatright is what I was looking for and it works! Thank you! soibangla (talk) 11:26, 5 July 2022 (UTC)[reply]

Help with redirect in JavaScript[edit]

The website xinhuanet.com has thousands of links that a redirecting to the home page. For example http://www.xinhuanet.com/english/2018-09/11/c_137460450.htm .. viewed in a browser it first redirects to http://www.xinhuanet.com/webSkipping.htm then to the home page. The webSkipping page contains an error message in Chinese The content you viewed has expired and been archived; thank you for your attention to Xinhuanet. This is simple enough. However if you view the page with JavaScript disabled (or with curl), the underlying content is still there - it has not been "archived". Further, looking at the JavaScript code there appears to be some kind of logic decision involved in determining when the webSkipping page is served versus the actual content, something is triggering the redirect that is yes or no. I'm not too familiar with JavaScript can anyone make out what might be happening? Maybe it works from Chinese IPs? Or the redirect expires at some point? Ultimately would like to determine if these pages should be converted to archive URLs or left alone. -- GreenC 16:20, 5 July 2022 (UTC)[reply]

@GreenC: Here's the script they use: pageCore.js. According to this file, if you access a page whose URL doesn't contain content_, you will be redirected to webSkipping.htm (and then the home page). Comments are mostly encoded so I'm not sure why this was used. NguoiDungKhongDinhDanh 03:05, 6 July 2022 (UTC)[reply]
This unicode converter says 是否为content_细揽 means 术否为content_绠揽. NguoiDungKhongDinhDanh 03:14, 6 July 2022 (UTC)[reply]
User:NguoiDungKhongDinhDanh: Interesting, thanks. It's weird because even links with content_ redirect: http://news.xinhuanet.com/edu/2009-04/09/content_11152862.htm .. I'm beginning to think this site just has a lot of dead links and soft-404s and not overthink too much. Some sites can bypass redirects by using a new URL such as changing "/c_" to "/content_" but that doesn't work either. -- GreenC 03:42, 6 July 2022 (UTC)[reply]
I accessed that link and was not redirected anywhere. It simply showed me a banner. NguoiDungKhongDinhDanh 04:02, 6 July 2022 (UTC)[reply]

"Create new section" tab and new editing interface[edit]

There has been a new editing interface added for the "Create new section" tab. There was an option to revert to the classic interface but this has disappeared. Why/how do I get it back. Regards, Cinderella157 (talk) 03:24, 6 July 2022 (UTC)[reply]

Disable "Enable quick topic adding" at Special:Preferences#mw-prefsection-editing. PrimeHunter (talk) 05:50, 6 July 2022 (UTC)[reply]
Thankyou PrimeHunter. I would note that the interface interferes with WP functions (eg AfD) that require adding a subst template. Cinderella157 (talk) 12:03, 6 July 2022 (UTC)[reply]
@Cinderella157 If you click the "Source" link on the top right of the new tool to switch to source mode, substing templates works just fine. You can also add dtenable=0 to the URL if there are specific cases where it should never be used. --Ahecht (TALK
PAGE) 14:06, 6 July 2022 (UTC)[reply]

Hidden category "Use dmy dates" truly is hidden on Ventricle (heart)[edit]

I do a lot of date format auditing and the majority of the time, the templates that create that hidden tracking category are plainly visible in the article. One in a great while though, the source of the hidden category is a mystery. In other words, the template isn't actually in the article, but is usually transcluded from another (navigation) template. With this article though, I haven't found the {{Use dmy dates}} template on any of the templates in the article. Is the issue me? Dawnseeker2000 10:19, 6 July 2022 (UTC)[reply]

It's coming from Template:Cardiovascular reference ranges (transcluded as {{Cardiovascular worksheet}} from Ventricle (heart)#Volumes). Looks like someone added it without <noinclude>...</noinclude> back in 2012. Anomie⚔ 10:31, 6 July 2022 (UTC)[reply]
@Dawnseeker2000 it is coming in via Template:Cardiovascular reference ranges, via the redirect from Template:Cardiovascular worksheet in the "Volumes" section. — xaosflux Talk 10:33, 6 July 2022 (UTC)[reply]
Thanks for the extra eyes 😳 Dawnseeker2000 22:45, 6 July 2022 (UTC)[reply]
If "Use dmy dates" should not be used in the template namespace, then the remaining cases of where it is used without noinclude should be removed too. Searching for it shows several more.--46.182.184.86 (talk) 10:05, 7 July 2022 (UTC)[reply]
I have checked and modified all of the transclusions of this template in template space so that they are either removed or noincluded. I have also updated the documentation. There was a 2021 discussion on the template's talk page, but nothing had been done about it. – Jonesey95 (talk) 15:58, 7 July 2022 (UTC)[reply]

Add shortcore for the redirection[edit]

Please, add You the shortcore for the redirection in MediaWiki:Gadget-charinsert-core.js. Dušan Kreheľ (talk) 14:30, 6 July 2022 (UTC)[reply]

@Dušan Kreheľ what? If you would like to suggest an edit to that script, please open an edit request at MediaWiki talk:Edittools with exactly what you would like done. — xaosflux Talk 14:36, 6 July 2022 (UTC)[reply]

What happened with MediaWiki:Titleprotected?[edit]

Tracked in Phabricator
Task T312317

I noticed that the titleprotected message no longer displays when creating pages that you can't create because they are protected. Was this message deprecated or what? Aasim - Herrscher of Wikis 18:06, 6 July 2022 (UTC)[reply]

@Awesome Aasim hmmm - seems like a redlink page, where protection level is not available to the user gets: MediaWiki:Noarticletext-nopermission, this uses Template:No article text here, which has been updated frequently. — xaosflux Talk 18:23, 6 July 2022 (UTC)[reply]
@Xaosflux Maybe I should have been clearer - for a user with the inability to create a protected page, such as by creating This page does not exist, there is just the top message that says only admins can create that page, but there is no bottom message giving the explanation for titleprotected. Aasim - Herrscher of Wikis 18:26, 6 July 2022 (UTC)[reply]
Depending on how you end up there, you may also get Mediawiki:Protectedpagetext or Mediawiki:Nocreatetext, which may lead you to versions of Template:protected page text or Template:no article text. I'm not sure exactly when that other message got diverted around for these usecase in the software - is there something specific you want to try to improve or are you just curious? — xaosflux Talk 18:32, 6 July 2022 (UTC)[reply]
I am wondering if this is a bug or what. I was going to suggest that "submit a page creation request" be added to the message to allow the user to create a protected edit request. However, the titleprotected message which gives instructions on what to do is not at all being shown.
What is being displayed is something similar to this:
Interface message displayed

You do not have permission to create this page, for the following reason:

Page notice
The message of MediaWiki:Titleprotected is not at all displayed here. It should be, that or the message gets moved to MediaWiki:Protectedpagetext. Aasim - Herrscher of Wikis 22:02, 6 July 2022 (UTC)[reply]

It looks like an attempt to create a page that's restricted to intadmins (e.g. User:192.0.2.16/common.js) is also not showing MediaWiki:Titleprotected (although the message that does show is different). Pages that are blocked by the title blacklist (e.g. Wikipedia:∀∀∀∀∀) also don't show it. So maybe MediaWiki:Titleprotected just isn't functional at all at the moment – I can't find any way to trigger it (at least not by using ?action=edit URLs). --ais523 22:14, 6 July 2022 (UTC)

These are the only places it is referenced, and some of these are false positives for other messages. --Izno (talk) 23:01, 6 July 2022 (UTC)[reply]
@Izno Should I open a ticket on phabricator? Or should we just adapt to this change? Aasim - Herrscher of Wikis 00:36, 7 July 2022 (UTC)[reply]
@Awesome Aasim so long as any configurable message is displaying, I'm not seeing what the problem is? Is the default text for the message that displays for a specific use case inaccurate? Especially if it is in usecases that have a normal workflow. In your example page:
https://en.wikipedia.org/w/index.php?title=User:192.0.2.16/common.js&action=edit yields a page with permissionserrorstext-withaction, customjsprotected, and nocreatetext.
While
https://en.wikipedia.org/w/index.php?title=User:192.0.2.16/common.js&action=edit&redlink=1 has a server side redirect since it isn't creatable, drops you to reading view and yields a page with noarticletext-nopermission
— xaosflux Talk 01:05, 7 July 2022 (UTC)[reply]
I don't think you understand @Xaosflux. Specifically, the MediaWiki:Titleprotected message is supposed to show up when the page title is protected from creation, not when the page is unable to be created due to lacking permissions or due to the CSS/JS/JSON page being in someone else's user space. For example, This page does not exist, Test page, and Red link example are pages protected from creation. In each of these cases, when attempting to create the page, two messages should displayed: MediaWiki:Protectedpagetext and MediaWiki:Titleprotected. The latter message is not being shown. This sounds like a bug. Aasim - Herrscher of Wikis 01:13, 7 July 2022 (UTC)[reply]
@Awesome Aasim I have a feeling that the messages outputs have just been updated to use new messages and some documentation is missing, but sure open a bug and someone will check in to that and verify. — xaosflux Talk 01:18, 7 July 2022 (UTC)[reply]
See phab:T312317. Aasim - Herrscher of Wikis 01:31, 7 July 2022 (UTC)[reply]

Looking at the source code, the message is supposed to appear on an attempt to edit a protected title, i.e. a page that appears on Special:ProtectedTitles, and not in any other context. I tried to edit one of those pages, and it didn't appear, so I'm guessing it's just broken at the moment. (Some of the relevant source code is marked as "deprecated", so maybe it doesn't work or is being moved to a new system.) --ais523 01:05, 7 July 2022 (UTC)

I have a feeling that MediaWiki:Titleprotected is the low-level error for a permission failure, but most if not all code paths that would display it are checking for the error condition and displaying a different message first. The low-level message still needs to exist in case there's still a code path somewhere that doesn't do a higher-level check first. Anomie⚔ 11:26, 7 July 2022 (UTC)[reply]

Dark mode Gadget and Vector 2022 skin[edit]

2022-07-07 Light & Dark Mode Vector 2022.png

Hello, I'm using Vector 2022 Skin and Dark mode Gadget. In the recent Vector 2022 skin, the title has moved up the tab. However, there is a problem here. There is no problem in light mode, but in dark mode, another line appears above the title (shown in red squares above). I don't know if this is a bug in a Vector or a bug in a Dark mode Gadget. Bluehill (talk) 11:17, 7 July 2022 (UTC)[reply]

It is because .mw-body has a 1px transparent border-top property which is causing the line to appear on the dark mode from what I understand. It is transparent with a white background, just not with dark mode, you could always disable this with custom css or change the color to the background color. Terasail[✉️] 11:25, 7 July 2022 (UTC)[reply]

Can't preview from Chrome using Vector 2022[edit]

I finally gave up and switched to Vector 2022 (see my post above) as it seems to be becoming the standard. But I can't preview from Chrome but can from Firefox. Doug Weller talk 16:44, 7 July 2022 (UTC)[reply]

At the risk of sounding like a broken record - have you disabled your personal user scripts and any special browser extensions and retested? — xaosflux Talk 17:33, 7 July 2022 (UTC)[reply]
I probably should have done that first, I was hoping there might be an easier answer. I’m finding everything a bit difficult with this damn chemo but I’ll do that tomorrow. Scripts are easier to disable now and that helps, but I can start by just blanking the relevant pages, easy to revert if it makes no difference. Doug Weller talk 17:41, 7 July 2022 (UTC)[reply]
@Xaosflux could it be as simple as not having a Vector 22.js file? Blanking Vector.js worked, but that might have been a script there. Doug Weller talk 08:37, 8 July 2022 (UTC)[reply]
@Doug Weller I think that right now vector-2022 skin loads both your Special:Mypage/vector.js and Special:Mypage/vector-2022.js scripts. — xaosflux Talk 09:26, 8 July 2022 (UTC)[reply]
@Xaosflux I don't have User:Doug Weller/vector-2022.js - easy to install but do I transfer my scripts there from vector.js? Doug Weller talk 10:00, 8 July 2022 (UTC)[reply]

Infobox images stacked instead of side-by-side[edit]

Hello, it seems like there is an issue occurring with {{Infobox sports rivalry}} on Yankees–Red Sox rivalry. On that article, the logos in the infobox are stacking instead of being side-by-side with the team names underneath. The correct infobox should look something like Big Game (American football). Any help would be appreciated. -- LuK3 (Talk) 18:11, 7 July 2022 (UTC)[reply]

@LuK3 I can tell you that it is {{Multiple image}} that is breaking the logos and making them stack because of Template:Multiple image/styles.css. It adds: "display:flex" to the infobox images. Terasail[✉️] 18:48, 7 July 2022 (UTC)[reply]
I updated the module and it should be fixed now. Terasail[✉️] 19:01, 7 July 2022 (UTC)[reply]
Terasail, thank you! I knew it was most likely something above my head. -- LuK3 (Talk) 20:07, 7 July 2022 (UTC)[reply]

Template:Uw-ew not substituting properly[edit]

When I tried to subst Template:Uw-ew onto someone's talkpage, any text I put in the additional text field disappeared, and I had to add it manually afterwards Nigel Ish (talk) 18:13, 7 July 2022 (UTC)[reply]

It should work find as long as you add the template in the format {{subst:uw-ew|pagenamehere|additionaltexthere}}. @Nigel Ish Do you have an example of this failing to subst additional text? Terasail[✉️] 18:21, 7 July 2022 (UTC)[reply]
It didn't here - the text in the additional text field completely disappeared - this was using the new and improved talk page editing system.Nigel Ish (talk) 18:25, 7 July 2022 (UTC)[reply]
Your text probably had en equals sign. The documentation says: use "2=" if the additional text contains an equals sign (such as a URL). The issue is the the second bullet at Help:Template#Usage hints and workarounds. PrimeHunter (talk) 20:58, 7 July 2022 (UTC)[reply]
Yes it did - there was a diff in the text - diffs are perfectly sensible things to include in things like edit warring templates, so this ideally needs to be fixed, or at least explicit warnings rolled out to all the user warning templates.Nigel Ish (talk) 07:23, 8 July 2022 (UTC)[reply]

Interface grammatical error[edit]

Moved to MediaWiki talk:Gadget-contribsrange.js. --Izno (talk) 05:28, 8 July 2022 (UTC)[reply]

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