Wikipedia:Village pump (technical)

  (Redirected from Wikipedia:VPT)
Jump to navigation Jump to search
 Policy Technical Proposals Idea lab WMF Miscellaneous 
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).

Newcomers to the technical village pump are encouraged to read these guidelines prior to posting here. 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.

Frequently asked questions (FAQ) (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 set a 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 Wikipedia: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 Metrics.
« Archives, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187

Background color[edit]

Hi, could anyone tell me is there an option/setting to change the (white) background color of WP (if yes, and what options are available)? Thank You!(KIENGIR (talk) 17:06, 10 January 2021 (UTC))

@KIENGIR: there are a few ways to go about this, first can you tell us how you normally view wikipedia? (Desktop, Tablet, Mobile, or Mobile App) — xaosflux Talk 17:24, 10 January 2021 (UTC)
There is no simple on/off option that will do that for you, but a simple user script can let you change the colour of any part of the page. What do you want changed? — GhostInTheMachine talk to me 18:20, 10 January 2021 (UTC)
Destop (which inludes as well laptop).
GhostInTheMachine, I consider watching too much bright white component would be not the best, I'd consider a less warm color which may work good with the black text color without having a visual interlace harming (= sorry I cannot phrase it better, it's like you'd put a bright purple text on a black background). So what I want to change is not the color of WP margins (headlines and sidelines), but the rest which serves the background of anything else, which is white.(KIENGIR (talk) 08:30, 11 January 2021 (UTC))
If it bothers you in Wikipedia, then I presume it bothers you equally on other websites that are not Wikipedia, and that also have bright white backgrounds? If this is the case, you can find the answer by googling change Chrome default color scheme (change "Chrome" to the name of the browser you use). Or try this search. Mathglot (talk) 09:13, 11 January 2021 (UTC)
@KIENGIR: Desktop "dark mode" is hard (see phab:T199634 for progress on the effort). You may customize your standard desktop background my updating this page: Special:MyPage/vector.css, and can request styling of many elements, for example putting:
.mw-body {
    background-color: #ccc;
on that page will change the main article body from whitish to grayish. — xaosflux Talk 11:59, 11 January 2021 (UTC)
especially I considered just in WP, and I don't use Chrome but Firefox. However, I managed to scale the exact background and text parameters, and I've found a good composition, however, the problem is then I don't see properly the diff marker color adjustment (= opening a diff, in which the changes are covered with a slightly bluish box, in which the text color became as well marked more darker)...
before analyzing in more details your suggestion - which may have been solved meanwhile as mentioned above, could you suggest the solution the newly mentioned emerging issue? Thank You(KIENGIR (talk) 12:23, 11 January 2021 (UTC))
@KIENGIR: just as you may use a personal style for most any element, you can also style those - just look at the source to find what the identifier is, then add the styling to adjust it; my example above was very simple for just the ".mw-body" id - but you can use it for most anything. — xaosflux Talk 15:30, 11 January 2021 (UTC)
Thanks your recommendation works, this green is fine (but still only if I put brightness & contrast to nil and Gamma to the minium allowed - 0.5 by this constellation). In this case the adjustment markers are as well ok. However I should dig in more into the issue on the browser examiner/console to locate all needed parameters and test their adjustments alltogether. Maybe I'll go ahead when having more time. Thanks for now!(KIENGIR (talk) 16:25, 11 January 2021 (UTC))
You're welcome KIENGIR - for your use case you may be better off with a browser extension, they may be more robust. The benefit of using the vector.css file is that it will follow you to other browsers and computers you may use (while logged in). — xaosflux Talk 16:28, 11 January 2021 (UTC)
@KIENGIR: I recommend you take a look at Dark Reader, a browser extension that automatically generates a dark theme from a site's normal colour scheme. It doesn't work perfectly 100% of the time – for example, it rarely produces unreadable yellow-on-yellow text –, but Wikipedia is normally usable very nicely with it. – Rummskartoffel (talk • contribs) 23:05, 16 January 2021 (UTC)
thank you I will test it!(KIENGIR (talk) 23:14, 16 January 2021 (UTC))
There is Preferences|Gadgets/Appearence - Use a black background with green text. DuncanHill (talk) 23:26, 16 January 2021 (UTC)
@KIENGIR:, addressing only your point about the difficulties with DIFF, I entirely agree; that you can easily fix however. It's especially difficult to see differences that consist only of white space, which prompted me to alter the DIFF program style I see. I thought this was in my common.css, but it's not; now I'm not sure where I made that change. Maybe someone else can tell you (and remind me, at the same time!). Cheers, Mathglot (talk) 05:34, 21 January 2021 (UTC)
@Mathglot: No, it's the third of these lines in User:Mathglot/vector.css:
/* Per [[MediaWiki talk:Monobook.css/Archive 4#Better rendering for .diffchange in diff's...]] */
/* See also: Wikipedia:Catalogue of CSS classes, Wikipedia:Village_pump_(technical)/Archive_37#Diff coloring again */
.diffchange {padding: 0px 2px 0px 2px; border: 1px dotted red; margin: 0px 1px 0px 0px}
so see MediaWiki talk:Monobook.css/Archive 4#Better rendering for .diffchange in diff's... and Wikipedia:Village pump (technical)/Archive 37#Diff coloring again. --Redrose64 🌹 (talk) 21:32, 21 January 2021 (UTC)
Redrose already reminded you, I also applied, it gives a little dotted border, however, regardless how many clues gave Redrose, I could not change the diffcolors (or I thought I did not but had no effect, you may check my vector.css edit history, I have been to lame and missed something?). Btw. I tried Rummskartoffel's suggestion and installed darkreader, seems work quite fine in total dark, even with diff markering, however if it is conflated with my vector.css set backgound color set know (kinda green), diffs would be again a problem. Anyway, I wish to successfully parametrize addeddifchange and "deletediffchange" cover color...what did I wrong? Thank You(KIENGIR (talk) 02:40, 22 January 2021 (UTC))

Why is Wikipedia logging me out?[edit]

It could be because of WP's 20th anniversary. But why is Wikipedia logging me out when I load a page? Sometimes even if I log back in it won't stay logged in. And I do have cookies enabled! Nearly but not perfect (talk) 05:23, 15 January 2021 (UTC)

No issues here. Amaury • 06:48, 15 January 2021 (UTC)
I had the same issue, but it seems to have stopped now. Whatever the reason was, it wasn't too cool. I didn't catch it at first and made one edit while logged out. If it was something that affected lots of people, then lots of people got their IP addresses revealed. -- Marchjuly (talk) 07:02, 15 January 2021 (UTC)
@I'm not perfect but I'm almost: Even if you have cookies enabled, the act of logging in does not guarantee that you will be served pages that indicate that you are still logged in. A number of factors are at work together: every time your browser requests a page, it sends the cookie at the same time, this is checked against the cookie table on the Wikimedia servers; only if this is present and valid are you treated as being logged in. So any of the following can cause you to be treated as logged out:
  • your browser sends the wrong cookie, a corrupt cookie, or no cookie at all
  • you have a dodgy internet connection causing the cookie to be damaged, received late, or lost altogether
  • the Wikimedia servers might be out of synchronisation (if the server that receives your cookie has a table that is different from the table on the server that first sent you the cookie)
For any given rendered page, several requests are sent to the server - one for the page content; one each for the various style sheets and Javascript files; one each for every single image. Even for a modest page like HTTP cookie that's a lot of requests (my browser sends 48), and each needs to be accompanied by your login cookie. There are lots of points of potential failure; the surprise is that it works well virtually all of the time. --Redrose64 🌹 (talk) 10:30, 15 January 2021 (UTC)
After logging in today, I started to get logged out just like I'm not perfect but I'm almost described. I stayed logged in after disabling JS. It seems to be related to one of the Gadgets, as it stopped after I disabled them. However, I'm not sure which one causes the problem yet. - Flori4nK tc 12:48, 19 January 2021 (UTC)
Nevermind, I reenabled all gadgets one-by-one and the problem seems to be gone. - Flori4nK tc 12:58, 19 January 2021 (UTC)
So I'm not the only one? This happened just a bit ago, and the only way for me to stay logged in was checking "keep me logged in" which I normally don't like doing. Sro23 (talk) 16:38, 20 January 2021 (UTC)
@I'm not perfect but I'm almost, Marchjuly, Flori4nK, and Sro23: Does WP:COOKIES help? Particularly the "I get logged out just after logging in" bit. --Redrose64 🌹 (talk) 23:30, 20 January 2021 (UTC)
@Redrose64: Cookies are enabled and I have been using the exact same (containerized, regularly reinstalled using a script) setup for 1.5 years. The cookies could only have been blocked by one extension, uMatrix, but * and * are whitelisted. Local caching can't be the cause either; it's disabled. Date and time are set correctly, they're automatically synchronized at startup by Ntpd. As the issue hasn't persisted, I probably can't provide any more information. - Flori4nK tc 21:57, 21 January 2021 (UTC)
@Redrose64: I've used Google Chrome for years. I've had cookies enabled for years. I've had adblockers for years. I've never had a problem with Wikipedia keeping me logged in until January 2021. Nearly but not perfect (talk) 02:35, 21 January 2021 (UTC)

How to deal with link rot on "Official Website"[edit]

[Fixed with Infobox OS parameter website special value of hide ] Lent (talk) 03:33, 22 January 2021 (UTC)

The "Official Website" for SUPER-UX (this version) is no longer valid. The displayed information is retrieved from Wikidata via Template:Infobox OS, as the website parameter is blank. The Wikidata information allows other language Wikipedia projects to use, and in this case provide, the website URL and have the information consumed and displayed by each of the Wikipedia projects.

I asked and updated the information as no longer valid, per a project chat over on Wikidata.

See: (On Wikidata) Best way to deal with link rot on "Official Website"

The Wikidata solution of setting the end time (P582) qualifier to the Wikidata statement(data) has been done. The rationale, I gather, is that old Wikidata information can be tagged with the end time (P582) to say the statement(data) was valid, up to and including the end time value. This implies, I gather, that some time after the specified end time value, the statement(data) should be treated as no longer valid.

As the Official Website still is rendered by the Infobox OS, I'm assuming that the official website (P856) value from SUPER-UX (Q2665351) is being used anyway.

What is the best way to resolve this?

  1. Set some other qualifier on the wikidata information that Infobox OS recognizes
  2. Wait/Request some bot to set things or note things properly, like Citation bot does for broken doi's
  3. Request a change to Infobox OS (or the parent/superclass template) to not display an Official Website if a P582 end time qualifier exists and the value is not in the future
  4. Workaround the Infobox OS to eliminate/modify the displayed value
  5. Workaround the Infobox OS to display URL for the last valid snapshot of the site cached at
  6. Something else

Or a mixture of the preceding?

Enquiring minds want to know :) Lent (talk) 12:39, 17 January 2021 (UTC)

Template:Infobox OS#Parameters mentions the option |website=hide. PrimeHunter (talk) 13:23, 17 January 2021 (UTC)
 Done THANKS! I missed that special value. I guess I'm spoiled by emphasis like bold and <code> in documentation. Lent (talk) 21:34, 17 January 2021 (UTC)
[Fixed with Infobox OS parameter website special value of hide ] Lent (talk) 03:33, 22 January 2021 (UTC)

Embedded video insist downloading rather than playback (on iOS mobile)[edit]

A Webm video. iPhone refuses playback, while Android insists to play from the beginning, ignoring the command to play from 41'
An ogv video. iPhone refuses playback, while Android plays perfectly from 1:52, as instructed

On iOS mobile device (Safari and Chrome), while playing Webm and ogv embedded in an Wikipedia article, it directs users to download the file rather than a simple playback (which is ridiculous for a >100Mb video). On Android (Chrome), while ogv works perfectly, Webm could only be played from the beginning, ignoring the time tag commands (Note: most users specify a starting time of the video so that it corresponds to relevant content to the article). The above issues does not happen on desktop computers. Is there a fix? -- love.wh 04:23, 19 January 2021 (UTC)

Try the same thing on testwiki:, especially the playback part. There is an different audio/video player there (video.js, instead of Kaltura here). There is an ogv file at testwiki:Equivalence_principle, for example.--Snaevar (talk) 17:31, 19 January 2021 (UTC)
Also, are you using the mobile app or the mobile website to access these? (If both, is it the same experience?) — xaosflux Talk 17:38, 19 January 2021 (UTC)
For me, the sample Webm played from 41" and Ogv plays but from 0:00. Then I retried the Webm and it was at 0:00. *scratches head* Desktop site, Timeless skin, iPad Air, Safari, iOS12. Pelagicmessages ) – (20:32 Sat 23, AEDT) 09:32, 23 January 2021 (UTC)

ReFill down again?[edit]

It's not worked for me this morning - is there a wider problem or is it just me? GiantSnowman 10:05, 20 January 2021 (UTC)

Reflinks is working fine. The C of E God Save the Queen! (talk) 14:32, 20 January 2021 (UTC)
Nice to know that reflinks is back but refill is still down. If someone who has access to phab would file a new request to get it going again that would be great. MarnetteD|Talk 14:58, 20 January 2021 (UTC)
many thanks, I'll use Reflinks for now. GiantSnowman 15:41, 20 January 2021 (UTC)
FYI GiantSnowman and The C of E as far as I can tell the current version of reflinks (unlike the one that was deactivated last year) only adds a bot generated title to the bare url. It does not actually put the url into a cite template. IMO that is not useful as it doesn't help with linkrot. You may feel differently but I wanted you to be aware of what I found. Regards. MarnetteD|Talk 18:45, 20 January 2021 (UTC)
That is what Reflinks has always done (or has for as long as I have done). Whenever this situation arises I always go back and re-convert properly using ReFill whenever it is fixed... GiantSnowman 18:47, 20 January 2021 (UTC)
@MarnetteD: Have you tried switching it to interactive? That does put the link in a cite template. I always use Reflinks and (barring a few it can't connect with), it does most of the work for you, you just have to trim the loose threads. The C of E God Save the Queen! (talk) 19:00, 20 January 2021 (UTC)
Thank you so much The C of E. Of course it would be something so simple that I was unaware of since I had never activated it before. Gosh it is nice to have this tool working again - now if we can just get reflinks back to working it'll be like the old days (all of two years ago) formatting bare urls. Thanks again. MarnetteD|Talk 19:07, 20 January 2021 (UTC)
Wow, that's great, thanks! GiantSnowman 20:08, 20 January 2021 (UTC)

Any idea why it is adding a 1970 date to websites published earlier today, such as this? I've manually remedied. GiantSnowman 22:33, 20 January 2021 (UTC)

My guess is that it's obtaining a null value for the date, and instead of recognising that it's not valid, it's instead applying a standard function to extract the year; and if you have a zero value (i.e. treated as 00:00:00 UTC Thursday, 1 January 1970), the year is 1970. --Redrose64 🌹 (talk) 13:02, 21 January 2021 (UTC)

Adding an automatically updated featured content section to Wikipedia:WikiProject_Zimbabwe/Rhodesia_task_force[edit]

I was wondering how you can get an automatically updated featured content section by the JL-Bot to Wikipedia:WikiProject_Zimbabwe/Rhodesia_task_force similar to what WP:WikiProject YouTube and WP:X/showcase have please? The C of E God Save the Queen! (talk) 14:41, 20 January 2021 (UTC)

The C of E, it looks like it's done through the template on JL-Bot's user page here. BlackcurrantTea (talk) 13:16, 23 January 2021 (UTC)
Thank you @BlackcurrantTea: How would that work for a subproject like Rhodesia as that's a task force? The C of E God Save the Queen! (talk) 13:22, 23 January 2021 (UTC)
That's a bit above my pay grade, The C of E. Try the bot's talk page. Cheers, BlackcurrantTea (talk) 14:01, 23 January 2021 (UTC)

Need some help building a proforma with sections autofilled based on username[edit]

Hi all

I've spent quite a lot of time building a resource to help keep people's multiple sandboxes organised to make writing draft articles and publishing them a bit easier

Whilst people can simply copy the page and change the name in the wiki text manually I would really like to make a page on Wikipedia where people can make their own version of this simply by clicking a button, this will make it easier to discover and also use the tool.

To make a version of this page for other users all that needs to happen is for my name to be replaced in the wikicode with the user who wants to use it (I have instructions at the bottom of the page for doing this manually). Because the page uses multiple tools there are two versions of the username that have to be replaced, one which replaces a space with a '+' and another which replaces a space with _, eg John+Cummings and John_Cummings.

Does anyone have an idea of how to create a button that would

  1. Read someone's username
  2. Add their username to a proforma adding in their username with either a '+' or a '_' in different places in the proforma (people can have 0 or 1 or 2 or a lot of spaces in their username)
  3. Saves the page or makes it very obvious how to save the page, either overwriting their existing sandbox or letting users chose where to save the page


John Cummings (talk) 15:23, 20 January 2021 (UTC)

@John Cummings: If I understand what you're asking, maybe an {{Edit}} link with a preloaded page (copy of your sandbox somewhere) and a Template to substitute their name, which would be pulled from magic word REVISIONUSER? Mathglot (talk) 19:36, 20 January 2021 (UTC)
Take a look at how we manage signups for the GOCE copy edit drives. There might be code in there that is helpful. – Jonesey95 (talk) 19:41, 20 January 2021 (UTC)
Thanks very much @Jonesey95: and @Mathglot: the bit I'm really stuck on is how to take a username with a space in and replace the space with a + in some places and a _ in other places on the same preload? John Cummings (talk) 20:00, 20 January 2021 (UTC)
@John Cummings: try {{#replace}}. Mathglot (talk) 20:24, 20 January 2021 (UTC)
Hmm, I see what you mean, I think... maybe the preload page should just be a one-line, template invocation of a second page which has your actual sandbox data, with the template of your design in the preload, which executes the task of replacing tokens in the second page with the userid the way you want it. Never tried that with a preload, and not sure if it will work; try it and let us know. Mathglot (talk) 20:31, 20 January 2021 (UTC)
I have used {{ROOTPAGENAME}} to automatically get the username in an unchanged copy.[1] I also made some other changes. PAGENAMEE with EE makes url encoding in magic words. PrimeHunter (talk) 11:15, 21 January 2021 (UTC)
Direct link for users to create their own sandbox manager. Only needs saving. Seems to work well, with this account and with my space-containing old account as well. --mfb (talk) 14:30, 21 January 2021 (UTC)
(edit conflict) If your /sandbox doesn't exist then this will open an edit window to create it with User:John Cummings/sandbox preloaded. There is no preload if the sandbox exists.
Adding &section=new will add a new section with the preload whether the page exists or not: [2]
&preloadtitle= can specify a section name which will also be in the automatic edit summary. It's blank in my example. I don't think you can make a preload command to overwrite existing content. You cannot preload from another wiki. mfb's link makes /Sandbox with uppercase S. This is not the link on "sandbox" in the default interface. PrimeHunter (talk) 14:35, 21 January 2021 (UTC)
Fixed the sandbox capitalization. In the German Wikipedia we made a template that does nothing but providing "$1", that way you can preload arbitrary text by using that template as preload and passing your text as parameter. If there would be a software solution for arbitrary preload texts (instead of pages) this could be made more international. --mfb (talk) 05:54, 22 January 2021 (UTC)

Lost "inspect diff" today in Chrome on Windows 10[edit]

Both have updated this week. On my iPad Chrome shows "inspect diff". Doug Weller talk 15:38, 20 January 2021 (UTC)

@Doug Weller:, context? Mathglot (talk) 19:40, 20 January 2021 (UTC)
@Mathglot: good question - I've replaced the section heading I used but must have erased with my fumble fingers before I saved. Doug Weller talk 19:50, 20 January 2021 (UTC)
@Doug Weller: "inspect diff" is made by this in meta:User:Doug Weller/global.js:
mw.loader.load("// Keeper/Scripts/commonHistory.js&action=raw&ctype=text/javascript");
It loads User:Writ Keeper/Scripts/commonHistory.js. I added it to my own global.js and it works for me in Windows 10, both in Google Chrome 87.0.4280.141 before updating, and 88.0.4324.96 after updating. What is your skin at Special:Preferences#mw-prefsection-rendering? Do you see "inspect diff" at WikiNews? I see it. PrimeHunter (talk) 09:13, 21 January 2021 (UTC)
@PrimeHunter: thanks, but now I'm even more confused. It came back on its own for enwiki, but I don't see it at wikinews. Doug Weller talk 09:23, 21 January 2021 (UTC)

Finding the connection between two categories[edit]

I'd like to know why Category:The Walt Disney Company is a distant subcategory of Category:Finnish people, but what's the fastest way to find it out? I don't want to click the blue ►'s on a category page until I find the connection. (talk) 18:33, 20 January 2021 (UTC)

Theoretical answer: express the category tree as a directed graph and do a breadth-first search from Finnish people cat until you get to that one. Not sure if a tool exists that does this. – SD0001 (talk) 18:49, 20 January 2021 (UTC)
Found it: Category:Finnish peopleCategory:Finnish diaspora‎Category:Finnish diaspora in North AmericaCategory:Finnish American‎Category:Finnish-American history‎Category:New SwedenCategory:Forts of New Netherland‎Category:Wall StreetCategory:New York Stock Exchange‎Category:Companies listed on the New York Stock Exchange‎Category:The Walt Disney Company‎. I wrote a quick script to do it; I don't know of a generic tool to solve this problem, unfortunately. — The Earwig talk 19:45, 20 January 2021 (UTC)
I love the category system. --Izno (talk) 20:10, 20 January 2021 (UTC)
If so, you'll find User:SDZeroBot/Category cycles interesting :P – SD0001 (talk) 05:13, 21 January 2021 (UTC)
Another endless backlog for a system that should have died when Wikidata was born. Yes, I love it! --Izno (talk) 05:34, 21 January 2021 (UTC)
Thanks. Too bad there's no tool that does this. Would be helpful when using WP:PetScan. (talk) 17:57, 24 January 2021 (UTC)

Citing a database query[edit]

Please see Wikipedia:Teahouse#Archival databases as sources where SacKate needs help on how to reference information extracted from a database. Roger (Dodger67) (talk) 06:20, 21 January 2021 (UTC)

Local display of WikiData edits[edit]

On my en.wikipedia watchlist I noticed:

  • "MØ (Q10670047) (diff | hist) . . Btcprox (talk | contribs) (Created claim: Property:P6935: m, connected with Wikidata for Firefox 🦊; Added reference to claim: Property:P6935: m, added with Wikidata for Firefox 🦊)"

The 'Wikidata for Firefox 🦊' leads there to because of it, on WikiData, being a Wikilink 'WikiData:Wikidata for Firefox'. It should lead to but because it is displayed here, the 'Wikidata:' is being interpreted as an interwiki, not as a namespace on WikiData. Is there any way to change this so that the links lead to the right place? --Dirk Beetstra T C 11:37, 21 January 2021 (UTC)

The edit summary is made by a tool by Shisma. If they change the link to [[d:Wikidata:Tools/Wikidata for Firefox|Wikidata for Firefox]] then it will work both at Wikidata and other wikis. Here it gives Wikidata for Firefox. [[wikidata:Wikidata:Tools/Wikidata for Firefox|Wikidata for Firefox]] would give Wikidata for Firefox which works here but not at Wikidata where the first wikidata: would be interpreted as the namespace. PrimeHunter (talk) 11:57, 21 January 2021 (UTC)
if I format the link like [ Wikidata for Firefox 🦊] (with single brackets), it should always lead to where it's supposed to lead, right? Is it a good idea to do so? How can I reproduce this bug?--Shisma (talk) 17:50, 21 January 2021 (UTC)
@Shisma: External link syntax doesn't render as a link in edit summaries. It has to be a wikilink. As I said, this will work: [[d:Wikidata:Tools/Wikidata for Firefox|Wikidata for Firefox]]. To reproduce the problem: Enable "Show Wikidata edits in your watchlist" at Special:Preferences#mw-prefsection-watchlist here at enwiki. Watch an enwiki page which had a recent edit with the tool at its Wikidata item, e.g. . (I don't know whether all Wikidata edits appear in enwiki watchlists but the MØ edit does). View Special:Watchlist. The edit summary in [3] had a link to Wikidata:Tools/Wikidata for Firefox.[4]. Viewed in an enwiki watchlist it gives the same wrong result as in my post. The Wikidata target does say: "There is a page at Wikidata:Tools/Wikidata for Firefox". That link works at Wikidata. Here at enwiki I had to pipe it with d: in front to get it to work. But the link only shows at Wikidata if the user has the default language "en - English" at wikidata:Special:Preferences. That's because it's made by a customized message at wikidata:MediaWiki:Wikibase-noentity which includes: {{#ifexist:Wikidata:{{FULLPAGENAME}}|*There is a page at [[Wikidata:{{FULLPAGENAME}}]].}}. The customized message has not been translated to any other languages at Wikidata according to wikidata:Special:PrefixIndex/MediaWiki:Wikibase-noentity. Unregistered users also get the English message but that's nearly irrelevant since unregistered users don't have watchlists. The problem can also occur at other wikis, e.g. the German Wikipedia where some users will have set German at Wikidata, or have a global preference for German. PrimeHunter (talk) 20:54, 21 January 2021 (UTC)

Captchas and blind people again[edit]

I am aware that this has been discussed before since I had a quick search of the archives. But the problem still persists that the captcha shown when you create an account or add a link to an article is not accessible to blind people such as myself.

Yes, you can request that someone creates an account for you, which is what I did when I joined. But many people may be put off by this.

I feel that Wikipedia should provide an audio challenge or use something like reCAPTCHA v2's I'm not a robot tick box. Many website's use either of these methods, and Wikipedia is one of the few I can think of that doesn't.

What are your thoughts on this, and is anyone currently working on a solution?

Many thanks.KaraLG84 (talk) 14:21, 21 January 2021 (UTC)

@KaraLG84: The local English Wikipedia community can not make this change, it would be at the very least a WMF-wide global change as accounts are global. You can follow up on the discussion about this here: phab:T6845. — xaosflux Talk 14:27, 21 January 2021 (UTC)
@Xaosflux: Thanks. Sadly it seems that nothing has been done about it. The last comment was over a year ago.KaraLG84 (talk) 14:42, 21 January 2021 (UTC)
KaraLG84, this is correct. Its a hard/expensive problem to solve. —TheDJ (talkcontribs) 15:54, 21 January 2021 (UTC)
One that has been solved many times by many organisations. DuncanHill (talk) 16:07, 21 January 2021 (UTC)
But not as open source. --Izno (talk) 17:55, 21 January 2021 (UTC)
Indeed, it needs to be open-source. Graham87 07:39, 22 January 2021 (UTC)

Wrong links in template documentation[edit]

Template:Redirect2/doc is an example of template documentation that contains links to PAGE1, which is an actual article. These should probably appear as redlinks like PAGE2, PAGE3, PAGE4 for the purpose in this usage. I think there are around 40 doc pages that link to PAGE1. Is there any way to fix this short of manually editing them all? MB 15:30, 21 January 2021 (UTC)

Don't we have foobar-style pages (analogous to Template:Foo) dedicated for this purpose? – Jonesey95 (talk) 15:39, 21 January 2021 (UTC)
Page1 is create-protected, so we could convert all the placeholder names to lower-case. — The Earwig talk 21:10, 21 January 2021 (UTC)
There are only 15 doc pages at [5] but I don't see a need to "fix" this. Page1 is red (deleted 10 times but not create-potected), but I think PAGE1 is easier to understand in documentation as something you have to edit in a real call. And Page3 is blue (or green if you color redirects). PrimeHunter (talk) 21:22, 21 January 2021 (UTC)
You are supposed to only make blue links with hatnotes and you can se the code works when they hit a target while the mix of red and blue may be a little distracting. I suggest we make them all blue by redirecting PAGE2 to (like Page 2), keep PAGE3 a redirect to Page 3, and redirect PAGE4 to Page Four (like Page 4). PAGE5 is not used in doc pages. PrimeHunter (talk) 21:33, 21 January 2021 (UTC)
Oops, I saw it had been create-protected but did not notice the protection expired (threw me off as salting is frequently permanent). — The Earwig talk 23:26, 21 January 2021 (UTC)

Problems rendering mathematical symbols[edit]

There can be problems displaying the equal sign (=) and the minus sign (-).

  • Example:
<math>\frac{dM}{dt} = Q - S = Q - \frac{M}{\tau}</math>

sometimes renders correctly and sometimes does not:

and in some contexts, such as here, always fails to display the minus sign.

  • Another example:
{{center|size bar: 30 µm}}

displays as expected, while

{{center|size bar = 30 µm}}

does not display at all. That is, the presence of the equal sign suppresses the display altogether — Epipelagic (talk) 21:48, 21 January 2021 (UTC)

@Epipelagic: It's two unrelated issues. I guess your browser is Google Chrome. See phab:T269222: "Minus signs not displaying in Math formulas (on certain zoom levels in Chrome browsers)". The minus displays for me at all zoom levels in Google Chrome 88.0.4324.96. The other issue is that {{center|size bar = 30 µm}} is interpreted as assigning the value 30 µm to a template parameter called size bar. You can get around it by writing {{center|1=size bar = 30 µm}} or {{center|size bar {{=}} 30 µm}}. See Help:Template#Usage hints and workarounds. PrimeHunter (talk) 23:16, 21 January 2021 (UTC)
Many thanks — Epipelagic (talk) 02:38, 22 January 2021 (UTC)

Notifications for WP Projects[edit]

I understand how to manage my own Watchlist, linking to pages I have personally edited.

But if I join one of the many Wikipedia Projects, some of which have their own Watchlists (associated with the Project, and not a specific User), how do I get alerted of changes to one of the watched pages?

I could, I suppose, place a ghost edit on each article within the category, but that would be tedious. One project I follow has 1,500 pages on its watchlist. Or is this somehow automatic, if I add my name to the participants list? Sorry I couldn't find this on the help FAQ. Jax MN (talk) 22:31, 21 January 2021 (UTC)

@Jax MN: See Help:Watchlist for many other features of the watchlist, including how to watch by a click, and Special:Watchlist/raw where you can insert a list of pages to watch them all. Be careful not to delete the existing entries and save. The watchlist has no page history. You cannot get notified of changes to a WikiProject watchlist without watching each page but there may be a link you can click to see recent edits like at Wikipedia:WikiProject Fraternities and Sororities/Watchlist#Instructions. PrimeHunter (talk) 23:29, 21 January 2021 (UTC)

What does unified login cover?[edit]

I went to upload something to wikisource just now and was surprised to discover I wasn't logged in automatically with my wikipedia account. Does unified login not include wikisource? -- RoySmith (talk) 22:48, 21 January 2021 (UTC)

Unified login does include wikisource. I'm not sure why you weren't logged in, but you should be able to log in with the same username and password you use at Wikipedia. * Pppery * it has begun... 23:02, 21 January 2021 (UTC)
You may need to disable any browser option which says "Block third party cookies". -- zzuuzz (talk) 23:14, 21 January 2021 (UTC)
Pppery, Yup, I was able to manually log in with my enwiki credentials (including being asked for 2FA). The log shows my wikisource account was created a couple of years ago. Well, anyway, I'm in, so thanks for the help. zzuuzz, I've never had to do that on other WMF projects (commons, wikidata, etc). -- RoySmith (talk) 23:17, 21 January 2021 (UTC)
@RoySmith: Try v:Wikiversity, which works the same as Wikisource. I guess it's something to do with the domain names, but never looked into it too closely. -- zzuuzz (talk) 23:24, 21 January 2021 (UTC)
Zzuuzz, Interesting, that worked automatically. Well, I'm not going to worry about it too much. Thanks. -- RoySmith (talk) 23:28, 21 January 2021 (UTC)
I sometimes have to click any link or reload a page before being logged in at another wiki. PrimeHunter (talk) 23:32, 21 January 2021 (UTC)
This has happened to me a time or two. It's rare, but it does happen. In fact, it happened just right now. I was fine clicking on Wikisource and Commons, but Wikidata had me logged out. When I tried to log in, I got a message that my login was "invalid or expired". I clicked on Commons (where I was logged in), then came back to Wikidata, and I was already logged in at Wikidata. — Maile (talk) 23:53, 21 January 2021 (UTC)

Selectable date format in a userbox, coding help needed[edit]

Please see WT:20th anniversary#A celebratory userbox I need help on how to allow users to select between two different versions of either just the date, or perhaps the entire text, whichever is simplest. Roger (Dodger67) (talk) 08:30, 22 January 2021 (UTC)

Hide the phrase shown below title[edit]


Is it possible for me to Hide the phrase "" , written below every article title. Perhaps some change into the commons.css or my skin ? Thank you. --Walrus Ji (talk) 10:40, 22 January 2021 (UTC)

@Walrus Ji: just put the following code snippet in Special:MyPage/common.css and it will hide it for you:
#siteSub {display: none;}
xaosflux Talk 11:35, 22 January 2021 (UTC)
Xaosflux, Thank you. Worked like a charm. Walrus Ji (talk) 11:49, 22 January 2021 (UTC)

Fonts too small[edit]


Has the EN.Wikipedia reading font been recently changed? I find it to be too small and hard to read. Fonts on other websites are OK including those on FR.Wikipedia, DE.Wikipedia and NL.Wikipedia. Is there a way to increase the font size just for EN.Wikipedia? Changing the Chrome (Version 87.0.4280.141) font setting makes the EN.Wikipedia font better but makes the font too large for all other sites. I use Windows 10 Version 2004 (OS Build 19041.746). Thanks. TheTrolleyPole (talk) 15:53, 22 January 2021 (UTC)

Just use Ctrl + or Ctrl - on the page to enlarge or reduce and it will keep the setting for that website. That's how Firefox does it and I think Chrome is the same. Also try Ctrl 0 to reset the font size and that might restore your normal Wikipedia size. —  Jts1882 | talk  16:48, 22 January 2021 (UTC)
Thanks. The tip works on Chrome. I suspect I may have accidentally pressed Ctrl - causing my reading problem. TheTrolleyPole (talk) 17:06, 22 January 2021 (UTC)

Fixing the refs in this article...what am I doing wrong?...[edit]

So...I have stumbled upon this article - It's Only a Play. While refs are present with good/correct information, none of them use the Citation Style 1 templates - cite web/news/journal etc. What tool should I be using to fix the refs? I have tried to run my ref tools on the article but either I get a message back that all is well or (literally) nothing happens. I think I need to update my tools - like Reflinks/reFill2/etc on my common etc pages - but am not sure what needs to be fixed. If some of you wonderful tech-wizards could figure out what I am doing wrong and tell me what I need to do to get it right, that would be awesome and a big help. Cheers & thanks - Shearonink (talk) 17:58, 22 January 2021 (UTC)

Hi Shearonink—per WP:CITEVAR, I don't think anything needs to be done. "To be avoided: adding citation templates to an article that already uses a consistent system without templates". — The Earwig talk 18:34, 22 January 2021 (UTC)
The first step is to get consensus on the article's talk page to change the established citation style. The second step would be to manually convert the citations to use {{cite web}} and similar templates, which would improve the display of the references, which have minor formatting errors (I see at least a half dozen errors in spacing) that are taken care of by the CS1 templates. – Jonesey95 (talk) 19:23, 22 January 2021 (UTC)
Manual conversion...btdt. Not my favorite housekeeping chore but I guess I'll do it again. If, of course, there's consensus for such a change. Shearonink (talk) 07:11, 23 January 2021 (UTC)

Editing news 2021 #1[edit]

Read this in another languageSubscription list for this newsletter

Reply tool[edit]

Graph of Reply tool and full-page wikitext edit completion rates
Completion rates for comments made with the Reply tool and full-page wikitext editing. Details and limitations are in this report.

The Reply tool is available at most other Wikipedias.

  • The Reply tool has been deployed as an opt-out preference to all editors at the Arabic, Czech, and Hungarian Wikipedias.
  • It is also available as a Beta Feature at almost all Wikipedias except for the English, Russian, and German-language Wikipedias. If it is not available at your wiki, you can request it by following these simple instructions.

Research notes:

  • As of January 2021, more than 3,500 editors have used the Reply tool to post about 70,000 comments.
  • There is preliminary data from the Arabic, Czech, and Hungarian Wikipedia on the Reply tool. Junior Contributors who use the Reply tool are more likely to publish the comments that they start writing than those who use full-page wikitext editing.[6]
  • The Editing and Parsing teams have significantly reduced the number of edits that affect other parts of the page. About 0.3% of edits did this during the last month.[7] Some of the remaining changes are automatic corrections for Special:LintErrors.
  • Венов дијаграм.svg A large A/B test will start soon.[8] This is part of the process to offer the Reply tool to everyone. During this test, half of all editors at 24 Wikipedias (not including the English Wikipedia) will have the Reply tool automatically enabled, and half will not. Editors at those Wikipedias can still turn it on or off for their own accounts in Special:Preferences.

New discussion tool[edit]

Screenshot of version 1.0 of the New Discussion Tool prototype.

The new tool for starting new discussions (new sections) will join the Discussion tools in Special:Preferences#mw-prefsection-betafeatures at the end of January. You can try the tool for yourself.[9] You can leave feedback in this thread or on the talk page.

Next: Notifications[edit]

White square with question mark.png

During Talk pages consultation 2019, editors said that it should be easier to know about new activity in conversations they are interested in. The Notifications project is just beginning. What would help you become aware of new comments? What's working with the current system? Which pages at your wiki should the team look at? Please post your advice at mw:Talk:Talk pages project/Notifications.

Whatamidoing (WMF) (talk) 01:02, 23 January 2021 (UTC)

Server problems?[edit]

Anyone else getting 503 varnish backend errors? I just lost an edit I was trying to save from classic source editor. And VE has slowed to a crawl. Pelagicmessages ) – (20:04 Sat 23, AEDT) 09:04, 23 January 2021 (UTC)

The MediaWiki namespace[edit]

I found something strange, every page that starts with "MediaWiki:Bad image list/" exists, and its specific text is

The format is as follows: Only list items (lines starting with *) are considered. The first link on a line must be a link to a bad file. Any subsequent links on the same line are considered to be exceptions, i.e. pages where the file may occur inline.

The more strange thing: none of these pages even actually exist: [10]. For example: MediaWiki:Bad image list/Archive 6, MediaWiki:Bad image list/MediaWiki:Bad image list, MediaWiki:Bad image list/hexuhv8o7d4ghfxg3sjiuyvh4s7dihrt876wtghf7.

I have no idea how this happened, but could someone please explain it to me? JJP...MASTER![talk to] JJP... master? 23:45, 23 January 2021 (UTC)

Bonus question: why does editing MediaWiki:Hello/xyz show "Hello"? Johnuniq (talk) 23:51, 23 January 2021 (UTC)
Johnuniq, so does MediaWiki:Hello/h4rdughnmjvf4cthedui4ngyhuckverhn. JJP...MASTER![talk to] JJP... master? 23:52, 23 January 2021 (UTC)
Johnuniq, Wait literally EVERY page in the MediaWiki namespace, even on my own private wiki, does this same thing! JJP...MASTER![talk to] JJP... master? 23:57, 23 January 2021 (UTC)
The subpage only shows content if the parent page is a system message in the software. For example, MediaWiki:Introduction is not a system message so it's not listed at Special:AllMessages, and MediaWiki:Introduction/XYZ is red. PrimeHunter (talk) 08:02, 24 January 2021 (UTC)

Text alignment in infoboxes[edit]

On Alexei Navalny, is anyone else having an alignment issue with the "Leader of the Russia of the Future Party" in the infobox? For me (Safari 14.0.2, OS 11.1), "Russia of the Future" is rendering slightly below the rest of the text; the problem goes away if you get rid of the link or the footnote at the end. Esszet (talk) 02:39, 24 January 2021 (UTC)

I see it in Safari 13.1.1 on Mac OS 10.14.6 (desktop) as well. It looks fine in Chrome and Firefox. The "Russia of the Future" link is below the black text, and the efn footnote in inline with the black text instead of superscripted. Strange. – Jonesey95 (talk) 04:44, 24 January 2021 (UTC)
You're right, I didn't notice that, it isn't superscripted at all. Esszet (talk) 15:25, 24 January 2021 (UTC)

Categorizing cross- and same-namespace redirects[edit]

Please see Template talk:R to project namespace#RfC: Should we categorize redirects to the same namespace? There have been some late comments. WhatamIdoing (talk) 20:20, 24 January 2021 (UTC)

Category count?[edit]

Counting the categories via {{PAGESINNAMESPACE:14}} does not work here – the PAGESINNAMESPACE magic word is expensive and so is disabled on this wiki. Is there a statistics page somewhere that will say (roughly) how many pages exist here in each namespace? — GhostInTheMachine talk to me 20:53, 24 January 2021 (UTC)

Is Wikipedia:Database reports/Page count by namespace what you are looking for? – Jonesey95 (talk) 01:02, 25 January 2021 (UTC)
Perfect! thanks — GhostInTheMachine talk to me 09:23, 25 January 2021 (UTC)


Blocked users currently see this text when they try to edit: MediaWiki:Blockedtext. However, if a blocked user is subject to multiple blocks (for example, they're directly blocked and their IP address is also hardblocked), they instead see this default text: MediaWiki:Blockedtext-composite. This is a wholly useless message, especially in comparison to the carefully designed MediaWiki:Blockedtext. It's worse than it looks on first glance; when I was testing, I found that "$2" is always replaced with something generically useless like "there are multiple blocks affecting your account". Could someone look into replacing it with a modified copy of MediaWiki:Blockedtext, especially by adding links to WP:AAB and WP:GAB? I would do it but unfortunately I don't have the time right now. Best, KevinL (aka L235 · t · c) 21:06, 24 January 2021 (UTC)

L235, I replaced it with a modified version of Blockedtext. However it still probably needs further work, I'm not sure of a clever solution for the $2, besides perhaps just omitting it altogether and putting something generic. Unless MediaWiki itself changes, I can't forsee a way to list out all the block reasons, but I hope someone more techy than I can give it a go. CaptainEek Edits Ho Cap'n! 07:07, 25 January 2021 (UTC)
There are explainations of the parameters at translatewiki:MediaWiki:Blockedtext-composite/qqq. I would look into using $5 instead of $2, it is after all not just an simple block ID number. Maybe count the number of ID's, in order to know the number of blocks?--Snaevar (talk) 14:03, 25 January 2021 (UTC)

ContentSub margins[edit]

For some reason, the ContentSub text style, used for things like short descriptions, has a much taller bottom margin. I'm using the legacy Vector skin and, to me, it looks off, having gotten used to the original spacing. -BRAINULATOR9 (TALK) 03:21, 25 January 2021 (UTC)

MediaWiki userspace and User Contribution special search for IPv6 broken?[edit]

The Special:Contributions seems broken when processing IP6 addresses. It cannot accept the format used by [&action=history] links. Special:Contributions requires upper case IP6 while [&action=history] generates lower case IP6. If you enter one into the other it comes up null. Special:Contributions should accept any miniscule/majiscule mix-and-match. (a regexp for recognizing an IPv6 entry and then either upcasing or downcasing the input to further process seems like a solution). This is a problem when manually adding {{unsigned}}. Also, this is a MediaWiki problem when accessing user pages. Could real user could masquerade as an IP address by using a different case or mixed case name? Where do we leave talk messages to such a user, since they appear to be different usernames with different userspace/usertalkspace pages?


-- (talk) 13:57, 25 January 2021 (UTC)

Yes, usernames are case sensitive. Impersonation should not be an issue, as we do not allow username selection that looks like an ip address. — xaosflux Talk 14:08, 25 January 2021 (UTC)
Regarding that template, post some examples at Template talk:Unsigned and someone may look in to the module that powers it to improve it (Module:Unsigned). — xaosflux Talk 14:09, 25 January 2021 (UTC)
Special:Contributions failing on lowercase IPv6 is a recent bug phab:T272225: "Special:Contributions no longer accepts display form of IPv6 addresses". PrimeHunter (talk) 17:38, 25 January 2021 (UTC)
Indeed, I was sure that lowercase worked, hence this edit. --Redrose64 🌹 (talk) 22:21, 25 January 2021 (UTC)

A workaround is probably needed. I started with a suggestion at Template talk:IPvandal#IPv6 needs to be uppercase. Johnuniq (talk) 00:10, 26 January 2021 (UTC)

Tech News: 2021-04[edit]

18:29, 25 January 2021 (UTC)

"An attempt to load a user script has failed"[edit]

When I'm using mobile I'm getting multiple "An attempt to load a user script has failed" error messages (apparently in my case it seems to involve DYKhelper). Other editors I've talked to on Discord have reported a similar issue. Narutolovehinata5 tccsdnew 23:29, 25 January 2021 (UTC)

It's being thrown by MediaWiki:Mobile.js: diff. — The Earwig talk 23:37, 25 January 2021 (UTC)
Jon (WMF): IMO, this was not handled well. The error says to see the JS console but most mobile users do not have access to a JS console. For most users, it's not clear what the problem is. (We could just say the error in the box instead of telling people to check another thing for the error. Is the concern the error is too technical? Then what are they supposed to do about it anyway?)
Unless we're going to go through thousands of personal JS files and replace peoples' importScript invocations (I assume this is a nonstarter)... rather than leaving things broken, can we copy this shim from Meta? I don't understand the point of forcing people to make their personal JS more verbose. I recognize there are alternate things in the works (phab:T27845 is WONTFIX, but has related tickets). Nevertheless, those things aren't here yet (as far as I know), so an importScript shim seems like the cleanest workaround for the moment. — The Earwig talk 00:01, 26 January 2021 (UTC)
I assume this is a nonstarter Why? That's exactly what we're doing with the globals. It just takes someone doing it. --Izno (talk) 00:33, 26 January 2021 (UTC)
You're right. But I think a shim still makes sense until it is done, so things are not broken. — The Earwig talk 00:36, 26 January 2021 (UTC)
The better shim seems reasonable to me? At any rate, this is all related to error reporting being turned on for enwiki, so I think some version of either of these is basically required ~ Amory (utc) 02:02, 26 January 2021 (UTC)
Directing users to the script that failed to load, rather than where the error is occurring (their common/skin js), results in confusion like this [14]. If a notification is to be shown on every page load, it should link to a tutorial page on how to actually fix the issue and where to ask for help. - Evad37 [talk] 01:08, 26 January 2021 (UTC)
My main goal was to suppress a large amount of errors we're seeing from mobile users trying to load incompatible scripts. How you want to deal with that I leave up to you. Providing a shim would also address the problem, but is just sweeping the issue under the rug adding technical debt to interface admins. I should note the mw.notify technique has been successful on other wikis, (with translation of course) for getting these scripts and gadgets fixed. Perhaps linking to Special:MyPage/common.js and the associated skin.js may help. Jon (WMF) (talk) 02:03, 26 January 2021 (UTC)
Maybe I'm crazy here, but I had no clue that importscript was being deprecated. Why was it first completely removed on mobile - the platform that most people have the least amount of access to identify the problem and resolve it, instead of first being removed/warned-on on desktop where people can actually click through links/etc to identify and fix the issue? And where was this notified to the community prior, because I watch this page and I may have just missed it but I saw no notice that what I presume is literally millions of uses of importScript and importScriptURI will have to be re-done, and presumably from the comments here and elsewhere others didn't either. I'm all for the change (one load instead of 4 separate ones) but jeez, roll it out in a way that lets people 'upgrade' to the new one, and helps people do so - not just throws a ton of errors and removes scripts from many people on mobile. Just my 2 cents, and regards -bɜ:ʳkənhɪmez (User/say hi!) 02:09, 26 January 2021 (UTC)
importScript, like many of its cousins, was deprecated in MediaWiki 1.29. 1.29 was formally released nearly 4 years ago at this point. I am 100% certain we have seen at least one Tech News covering the deprecation.
I agree that we should be less verbose about the issue on mobile and instead be verbose for users on desktop first. On mobile, we should silently fail to load and continue to throw errors in the console (not that will help much since neither Firefox nor Chrome these days provide access to console trivially or at all [I need to go see if Firefox can be configured on]). --Izno (talk) 02:42, 26 January 2021 (UTC)
Oh wow. That's news to me. I assumed once I saw like 2/3 scripts that recommended install using that, it was the proper way. Not to mention that User:Enterprisey's scriptinstaller still uses importScript. Point being, even if it was announced, it obviously wasn't done so well enough if people like Enterprisey who have multiple scripts never updated, and regardless, this rollout of "screw people on mobile with a bunch of useless errors they can't fix at that time" is.. botched. Is there a way to have a bot change all instances of importScript (and its cousins) to the new version? I'm surprised in 4 years of it being deprecated nobody's made one (or if they have, that it doesn't run every so often to catch new uses). -bɜ:ʳkənhɪmez (User/say hi!) 02:48, 26 January 2021 (UTC)
Amory above is working on the deprecated global config variables right now (as is Legoktm, globally, heh). I can't speak for their interest in working on this one, but it's similar niche work (that, yay, requires interface admin hat). It probably will bubble up a lot of scripts that don't work as a result, since importScript assumes synchronous load or something (I think) and mw.loader.load does not, so some dependency declarations may be missing.
I did mention in an offwiki discussion that I too am concerned that our technical documentation and support tools like Enterprisey's installer need to be updated. Even just the fact that {{Iusc}} was not updated to (redirect to) {{Lusc}} is bothersome, because of a 2-person talk page discussion over half a decade ago. But we have to start somewhere, otherwise, as you did, Monkey See, Monkey Do.
The reason no-one has made one is because the problem is essentially invisible. At best we hear about broken scripts, usually on this page (for one reason or another, not necessarily importScript only). At worst, silence as editors go inactive or they miss that their favorite script doesn't work, or.... I'm sure you see the problem. Given how many user Javascript pages there are, a bot is more or less the only feasible way to deal with the problem. I haven't actively inquired before, but it might be a good idea to make a Phabricator task so that we can identify active users with Javascript subpages (using deprecated Javascript if possible) and start by updating those pages instead. Maybe Jon (WMF) can help with that problem. --Izno (talk) 03:11, 26 January 2021 (UTC)
If importScript is deprecated and support is actively being removed soon, it would help those of us who are somewhat technical but need a cookbook if someone here could point to or whip up a page describing the steps to migrate from importScript to whatever is supported. Also, when I look at my vector.js, I see the following warning in a red box: Code that you insert on this page could contain malicious content capable of compromising your account. If you import a script from another page with "importScript" or "iusc", take note that this causes you to dynamically load a remote script, which could be changed by others. If importScript has long been deprecated, should this text be modified? – Jonesey95 (talk) 03:25, 26 January 2021 (UTC)
Yes, that is an example of documentation that should be updated (at least insofar as it should not mention importScript, not the other part of that sentence, which naturally remains true).
The cookbook is and has been mediawikiwiki:ResourceLoader/Migration guide (users). --Izno (talk) 03:33, 26 January 2021 (UTC)
The larger task here is phab:T130879 created in 2016, but stalled for some time. For the record, the method was soft deprecated on desktop first and the mobile site never inherited the importScript function because the mobile site was built after deprecation began, and at the time the mobile site couldn't even run user scripts so we didn't know it was an error. An error in a JS script on mobile like this basically stops the rest of the script execution. There's a lot of moving parts, but we have better tooling and visibility now, so going forward we're in a much better place, and hopefully this can be sped up, but there's going to be a lot of work to be done, to make up for lost time and fix existing code. user:Izno, User:Ladsgroup has recently got global interface editing rights, and has a bot for fixing related legacy code (see phab:T72470). I imagine he would be a good person to help with enwiki's efforts but right now his focus is on deprecating the wg variables. I'd hope the bot he's been using could also be used for importScript when we get round to it. Jon (WMF) (talk) 04:13, 26 January 2021 (UTC)
I'd prefer either making importScript a wrapper around mw.loader.load, or making a new wrapper ("importScriptAsync"?) and migrating to that; I find the URLs less readable. Should those two options be RfC'd? I'd be happy to do the migration work. The one issue with the former is that people might've been depending on the load order (admittedly unlikely). Enterprisey (talk!) 03:51, 26 January 2021 (UTC)
As I said offline, I'm not a fan, and that the real issue is that users have to edit their Javascript pages is what sucks, not the fact that the API for importing foreign Javascript isn't framed in terms of wiki pages (and the related task on the Phab side was declined). --Izno (talk) 04:19, 26 January 2021 (UTC)

I definitely can help in migrating, just currently busy with thousands of usages of deprecated globals (just counting mediawiki namespace). Once I'm done with that, ping me and I help with this one too User:Jon (WMF) Ladsgroupoverleg 05:59, 26 January 2021 (UTC)

  • In simple terms, how can us relatively non-techie folks fix this? Do we need to swap failing scripts to the "mw.loader" style? Do we need to swap alls scripts to that? Is there another better solution? Plz ping me :) CaptainEek Edits Ho Cap'n! 08:34, 26 January 2021 (UTC)
  • While you’re all figuring this out, whatever this is, can someone disable the stupid warning on mobile devices? It’s sticky, it doesn’t go away, it’s highly annoying and it’s also quite useless... if there’s something to fix here, use a bot, edit the gadgets/templates, add a shim, whatever, but whilst the templates/gadgets are all using the old format it’s way too early to be bugging people to update their own common.js to fix this. ProcrastinatingReader (talk) 11:45, 26 January 2021 (UTC)

Are we talking about a retrospective change to all user scripts that still use the equivalent of {{iusc}} / {{Install user script}} to use {{Lusc}} / {{Load user script}} instead? — GhostInTheMachine talk to me 13:52, 26 January 2021 (UTC)

  • Borrowing words from ProcrastinatingReader can a tech wizard please disable the notice for those using mobile devices? The notice I’m seeing is permanent & just takes up almost all the space on the screen, to say this is upsetting is to put it mildly, it’s even more annoying than the “image greying” problem we mobile phone editors faced last year. And please, like CaptainEek said can one of y’all tech wizards be so kind as to explain to us 'laymen' (which I gladly accept that I am regarding anything related to advanced coding) the simplest manner in which we can fix this error? Please this is a cry for help. @PrimeHunter aren’t you affected by this also? Celestina007 (talk) 15:43, 26 January 2021 (UTC)
  • Administrator note I've disabled this for now, at the very least some more discussion is warranted as this is disruptive to contributors. — xaosflux Talk 15:54, 26 January 2021 (UTC)
@xaosflux, Many thanks for helping out, all is back to normal. Celestina007 (talk) 18:01, 26 January 2021 (UTC)

Article / Page Referral Data[edit]

Hi All, I thought I had asked this question before, but, not able to find in the archives, so, I am beginning to wonder if I ever asked this question here at all.

While working at WP:ITN and WP:ITNRD we want to answer a simple question. What fraction of an article's page views come from clicks on the homepage when an article is listed on ITN. So, all I am looking for is referral data for a page saying of x page views, y came in from the homepage. This referral data seems like it would be collected for sure, but, have not seen this in the page views tool. Is there some other place where we can find this information? We want to use this data to get a better understanding of what links the users click on our homepage, and more specifically on the ITN panel. Thanks in advance. Ktin (talk) 23:36, 25 January 2021 (UTC)

I think this has been asked for somewhere or another. Not sure where though. --Izno (talk) 00:34, 26 January 2021 (UTC)

Watching archived pages[edit]

Maybe this is a non-issue, but I always have to go through and unwatch pages that are archived (old PRs, GAs, FACs etc.) and I certainly have forgotten to do so plenty of times. Is there a reason that we're able to continue watching archived pages? Maybe this is a non-issue, as in it doesn't take anything extra to watch them, but at the same time it seems pointless. Any thoughts? Apologies if this has been discussed before. Aza24 (talk) 00:18, 26 January 2021 (UTC)

I prefer to keep watching my GA reviews so as to ensure vandalism on the pages doesn't go unnoticed and most of the time it is no additional trouble. Eddie891 Talk Work 00:26, 26 January 2021 (UTC)
Consider using the new temporary watch feature. :) --Izno (talk) 00:35, 26 January 2021 (UTC)
Archives can be edited like any other page, they just rarely are. There is no need to unwatch them. You can search (Ctrl+f in many browsers) Special:EditWatchlist for "archive" and unwatch if you want. I have 136 and don't care. PrimeHunter (talk) 08:55, 26 January 2021 (UTC)
  • Yeah, I agree with the above that watching e.g. old GA reviews is a good thing. 99% of the time nothing happens to them, and the remainder is typically vandalism or something else I want to know about so I can revert or respond to it. {{u|Sdkb}}talk 16:44, 26 January 2021 (UTC)

Moving of categories[edit]

I understood that there are categories about Serres regional unit, of Central Macedonia Region at Greece that have problem to the name. Category "People from Skoutari" refers to municipal unit of Skoutari, however there is the village of Skoutari (the capital of municipal unit), too. Or the category People from Nea Zichni. This category refers to Municipal of Nea Zichni but there are also the municipal unit of Nea Zichni and the village of Nea Zichni (capital of the Municipal and the municipal unit.) Maybe someone user can help to the rename of the categories? BILL1 (talk) 01:01, 26 January 2021 (UTC)

I think that category about the people from Nea Zichni must rename to "People from Nea Zichni (municipal)" (because there is also village and municipal unit with this name. A possible future category about people from Nea Zichni municipal unit can named "People from Nea Zichni (municipal unit) and a possible future category about the people from Nea Zichni village can named "People from Nea Zichni". BILL1 (talk) 01:10, 26 January 2021 (UTC)

Izno can you help me? BILL1 (talk) 03:35, 26 January 2021 (UTC)

BILL1, you should use the requested moves process. --Izno (talk) 03:37, 26 January 2021 (UTC)
Izno ok thank you BILL1 (talk) 03:52, 26 January 2021 (UTC)
Actually, you should use WP:CFD, not RM. — JJMC89(T·C) 07:04, 26 January 2021 (UTC)