22:53, 25 April 2022 (UTC)

Hey, folks,

I'm not sure what is up but I've noticed lately that when I'm moving an article, even if I have Move talk page box checked off, the Talk page isn't moved along with the article. Most recently, an editor noticed and tagged the Talk page to be moved separately. I'd say that this has happened 6 or 7 times over the past week but I can't figure when it happens or why it happens. It's not every time, I'd say it happens about 25% of the time that I move a page with a talk page. Any ideas what might be going on? Liz ^{Read! Talk!} 03:19, 25 April 2022 (UTC)

In one of the last move log entries before your message here, both the article KJR-FM and its talk page required admin assistance to move them due to edits that were in the way. If you move an article but the talk page move is blocked like this, the talk page does not get moved along with the article automatically (and there's an easy-to-miss message near the end of the "move succeeded" page saying that the talk page move failed). Graham87 08:29, 25 April 2022 (UTC)

I love that post. Here we have Graham87, who totally relies on screen-reader software, telling the sighted people that a message is easy-to-miss. I often wonder how much low-relevance yada yada that Graham has to put up with before hearing the things that really matter. I admit that I tune out of background noise and may miss things I should be hearing. --Redrose64 🌹 (talk) 20:43, 25 April 2022 (UTC)

I think I've said something like this before, but if it weren't for the ability to cut off a screen reader's speech at any time, Wikipedia (and the web/computing in general) would be almost unusable for screen reader users. Graham87 01:26, 26 April 2022 (UTC)

I don't know if this is intentional, but I seem to keep getting the same notifications appear on my watchlist after dismissing the notification ... multiple times. For example, at the present time, there is a notification that there is an WP:RFA in progress and a notification for the most recent issue of the Signpost. However, after I dismiss these notifications, they stay dismissed until I log out and log back in ... then they reappear. If I recall, after a notification is dismissed, it stays dismissed, even after logging out and logging in. Is this not/no longer the case? Steel1943 (talk) 19:01, 26 April 2022 (UTC)

@Steel1943 the dismissing part is dependent on a client-side cookie (more technically a local storage object). So for example if you are using a private browsing session, it won't be maintained. — xaosflux ^Talk 19:10, 26 April 2022 (UTC)

Hi, I want to create a template like this {{#ifeq: {{{letter}}} | A OR B OR C | true | false }}. If you didn't understand, I will provide a specific example. Thanks! ⇒ AramTalk 21:01, 26 April 2022 (UTC)

@Aram,
{{ifor| test1 = {{{letter}}} | val1 = A | test2 = {{{letter}}} | val2 = B | test3 = {{{letter}}} | val3 = C | then = true | else = false}} ― Qwerfjkltalk 21:10, 26 April 2022 (UTC)

Or a casual {{#switch:}}. --Izno (talk) 21:11, 26 April 2022 (UTC)

Really amazing and helpful! Thank you both! ⇒ AramTalk 21:28, 26 April 2022 (UTC)

mw:Help:Extension:ParserFunctions##switch is certainly the best method if this is your real situation.

{{#switch:{{{letter}}}|A|B|C=true|false}}. That's all. PrimeHunter (talk) 22:14, 26 April 2022 (UTC)

I have just closed an RM at Talk:Ukrainian anti-Soviet armed resistance and noticed the links to its own article page are red, like in "moved to Ukrainian anti-Soviet armed resistance". The source seems to show just a regular link. Any idea what could be the issue? Vpab15 (talk) 22:41, 27 April 2022 (UTC)

A WP:PURGE seemed to have fixed it. Suffusion of Yellow (talk) 22:55, 27 April 2022 (UTC)

Great, thanks a lot! Vpab15 (talk) 23:06, 27 April 2022 (UTC)

I was using jQuery UI's date picker to format date strings, but it appears that this has been deprecated now, as I saw the message This page is using the deprecated ResourceLoader module "jquery.ui". Please use OOUI instead. in my Javascript console, but I couldn't find any date-related objects in OOUI. I know I can do it myself but I find it annoying to have to reinvent the wheel. Thanks in advance. —howcheng {chat} 04:39, 28 April 2022 (UTC)

There are mw.widgets.DateInputWidget and mw.widgets.datetime.DateTimeInputWidget. Nardog (talk) 04:45, 28 April 2022 (UTC)

Thanks, but I wasn't looking for UI widgets. DateTimeFormatter looked a little more promising but I can't quite figure out how to use it. I just went and did it the vanilla JS way. —howcheng {chat} 05:09, 28 April 2022 (UTC)

Moment is shipped with core so you can use it from ResourceLoader. Nardog (talk) 05:24, 28 April 2022 (UTC)

MediaWiki is allready moving away from Moment, see phab:T146798. Previous uses where replaced with Date.toLocaleString or an formatted date from the API. Anyway, just so you know, MediaWiki is eventually also going to go away from OOUI in several years time, to Vue.js, codex is the name of the WMF implementation of it.--Snævar (talk) 05:42, 28 April 2022 (UTC)

(Yay, someone saw the deprecation notice and did something about it!) Izno (talk) 05:29, 28 April 2022 (UTC)

@Izno: It was pretty lucky. I noticed my script stopped working due to changes in the API so I had to fix it, and while debugging I saw the console logs. —howcheng {chat} 07:37, 28 April 2022 (UTC)

If you have email notifications for pages on your watchlist enabled then you receive emails that start The Wikipedia page PAGENAME has been changed on 19 April 2022 by ... I'm dealing with a VTRS enquiry where someone wishes to suggest a change to the wording, but I don't know where to point them to initiate such a discussion. Is the notification content hosted here or on mediawiki? Nthep (talk) 10:38, 28 April 2022 (UTC)

@Nthep I think that is from one of these messages. We are unlikely to localize these without good reason though. If there is something that would make it better for everyone that uses any mediawiki installation, they can file a request at phab. — xaosflux ^Talk 12:49, 28 April 2022 (UTC)

@Xaosflux it's MediaWiki:Enotif body intro changed, the correspondent considers "was changed on" to be more grammatically correct than "has been changed on". Depending on how soon after the event you see the notification (e.g. next day) then they may have a point. Nthep (talk) 13:26, 28 April 2022 (UTC)

@Nthep ok, so since that is a semantic change, it should be done upstream (if it is warranted) - so they should file a phab feature request. They will need to register an account (here on Wikipedia is fine) then attach it to phabricator, then use this form. It may or not be accepted by the developers, but if so we will get the new verbiage here, and it will be available for translation on every project. I don't think we should localize this for only users with English as their primary language, and only on the English Wikipedia (then you would get different messages from other projects you also edit on). They certainly could start a discussion here and try to form a consensus for a local override if they really wanted to. — xaosflux ^Talk 13:42, 28 April 2022 (UTC)

Here Category:Tor (anonymity network) we have 2 large infoboxen templates that cover the actual content of the category. Can we move those to the bottom or rather should they just be removed? --Palosirkka (talk) 13:35, 28 April 2022 (UTC)

What do you mean they "cover the actual content of the category"? On the desktop site the navboxes are collapsed, and even if they're not because you're on the mobile site or have turned JavaScript off or for some other reason, you can just scroll down, can't you? Nardog (talk) 13:43, 28 April 2022 (UTC)

@Palosirkka those should be "collapsed" if they are not, make sure you have javascript enabled. As for your question though, it is not currently possible to put templates below the category listing. If this was an article or project page, we could - but the category page type doesn't support that format. — xaosflux ^Talk 13:44, 28 April 2022 (UTC)

I recommend removing these navboxes from the category page. It is quite uncommon to have them there, and their contents should duplicate the articles listed on the category page if the navboxes and categories are designed and assigned well. – Jonesey95 (talk) 13:59, 28 April 2022 (UTC)

Thank you all. I forget things look different with JavaScript (which I disable for security and privacy). I'll go ahead and remove them per Jonesey95. --Palosirkka (talk) 14:22, 28 April 2022 (UTC)

Resolved

 – GIGO. — xaosflux ^Talk 12:51, 28 April 2022 (UTC)

Transcluding the template if IP shows the result "You are not logged in" even though I am logged in.

Some specifications:

• I use Chrome 100.0.4896.127 stable on Windows 10 21H2. Using a Chromebook running on version 100 didn't change anything. Changing to Firefox, whether on Windows or on a virtual machine, didn't change anything.
• I use MVPS HOSTS for my hosts file to block advertising domains. Again, using a Chromebook or Firefox in a virtual machine, whose hosts files don't have anything, didn't work.
• I use uBlock Origin 1.42.4 to block any missing trackers. Disabling uBlock didn't change anything.

• Wikipedia and Wikimedia are both whitelisted. All traffic from the Wikimedia Foundation is whitelisted.

• I use Vector 2022 as my skin. Changing to Vector 2010 didn't affect anything.
• I'm a rollbacker and pending changes reviewer on enwiki. Other users on enwiki who have more permissions saw the template correctly.

• I don't have an additional account on Wikimedia per policy.
• I don't have two-factor authentication available in my account because I haven't sent a request at Meta.

• I have Hotcat, Lupin, ProveIt, Twinkle, wide-vector-2022, and WikEd. Disabling all of them did not work.
• The Chinese version of the template works.

Hopefully someone can help me with this.

— B. L. I. R. 04:35, 28 April 2022 (UTC)

@BeywheelzLetItRip: It uses code in MediaWiki:Group-user.css. What do you see here: You are not logged in. I see nothing. User:BeywheelzLetItRip/common.css should have CSS but it has wikitext. Maybe it contains something that messes up your other CSS loading. Try blanking it. If you want to transclude wikitext on your user page then I strongly recommend you don't place it in a CSS page. PrimeHunter (talk) 08:59, 28 April 2022 (UTC)

And if you do want to use that "css transclusion hack" don't do it on that page, use something like User:Username/fakecsspage.css — xaosflux ^Talk 10:26, 28 April 2022 (UTC)

I moved wikitext to a new stylesheet here and removed everything from the common.css file. It works now. — B. L. I. R. 10:56, 28 April 2022 (UTC)

Wikitext in a .css page is still very confusing and may cause trouble but at least it's not processed as CSS in your new fake css page. xaosflux wasn't suggesting to actually use a new .css page but merely saying it wouldn't be as bad as using common.css. PrimeHunter (talk) 11:35, 28 April 2022 (UTC)

Understandable, the protection policy for user pages does not say what the implications will be for users who are using transcluded CSS files on their user pages. It's only when a user attempts to create and/or edit a stylesheet that a warning appears. — B. L. I. R. 12:30, 28 April 2022 (UTC)

Agree, it's not "recommended" - it just won't also break other things. Base userpages are already semi-protected by an edit filter as well. — xaosflux ^Talk 12:51, 28 April 2022 (UTC)

Got it, thanks a lot for the help and for clearing the confusion up! I'll do my best not to break functionality via CSS. — B. L. I. R. 15:34, 28 April 2022 (UTC)

I have the watchlist set to show every revision of each article on my list displayed in bold, compared to the last time I checked the watchlist. I will go thru each revision (diff) in one article, clicking "next edit" till I get to the most recent revision of the article. I will then return to the watchlist and refresh to see all revisions from the article I visited as read (non-bold). Sometime later, though, I will notice on another refresh that some of the most recent revisions of the same article will be marked unread again. There's also times when I will only check some of the revisions of an article, and then check the watchlist to see that all of the revisions are marked read, when I didn't go thru all of them. What is going on?

I just cleared all cookies to all Wikipedia sites a few minutes ago, and the problem is still happening (for those of you suggesting that I clear cookies). MPFitz1968 (talk) 19:11, 28 April 2022 (UTC)

This is a recurring problem. It is tracked in T218511. I haven't noticed it for a while, but it just started happening again to me about two days ago. – Jonesey95 (talk) 19:25, 28 April 2022 (UTC)

I've been mulling over this for a while now, but I haven't the technical knowledge to know what could be done. I add a lot of language tags to Wikipedia – think {{lang}}, {{transliteration}} and the like – and the problem is that I'll go through an article, I'll mark up all non-English text with the correct template, and then editors adding new content, even content that features words marked up throughout, commonly just slap some italic markup either side and call it a day.

I know that consistency of edits is a problem, and that obviously some templates are going to be missed here and there. But these are articles with a lot of foreign-language text, articles where terminology is unavoidable and where that terminology is unavoidably not English. I've tried to inform editors here and there about language tagging, but that's no guarantee that they'll remember, and having to keep very large articles on my watchlist in the event that one or two language tags need adding in the future has resulted in my watchlist ballooning to 568 articles. And the articles I'm focusing on are pretty much only Japanese arts and culture articles.

I don't think this can be avoided by just informing enough editors about language tagging. There's too many articles, and I'm wondering if there's something technical that could be done about this. At the end of the day, it's consistent markup vital to accessibility that can be easily broken by unwitting editors. I figured I'd ask here, if nothing else.--Ineffablebookkeeper (talk) ({{ping}} me!) 17:53, 28 April 2022 (UTC)

"Is there a way to get people to do things they don't know they should do?" can unfortunately not be answered positively, especially since the addition of italics can be for non-language related reasons (ship, species, and work names prominently). We could theoretically ban the use of '' and ensure there are sufficient templates to cover the use cases for italics, but I don't anticipate that being favored by the general populace. We could add an edit notice for every page of interest, but that extends into the thousands or hundreds of thousands of pages where an English-foreign term is used.

Really the only thing you can do is tell people when you see it. Part of the note can be "if you see someone do it like you used to, let them know to change what they're doing too". Izno (talk) 19:31, 28 April 2022 (UTC)

It's a pain. As is the occasional default to Visual with the inability to preview. Doug Weller talk 11:07, 27 April 2022 (UTC)

If you use the {{Ping}} template in Visual it will nowiki it. Use the button instead. I personally haven't experienced it defaulting to visual or refusing to preview. --Ahecht (TALK
PAGE) 15:39, 27 April 2022 (UTC)

Thanks. I'll keep an eye on it more carefully to see if it goes to visual again. Doug Weller talk 15:44, 27 April 2022 (UTC)

In Visual mode, as you type {{ you should see a "Wikitext markup detected" notification at the top-right, warning you that you're using the visual editor. Note also you can ping in both visual and wikitext mode by typing @. — MusikAnimal ^talk 16:49, 27 April 2022 (UTC)

I didn’t know that, thanks. Doug Weller talk 17:35, 27 April 2022 (UTC)

@Ahecht: it works fine for me - I just used the ping template on you here. — xaosflux ^Talk 15:58, 27 April 2022 (UTC)

OK, think I was able to replicate the workflow that causes this. (a) Use reply tool (b) use the Visual Editor Mode (c) Use wikitext like a template (d) Ignore the toast that wikitext isn't supported in this mode. — xaosflux ^Talk 09:55, 28 April 2022 (UTC)

Probably. I presume "toast" means text? Doug Weller talk 09:57, 28 April 2022 (UTC)

Sorry, jargony. "Toast" is something that pops up :) If you try to put markup in replytool visual mode, you should get a pop-up notification warning you about it. — xaosflux ^Talk 12:55, 28 April 2022 (UTC)

Lol! Of course! Doug Weller talk 13:39, 28 April 2022 (UTC)

The ability to use templates in the visual mode depends on some background work. The software would need to be able to wrap a complex comment in some kind of code to indicate that this whole thing belonged in the "list" (the single item beginning with the ::::). Otherwise, if someone adds, say, an infobox, they'll get a mess. Right now, you'd get something like this:

::::{{infobox

::::| name=Alice

::::| country=here

::::}}

::::I have a question about this infobox.

But you want something like this:

::::<<<{{infobox

| name=Alice

| country=here

}}

I have a question about this infobox.>>>

(which would display as an infobox, not as a bunch of broken wikitext). Whatamidoing (WMF) (talk) 20:03, 28 April 2022 (UTC)

Hello! Is there any way we can do the following actions:

1. Change a page's title while creating it? (Example: I noticed I had a typo in my new page's title but the content is correct.)
2. Search for a page's title while being in https://en.wikipedia.org/w/index.php?search=.... (the page you get the search results when not jumping immediately to a page after searching for its title in the search box) and if it exists, immediately jump to it, not have it load up as a title there first and then have to click on it to open it. - Klein Muçi (talk) 11:11, 27 April 2022 (UTC)

1. There is no Wikipedia feature but it can be done in seconds with a Windows browser. Use Ctrl+A in the edit area to mark everything and Ctrl+C to copy it to the clipboard. Manually change the page name in the url and insert the copy with Ctrl+V
2. Search pages also have the normal search field. You would have to use that as far as I know. PrimeHunter (talk) 11:34, 27 April 2022 (UTC)

   @PrimeHunter, thank you for your answers! In regard to 1, changing the title in the URL is better than what I do, that is, creating a new page from scratch after copy-pasting the content. As for 2, that's what I'm referring to, the search field. If you search something there while being in the search page and the title you're searching for comes as a suggestion in it there is no way to just straight up to that page like when normally using the search field in, let's say, the main page, is there? (If my explanation is still not good enough, I can provide a specific example.) - Klein Muçi (talk) 11:51, 27 April 2022 (UTC)

   The page name can be clicked with right mouse and then open[ed] in new tab just like any other links. NguoiDungKhongDinhDanh 12:05, 27 April 2022 (UTC)

   @NguoiDungKhongDinhDanh, eh. I was hoping to not do that but instead have it behave the same as when you normally search something in the search box, that is immediately "jump", open the wanted title in the same tab. Looks like there is no way to do that. Thank you anyway! :) - Klein Muçi (talk) 12:11, 27 April 2022 (UTC)

   My browser's right-click menu lets me search for text I have highlighted, opening a new tab. It only offers my default search engine, but that could be set to Wikipedia. A third-party "Search with Wikipedia" add-on for Firefox adds Wikipedia search to the right-click menu; other browsers may have similar extensions. Certes (talk) 13:35, 27 April 2022 (UTC)

   I mean that Special:Search has two search fields, the normal search field on every page (the position depends on your skin) and the bigger field on search pages. As far as I know, only the normal search field has a feature to go directly to a page. Only the bigger field is prefilled with your previous search so it's inconvenient to use the normal field. PrimeHunter (talk) 12:08, 27 April 2022 (UTC)

   @PrimeHunter, oh... Funnily enough I hadn't been aware that there were 2 search fields which behaved differently. Any idea why does the "bigger field" behave like it does? What benefits are supposed to be had from that behavior, assuming that is intended? My first instinct is to ask "why can't we make both fields behave the same" but I'm assuming that change is deliberate. - Klein Muçi (talk) 12:14, 27 April 2022 (UTC)

   Many users don't know how to avoid the Go feature in the normal search field when they want to. The search page helps. PrimeHunter (talk) 18:18, 27 April 2022 (UTC)

   Interesting... To my everyday usage it feels like an extra step which only makes my usage feel more clunkier but I can see the need for it now. Thank you! - Klein Muçi (talk) 01:10, 28 April 2022 (UTC)

   MonoBook has separate "Go" and "Search" buttons. Vector's normal search box defaults to "Go", and the search box on Special:Search defaults to "Search". Whatamidoing (WMF) (talk) 20:05, 28 April 2022 (UTC)

Hi, I don't know if it's quite yet Thursday on the wiki, but I don't have a cursor in the reply tool. It's behaving perfectly normal, I just can't visibly see it. I've purged my cache, and tried a bunch of pages, but it's not there. The only code I've messed with in the past day was to DISABLE two scripts on my globaljs, so i doubt that affected me. Happy Editing--IAmChaos 04:01, 28 April 2022 (UTC)

 Works for me @IAmChaos: are you in visual editor mode or wikitext mode? If you start typing does it appear (i.e. is it just against the left border)? — xaosflux ^Talk 09:53, 28 April 2022 (UTC)

Hi, I am in source mode, and no it is still invisible when typing. I can tell where it is, because I can still type and move it with arrow keys and type between old text, it just doesnt visually appear. It's only in the reply tool, works in regular editing and in the quickedit box (I dont remember if quickedit is a script or gadget or what). Happy Editing--IAmChaos 09:57, 28 April 2022 (UTC)

This is a reply tool in visual mode. I mean to me it looks the same as source mode (without a preview), and there is still no cursor. Happy Editing--IAmChaos 09:59, 28 April 2022 (UTC)

@IAmChaos could you try using a different web browser to see if it is a browser-specific problem? — xaosflux ^Talk 10:27, 28 April 2022 (UTC)

Hey, So it's working on my alt on Chrome (there is a cursor). My main is on unmodified Safari 15.3. Unfortunately with a dead phone, I can't try my main on Chrome, my apologies. IAmChaos(alt acct - please ping my main) 10:31, 28 April 2022 (UTC)

Back on my main, I Did this to my commonjs, and it's still invisible after another cache clear. Happy Editing--IAmChaos 10:35, 28 April 2022 (UTC)

To rule out scripts, you could try to load this page in safe mode. Are you saying right now you only see this problem in Safari? — xaosflux ^Talk 12:52, 28 April 2022 (UTC)

In safemode now (Safari), and yes it is only safari that I see this issue. (including safemode) Happy Editing--IAmChaos 12:56, 28 April 2022 (UTC)

Can you reproduce this in the visual editor? Try https://en.wikipedia.org/wiki/User:Whatamidoing_(WMF)/sandbox?veaction=edit for the visual editor. Whatamidoing (WMF) (talk) 20:15, 28 April 2022 (UTC)

Is anyone able and wiling to add a feature or two to the Navigation popups gadget, please?

Specifically (and in order of my reference, FWIW) those described at:

• Wikipedia talk:Tools/Navigation popups/Archive 10#Wikidata ID
• Wikipedia talk:Tools/Navigation popups/Archive 11#Patrolling
• Wikipedia talk:Tools/Navigation popups/Archive 9#Template sandboxes and testcases

-- Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:13, 27 April 2022 (UTC)

You may check or file this at https://phabricator.wikimedia.org/tag/navigation-popups-gadget/ instead where feature requests for that gadget are handled. Malyacko (talk) 20:36, 27 April 2022 (UTC)

I have been told elsewhere (and some time ago) "This tool is not under active development ... If you want a feature, you will have to find someone willing to program it.". The Patrolling request has been on Phabricator since June 2019, with no substantive responses, other than support. The Wikidata request has been there since January 2020, with zero responses. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:19, 28 April 2022 (UTC)

I've noticed some experienced contributors are averse to the use of tables in articles. They claim tables are "too heavy" or "too distracting". This seems very strange to me. I think tables are very useful and they should be used whenever they work better than plain text. But I have to admit the tables in Wikipedia are visually heavier set than I would prefer. This may have something to do with the aversion some contributors feel. In his books, Edward Tufte advises using only the minimum amount of "data ink". As I interpret it, the absolute minimum of data ink in a table would be something like a very thin border of very light gray and no background color at all. But in Wikipedia, the tables are much much darker than this. Would it be possible to lighten up the default color of all tables in Wikipedia? I believe this could be achieved by adjusting two values in the CSS code that governs all tables. What would be the correct procedure for this? --Inehmo (talk) 19:40, 27 April 2022 (UTC)

@Inehmo: Tables should be used for tabular data, not for anything that subjectively "works better". Feel free to provide specific examples including full links. Thanks, --Malyacko (talk) 20:34, 27 April 2022 (UTC)

I created a few examples of what I had in mind. Here: https://fi.wikipedia.org/wiki/K%C3%A4ytt%C3%A4j%C3%A4:Inehmo/Hiekkalaatikko – Inehmo (talk) 22:53, 27 April 2022 (UTC)

The standard wikitable class is deliberately "light" with minimal background colors. Additional colors are added most often by fans of the particular page topic. (Sports is the worst issue in this regard.) There's only so much we can do about it; right now our minimum limit is basically at the point of WP:ACCESS color contrast requirements which we enforce by a template system. Izno (talk) 21:07, 27 April 2022 (UTC)

Accessibility is certainly a compelling reason. But a lighter background color would increase the contrast with text and thereby improve the situation. – Inehmo (talk) 05:07, 28 April 2022 (UTC)

Maybe I can be considered one of those editors. Even though not dealing that much with articles per se, after nearly 9 years of contributing around I'm still averse of tables in Wikipedia. Their overall usage feels very, very clunky technically vise and the visual aspect is generally unappealing and/or bland. In my decade of contributions I've only been forced to work "intensively" with tables only twice. One time I had to translate the contents of a table and it took me literal days to be able to preserve the original table structure without messing it while translating. The other time was this, a task which I couldn't accomplish even after asking multiple users for help. - Klein Muçi (talk) 01:06, 28 April 2022 (UTC)

I agree with you about tables being challenging to edit and modify in wikitext view. I don't use the beta Visual Editor, but I understand that it makes table editing a lot easier. – Jonesey95 (talk) 04:03, 28 April 2022 (UTC)

Yes, that is the more fundamental issue. I have some experience with many kinds of tables all around the web and I fully agree: tables are quite impossible in wikitext format. Their current implementation requires a thorough rethinking. Luckily, the Visual Editor is very capable. It is a great relief, if not a complete solution to the problem. – Inehmo (talk) 05:27, 28 April 2022 (UTC)

I hope I won't forget this topic until the new community wishlist happens. - Klein Muçi (talk) 13:06, 28 April 2022 (UTC)

Hey @Klein Muçi, you can make a note in Community Wishlist Survey/Sandbox :) SGrabarczuk (WMF) (talk) 20:14, 28 April 2022 (UTC)

@SGrabarczuk (WMF), thank you! Just did. - Klein Muçi (talk) 02:06, 29 April 2022 (UTC)

In the world of Featured/Good content, tables are a must, it seems, an indication of superior quality, I guess. Glad to see there are others who are table-adverse. They are irksome to read when long lines are stuffed into boxes with lots of line wraps - it seems tidy, except for those who consume the information. Bulleted lists are often better as you have the space and freedom to build out without being confined to tidy little boxes for the sake of signaling a quality production. -- GreenC 05:36, 28 April 2022 (UTC)

While working with Special:ProtectedTitles I saw that there are not a lot of things you can do at that page.

Do you think it would be beneficial to add the following options:

1. Allow ordering by level of protection and/or ending date of protection;
2. Show links beside entries for changing protection level ("similar" to what we get in Special:BrokenRedirects);
3. Maybe show the protection summary provided on each entry somewhere (maybe when hovering over them?)

All what I said above would be helpful in my admin work at SqWiki but I was wondering how would other admins here feel about those. - Klein Muçi (talk) 11:16, 25 April 2022 (UTC)

#1 may be expensive (ORDER BY outputs on huge outputs can be) - you can already filter results by namespace and level, perhaps a single additional filter of 'indefinite protections only' (like on Special:ProtectedPages) would work? — xaosflux ^Talk 13:49, 25 April 2022 (UTC)

#2 is a "meh" for me, you can do this client-side several ways already, it is already available in things like navpopups's on-hover menu — xaosflux ^Talk 13:45, 25 April 2022 (UTC)

#3 above is phab:T65318. — xaosflux ^Talk 13:44, 25 April 2022 (UTC)

I know nothing of query limits. If ordering is expensive, I believe enhancing ProtectedTitles to have the same interface as ProtectedPages would probably be enough. That idea is also entertained in the task you mentioned.

As for the change protection link, navpop is what I'm currently using for that as well. I just think that special pages themselves in general should have links that serve their main functions instead of acting just as lists. - Klein Muçi (talk) 16:03, 25 April 2022 (UTC)

I wonder what you actually need. Would a filter work (e.g., show full protection only, indef only, expiration date in the next week)? Maybe if you can tell us more about how you would use that information, we could come up with some options that aren't potentially expensive and would do what you need. Whatamidoing (WMF) (talk) 17:52, 25 April 2022 (UTC)

@Whatamidoing (WMF), given that indefinite protection is the default one, a lot of our admins use only that for their title protections no matter what the case. Currently I'm the only active admin for many months now. There are many cases where the protection shouldn't be indefinite, the most typical of which are the cases where the title is good on its own but it has been protected nonetheless because its content was being abused, for example "Albania's economy", with content such as: AAAAAAAAAAAhahahaha

So basically I'm reviewing the whole entries which are protected indefinitely and it felt a bit frustrating that I couldn't do much from that special page beside sorting by namespace and type of protection. - Klein Muçi (talk) 01:42, 26 April 2022 (UTC)

Reviewing is going to be slow this way. Would it help prevent this problem if the default was changed? I suspect that it's just a config change. Whatamidoing (WMF) (talk) 19:38, 28 April 2022 (UTC)

Hmm... Maybe that would be a good idea. - Klein Muçi (talk) 02:10, 29 April 2022 (UTC)

In this edit I tried to bring the template further up in the article as per MOS:LAYOUT, but as a user pointed out (and you can see it in the diff link preview), it creates an ugly gap between the title and the main content of the article. Why does this happen? 0xDEADBEEF (T C) 15:56, 29 April 2022 (UTC)

{{DISPLAYTITLE}} and {{Short description}} both creates no visible wikitext, so their lines are treated as blank ones. Try placing them on the same line? NguoiDungKhongDinhDanh 16:16, 29 April 2022 (UTC)

^ should work. Izno (talk) 19:38, 29 April 2022 (UTC)

There is a problem with the coding. {{DISPLAYTITLE}} creates an extra blank row while {{Short description}} doesn't. If we place {{DISPLAYTITLE}} under {{Short description}} as per WP:LAYOUT, this blank row will appear. If we delete {{Short description}} or place {{Short description}} under {{DISPLAYTITLE}}, the extra blank row will disappear. The only way to comply with the template order stated in WP:LAYOUT while avoiding that extra blank row is placing both {{Short description}} and {{DISPLAYTITLE}} on the same line, but it makes the codes look messy, I don't like it. 2001:8003:9008:1301:1516:F3EF:6434:339B (talk) 04:23, 30 April 2022 (UTC)

If you preview a page with nothing but

[[Foo|{{tq|Bar}}]]

{{tq|[[Foo|Bar]]}}

you get

<p>
  <a href="/wiki/Foo" class="mw-redirect" title="Foo">
    <style data-mw-deduplicate="TemplateStyles:r989825325">?'"`UNIQ--templatestyles-00000001-QINU`"'?</style>
    <q class="inline-quote-talk">Bar</q>
  </a>
</p>
<p>
  <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r989825325">
  <q class="inline-quote-talk">
    <a href="/wiki/Foo" class="mw-redirect" title="Foo">Bar</a>
  </q>
</p>

which appears like

Bar

Bar

If you preview

{{tq|[[Foo|Bar]]}}

[[Foo|{{tq|Bar}}]]

you get

<p>
  <style data-mw-deduplicate="TemplateStyles:r989825325">.mw-parser-output .inline-quote-talk{font-family:Georgia,"DejaVu Serif",serif;color:#008560;quotes:none}.mw-parser-output .inline-quote-talk-italic{font-family:inherit;font-style:italic}.mw-parser-output .inline-quote-talk-marks{quotes:"\"""\""}</style>
  <q class="inline-quote-talk">
    <a href="/wiki/Foo" class="mw-redirect" title="Foo">Bar</a>
  </q>
</p>
<p>
  <a href="/wiki/Foo" class="mw-redirect" title="Foo">
    <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r989825325">
    <q class="inline-quote-talk">Bar</q>
  </a>
</p>

which appears like

Bar

Bar

Naturally I want to use {{tq}} inside the link so the text turns green, but I can't do that unless the same TemplateStyles is called earlier on the page outside a link. Is this a bug or a feature? Has it always been this way? Nardog (talk) 14:06, 30 April 2022 (UTC)

As you may have noticed, Anomie added the relevant task. The way this might worked around would be something like {{tq|colorlinks=y|Example text}} which could add an appropriate class, and then TemplateStyles would add the appropriate CSS to color links. Obviously this would need to be opt-in. Izno (talk) 19:48, 30 April 2022 (UTC)

How many pixels should I set an image to that is best for both mobile and desktop?

The image in question is the map at the top of United States#Religion. If I just do the default without specifying pixels, the map doesn’t take up the whole width of the mobile screen, so it’s hard for readers to read the map legend. I think more pixels is obviously better, but I don’t wanna run into issues where it’s excessively large in desktop view, and/or protrudes past the right edge and requiring an unnecessary horizontal scroll bar just to look over the entire image.

I carried over the “300 pixels” setting from the previous outgoing image, and it’s slightly blurry in mobile view, not as clear as I would like. On desktop it still seems to be fine. It looks like the pixel setting only applies to mobile view?

Any assistance would be greatly appreciated. Thanks!

Mrbeastmodeallday (talk) 20:01, 30 April 2022 (UTC)

@Mrbeastmodeallday: You've set |350px, which is against MOS:IMGSIZE and WP:THUMBSIZE, particularly since it's not in the lead section. Since there is no |link= option, the image may be clicked to enlarge it, should users so desire. --Redrose64 🌹 (talk) 21:43, 30 April 2022 (UTC)

And it needs deletion as a BLP violation, see [4]. Thannks. Doug Weller talk 12:34, 1 May 2022 (UTC)

Deleted at Commons as copyvio. Doug Weller talk 13:43, 1 May 2022 (UTC)

As noted at WP:Bureaucrats' noticeboard#The time allocated for running scripts has expired, something has gone wrong with {{Centralized discussion}}. I previewed an edit of that template after replacing its contents with {{RfA watchlist notice|format=cent}}. I previewed it with Wikipedia talk:Centralized discussion. That showed Lua time usage 8.038/10.000 seconds so {{RfA watchlist notice}} is responsible. I don't have time to look any further at the moment and hope others will fix it! Johnuniq (talk) 10:56, 1 May 2022 (UTC)

It seems that, even though countRfas in Module:RFX report only needs to count the number of transcluded RFA pages, it's also parsing each RFA and counting the number of support/oppose/neutral votes on each. The counting of votes (specifically, the call to textSplit in parseVoteBoundaries in Module:Rfx) appears to be what was slowing things down so much. Now that Kusma has removed the call to that module from User:Amalthea/RfX/RfA count things should be back to normal. Anomie⚔ 15:53, 1 May 2022 (UTC)

On the page Royal and Prior School the map says aphoe instead of Raphoe. I can't find the map to change it, and probaby wouldn't know how to if I did. Does anyone know how to fix it? Thanks, DuncanHill (talk) 19:54, 1 May 2022 (UTC)

@DuncanHill: Try zooming in and you will see the full word. I'm not sure why, since the map is and has always been correct. NguoiDungKhongDinhDanh 20:09, 1 May 2022 (UTC)

@NguoiDungKhongDinhDanh: The page you linked to says "There is currently no text in this page. You can search for this page title in other pages, or search the related logs, but you do not have permission to create this page". Perhaps we could add a message to the infobox saying "zoom in for correct spelling". DuncanHill (talk) 20:14, 1 May 2022 (UTC)

@DuncanHill: Oops, my bad. Here it is. I suggest filing a Phabricator task instead of doing so. NguoiDungKhongDinhDanh 20:19, 1 May 2022 (UTC)

Done at https://phabricator.wikimedia.org/T307309 DuncanHill (talk) 20:35, 1 May 2022 (UTC)

I changed the default zoom level in the infobox; the full name now appears in the article. MB 21:17, 1 May 2022 (UTC)

Hi there...is there a way to hide Wikidata edits from being displayed on my watchlist? They clutter things up and at times overwhelm the actual edits I want to keep an eye on. There's a checkbox in Preferences for "Show Wikidata edits in your watchlist," but this is already unchecked for me and I'm still seeing tons of Wikidata edits. Thanks. WildCowboy (talk) 22:56, 1 May 2022 (UTC)

Under the "Mark all changes as seen" button, you can see a list of "Active filters". Does "Wikidata edits" appear in that list? If it does, disabling it should solve the issue. —CX Zoom[he/him] ^{(let's talk • {C•X})} 23:40, 1 May 2022 (UTC)

There is an option under "Type of Change" to filter for Wikidata edits, though not an option for "Not Wikidata edits." I'm assuming by checking all of the other options in that section and leaving Wikidata edits unchecked that I'll get what I'm looking for and not miss out on any other type of edits that I might want to follow. Will give it a try. Thanks! WildCowboy (talk) 23:55, 1 May 2022 (UTC)

Hello. The last set of improvements from WMDE’s Templates project will be deployed to English Wikipedia soon:

1) You’ll receive a fundamentally improved template dialog in VisualEditor and New Wikitext mode. This will make it easier to understand what is expected from a template, how to navigate the template dialog, and how to add parameters. These improvements have been active on a few wikis for some months already. The little video here summarizes the changes that were made. If you like to learn more, please visit our project page.

2) It will become easier to find and insert templates with an improved search and added warnings (in the TemplateWizard & in the template dialog of VisualEditor and New Wikitext mode).

3) In syntax highlighting (CodeMirror extension), a colorblind-friendly color scheme will be added. You’ll be able to activate it with a user setting.

The planned deployment for 1) and 2) on English Wikipedia is May 17. 3) is planned for May 10. These were the last three out of seven projects in the Templates focus area. Apart from these bigger projects, the Technical Wishes team improved a few other user-facing issues and fixed some bugs related to working with templates. You can learn more about it here.

Feedback on all the projects is much appreciated on their respective talk pages. – Thanks a lot on behalf of WMDE’s Technical Wishes team, Johanna Strodt (WMDE) (talk) 10:47, 29 April 2022 (UTC)

I'm confused. I thought this was already planned to be released previously? ― Blaze Wolf^Talk_{Blaze Wolf#6545} 13:28, 29 April 2022 (UTC)

Yes some of this was previously announced, but then delayed in the week that it was supposed to go live. —TheDJ (talk • contribs) 19:17, 29 April 2022 (UTC)

Ah alright. Thanks for the clarification. ― Blaze Wolf^Talk_{Blaze Wolf#6545} 19:22, 29 April 2022 (UTC)

@Blaze Wolf: Thanks for the question, and @TheDJ: +1, thanks for the clarification! We hope these changes will bring a significant improvement for working with templates. -- Have a good week, Johanna Strodt (WMDE) (talk) 07:38, 2 May 2022 (UTC)

For the past three days the Watchlist can take 15+ seconds just to respond to being clicked. Everything else responds normally as usual. soibangla (talk) 11:47, 1 May 2022 (UTC)

Happening for me too, even with a relatively small watchlist (sub-200 pages total). Buttons to Push Buttons (talk | contribs) 13:30, 1 May 2022 (UTC)

Same for me, sometimes 5 seconds, sometimes over 10. Kante4 (talk) 13:32, 1 May 2022 (UTC)

EVERYTHING is slowing down. Ongoing issue - see phab:T300914. I noticed it at both DYK and my watchlist a couple of days ago, and it just isn't getting better. — Maile (talk) 14:54, 1 May 2022 (UTC)

I came here to see if anyone else was experiencing this slowdown. Evidently so! It doesn't appear to be related to the size of the watchlist: I tested it with User:Smallerjim's watchlist which has only one item and it still takes about 10s, same as my main one. I haven't noticed an effect on anything other than watchlists, but if anything the delays there are increasing.  —Smalljim  15:07, 1 May 2022 (UTC)

Try turning down the enhanced filters - phab:T307214.--Snævar (talk) 15:30, 1 May 2022 (UTC)

Since MediaWiki:watchlist-messages transcludes Template:RfA watchlist notice, it's probably the same underlying issue as #Time-expired problem at Template:Centralized discussion above. I note that using a different language loads much faster, which further supports that guess. Anomie⚔ 15:34, 1 May 2022 (UTC)

I think parsing Tamzin's RfA every time might be causing it? I've tried this; does this improve things? —Kusma (talk) 15:46, 1 May 2022 (UTC)

@Kusma: Back to normal for me. Kante4 (talk) 15:48, 1 May 2022 (UTC)

Bravo. Well done, thank you. -Roxy the grumpy dog. wooF 15:52, 1 May 2022 (UTC)

Wait. How did that change affect me? -Roxy the grumpy dog. wooF 15:53, 1 May 2022 (UTC)

Much improved, thanks Kusma. Same question!  —Smalljim  15:58, 1 May 2022 (UTC)

To put what Anomie said slightly differently, the watchlist notice displaying the number of RfAs currently active was causing the slowdown, as it was changed earlier this year to parse the RfA page to count the RfAs. This change was reverted to be a hardcoded number (and so the number may lag the actual number once again). isaacl (talk) 16:02, 1 May 2022 (UTC)

I'll take my share of the blame; although I couldn't find the conversation in a quick search, I'm pretty sure I'm the one who suggested using the module to generate the count. (I didn't discuss the implementation, but I did look at it once it was implemented and didn't raise any red flags.) My apologies for the slowdown. isaacl (talk) 16:20, 1 May 2022 (UTC)

Back to normal for me, thank you! soibangla (talk) 16:04, 1 May 2022 (UTC)

Still don't understand what happened (too stupid for any technical stuff) but thanks. :D Kante4 (talk) 16:10, 1 May 2022 (UTC)

As I understand it, on everyone's watchlist there's a notice that pops up every time there's a new RfA (to encourage participation). Apparently it used to be updated manually, but when it was automated back in January it now has to read/parse(?) all of the edits in each outstanding RfA (I don't know why), and it has to do this even if the notice is no longer being shown because it's been closed. So Tamzin's current RfA, which has hundreds of edits is slowing it down. Is that anywhere near the truth, techies?  —Smalljim  16:37, 1 May 2022 (UTC)

Fairly close, since you asked. It doesn't parse the edits, but it does process the wikitext of the page enough to count the number of !votes in each section. And it doesn't actually have to do that, it just happens that the existing code that was re-used does so. Anomie⚔ 16:49, 1 May 2022 (UTC)

Wow! After reading the above, I simply dismissed the RFA notice, which never returned. And now my Watch List loads at lightening speed. — Maile (talk) 17:10, 1 May 2022 (UTC)

Hmm, not entirely convinced... I removed that RfA notice from my watchlist a couple of days ago, and although the list seems to load faster now, it's still loading noticeably slower than it used to. -- DoubleGrazing (talk) 11:54, 2 May 2022 (UTC)

While waiting (!) for the mobile user notification problem (WP:THEYCANTHEARYOU) to be one day maybe (!!) fixed, would it be a) possible and b) good idea to implement in the meantime a warning which automatically appears on the top of the user talk page of a user who is likely to be not getting notifications (ie. edits only or or mostly on an affected mobile device, and does not edit their talk page)?

I realise this would do nothing to help such users receive the said notifications, but it would at least make it easier for the rest of us to identify this as a possible explanation for their lack of response to warnings etc., helping to AGF and not raise blood pressures unduly. I've seen many user talk pages where the attempts at communicating with the user get increasingly desperate, until someone points out this as the likely reason. I just thought maybe that could be done automatically by way of some clever code.

Thoughts? -- DoubleGrazing (talk) 07:25, 30 April 2022 (UTC)

I don't see how "automatically" can be done. I would prefer to just disallow editing from any remaining THEYCANTHEARYOU system, ideally combined with pointers to our many working systems instead of a broken one. (This post was written on my phone using a browser and the Monobook skin, which is both easier to use and more powerful than any of the crippled "mobile solutions"). —Kusma (talk) 08:26, 30 April 2022 (UTC)

By "automatically" I meant some sort of user-side script which I could opt in and put in my common.js or somewhere. When I then visit a user talk page, the script checks the user's edit history and displays (to me) a warning, flagging up things like 'user has never edited their user talk page' or 'user edits using iOS devices only', or whatever the relevant criteria are. Is that not doable? -- DoubleGrazing (talk) 10:04, 30 April 2022 (UTC)

@DoubleGrazing, WP:SCRIPTREQ? Both of the flags you listed above are probably doable. ― Qwerfjkltalk 10:02, 2 May 2022 (UTC)

Thanks @Qwerfjkl — didn't even know such a place existed! :) Will try there... -- DoubleGrazing (talk) 11:55, 2 May 2022 (UTC)

Is there a way to see how much time you spend surfing/working on Mediawiki projects? I'm curious. - Klein Muçi (talk) 15:56, 27 April 2022 (UTC)

It would need to be client-side, logs of 'reading' pages is not available publicly for privacy reasons. — xaosflux ^Talk 16:02, 27 April 2022 (UTC)

@Klein Muçi This may not be exactly what you're looking for, but xtools' edit count report includes a timecard that shows what time of day and day of week your edits tend to occur on. ~ ONUnicorn^{(Talk|Contribs)}problem solving 17:41, 27 April 2022 (UTC)

Some tasks involve offline work, such as researching in books or analysing database dumps, and there's no way to record that. Most edits I can do in seconds but a few take days to prepare and that's not recorded anywhere. Certes (talk) 17:47, 27 April 2022 (UTC)

Thank you to everyone who commented! The timecard was indeed interesting in regard to my question. I was just curious to know how many hours a day I spend at "Wikipedia" averagely. The only reason I didn't say "Wikipedia" is because, beside changing back and forth between at least 3 different languages of Wikipedias, I also switch back and forth between different projects such as WikiQuote, Meta and MediaWiki. My ideal outcome would also take into consideration the time spent at the Phabricator, the Wikimedia Code Review and SWViewer (or even other offline work as user Certes mentions) but knowing such a thing could be hard to achieved (if not impossible, considering the offline element) I was mostly hoping for a "client-side tracking script" that could track the activity in the aforementioned MediaWiki projects but it looks like such a thing isn't really a thing so...

Thank you anyway! :) - Klein Muçi (talk) 00:52, 28 April 2022 (UTC)

Klein Muçi, you might find Wikiscan interesting. It has figures for average time per day on different projects. BlackcurrantTea (talk) 14:11, 2 May 2022 (UTC)

@BlackcurrantTea, I do. Any way I can change the project, let's say, for example, from SqWiki to EnWiki or MediaWiki?

Also, considering that these stats do exist, is it so hard to have a conglomerate of all projects in one place? That would be exactly what I'm looking for. - Klein Muçi (talk) 14:15, 2 May 2022 (UTC)

At the top, there's a list of projects on the right; click on each one to see the statistics. I don't know if there's a page with totals for all projects for a single user. I see the figures as an approximation of time spent doing things that the servers can record. As Xaosflux and Certes noted, there are many things that can't be tracked. BlackcurrantTea (talk) 15:16, 2 May 2022 (UTC)

While attempting to figure out how to use a tree list, I found Template:TreeList/Branch End and Template:TreeList/Final Branch which don't seem to do anything or be connected to anything. The creator has been indeffed for years, and these are only used in an abandoned user sandbox from said indeffed user. I imagine these are useless and should probably be deleted/redirected, but as "I don't see a use for this" isn't a valid deletion rationale, I wanted to see if anyone more familiar with the template space than me could determine if these are truly junk. Hog Farm _Talk 17:48, 2 May 2022 (UTC)

It would appear to be a duplicate of Template:Tree list/branching. Either redirect or send to TFD. Izno (talk) 18:02, 2 May 2022 (UTC)

I've redirected them. Hog Farm _Talk 18:07, 2 May 2022 (UTC)

19:32, 2 May 2022 (UTC)

When reading a Wikipedia page through Google Translate I get this mw.notify popup: "Central login You are centrally logged in. Reload the page to apply your user settings." I don't get it when I'm logged out on Wikipedia. Would this mean Google could see my username when I read a Wikipedia page through Google Translate? — Alexis Jazz (talk or ping me) 14:01, 2 May 2022 (UTC)

@Alexis Jazz when quickly looking at the debug from say "en-m-wikipedia-org.translate.goog" - I'm seeing tons of direct connections from my client to WMF sites. So I think this is a "maybe" - but not because Google is proxying your request, but possibly because your client is sending that data to Google yourself and asking them to translate it. — xaosflux ^Talk 14:14, 2 May 2022 (UTC)

Xaosflux, would it technically be possible for someone to set up "whatismywikimediausername.com", similar to sites like whatismyip.com? I feel like that shouldn't be possible (imagine for example a Christian school harvesting Wikimedia usernames from students to ensure they don't edit unholy subjects), but it scares me a bit that you said "maybe". — Alexis Jazz (talk or ping me) 14:53, 2 May 2022 (UTC)

Cross Original Resource Sharing is blocked by default in modern browsers, however most browsers have ways you can purposefully enable this. — xaosflux ^Talk 15:18, 2 May 2022 (UTC)

From what what I can gather looking at the requests, all the requests that are successfully being made that include your username are saving it in cookies only accessible by mediawiki sites. The request that gets your username to add to the central login notice doesn't go through properly, but even if that were fixed, it is would still be blocked by the Cross Origin Resource Sharing (CORS) policy. That's why you see the message "You are centrally logged in. Reload the page to apply your user settings." and not "You are centrally logged in as USERNAME. Reload the page to apply your user settings." So unless the CORS policy is ignored by the browser, it wouldn't be possible to create a site like "whatismywikimediausername.com". – BrandonXLF (talk) 19:38, 2 May 2022 (UTC)

Hi all, if you have ideas about an opt-in gadget to widen the viewport in vector-2022, feedback is welcome at MediaWiki_talk:Vector-2022.css#widener_gadget?. — xaosflux ^Talk 14:46, 26 April 2022 (UTC)

@Xaosflux: Would the CSS in the collapsed bit would sort of show what it would look like if it were implemented? ― Blaze Wolf^Talk_{Blaze Wolf#6545} 15:26, 26 April 2022 (UTC)

Need to be able to hide TOC like the Main Menu ....for more info see Wikipedia:Village pump (technical)#‎Side bar. Causing readability issues for those who use this on mobile view for full screenMoxy- 19:37, 26 April 2022 (UTC)

When did this change? It looks absolutely horrible on my widescreen monitor, most pages barely utilize more than like 10% of the total page width, and look almost as if CSS styles failed spectacularly! I'd like to know how to revert it ASAP! KPu3uC B Poccuu (talk) 13:01, 28 April 2022 (UTC)

In Special:Preferences#mw-prefsection-rendering, you can change Skin (I use "Vector legacy (2010)"), then click Save at the bottom. Certes (talk) 14:09, 28 April 2022 (UTC)

This doesn't change anything for me. Out of all present skins, only Monobook and Timeless (I think is its name) aren't width-limited. KPu3uC B Poccuu (talk) 06:59, 3 May 2022 (UTC)

Strange. I use Vector 2010 because it displays full width. I can't see any other options or gadgets that may impact this — GhostInTheMachine ^{talk to me} 10:43, 3 May 2022 (UTC)

This worked at one point:

.mw-page-container {
  min-width: none;
  max-width: 1300px;
  padding: 0;
}
.mw-workspace-container {
  max-width: 1400px;
}
.mw-content-container {
  max-width: 1400px;
}

I don't know if it works any longer. (You change the "1300px" and "1400px" to whatever numbers work for you.) Whatamidoing (WMF) (talk) 19:44, 28 April 2022 (UTC)

@KPu3uC B Poccuu (and FYI to @Whatamidoing (WMF)) there is an experimental gadget you can load from preferences (all the way down in "testing and development") called "wide-vector-2022", you can try that to reclaim your screen from all that whitespace. — xaosflux ^Talk 20:00, 28 April 2022 (UTC)

Hello all, I intend to remove the messagebox and standard-talk classes from Common.css Soon as a part of moving to TemplateStyles (see MediaWiki talk:Common.css/to do#description). This is because these classes already have well-known replacements (primarily {{ombox}} and {{tmbox}} and "hand-coded" tables/divs).

I am leaving this note here (atypically) because while I have done my best to remove the vast majority of uses that are "public facing" and not archived discussions/unused WikiProjects (see MediaWiki talk:Common.css/to do#messagebox; between this account and my repeat-edits account I'm in the 10k edits range mostly un-substing old AFD messages), I am essentially unable/unwilling to do anything about the 120 thousand uses on user and user talk pages. These uses are mostly WikiProject invitations and barnstars (as best I can, I've fixed the templates that generate the classes).

I do not think making changes to those pages makes sense. It is bot scale to preserve the width, centering, and background of these tables, which is not ultimately deleterious to the page content. However, I would anticipate many editors looking at their user pages and being sad.

I have previously written a transition guide for people who want to restore NavFrame-similar styles to their user pages (which had a similar issue), which I can do here as well if desired. It is fairly trivial in this case for individual editors to adjust their uses of these classes. I am not currently certain where that guide would live.

Please let me know what you think. Izno (talk) 21:33, 27 April 2022 (UTC)

It sounds to me like a reasonable idea. The old pages will still have its content preserved, which is the important thing in my opinion. as best I can, I've fixed the templates that generate the classes) is good to hear. Rlink2 (talk) 21:41, 27 April 2022 (UTC)

I've made up MediaWiki talk:Common.css/messagebox in case anyone wants to look at it and/or provide feedback. Izno (talk) 23:24, 29 April 2022 (UTC)

This is now done. Izno (talk) 21:35, 3 May 2022 (UTC)

If I go to the contribs page for a given user - say Special:Contributions/Redrose64 - open up the "Search for contributions" collapsed box, and select a namespace, I am then offered two more checkboxes: "Invert selection" and "Associated namespace". Whatever I do with those two, if I click on Search, then use my browser's "back" feature and open up the "Search for contributions" collapsed box again, the chosen namespace is still selected, but the two checkboxes are no longer present. To get them back, I need to select a different namespace, then reselect the one that I wanted first time. Firefox 99.0.1, all skins. --Redrose64 🌹 (talk) 20:45, 3 May 2022 (UTC)

I filed this as T307530 and I'll submit a patch. Fun little bug. Matma Rex talk 22:32, 3 May 2022 (UTC)

Thank you --Redrose64 🌹 (talk) 23:17, 3 May 2022 (UTC)

Is there an opption to not have the new contents side bar as this is causing mass sandwich effect for me....so bad many articles are non readable.--Moxy- 22:06, 25 April 2022 (UTC)

You are using Vector 2022 currently. If you wish to return to previous Vector, see Special:Preferences under the Appearance tab. Izno (talk) 22:42, 25 April 2022 (UTC)

That said, I've just now been given a dose of it offwiki and it's, uh, not pretty. Izno (talk) 22:48, 25 April 2022 (UTC)

Yes Vector 2022...its the skin we tell people that use desktop view on mobile devices to use////because it normally allows you to pick full screen ...as in no "Main menu" but now we have TOC there taking up even more room then the Main meun did. Moxy- 23:23, 25 April 2022 (UTC)

I don't think anyone should be suggesting Vector 2022 for mobile use at this time. Timeless, Minerva, and Monobook with the responsive option on are all more appropriate. Izno (talk) 23:45, 25 April 2022 (UTC)

Non allow full screen. To be honest its odd we dont have full screen option on all skins...no need for "main menu" all the time....plus its the way for editing in desktop view on mobile devices.-- Moxy- 00:30, 26 April 2022 (UTC)

And neither does Vector 2022. I do know it is trivial to get full screen in Timeless. Izno (talk) 01:22, 26 April 2022 (UTC)

What?/ full page view Moxy- 03:42, 26 April 2022 (UTC)

The linked Phabricator ticket, won't help with this particular issue (currently we hide the table of contents at low resolutions if you resize your browser, but this is viewport not window size). It likely needs a modification to the meta[name="viewport"] tag to set an initial-scale that zooms out to keep it consistent with the current legacy Vector experience.

Neither Vector's are responsive, so the phone is trying to compensate.

I'll have a think about this and get back to you later in the week with a more appropriate ticket. Jdlrobson (talk) 03:51, 26 April 2022 (UTC)

The static TOC in the sidebar is an accessibility issue - specifically, it fails MOS:COLOUR (second bullet) Links should clearly be identifiable as a link to our readers. - because the subsection names are shown in black, despite being links. --Redrose64 🌹 (talk) 21:08, 26 April 2022 (UTC)

This will be fixed with T306562. – Jonesey95 (talk) 14:42, 28 April 2022 (UTC)

Hey all - thanks for bringing these issues up. A quick update from the team's side. We are aware of some of the issues with the new ToC and are working on and deploying fixes this week and next week. In particular we're looking at the list below.

- ToC on narrower screens. We have increased the threshold for which the ToC currently hides to 1000px. (See T306904 for more context). This was to make it more comfortable to read on narrower screens. This is a temporary fix, though. The conversation about the best solution will continue in T306660. By the end of this week we hope to have clear next steps on our preference of the options presented there.

- We have begun the work on reducing the margins for screens between 1000px - 1200px. This will make the table of contents smaller and create more space for text. We will track this in T307004 and will probably have the implementation ready within a few days. OVasileva (WMF) (talk) 07:45, 4 May 2022 (UTC)

Restore ToC

Hi, how can I restore the old behaviour of the ToC in Vector 2022? The new one takes up almost a third of the screen. ―  Qwerfjkltalk 15:49, 2 May 2022 (UTC)

And by old behavior you mean...? Izno (talk) 18:01, 2 May 2022 (UTC)

If you mean that the TOC takes up too much screen width, maybe add the full width gadget referenced in the next section. That way, hiding the TOC will expand the main page area. If you mean the vertical "sticky" TOC, then you need to switch back to Vector 2010 — GhostInTheMachine ^{talk to me} 11:01, 3 May 2022 (UTC)

I guess you didn't get caught by the A/B testing Izno? Vector 2010's left-hand menu took 16% of my screenwidth. Vector 2022 took 0% (yay, a great gain in working space), this ToC on the left instead of at top experiment takes a massive 28%. It's ..., it's ... bleurgh! Cabayi (talk) 12:16, 3 May 2022 (UTC)

The benefits of using Timeless. Izno (talk) 17:32, 3 May 2022 (UTC)

More annoying is that the TOC is gone on mobile (desktop mode) due to the low screen width. ―  Qwerfjkltalk 20:00, 3 May 2022 (UTC)

I had trouble deciding where to report the Chromium regression in the Vector-2022 TOC, and only later found a discussion further up this page. I think it would be useful to have a place to focus reports, announcements, and comments rather than scatter them in this page and presumably others. Would it be possible to create its own talk page (if it doesn't exist) and, so long as it remains experimental, add static code creating a collapsible banner in the Vector-2022 skin only pointing to said page? If the page already exists, am I the only one who can't find it? David Brooks (talk) 14:21, 3 May 2022 (UTC)

@DavidBrooks probably mw:Talk:Reading/Web/Desktop Improvements is the best place for the near term, assuming you are not running in to something that only affects the deployment on the English Wikipedia. — xaosflux ^Talk 14:44, 3 May 2022 (UTC)

Agree, that being the talk page for mw:Skin:Vector/2022. --Redrose64 🌹 (talk) 19:49, 3 May 2022 (UTC)

I got a reply on mw:Talk:Reading/Web/Desktop Improvements#Provide a link to this page?: there already is a plan (phab:T307113) to add a pointer to that page in the Preferences/Appearance table next week. David Brooks (talk) 14:28, 4 May 2022 (UTC)

Hi all, I'd like to restrict several of my scripts to a certain time limit. So I'd like to know what code to use that is technically the same as the following line:

If current time is less than 1830hrs OR greater than 1930hrs, then
Run scripts

Thanks! —CX Zoom[he/him] ^{(let's talk • {C•X})} 14:56, 4 May 2022 (UTC)

@CX Zoom: here is a super quick example you can build from:

date = new Date();
time = date.getHours();
if (time <= 5 || time >=12) {
  mw.notify('The time is '+time);
}

This pop ups the current hour if it is before 5 or after 12. You can replace mw.notify('The time is '+time); with your list of scripts. — xaosflux ^Talk 15:26, 4 May 2022 (UTC)

Note that the Date() constructor uses your browser's time zone. NguoiDungKhongDinhDanh 15:44, 4 May 2022 (UTC)

The dark mode is too extreme in my opinion, the blue text doesn't really look very good on a black background. Can I suggest to any of the developers reading this to make the dark mode a dark grey with white text and lighter grey for article links, similar to the design of Wiki Wand? Though something which places the article titles on a black background with white text I think would be a good addition too, something to embolden the article names.The black is too extreme for the article backgrounds though. Perhaps an option to have the article title and side panels with black and white and the articles white and normal that would be useful rather than the whole thing black and white. ♦ Dr. Blofeld 08:58, 4 May 2022 (UTC)

@Dr. Blofeld please follow up at Wikipedia talk:Dark mode (gadget). — xaosflux ^Talk 15:03, 4 May 2022 (UTC)

Thanks.Zao.♦ Dr. Blofeld 16:35, 4 May 2022 (UTC)

Wikipedia being a very popular website can have a high impact in reducing global warming by reducing computer resource use in server and clients. More and more devices use OLED technology, and energy can be saved by using black backgrounds. Mobile vendors have automated this, switching to dark mode when battery is low.

Wikipedia's commitment to reduce global warming is mandatory. Let's set dark mode as default. Let's change the world. — Preceding unsigned comment added by 190.19.176.171 (talk) 22:09, 1 May 2022 (UTC)

To anyone interested, if you enable the dark-mode gadget and set window.wpDarkModeAutoToggle = true in your common.js, dark mode will automatically turn on/off when your device changes its colour scheme (eg. in Mac you can set system theme=auto so that dark mode is activated at sunset). – SD0001 (talk) 07:13, 2 May 2022 (UTC)

OP: [citation needed]. – Jonesey95 (talk) 23:15, 2 May 2022 (UTC)

OLEDs don't have a backlight, so dark mode does save a small amount of energy. I believe that most recent iPhones use this technology, and that almost no desktop computers do. On a modern non-OLED display, the energy difference is on the order of 5% of the power used by the display itself, which is not necessarily the most significant source of power use by the whole computer (power use depends significantly on what you're doing, not just whether the computer is turned on). Whatamidoing (WMF) (talk) 18:27, 4 May 2022 (UTC)

Hi all, I don't know where this query fits best, so I'm asking it here. Are newcomers who are guided by the Newcomers task feature, told about MOS:ENGVAR before giving them the task of copy-editing? So far, I've found quite a few Newcomer copyeditors switch British English to American one and vice-versa. If they aren't told about it already, can it be added to the guide somehow? (Noting that I know nothing about how this thing works) Thanks! —CX Zoom[he/him] ^{(let's talk • {C•X})} 19:28, 29 April 2022 (UTC)

Does not seem to be mentioned anywhere. The relevant guidance, reproduced here, is:

• MediaWiki:growthexperiments-help-panel-suggestededits-quick-start-tips

  Copy editing is about making a small fix to the way an article is written, such as spelling, grammar, or the clarity of the text. Copy edits help articles to be more professional and trustworthy.

• MediaWiki:growthexperiments-help-panel-suggestededits-tips-vector-visualeditor-copyedit-example-value

  Reaching Mercury from Earthh poses significant technical challenges.

• MediaWiki:growthexperiments-help-panel-suggestededits-tips-vector-visualeditor-copyedit-main-calm

  To make a difference, you only need to make one or two small corrections. You do not need to work on the entire article. You also don't need to have any special knowledge about the topic.

• MediaWiki:growthexperiments-help-panel-suggestededits-tips-vector-visualeditor-copyedit-main-rules1

  You can fix spelling and grammar errors. This might include sentences that are too long, repeated words, or incorrect punctuation.

• MediaWiki:growthexperiments-help-panel-suggestededits-tips-vector-visualeditor-copyedit-example-rules1

  Mars has has two small moons.

• MediaWiki:growthexperiments-help-panel-suggestededits-tips-vector-visualeditor-copyedit-main-rules2

  You can also rewrite sentences so that they do not contain opinions. Wikipedia content should be neutral, clear, and encyclopedic. However, be careful not to change the facts in the sentence.

• MediaWiki:growthexperiments-help-panel-suggestededits-tips-vector-visualeditor-copyedit-example-rules2

  Jupiter is the largest, and most interesting, planet in the Solar System.

• MediaWiki:growthexperiments-help-panel-suggestededits-tips-vector-visualeditor-copyedit-text-rules2

  This sentence contains an opinion that should be removed.

• MediaWiki:growthexperiments-help-panel-suggestededits-tips-vector-visualeditor-copyedit-main-step1

  Once you see a correction you want to make, click "Edit" to get started. Then go ahead and fix issues by deleting and typing as needed.

• MediaWiki:growthexperiments-help-panel-suggestededits-tips-vector-visualeditor-copyedit-main-publish

  Either find more changes to make, or go ahead and click "Publish changes" to publish your edit!

* Pppery * _{it has begun...} 19:52, 29 April 2022 (UTC)

So we should add "Do not change American to British spellings or vice versa" to main-rules1 ? —Kusma (talk) 07:57, 30 April 2022 (UTC)

I think we need to tell newcomers about that. Newcomers using the guide, thinking that they're making good contributions only to get reverted per ENGVAR doesn't look good. —CX Zoom[he/him] ^{(let's talk • {C•X})} 13:31, 30 April 2022 (UTC)

Is there a way to replicate newcomer messages on my account. —CX Zoom[he/him] ^{(let's talk • {C•X})} 13:37, 30 April 2022 (UTC)

Go to Special:Preferences#mw-prefsection-personal-homepage, turn on "Display newcomer homepage", then visit Special:Homepage * Pppery * _{it has begun...} 13:42, 30 April 2022 (UTC)

@Trizek (WMF), I think this is for you. Whatamidoing (WMF) (talk) 17:47, 4 May 2022 (UTC)

@CX Zoom @Kusma @Pppery, thank you for starting this feedback loop.

What we usually suggest is to edit local messages to fit local rules, only if there is no other way to pass an important information. This information has to be really important, and should not break the concise texts that already exists, because of the well known TL;DR effect.

I would suggest on main-rules1 to go with "You can fix spelling and grammar errors. This might include sentences that are too long, repeated words, or incorrect punctuation. Keep the English spelling used (British, American...)."

What do you think? Trizek (WMF) (talk) 19:08, 4 May 2022 (UTC)

@Trizek (WMF): I'm not fully convinced this is better than my suggestion. The advantage of your text is that it makes it clear that American and British English are not the only possibilities; that is the main reason I have not WP:BOLDly made a change yet. "Keep the variety of English used (British, American, ...)?" "Do not change the variety of English used (British, American, ...)"? It should be short and to the point, and probably not include a link, especially not to something as terrifying as the MOS. —Kusma (talk) 19:53, 4 May 2022 (UTC)

@Kusma, it is more encouraging to have Do-s rather than Don't-s. :) This is why I suggest along the lines of "Keep the variety of English used (British, American, ...)". I agree on keeping it short and to the point, and not including the link: a single sentence is supposed to suffice to explain this part of the MOS. But the final call is yours (yours as in "the community"). Trizek (WMF) (talk) 20:16, 4 May 2022 (UTC)

Seeking advice from anyone who uses Chrome. I use both Chrome and Firefox. In Firefox, we have a Settings tab that opens to a selection for Fonts. I've never had any issue with the Firefox fonts. In Chrome, I have the browsing window fonts the size and look I want. But no matter how I adjust Settings, Appearance, Fonts, my edit window has such teeny tiny fonts that I can't read them even with a magnifying glass. It's been this way for a while. I have one device that runs on Windows 10, and one that runs n Windows 11 - both have this issue with Chrome. Can anyone offer advice on how to adjust the edit window view in Chrome? Edge browser does the same as Chrome, but I rarely use Edge. Thanks. — Maile (talk) 22:55, 1 May 2022 (UTC)

@Maile66 this probably isn't it, but especially if you are using modern or monobook, you have kind of a mess of personal css going on. You are double importing the same personal user script in your common.css and your skin css'; but that script is then turning around and loading a gadget. If you want to use navpopups I suggest you remove all the entries to it in User:Maile66/common.css, User:Maile66/modern.css, and User:Maile66/monobook.css - and just use the gadget in preferences.

The next step to try would be to at least temporarily turn off everything in User:Maile66/common.js and see if your issue gets better. — xaosflux ^Talk 18:35, 4 May 2022 (UTC)

@Xaosflux: I don't use Monobook, but maybe I did in the past and it loaded. I deleted Monobook css and deleted the Modern css. So far, nothing changes on Chrome, but I haven't yet deleted that Modern css. FYI, I have a newer computer that I've just set up. On Firefox, I had these issues, until I installed NoScript, which magically corrected everything on that browser. I'm thinking I used to have NoScript on Chrome, but Chrome now blocks NoScript from being added, and deleted it from my Chrome browser some time ago. That might be why Chrome has gone weird. Wikimedia Commons itself looks strange to me on Chrome. — Maile (talk) 19:34, 4 May 2022 (UTC)

@Maile66 perhaps you have javascript disabled? See if you can see your own address on this page after clicking the button: Wikipedia:Get my IP address — xaosflux ^Talk 20:40, 4 May 2022 (UTC)

@Xaosflux: Yes, clicking on that link, and then clicking as instructed when it tells me to, brings up my IP address. — Maile (talk) 21:16, 4 May 2022 (UTC)

Why since 1-2 months this link loads very slowly and since few days it shows only "No result for source categories" while other categories works and loads fast? Time to time there is always some problem with this tool. If it's due to Wikimedia softare update - can't someone chceck if tool works before or atleast after update implementation? Eurohunter (talk) 12:08, 4 May 2022 (UTC)

You will need to ask the developer of Petscan. Izno (talk) 17:39, 4 May 2022 (UTC)

It's a problem that has been going on for at least four months. I first noticed it in early January this year. --Redrose64 🌹 (talk) 21:33, 4 May 2022 (UTC)

Hello, Village Pump Technical folks,

I was wondering if anyone here knew who or what bot was responsible for updating the Special Pages lists. Specifically, I'm interested in Special:UnusedCategories and Special:WantedCategories, lists which typically update every 3 days and are hours late updating today. The Wanted Categories helps us get rid of red link categories (per WP:REDNO) and the Unused Categories includes categories that are not included on the Database report of empty categories like maintenance categories so it is very useful. If I had my way, these lists would update daily, not every 3 days but, again, I'm not sure who to contact about this. The lists do have talk pages but if you visit them, you'll find questions posted from years ago that were never replied to so I'm not sure who is involved with maintaining these "special pages".

Any help or referral to who I could ask about this delay in posting the lists, would be much appreciated! Thanks! Liz ^{Read! Talk!} 20:02, 1 May 2022 (UTC)

MediaWiki itself updates the lists automatically and periodically. It is also reported that other things have been much slower recently, so I guess this is just another one in multiple of consequences. NguoiDungKhongDinhDanh 20:24, 1 May 2022 (UTC)

Those can't really be put on an less than 3 day update scheme, because all of the special pages collectively take 3 days to update - source: phab:T17434. Those are the responsibility of the developers.--Snævar (talk) 20:36, 1 May 2022 (UTC)

Thank you so much for this information, NguoiDungKhongDinhDanh and Snævar, this is much more than I knew before about this group of pages. If it is coming from MediaWiki, well, then there is no bot operator I can try to convince to change the timing. I'll just be grateful for the reports when they do get updated. Thanks again. Liz ^{Read! Talk!} 21:36, 1 May 2022 (UTC)

The special pages I use updated, as expected, on today, May 4th, so I guess what was broken has been fixed. Again, I appreciate the information provided here. Liz ^{Read! Talk!} 05:55, 5 May 2022 (UTC)

• Edge version: 100.0.1185.50 (64-bit)
• Chrome version: 100.0.4896.127 (64-bit)
• Issue: On gallery templates, image previews look noticeably worse

Tube·of·Light 14:31, 4 May 2022 (UTC)

I'm not exactly seeing the issue here. The images look perfectly fine. ― Blaze Wolf^Talk_{Blaze Wolf#6545} 14:33, 4 May 2022 (UTC)

On the top four picture thumbnails there is some weird phenomenon kinda like aliasing (the left side of the linked picture). When I click on the thumbnails, it shows clear pictures. Tube·of·Light 16:09, 4 May 2022 (UTC)

Ohhh! I see now. They're slightly pixelated. I was bit confused when you said the images were blurry. ― Blaze Wolf^Talk_{Blaze Wolf#6545} 16:11, 4 May 2022 (UTC)h

I can reproduce the issue in the same article as OP. The issue here seems to be related to wrapping the gallery onto multiple lines. If all the images are on the same line you get undersized and blurry previews, if you adjust the browser window so that the gallery wraps onto multiple lines they pop back to being full quality. 163.1.15.238 (talk) 15:13, 4 May 2022 (UTC)

I checked just now and the images are blurry at zoom levels of 100% and lower, while zooming to 110% or higher fixes the issue. Tube·of·Light 16:11, 4 May 2022 (UTC)

Gallery's do some up/down scaling at certain sizes, depending on the available space in the page, to try to make them fit the entire width of the page. This scaling can definitely have this effect and there probably is a bug that scales it down by 1 pixel, even at 100%. This is pretty old code that does this, and in hindsight, probably wasn't the smartest idea to add it at all, but its been in place for 10'ish years. The whole thing is not helped by the fact that Windows isn't that good at scaling images/text. —TheDJ (talk • contribs) 09:09, 5 May 2022 (UTC)

Hello! I'll be developing an all-purpose file tool that includes the feature to detect potential copyright-violating images that also appear on the Internet. I thought it would be a good idea to request a Movement Strategy Implementation Grant from the Wikimedia Foundation. You can find more information about the scope of the tool and the grant on m:Grants:Project/MSIG/EpicPupper/Fortuna. Feel free to leave comments, questions, suggestions, or ideas on the grant talk page, and endorsements or offers to translate or localize the tool in the relevant sections. Thanks! 🐶 EpicPupper ^{(he/him | talk)} 09:24, 5 May 2022 (UTC)

Hi, I want to copy a specific part of a RAW Html content, but I don't know how to do it. For example, I want to get <pre>...</pre> content in this link and then use it in a Mediawiki namespace page. Thanks! ⇒ AramTalk 00:07, 29 April 2022 (UTC)

@Aram don't think that is very feasible (maybe with some Lua) - what is the end result you are trying to accomplish, perhaps there is another way to go about it. — xaosflux ^Talk 11:50, 29 April 2022 (UTC)

Special:ExpandTemplates may be helpful to strip template content. Otherwise look at the page source, on Firefox it is more tools > view source. --Jules (Mrjulesd) 13:05, 29 April 2022 (UTC)

@Xaosflux and @Mrjulesd I want to add a drop-down list to Special:Upload (on ckbwiki) to add non-free templates (i. e. Template:Non-free use rationale album cover) just like Licensing drop-down list. And I wrote some codes (see below), but I don't know how to get those template codes.

var albumCoverValue = "Album Cover template";

var templateTypeLabel = '<td class="mw-label"><label for="templateType">Template type:</label></td>';
var selectTag = '<select name="templateType" id="templateTypeSelector" onchange="changeOption(this)">' +
    '<option value="">Choose</option>' +
    '<option value="' + albumCoverValue + '">Album Cover</option>' +
    '<option value="poster-value">Poster</option>' +
    '</select>';

var selectTagWrapper = '<td class="mw-input">' + selectTag + '</td>';

$('.mw-htmlform-field-HTMLTextAreaField').after('<tr class="mw-htmlform-field-Non-free-use-rationale-templates">' +
    templateTypeLabel + selectTagWrapper + '</tr>');

function changeOption(selected) {
    var x = selected.options[selected.selectedIndex].value;
    document.getElementById("wpUploadDescription").value = x;
}

Try above in console. We should do something to get template codes for albumCoverValue variable. ⇒ AramTalk 18:28, 29 April 2022 (UTC)

@Aram: Try using a JSON page? NguoiDungKhongDinhDanh 19:09, 29 April 2022 (UTC)

@NguoiDungKhongDinhDanh I've never worked with JSON. Do you have any idea? ⇒ AramTalk 19:46, 29 April 2022 (UTC)

@Aram: You apparently know JS, so I think I can safely assume that you also know what JSON is. Create a JSON page (by changing content model or using a title that ends with .json) with all template codes, then use some JS code to query that page's content. NguoiDungKhongDinhDanh 19:53, 29 April 2022 (UTC)

I suggest you just add as a section within your existing form; they can be seen here: MediaWiki:Licenses; attempting to insert additional input boxes there will likely become problematic with different skins and with different releases. I sent you a note on ckbwiki where I might be able to look further. — xaosflux ^Talk 19:54, 29 April 2022 (UTC)

@NguoiDungKhongDinhDanh I have basic information about it, but I haven't worked on it. Of course, I have created Wikipedia JSON pages, but those were just a copy-paste from other projects (without my skills). So far, I have no idea how to get information from it, but now you've given me some ideas about how it works, and I thank you for that. I need to read some information about it so I can work with it. Thank you!

@Xaosflux I'm not technically that good. But I don't know how the MediaWiki:Licenses page can add those templates contents to the box. If we do so, it may be confused because it merges with the license section. Anyway, I'll wait for your notes. ⇒ AramTalk 20:32, 29 April 2022 (UTC)

@Aram: When you edit MediaWiki:Licenses the bulleted items work like this:

*$TemplatePageName|$Label

So for example on w:ckb:MediaWiki:Licenses there is a line:

*cc-by-3.0|Creative Commons Attribution 3.0

This uses the template at w:ckb:داڕێژە:Cc-by-3.0

So create any templates you want, apply appropriate protection to them, then edit that Licenses page to add them. Is that what you are looking for? — xaosflux ^Talk 20:50, 29 April 2022 (UTC)

@Xaosflux No, I'm not talking about the licensees, but about the usage of Template:Non-free use rationale. On ckbwiki, only the ckb:Template:ھۆکاری بەکارھێنانی نائازاد provided (see ckb:میدیاویکی:Onlyifuploading.js#L-20). There are more templates (see Category:Non-free use rationale templates). I mean how to add those templates usage codes to the box instead of the ckb:Template:ھۆکاری بەکارھێنانی نائازاد? Am I clear? ⇒ AramTalk 21:21, 29 April 2022 (UTC)

Think I'm missing your goal a little bit. Your Special:Upload already includes lots of non-free templated options, you can remove ones that you don't want be editing the Licenses page as well. — xaosflux ^Talk 21:43, 29 April 2022 (UTC)

Hello again @Xaosflux and @NguoiDungKhongDinhDanh, Sorry for reopening this section. I was about to read those documentations User:NguoiDungKhongDinhDanh had provided here and they were very useful for this case. I tried to get some information through JSON, I updated the code above according to those documentations and produced the below code; I'm not that good at coding, but anyway, I made something.

// Choose a non-free template

var url = "https://test.wikipedia.org/w/api.php?" +
	new URLSearchParams({
		"action": "query",
		"format": "json",
		"prop": "revisions",
		"revids": "363256|511722",
		"formatversion": "2",
		"rvprop": "content|ids"
	});

//try {
async function getTemplates() {
	var req = await fetch(url);
	var json = await req.json();

	var query = json.query;
	var Non_free_use_rationale = query.pages[0].revisions[0].content.valueOf();
	var Non_free_use_rationale_poster = query.pages[1].revisions[0].content.valueOf();
	//var comingSoon = query.pages[0].revisions[0].content.valueOf();

	var
		optionText = "Choose", // Disabled

		optionText1 = "Non free use rationale",
		optionVal1 = Non_free_use_rationale,

		optionText2 = "Non free use rationale poster",
		optionVal2 = Non_free_use_rationale_poster;

	//optionText3 = "More coming soon...",
	//optionVal3 = comingSoon;

	var optionTags = $('#templateTypeSelector')
		.append($('<option>').text(optionText).attr('disabled', 'disabled'))
		.append($('<option>').val(optionVal1).text(optionText1))
		.append($('<option>').val(optionVal2).text(optionText2));
	//.append($('<option></option>').val(optionVal3).text(optionText3));

	var templateTypeLabel = '<td class="mw-label"><label for="templateType">Template type:</label></td>';
	var selectTag = '<select name="templateType" id="templateTypeSelector" onchange="changeOption(this)">' + optionTags + '</select>';
	var selectTagWrapper = '<td class="mw-input">' + selectTag + '</td>';

	$('.mw-htmlform-field-HTMLTextAreaField').after('<tr class="mw-htmlform-field-Non-free-use-rationale-templates">' +
		templateTypeLabel + selectTagWrapper + '</tr>');
}

function changeOption(selected) {
	var x = selected.options[selected.selectedIndex].value;
	document.getElementById("wpUploadDescription").value = x;
}
getTemplates();

//}
/*catch (e) {
	console.error(e);
}*/

Please notice that I changed the API source and it's "revids" to allow you try the the code (here: Special:Upload on testwiki) in your browser console and see a drop-down list created just above the "Licensing" drop-down list, but the problem here is an empty list, which produces [Object object], but if try the same code again just after the first time, you now can see the drop-down list we wanted. Can you tell me why it's not completely created at the first time? And if you have any other note about the code, I'm glad to hear them. Thanks! ⇒ AramTalk 13:40, 3 May 2022 (UTC)

@Aram: I'm not sure why your code doesn't work, but here's how I write it:

$(function() {
	(new mw.Api()).get({
		action: 'query',
		prop: 'revisions',
		revids: [363256, 511722],
		rvprop: ['content', 'ids'],
		format: 'json',
		formatversion: 2
	}).done(function(response) {
		var options = [];
		var text = ['Choose', 'Non free use rationale', 'Non free use rationale poster']; // etc.
		options.push({
			text: text[0]
		});
		for (let i = 0; i < response.query.pages.length; i++) {
			options.push({
				text: text[i + 1],
				value: response.query.pages[i].revisions[0].content
			});
		}
		
		$('.mw-htmlform-field-HTMLTextAreaField').after(
			$('<tr>').addClass('mw-htmlform-field-Non-free-use-rationale-templates').append(
				$('<td>').addClass('mw-label').html($('<label>').attr('for', 'templateType').text('Template type'))
			).append(
				$('<td>').addClass('mw-input').html(function() {
					var r = $('<select>').attr('name', 'templateType').attr('id', 'templateTypeSelector');
					for (let i of options) {
						console.log(i);
						if (i === options[0]) {
							r.append($('<option>').text(i.text));
						} else {
							r.append($('<option>').val(i.value).text(i.text));
						}
					}
					return r;
				})
			)
		);
		$('#templateTypeSelector').on('change', function() {
			$('#wpUploadDescription').val($(this).val());
		});
	});
});

NguoiDungKhongDinhDanh 14:29, 3 May 2022 (UTC)

 Great! @NguoiDungKhongDinhDanh: I really want to thank you! Thank you for rewriting, cleaning the code up and removing any potentially error! It's working properly now! ⇒ AramTalk 17:44, 3 May 2022 (UTC)

@Aram: Hi, you may want to make it a gadget and add a condition instead of inserting directly to MediaWiki:Common.js which will be load for every user on every page. NguoiDungKhongDinhDanh 15:41, 4 May 2022 (UTC)

NguoiDungKhongDinhDanh Done, but after creating the gadget (see ckb:میدیاویکی:Gadget-UploadTemplates.js), it doesn't worked and produced this error: JavaScript parse error (scripts need to be valid ECMAScript 5): Parse error: Unexpected token; token ; expected in file 'MediaWiki:Gadget-UploadTemplates.js' on line 33. I think this is related to phab:T75714. Do you have any idea? ⇒ AramTalk 14:36, 5 May 2022 (UTC)

Change let into var. ES6 is no supported for directly loaded JS, only inside lazy loaded JS under certain conditions. —TheDJ (talk • contribs) 14:42, 5 May 2022 (UTC)

This is highly recommended. You will also need to change line 46 to var j of options, as well as all of its usage in the loop (i to j) to avoid potential overlapping. NguoiDungKhongDinhDanh 14:48, 5 May 2022 (UTC)

@Aram: As mentioned in the task, you can move the real code to somewhere else while keeping a mw.loader.load at the gadget page. NguoiDungKhongDinhDanh 14:43, 5 May 2022 (UTC)

@TheDJ and @NguoiDungKhongDinhDanh, Thank you both! It works now. But in the line 46, I just changed the let to var (because var j of options is not working). As a result, I just loaded the gadget (ckb:میدیاویکی:Gadget-UploadTemplates.js) and changed let to var. That is all. Special thanks to you all! ⇒ AramTalk 15:40, 5 May 2022 (UTC)

Hi, in the new vector (2022), the "table of contents" exists in the left side bar, as the last item of it. The problem is that all of headings and subheadings listed in this table misses a hyperlink that redirect the page to the related heading/subheading. I mean, after the event of "clicking on the text" we should scroll/redirect to a heading (via a URL, that its "heading text" is preceded by a "#" sign).

For example, when we open the article Variety_(universal_algebra) in the new vector (2022), there exists a table of content in the left side bar that if we click, for example, on the "Definition" item of that list, no action happens for now, but the correct scenario is that, after clicking, we should scroll the page to the section "https://en.wikipedia.org/wiki/Variety_(universal_algebra)#Definition". Please add required hyperlinks to the table of contents items in the new vector. Thanks, Hooman Mallahzadeh (talk) 10:10, 1 May 2022 (UTC)

This is a bug in the latest version of Chrome —TheDJ (talk • contribs) 11:17, 1 May 2022 (UTC)

@TheDJ: I am using Microsoft Edge browser, and this problem exists there. Hooman Mallahzadeh (talk) 11:29, 1 May 2022 (UTC)

@TheDJ But Opera browser has no such a bug. Hooman Mallahzadeh (talk) 11:32, 1 May 2022 (UTC)

@TheDJ A browser layer, like Chrome or Edge, is under the layer of a web pages of a website, like articles of Wikipedia. So this bug is on behalf of Wikipedia not from these browsers. We should change and modify Wikipedia such that it would be compatible with all types and versions of browsers like Edge.

Note that we should write Wikipedia webpages in a version of HTML language that is the most standard and basic tags of it, so that a it should not be dependent on a specific version of HTML. The uncompatibility that we face here, exactly comes from the neglection of this principle. Hooman Mallahzadeh (talk) 11:50, 1 May 2022 (UTC)

The browser version has been out for just a couple of days, fixing bugs takes time. —TheDJ (talk • contribs) 21:04, 1 May 2022 (UTC)

Yes, Chromium, which is the rendering engine for Chrome, is also used for the same purpose in Edge. It would naturlaly occur in both. Izno (talk) 17:06, 1 May 2022 (UTC)

Although (as I note below) a device may have different Chromium versions installed with the two browsers at any given time due to different update cycles, which is why I saw different behavior between them. David Brooks (talk) 00:23, 3 May 2022 (UTC)

Vector-2022 sidebar not clickable in Edge

Subject line says it. Using Edge (version 101.0.1210.32), I can't click the TOC sidebar; also the "page-down" scrolling behavior switching between the sidebar and the main text is hard to describe or predict. The TOC does work as expected in Chrome, which is odd because the two browsers share an engine. Sorry, but I don't know of a better place to record skin problems. David Brooks (talk) 13:30, 2 May 2022 (UTC)

DavidBrooks, phab:T307360 — Alexis Jazz (talk or ping me) 14:05, 2 May 2022 (UTC)

Now phab:T307271. — xaosflux ^Talk 14:09, 2 May 2022 (UTC)

Which is now fixed; thanks to the developers. I've been retired from the business too long, and I apologize for not also reporting my Chrome version, which was 100.0.4896.127. The Chromium (shared by Chrome and Edge) regression was introduced between those builds. David Brooks (talk) 00:20, 3 May 2022 (UTC)

@Xaosflux@DavidBrooks@Alexis Jazz Today, the same problem raised again in Edge. Hooman Mallahzadeh (talk) 09:07, 5 May 2022 (UTC)

Thanks for the note, I see phab:T307271 is reopen. — xaosflux ^Talk 09:45, 5 May 2022 (UTC)

@Hooman Mallahzadeh, Xaosflux, and Alexis Jazz: I'm not clear whether the WP HTML fix also works in the older browser releases (100.x) as well as 101.x, where the Chromium regression happened. Did the fix for 101 break 100? In any case, Hooman, it's probably worth while to check your Edge version. Use ..., Settings, About Microsoft Edge. David Brooks (talk) 16:21, 5 May 2022 (UTC)

@DavidBrooks This problem raised today temporarily, for about 4 or 5 hours. But now in my version of Edge browser (Version 101.0.1210.32 (Official build) (64-bit)), ToC links are clickable, too. Thanks for your reply. Hooman Mallahzadeh (talk) 16:40, 5 May 2022 (UTC)

@Hooman Mallahzadeh: Happy to help. I believe Edge does quietly update itself when it's in the mood (it can take MS a few days to roll out updates of anything Windows-related). I'm on 101.0.1210.32. David Brooks (talk) 16:47, 5 May 2022 (UTC)

For some reason at thumbnail size the legend of File:2022 Russian invasion of Ukraine.svg at bottom left appears in English, but the full size shows legend in Russian. Is it fixable? Also, the names of smaller villages and towns are illegible even at full size, but this is for Graphics Lab, it seems. Brandmeister^talk 15:53, 1 May 2022 (UTC)

@Brandmeister: You are using Russian as interface language, not? NguoiDungKhongDinhDanh 16:09, 1 May 2022 (UTC)

No, it seems, the Render this image parameter below the image is set to English and in my Preferences, Internationalisation is set to en - English. Brandmeister^talk 16:16, 1 May 2022 (UTC)

After a while playing with it myself, I guess this is the intended behaviour, and that there are no bugs to be fixed. You can view any version by appending ?lang=langcode to the URL. NguoiDungKhongDinhDanh 16:32, 1 May 2022 (UTC)

@Brandmeister: The original SVG file has text versions in multiple languages and your browser apparently chooses Russian. Mine chooses English. A thumb version is not an SVG file but a PNG rendered by MediaWiki which chooses English at the English Wikipedia, Russian at the Russian Wikipedia and French at the French Wikipedia (I didn't test the remaining languages in the SVG file). PNG is a purely graphical image format which doesn't support text in multiple languages. It doesnt support text at all but just displays an image which may contain symbols interpreted as text in some language. PrimeHunter (talk) 23:27, 3 May 2022 (UTC)

How odd, ok. Brandmeister^talk 18:30, 4 May 2022 (UTC)

@Brandmeister: It's determined by the browser and not MediaWiki when you view the original file. Your browser may have a way to set a list of preferred languages. My Firefox does. If you prefer English then you can examine browser settings or ask for help at Wikipedia:Reference desk/Computing. Remember to name your browser. The setting can also affect multilingual websites. PrimeHunter (talk) 19:32, 5 May 2022 (UTC)

I use Firefox in Russian and now understand it, it seems. But on the other hand this is counter-intuitive and at first looks like odd behavior. Brandmeister^talk 19:40, 5 May 2022 (UTC)

In some regex implementations, \U, \L, \I and \F change case (to upper, lower, intials and first, respectively). Does the regex replace in WP's source editor do that? Cheers. — Guarapiranga ☎ 11:57, 3 May 2022 (UTC)

@Guarapiranga: No, since they are not supported by JS regex. NguoiDungKhongDinhDanh 13:10, 3 May 2022 (UTC)

Wouldn't testing it be a quicker way of knowing? Izno (talk) 17:34, 3 May 2022 (UTC)

I did, of course, thank you. My question was whether it had any particular, perhaps undocumented, syntax that did that. — Guarapiranga ☎ 23:53, 5 May 2022 (UTC)

You can do some things by replacing with a subst expression using string templates. See e.g. Template:String-handling templates. PrimeHunter (talk) 18:14, 3 May 2022 (UTC)

Right! Hadn't thought of that, PrimeHunter. Thanks.

P.S.: Actually, this is what I needed. — Guarapiranga ☎ 23:55, 5 May 2022 (UTC)

After the help I got here I was able to make this script work. Is anyone crafty enough to point me how to rewrite it in a more elegant way so I don't have to rewrite lines like I've already done? - Klein Muçi (talk) 00:23, 5 May 2022 (UTC)

VPT is not a general support forum. Either return to the reference desk or try one of the many other forums on the Internet. Izno (talk) 01:31, 5 May 2022 (UTC)

@Klein Muçi the link doesn't work for me.

While i do think generally the VPT should be restricted to wikipedia, I'm not totally opposed to this request because there are many people here who would know how to fix it but dont watch that page. Besides, the ratio of Wikimedia to non wikimedia stuff Klein posts on here is very very very high so I don't think one off topic request is a bad thing. Rlink2 (talk) 01:58, 5 May 2022 (UTC)

@Izno, is the Reference Desk located so far from the VPT as to treat like a whole different place? Just to be clear I was surprised myself when I heard about the existence of the ref-desk in the computing aspect in here (EnWiki) which basically replicated Stack Overflow, and it did take me quite some reading through its archives to make sure it was really supposed to work like that. For your personal curiosity, the whole thing is in fact 90% "related" to Wikimedia because of this and MediaWiki Gerrit notifications. It's been a while I'm struggling to deal with the large amount of emails from Wikimedia outlets. See phab:T300030 and this discussion to see what I mean. I get around 500-1000 emails per month just in regard to Wikimedia projects. You can also see this discussion with my attempts in automatic watchlist expirations and even my big support for such a feature in the 2022 Wishlist (ironically my vote is just behind yours), all attempts to cull the number of emails I get in an organic manner.

@Rlink2, maybe this one will? - Klein Muçi (talk) 02:33, 5 May 2022 (UTC)

@Klein Muçi: is the Reference Desk located so far from the VPT as to treat like a whole different place? Unequivocally. The reference desks are barely tolerated. VPT is for technical discussion focused on English Wikipedia. Izno (talk) 03:48, 5 May 2022 (UTC)

The reference desks are barely tolerated. - I wasn't aware of this reality at all. I will be more careful in regard to that aspect now. - Klein Muçi (talk) 07:54, 5 May 2022 (UTC)

I think in the future a notice saying "intrested people might be able to answer the question at the reference desk" so all discussion happens there, while still notifying the people that could answer the question. Again, 99% of people would probably be happy to answer anywhere, but just to keep 100% happy that is probably the best approach. And no one has identified any issues with him posting this here, all thats being said is that "its offtopic". Its kinda of like saying WP:IDONTLIKEIT. If someone thinks something is a problem, identify why it is a problem instead of just saying "its a problem". The time spent on saying "off topic" could be used to type out "its off topic, but i solved your question anyway here you go."

I think Klein's post was acceptable because there is no way I would have known if he hadn't posted here. Because of his post, we got the problem fixed - at the end of the day Wikipedia is not a real life or a beucracrcy, we don't need to follow rules 100% exactly. Rlink2 (talk) 23:54, 5 May 2022 (UTC)

I'm sure user Izno was only acting in good faith in protecting the integrity of the VPT domain. We have had the chance to stumble on each-other on some discussions around EnWiki on the past and I'm sure he also respects me the same as I do respect him and his contributions on this project.

I was trying to get "straight to the point" with my title thinking that it would be a trivial deed which wouldn't require too much work and words (hence also the 2 lines of text below it) but some titles can be provocative and maybe coupled with the fact that the provided link (which should have brought more context) wasn't working, the post may have appeared a bit too "alienated" with this place.

I already got my help thanks to you though so I suppose we can also end this discussion here if nothing else is to be added. Cheers! :) - Klein Muçi (talk) 02:05, 6 May 2022 (UTC)

@Klein Muçi still not working, says its "private" Rlink2 (talk) 12:42, 5 May 2022 (UTC)

@Rlink2, hmm... I'll continue this conversation on your talk page if that's okay with you. - Klein Muçi (talk) 12:44, 5 May 2022 (UTC)

As of gerrit:778684, there is now an implicit "named" group; currently, it applies to all users. This is causing issues in some scripts, but seems to be intended behavior on MW's end, so I haven't filed a Phab task about it. If someone does think it's unintended behavior, they're free to file.

What it does mean, though, is that a number of scripts need to be updated to exclude "named" as a meaningful group, just like they exclude "user" and often "autoconfirmed", perhaps most notably Navigation popups. I'll try to get to that and User:PleaseStand/userinfo.js presently, but I'm sure there's others. -- Tamzin^{[cetacean needed]} (she/they) 12:12, 5 May 2022 (UTC)

Okay, looks like this is being disabled for now. Still might be a good idea to cover these bases before it does go into effect as part of IP masking. -- Tamzin^{[cetacean needed]} (she/they) 12:45, 5 May 2022 (UTC)

Self-closing. Tim said the name "named" may change, so there's nothing that can be done now, script-update-wise. -- Tamzin^{[cetacean needed]} (she/they) 12:51, 5 May 2022 (UTC)

Unclosed for more comments. — xaosflux ^Talk 13:48, 5 May 2022 (UTC)

I was about to unclose this myself, as based on further conversation with Tim, it does look like "named" will be final as the internal name, with the default message for the name still TBD (maybe "registered user"). -- Tamzin^{[cetacean needed]} (she/they) 13:52, 5 May 2022 (UTC)

I initiated the local messages and updated the most popular gadget (navpopups) using this to put the name "Named user" on it, and not to populate navpopups with this. — xaosflux ^Talk 13:48, 5 May 2022 (UTC)

This is a stopgap, expect we can revert once the train comes around again and use "Registered user" or whatever it will be. — xaosflux ^Talk 15:32, 5 May 2022 (UTC)

This is confusing nomenclature. What exactly is a "named user" as opposed to just a "user"? I believe all "users" are registered accounts, so what's the difference from "named user"? Themaxtiger (talk) 15:56, 5 May 2022 (UTC)

@Themaxtiger In a few months/years editors that aren't logged in are going to be identified by pseudo-anonymous names rather than IP addresses (for some kind of privacy reason that hasn't really been explained), so instead of the software having groups "all" (for both IPs and logged in editors) and "users" (for registered accounts) they're going to have groups that will be something like "registered users/named users" and "unregistered users/anonymous users". This should be a mostly behind the scenes change, We'll probably have to fix a few edit filters and the like but most things where this is used (like determining whether you have the right to perform an action) should be updated by the devs. 192.76.8.77 (talk) 18:44, 5 May 2022 (UTC)

for some kind of privacy reason that hasn't really been explained → see this on meta. It gives two reasons: preventing unsavory governments from finding out who made certain edits, and something about privacy norms related to RGPD (it’s not clear from the text if Legal believes that posting the IP addresses could be a legal problem, or if they think the spirit of RGPD means there is some societal pressure to mask it).

IMO the most likely attack model is not government actors. Rather, if Alice shares a household or at least a computer with Bob (she could be a spouse, roommate, parent...), she can easily see what edits Bob made, retrieving Bob’s IP address with access to the computer takes little technical skill. (I know, IP rotate with DHCP etc. but Alice can at least find out a good portion of Bob’s edits.) Tigraan^{Click here for my talk page ("private" contact)} 13:26, 6 May 2022 (UTC)

If Bob is so worried about his abusive relationship with Alice, he can sign up for a free account. --Ahecht (TALK
PAGE) 14:55, 6 May 2022 (UTC)

User:Skyblueshaun/sandbox2 is being artificially transcluded via template into three articlespace categories; however, as WP:USERNOCAT strictly prohibits this, I have to disable or remove the categories from the page, but I can't figure out what templates the categories are coming from: none of the navigational boxes seem to be transcluding any categories that I can see, so I tried wrapping {{Infobox football club season}} in {{Suppress categories}} on the theory that the categories were coming from there, but that didn't work either. Can somebody determine where the categories are coming from so that the page can be removed from them somehow? Thanks. Bearcat (talk) 14:12, 6 May 2022 (UTC)

Fixed in Special:Diff/1086498714 * Pppery * _{it has begun...} 14:17, 6 May 2022 (UTC)

Probably from Module:Sports table. Gonnym (talk) 14:17, 6 May 2022 (UTC)

Actually it wasn't from that module, but from a transclsuion of the entire article 2022–23 EFL League One. The approach I used to find the categories was to run {{User:Skyblueshaun/sandbox2}} through Special:ExpandTemplates and the Ctrl-F for "Category:" * Pppery * _{it has begun...} 14:19, 6 May 2022 (UTC)

Thanks. Bearcat (talk) 14:52, 6 May 2022 (UTC)

Unfortunately, now I've got another case: User:Ɱ/sandbox and User:Ɱ/sandbox29 are both displaying in Category:Columbus Register properties. I tried using the tool mentioned above to solve this myself, but both pages are such utter profusions of templates upon templates that I just can't make heads or tails of the results in order to know where to throw a {{Suppress categories}} wrapper. Help? Bearcat (talk) 15:31, 6 May 2022 (UTC)

 Fixed in Special:Diff/1086509364 * Pppery * _{it has begun...} 15:33, 6 May 2022 (UTC)

And now User:Mdale/wikitrust.js, which is showing up in Category:Computer graphics — but since it's obviously a user's javascript settings file rather than a sandbox, I don't know how to fix it at all since it's not a conventional category declaration and the page is protected at a usergroup level ("interface administrator") that I don't think I have, but the page still can't be left in an articlespace category. Bearcat (talk) 15:39, 6 May 2022 (UTC)

User talk:Mdale/wikitrust.js#Interface-protected edit request on 6 May 2022. For what it's worth you indeed don't have interface administrator access. Thank you for doing this cleanup, by the way. * Pppery * _{it has begun...} 15:45, 6 May 2022 (UTC)

Was somewhat alarmed to see Google indexing User Sandbox pages e.g. This one [10]. I typically use this as an incubation page before getting articles to minimum standards for mainspace. But, this one was somewhat surprising almost alarming. Ktin (talk) 03:37, 5 May 2022 (UTC)

Hard to say, as it is now moved and the search results already updated. But in general, Google considers almost everything a hint. Like noindex, is used by them as 'index but do not return in results'. And I'm pretty sure that if you are specific enough and its search ranking is high enough for what you are looking for it might STILL bring it to the surface. —TheDJ (talk • contribs) 08:59, 5 May 2022 (UTC)

@TheDJ: Yup. Hard to say. Still seems to be returning the sandbox result. https://www.google.com/search?q=david+walden+wiki Ktin (talk) 16:21, 5 May 2022 (UTC)

@Ktin: You could consider putting {{User sandbox}} at the top of all your sandbox pages. This will apply the __NOINDEX__ magic word. But be aware that once Google has indexed any page, it's difficult to persuade them to unindex it - whilst they may act on a page being changed from normal to NOINDEX, it's certainly not instantaneous. More at WP:NOINDEX. --Redrose64 🌹 (talk) 22:37, 6 May 2022 (UTC)

On different days, trying to edit different articles, when using the Safari browser, I was always receiving the "This IP address has been blocked from editing Wikipedia" message. I do not receive the message when using Chrome.

I'm on a Macbook Air m1 (2020); macOS Monterey 12.3.1 (21E258); Safari Version 15.4 (17613.1.17.1.13) [most recent, up-to-date versions].

If I google "What is my IP" on Safari I get an IPv6 address (xxxx:xxxx:xxxx:xxx::xx:xxx); on Chrome I get an IPv4 address (xx.xxx.xx.xxx). That might be normal - I don't know much about how this works.

I might have fixed the problem, but I'm not sure. I realized that iCloud Private Relay might be the problem. So I changed the Safari privacy setting [Safari > Preferences > Privacy > Hide IP address] from “From Trackers and Websites” to “From Trackers Only”. I closed Safari and then opened it. I no longer received the "this IP address has been blocked" message. Interestingly, when I changed the privacy setting back to "From Trackers and Websites" I was still good, i.e., I'm not blocked. (I spoke too soon. The block returned after 20 minutes. I have now changed it back to "From Trackers Only" where it will stay so that I can edit Wikipedia using Safari.)

Is iCloud Private Relay the likely culprit? If so, then I know what to do if this happens again! :)

Many thanks - Mark D Worthen PsyD (talk) [he/him] 07:15, 4 May 2022 (UTC)

You will probably want to tune in to the discussion at meta:Talk:No open proxies/Unfair blocking and some set of the Phabricator tasks in this search. Izno (talk) 07:19, 4 May 2022 (UTC)

Ah, thank you Izno. Now that I know what to search for, I found this also, in the Village pump archives: Effect of Apple’s iCloud Private Relay. Much appreciated - Mark D Worthen PsyD (talk) [he/him] 07:23, 4 May 2022 (UTC)

Yes, we broadly block editing (not reading) from proxies and VPN's. You should turn that off here. — xaosflux ^Talk 15:05, 4 May 2022 (UTC)

You can't turn it off "here". You have to turn it off "everywhere, including in situations that most internet-savvy people consider to involve bigger-than-usual privacy risks". There is no way to use that service only for certain websites and not for others. Whatamidoing (WMF) (talk) 18:40, 4 May 2022 (UTC)

Maybe something like: Close your other tabs, switch off your Private Relay, edit Wikipedia, then turn Private Relay back on. Alternatively, just use another browser to edit here. And I'd just add that yes, it probably is the cause. Your experience varies because some Private Relay addresses are blocked, and some are not. -- zzuuzz ^(talk) 19:07, 4 May 2022 (UTC)

Hmm, doesn't this feature you enabled only work with Safari? Perhaps use a different browser for sites you don't want to run through Apple's proxy? — xaosflux ^Talk 13:03, 6 May 2022 (UTC)

That would be a solution for people like me, who normally keep multiple web browsers open anyway. I don't think it's practical for mobile editors or less tech-savvy people, though. You'd have to correctly guess what the cause is and guess that switching browsers would change your IP address (=a non-standard behavior). Whatamidoing (WMF) (talk) 20:47, 6 May 2022 (UTC)

Isn't the standard behavior not to use that VPN? You have to both be a paying customer and opt-in for it? Perhaps we can improve some of our block messages to hint people about this. Looks like we have some hints in {{CDNblock}}, but not in {{Colocationwebhost}} - both of which I'm seeing on some of these blocks. @Markworthen - are you getting more in the block message than just "This IP address has been blocked from editing Wikipedia"? — xaosflux ^Talk 21:14, 6 May 2022 (UTC)

@User:Xaosflux - Nothing else. Adding info about iCloud Private Relay and similar "innocent" causes would forestall frustration and perhaps reduce support requests. Given our ongoing struggle to attract and retain good editors, improving usability is a worthwhile goal. Mark D Worthen PsyD (talk) [he/him] 01:53, 7 May 2022 (UTC)

I've caught an issue with a bot that may need somebody here to fix. It's not a "permanently deprecate the bot entirely" level of crisis or anything, but it does need some attention.

User:Jura1/pages with Wikidata items without any statements is a report page, automatically generated by User:ListeriaBot to keep track of a maintenance issue. It seems like a perfectly legitimate and useful list in principle — but the problem is that if one of the pages it picks up corresponds to a category, then it just lists the category like an article and causes that workpage to be filed in the category instead of just linking to the category. However, pages like that aren't supposed to be filed in articlespace categories at all, meaning that I have to remove or disable the categories — but then ListeriaBot will undo any changes I make to the list the next time it runs that job, and thus throw the page right back into categories it isn't supposed to be in again.

But ListeriaBot's primary owner hasn't edited Wikipedia since December 2021, so I don't know if leaving a talk page message for them would reach them or not.

So does anybody know if User:Magnus Manske is actually active and just not contributing here that much, or can anybody else go into ListeriaBot themselves, to ensure that if ListeriaBot has to output a category to a worklist for whatever reason, it does so as a disabled text link (e.g. leading colon or the {{cl}} template) so that the worklist doesn't get categorized as an article? Thanks. Bearcat (talk) 13:09, 6 May 2022 (UTC)

@Bearcat that user has edited globally as recently as yesterday - so yse, you should start by asking on the botop's talk page (perhaps post at User talk:ListeriaBot and leave a message on the botop talk page pointing to it). — xaosflux ^Talk 13:12, 6 May 2022 (UTC)

Okay, thanks, I didn't know how to check whether Magnus was still active on other projects or not. If he is, I'll just approach him directly. Thanks. Bearcat (talk) 13:15, 6 May 2022 (UTC)

FWIW to check if a user has edited recently, see their global contributions linked from the contribs page (example). Graham87 08:53, 7 May 2022 (UTC)

I used to put in vector.js the scripts I wanted on the desktop, but not on the mobile (is that the best way?). Now, I've decided to migrate it all to my global (meta.WM) profile, as I've started to contribute more to non-enwiki. I've tried the same 'trick' there, but to no avail. Is there a global equivalent to skin specific js files? How does one separate mobile vs desktop scripts, globally? Cheers. — Guarapiranga ☎ 11:59, 6 May 2022 (UTC)

@Guarapiranga you can't do exactly what you want. You centralwiki:User:global.(js|css) is a uniquely special page. You can read more about it here: mw:Help:Extension:GlobalCssJs. You can put conditionals or more specific class items in it (e.f. mw:Help:Extension:GlobalCssJs#Per-skin_customization). In general you can select mobile or not mobile best by applying things to the minerva skin. — xaosflux ^Talk 12:24, 6 May 2022 (UTC)

That clears it, @Xaosflux. Cheers. Specifically, FWIMC:

Currently the extension does not provide global CSS/JS for specific skins (mw:Help:Extension:GlobalCssJs#Per-skin_customization)

My solution then is to bracket everything with if (mw.config.get('skin') === 'vector') { ... } for now, and progressively pull out the stuff I want to see on the mobile too. Probably also a better solution than what I was doing for lang specific common.js. Thanks. — Guarapiranga ☎ 12:39, 6 May 2022 (UTC)

@Guarapiranga: Unless you change skin setting, you have three places to put user scripts, all are linked from Preferences → Appearance:

• Special:MyPage/skin.js - for scripts specific to one skin on one wiki
• Special:MyPage/common.js - for scripts suitable for all skins on one wiki
• m:Special:MyPage/global.js - for scripts suitable for all skins on all wikis

In each case, there is a corresponding .css page available. There is no provision for skin-specific pages shared by all wikis. Regarding your JavaScript code snippet, the technique for m:Special:MyPage/global.css would be different - each skin-specific rule would, in general, need to have each of its selectors prefixed with .skin-minerva - note the trailing space. So a rule like

.foo, .bar { display: none; }

would become

.skin-minerva .foo, .skin-minerva .bar { display: none; }

HTH. --Redrose64 🌹 (talk) 13:56, 7 May 2022 (UTC)

Hey, Village Pump Tech folks,

I have a clock in the upper-righthand corner of my browser window and lately, the time has been off by, I'm guessing, 10-20 seconds. For example, if the clock states that it is 10:49:40 UTC and I make an edit, the edit summary on the page states that it occurred at 10:50. I've only noticed this happening recently. I checked in my Preferences and I think the clock is Gadget-UTCLiveClock.js so I've left a message at the MediaWiki talk page but I thought I'd mention it here in case anyone noticed that their clocks were a bit off. Also, the time moves at an inconsistent speed, some seconds pass by quicker than others for some reason. I really don't spend my time on Wikipedia watching the clock but some tasks are time-sensitive and the time an edit happens is important. Or could this just be my laptop? Thanks for any clue you can bring to my query. Liz ^{Read! Talk!} 02:07, 7 May 2022 (UTC)

I am curious which non bot tasks on Wikipedia are so time sensitive that 10-20 seconds will make a difference? ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 05:31, 7 May 2022 (UTC)

There are a few possible factors here:

• The gadget shows the time set on your local computer, which may be off. Wikimedia's servers most likely use Network Time Protocol to set accurate time.
• If your edit takes 10 to 20 seconds after hitting "submit" to travel the Internet and be processed and saved, that could also make the difference.
• As for the "some seconds pass quicker", again it's running on your laptop. Your browser may be delaying or skipping some of the updates of the display, particularly if other programs are using a lot of CPU. There's also the possibility that the stopped-clock illusion plays a part.

HTH. Anomie⚔ 11:22, 7 May 2022 (UTC)

Try going to https://time.gov/. NIST is the authoritative source for time in the US (and a major collaborator in the international pool of time reference sources). They're telling me that my system clock is off by -0.019s. No wonder I'm always showing up late for meetings :-) I'd be surprised if anybody's system clock was off by more than a fraction of a second. NTP is totally ubiquitous these days, and most operating systems come with it enabled out of the box.

You can call +1 303 499 7111 to hear the time signal on your phone. In the old days, this was an exceptionally accurate way to get the time. These days, I'm not so sure. Calls today often use VOIP, which introduces all sorts of network delays. The signal was certainly accurate when it left the transmitter in Ft. Collins, Colorado, but who knows what happens by the time it comes out of your cell phone speaker. If you have a shortwave receiver, you can listen to WWV (or similar stations around the world).

Sorry, I've digressed. Can you tell I'm a time freak? But seriously, go to time.gov to see if your system clock is set right. -- RoySmith (talk) 14:47, 7 May 2022 (UTC)

Were I on, say, the Portuguese Wikipedia, what MediaWiki Javascript function can I use to parse an arbitrary string (e.g ':uSuÁrIo : example') and get the same result as {{FULLPAGENAME:uSuÁrIo : example}} (Usuário(a):Example)?

I'm aware of mw.Title but it requires a second argument to specify namespace. I need a high-performant one so action=parse is not an option either. NguoiDungKhongDinhDanh 15:03, 7 May 2022 (UTC)

mw.Title.newFromText(':uSuÁrIo : example').toText() – SD0001 (talk) 15:54, 7 May 2022 (UTC)

Thanks! NguoiDungKhongDinhDanh 16:19, 7 May 2022 (UTC)

Is there any way to access infobox and other templates without "View this page" (V) button without need to go to "Edit" then copy name of template and search Template: + name of template? Eurohunter (talk) 09:53, 7 May 2022 (UTC)

I get a list of all templates used in an article below the edit box. —Kusma (talk) 10:21, 7 May 2022 (UTC)

That only happens if you use the edit tab for the whole page. If you edit a section, the template list only appears if you use the Show preview button while editing. --Redrose64 🌹 (talk) 18:41, 7 May 2022 (UTC)

@Eurohunter: "Page information" under Tools shows up to 50 transcluded pages but we often have far more. The edit tab for the whole page has a complete list under "Pages transcluded onto the current version of this page" at the bottom of the edit window. You may have to click a small triangle to see the list. PrimeHunter (talk) 21:31, 7 May 2022 (UTC)

{{Infobox album}} is forcing an italic title at Poison box sets which I can't turn off by applying | italic_title = no or with {{DISPLAYTITLE}}. Can someone help me out please? Shhhnotsoloud (talk) 08:49, 8 May 2022 (UTC)

@Shhhnotsoloud: The cause is {{Italic title}}; I have removed it. NguoiDungKhongDinhDanh 09:11, 8 May 2022 (UTC)

@NguoiDungKhongDinhDanh: I couldn't see the wood for the trees. Thank you! Shhhnotsoloud (talk) 09:36, 8 May 2022 (UTC)

Hello, I would like to conduct some research on Wikipedia, but appeared that there is no documentation on how to import it into MySQL, at least for Windows case. I'm stuck with converting XML-file into SQL-file. Could somebody help me out with this? --Igor Yalovecky (talk) 16:30, 7 May 2022 (UTC)

Depending what information you want, dumps are available both in SQL and in XML. Beware that some files are very large. More information: WP:DUMP, which has several useful links. Certes (talk) 17:30, 7 May 2022 (UTC)

Even better, meta:Data dumps. And "very large" is an understatement. The most recent full dump for enwiki is 1.8 TB for the compressed files. Importing this into your typical desktop PC just isn't going to be practical. For most people, a more useful strategy would be to get a Cloud VPS or Toolforge account and access the data that way, either by using the on-line dump files, or by executing queries against the database replicas. Be aware, however, that there is a bit of a learning curve to this. -- RoySmith (talk) 02:57, 8 May 2022 (UTC)

@Igor Yalovecky Does MySQL "Load XML" not do what you want?

I know that I risk getting flamed by free software advocates (I understand, I really do)... But FYI, Microsoft SQL server has had a free version (for both development and production) for a few releases now -- and it has a true XML datatype that works pretty well. Unfortunately, the free version of MS SQL is limited to a 10GB database. For about $700, you can get the Standard edition, which us limited to ... um .... a 524 petabyte database size.... If you have that much storage! This probably didn't help much, sorry. 73.127.147.187 (talk) 10:10, 8 May 2022 (UTC)

If I look at for example Günter Bechly, I see a kind of deletion-log, info about old deleted versions.

However, can I, a non-admin, see this info for an article currently in main-space? For example, I recreated Christoph Steidl Porenta, which had been deleted (for good reason, WP:G11) a couple of times, but afaict, these deletions can't be seen at Revision history, Page statistics or Page information. I think it was briefly visible when I started the draft or when I moved the draft to mainspace, though.

I'm not after a WP:REFUND, I'm just curious about seeing the "facts" like at the Bechly link. Can I, somewhere, or are they admin-only? Gråbergs Gråa Sång (talk) 09:55, 8 May 2022 (UTC)

@Gråbergs Gråa Sång: Yes; see page logs. Note that the logs were recorded at Draft:Christoph Steidl Porenta, not Christoph Steidl Porenta. NguoiDungKhongDinhDanh 10:08, 8 May 2022 (UTC)

Ah, tricky. Thanks! Gråbergs Gråa Sång (talk) 10:43, 8 May 2022 (UTC)

I've added the following question at Module talk:Graph, but since the edit notice there suggests posting it here (as that page is not watched by as many users), I'm copying it here too:

The default d3 curvature parameter for the bundle interpolation method, .85, can often be too "erratic" in some applications (as pointed out here, and seen there). The basis method is even more "erratic," as it's standard spline bolted at the extremities, corresponding to a bundle beta of 1, but d3 also accepts other betas. Is that an option with this module (and accompanying template)? I couldn't figure it out from perusing the code. Cheers. — Guarapiranga ☎ 11:15, 4 May 2022 (UTC)

— Preceding unsigned comment added by Guarapiranga (talk • contribs) 13:35, 6 May 2022 (UTC)

Code in software that WMF uses and is maintained by other parties is not changed by the WMF or any volunteer of WMF. This would be fixed by the Vega or D3 team. There is some work that exists to upgrade Vega to Vega 3, see phab:T223026, but no WMF team is responsible for Vega/Graph right now. Only an developer can answer the D3 question, so please lets keep this discussion to the issue at hand and not try to figure out some fixes in Vega/D3 codebase. For those that are curious, Module:Graph uses Vega, which in turn uses D3.--Snævar (talk) 16:41, 6 May 2022 (UTC)

What's to fix, Snævar? I just asked whether Module:Graph had the beta parameter already in d3 (not sure about Vega--couldn't find anything about it in its docs). If not, I aimed at inspiring someone to add it in (I looked through the code, but it wasn't evident to me where it would fit in). — Guarapiranga ☎ 04:42, 7 May 2022 (UTC)

First, test if this also is the case in recent Vega (putting the Module:Graph invoke into Special:ExpandTemplates, removing the graph tags and copying that into Vega editor will suffice). Secondly, if it is also an issue there, report it in vega/D3 bugtrackers, it is upto them to fix it.--Snævar (talk) 07:26, 8 May 2022 (UTC)

I don't have an "issue," Snævar; there's nothing to "fix" (that I can see). It's really an enhancement that I'm after. Module:Graph is working splendidly, but it could work even better if editors were able to specify the beta parameter in the bundle interpolation, so that trends could be made less "erratic" than this, as MathewMunro pointed out here.

I tried your exercise, but I'm afraid I failed. Copying over the expanded template (in between <graph> tags) into the Vega editor gave me a bunch of warnings and errors. I'm clearly not doing this right. I was able, though, to load up their own example, add the bundle interpolation there (which was oddly missing among all the others present), and make the curve change. Again, I couldn't figure out where to stick in a beta there. The d3 doc (is Vega a d3 wrapper?) only says to call it like this, e.g.:

const line = d3.line().curve(d3.curveBundle.beta(0.5));

Cheers. — Guarapiranga ☎ 11:42, 8 May 2022 (UTC)

Hello, all. I ran across an odd issue on this article. Attempting to edit the section "Births" or "Deaths" section redirects me to editing Module:For nowiki (technically, I'm trying to edit it but it's protected). Can anyone else reproduce this issue? If so, I'm curious if this feels like a MW bug or a module issue. I'm not very familiar with the module system in general so I hesitate to report it to Phab if it's a local issue. ~ Matthewrb ^{Talk to me · Changes I've made} 07:16, 8 May 2022 (UTC)

@Matthewrb: Those two sections are transcluded from other pages, per the hatnotes at their tops. The {{Births and deaths by year for decade|16}} template performs the transclusion and generates those two headings. --Redrose64 🌹 (talk) 07:48, 8 May 2022 (UTC)

The headings should definitely be fixed. {{Events by year for decade}} manages to create edit links for the specific sections, and avoid the edit link for its heading, so probably something similar needs to be done for {{Births and deaths by year for decade}} Galobtter (pingó mió) 07:51, 8 May 2022 (UTC)

Thank you both. It looks like {{Events by year for decade}} is a module, while {{Births and deaths by year for decade}} uses template markup. Wonder if that's related? Like I said, I don't understand modules very well... ~ Matthewrb ^{Talk to me · Changes I've made} 16:19, 8 May 2022 (UTC)

I definitely am doing something wrong here. I want to request a move from a draft article, to its former article status, but my move request in the Wikipedia:Requested moves/Technical requests definitely broke something. Where is the proper avenue/way to request this move? ~ 🦝 Shushugah (he/him • talk) 18:14, 8 May 2022 (UTC)

• I fixed it. The issue was with the space character. -Kj cheetham (talk) 18:15, 8 May 2022 (UTC)

An interesting observation was made about an external MediaWiki-based wiki in relation to a wrong URL, and it can happen here, too. If a title containing a question mark is pasted into a page URL, it and anything at follows will be dropped, but it will still appear in the website if the visited page is not a redirect.

• https://en.wikipedia.org/wiki/index.php?title=Main_Page (goes to the redirect Index.php → Web server directory index)
• https://en.wikipedia.org/wiki/Arsenic?title=Main_Page (goes to the article Arsenic)
• https://en.wikipedia.org/wiki/?_(film) (goes to Main Page)
• https://en.wikipedia.org/wiki/%3F_(film) (goes to ? (film))

–LaundryPizza03 (dc̄) 04:02, 9 May 2022 (UTC)

That is the intended behaviour. Our wgArticlePath is /wiki/$1 and that overrides the value of title parameter, if any. In your third example, the ? mark is treated as the start of URL query string, and since _(film) is not followed by any value (and is not supported by MediaWiki itself), the rest gets ignored. Meanwhile, that of the fourth is encoded and hence not a part of query string (i.e. a ? mark literally/as-is). NguoiDungKhongDinhDanh 04:36, 9 May 2022 (UTC)

I am trying to create a query that will get a list of IP talkpages that; have not been edited in the last 5 years, the IP is not currently blocked and there have been no edits from that IP in the last 5 years. I have individual queries to get list of IP talkpages, check if an IP is blocked, check if an IP has edited after a timestamp and check whether a page has received edits after a timestamp. I tried to combine all 4 of these to work together at quarry:query/64344 but not having any luck. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 11:20, 7 May 2022 (UTC)

@ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ: WT:Quarry is a good place to ask, but I've had a go in quarry:query/64387. I've joined to the current revision rather than having a subquery check for all recent ones, and used the revision_userindex alternative view for efficiency when checking for edits to other pages. It doesn't detect range blocks; that would naively need page_title between ipb_range_start and ipb_range_end, except that doesn't work: 1.2.100.0 is textually between 1.2.0.0 and 1.2.3.255 but unaffected by a block on that range. You'd need to do some intricate string manipulation to pad with zeroes. This won't be a quick query – we have a lot of IP editors – and may need splitting with and page_title like "1%" etc. (Beware that most IPv6s begin with 20.) Certes (talk) 13:47, 7 May 2022 (UTC)

@Certes: thanks for the effort. For IP ranges, I tested quarry:query/64379; it seems like it is possible to check if an IP is between a range by converting it to hexadecimal using HEX(INET6_ATON('<ip_address>')). ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 16:50, 7 May 2022 (UTC)

I have forked and created quarry:query/64398 to check for range blocks as well, but it takes a long time to execute even when the first octet is specified. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 12:23, 9 May 2022 (UTC)

15:20, 9 May 2022 (UTC)

Hey, is it possible for a template to add pages to a category if it creates a table that only has one row? The template generates rows based on rotten_tomatoesN and metacritcN, so maybe something like if both of those with 2 in place of N is blank, then add to category or error, but not sure if possible to implement. Posted on talk page of the template three weeks ago (Template_talk:Television_critical_response#One_row_category_not_working) and no response so hope you can help please? Thanks, Indagate (talk) 18:02, 9 May 2022 (UTC)

I think the problem is at Module:Television_critical_response#L-233 where it checks whether #SeasonEntries is 1. This would work well if table SeasonEntries were a sequence with numeric keys 1, 2... However, it has string keys "1", "2"..., so the # operator spots that there is no numeric key 1 and returns 0. Certes (talk) 18:37, 9 May 2022 (UTC)

@Certes Ah ok, thanks for responding, would it work if replace L-233 with "if not rotten_tomatoes2 or metacritic2 or cinemascore2 then"? Instead of saying if seasonentries = 1, we're saying if content is not added for a row, then add to category. Or is it possible to change the string keys to numeric keys? Indagate (talk) 19:50, 9 May 2022 (UTC)

That should work, or you could try copying from Module:Television critical response/sandbox which I just created. Someone who knows the application area better than me should test it first! Certes (talk) 19:59, 9 May 2022 (UTC)

I think we need the sandbox version because we can legitimately have series "numbers" such as "3S" for special episodes (e.g. Sherlock). I've assumed that we want to detect single rows, not rows with a maximum series number of 1 (which might be 1 + 1S or similar). Certes (talk) 20:18, 9 May 2022 (UTC)

Thanks, created Template:Television critical response/sandbox and tested in preview mode for a few articles and doesn't break anything Indagate (talk) 20:30, 9 May 2022 (UTC)

Thanks. I've promoted the module sandbox. Certes (talk) 21:02, 9 May 2022 (UTC)

Thanks, looks to be working now, just picking up single uses where it's nested so will pick up if it gets used without in future Indagate (talk) 21:10, 9 May 2022 (UTC)

In this edit, after clicking "save", they appeared two cows instead of <ref name=":03" />
I suppose it is the effect of an automatic substitution of text in emoticons. Could you check if it is just my problem or is related to some Mediawiki software bug? Thanks. --Ensahequ (talk) 19:19, 9 May 2022 (UTC)

I just did a null edit and nothing changed. (The symbols seem to be ☃ snowmen for me.) I see that your edit also replaces double spaces by single spaces: perhaps you have something locally which enforces that preference and also generates unwanted emojis. Certes (talk) 19:46, 9 May 2022 (UTC)

IIRC this is a VisualEditor bug: WP:☃. NguoiDungKhongDinhDanh 22:21, 9 May 2022 (UTC)

See also this VPT thread from 2019 and T262515. Preferences has an option to "Temporarily disable the visual editor while it is in beta", which I recommend for most editing until a pile of long-standing bugs are fixed. – Jonesey95 (talk) 03:37, 10 May 2022 (UTC)

And more mentions in the VE/Feedback archives, dating back to 2013, including a link to fr.WP's edit filter that tries to prevent these snowmen from being saved, and links to multiple phab tickets. – Jonesey95 (talk) 03:45, 10 May 2022 (UTC)

Web references on Wikipedia come optionally with a url-access parameter that warns the user of potential registeration/paywall to see the content. These days a lot of content online is behind such measures. Most references sadly do not contain this useful data. Could we somehow automate it? Maybe with Wikidata? Or just add it to refs with bot runs? How would you do it? --Palosirkka (talk) 12:26, 10 May 2022 (UTC)

I don't think this is actionable. Araik there are no hooks for code that would do what you suggest, and any such routine would be highly speculative and prone to false positives (and negatives). Also keep in mind that access status may not always be the same. 74.64.150.19 (talk) 12:47, 10 May 2022 (UTC)

Moved from Wikipedia:Teahouse § Only Talk page showing up on Google search

What accounts for the Talk page of this article, but not the article page, appearing in the Google index?

In this Tea house discussion, OP Llmeyers (talk · contribs) asks about the recently created Carey R. Dunne article, and why a Google search turns up only the Talk page, providing the following link: https://www.google.com/search?q=carey+r+dunne+wiki&oq=carey+r+&aqs=chrome.0.69i59l3j69i57j0i512j69i60l3.1165j0j9&sourceid=chrome&ie=UTF-8

Checking their link, I can confirm that "Talk:Carey R. Dunne - Wikipedia" appears as Google's #2 result (and that the article page does not appear anywhere on the result page). Note that their search query includes the keyword "wiki" along with the article title, and dropping that keyword changes the results so that the Talk page result appears at #24 in the results, but still doesn't surface the article page. I thought our Talk pages weren't indexed at all, but that's clearly not true. Mathglot (talk) 22:32, 5 May 2022 (UTC)

@Mathglot Seems like Google is doing their best. That article is new, and is still unreviewed, if you patrol it it should become indexed and Google will likely give it precedence. — xaosflux ^Talk 23:07, 5 May 2022 (UTC)

Do we know (or can we guess) what property of the talk page makes it more attractive to Google than the article? I realise that search engines are requested not to index new articles, but I assume that applies to new (and old) talk pages too. Certes (talk) 23:58, 5 May 2022 (UTC)

Yes, that's what confused me, as well. Seems to me, any noindex metatag on a mainspace article should be automatically propagated to Talk. Maybe I should add a phab ticket about this? Mathglot (talk) 00:27, 6 May 2022 (UTC) Tracked in T307753. Mathglot (talk) 00:44, 6 May 2022 (UTC)

The Google hit is https://en.wikipedia.org/wiki/Draft_talk:Carey_R._Dunne which redirects to https://en.wikipedia.org/wiki/Talk:Carey_R._Dunne. But MediaWiki doesn't make normal url redirection like HTTP 301. Instead it has JavaScript which rewrites the url in browsers with JavaScript enabled, but doesn't reload the page afterwards. The content is loaded from the original url. You see the contents of https://en.wikipedia.org/wiki/Talk:Carey_R._Dunne but you are actually on https://en.wikipedia.org/wiki/Draft_talk:Carey_R._Dunne. I guess that's how Google treats it. PrimeHunter (talk) 01:29, 6 May 2022 (UTC)

I didn't completely follow your explanation about Google vs. Mediawiki, but let's start at the top with what we do know and control, namely, with which pages we tag as noindex and which ones we don't. Here's what we have currently (a 'yes' below means that the page code contains <meta name="robots" content="noindex,nofollow"/> on the page). Note the asymmetric distribution of "noindex" metatags among the four related articles:

• Carey R. Dunne – yes
• Talk:Carey R. Dunne – no
• Draft:Carey R. Dunne – yes (redirects to Carey R. Dunne)
• Draft talk:Carey R. Dunne – yes (redirects to Talk:Carey R. Dunne)

Given this situation, when you say "The Google hit is https://en.wikipedia.org/wiki/Draft_talk:Carey_R._Dunn", how can that possibly be? Even a targeted site search query doesn't find the Draft page. So that theory (or at least, the first part of it, which I think I understood) can't be right. Mathglot (talk) 03:46, 6 May 2022 (UTC)

Why don't we add noindex,nofollow to Talk: pages, at least when the corresponding mainspace page has noindex,nofollow? Certes (talk) 11:56, 6 May 2022 (UTC)

Your links made with {{noredirect}} link to en.wikipedia.org/w/index.php. Our robots.txt at https://en.wikipedia.org/robots.txt says Disallow: /w/ so indexing is disallowed. robots.txt tells spiders like Googlebot that they shouldn't even visit the page to see whether it has noindex. At the English Wikipedia we can only control indexing for some links to en.wikipedia.org/wiki/. If you view https://en.wikipedia.org/wiki/Draft_talk:Carey_R._Dunne with JavaScript disabled in your browser then you see the contents of the redirect target https://en.wikipedia.org/wiki/Talk:Carey_R._Dunne but you still have the former url in the adress bar and there is no noindex. Normal Internet redirects use List of HTTP status codes#3xx redirection, typically HTTP 301, and don't require JavaScript. A MediaWiki redirect is not a "real" redirect. https://en.wikipedia.org/wiki/Draft_talk:Carey_R._Dunne gives HTTP 200. It can be checked with an external tool like https://www.redirect-checker.org/, or with a feature in many browsers. PrimeHunter (talk) 16:08, 6 May 2022 (UTC)

I can barely follow all this! Super technical. :( Llmeyers (talk) 18:51, 7 May 2022 (UTC)

If you ask me to mail you a copy of Alice in Wonderland, I can mail you a note to you saying, "Please ask me for Alice's Adventures in Wonderland". You would then ask me for Alice's Adventures in Wonderland and I'd mail you a copy of the book. This is the standard way to do redirection, and so any metadata associated with the request containing the correct name will be returned with the second envelope. Alternatively, I can just return Alice's Adventures in Wonderland directly to you, saving you from having to make another request. However since I've just pretended that the book has a different name, you're getting the reply envelope from the first request, Alice in Wonderland, but with the book Alice's Adventures in Wonderland inside. Google is still getting a response using a request to the Draft talk page, but with the contents of the article talk page, so it gets the article talk page inside the reply envelope for the Draft talk page. isaacl (talk) 20:08, 7 May 2022 (UTC)

Yes, the problem is that the article has noindex but the Talk: page (which you get whether you ask for Talk: or Draft talk:, due to the MediaWiki redirect) has not. Should we be making Talk: pages more visible than their articles in that way? Certes (talk) 20:29, 7 May 2022 (UTC)

(edit conflict) @Llmeyers:, I'm sorry, yes, it is quite technical in parts, and some of it is difficult for me to follow, as well. I think part of the confusion here, is that there are essentially two conversations going on here at once, and they aren't separated into separate subsections, but are interleaved together. One conversation, as I see it, is functional: "Here is what happens now; do we want it to happen that way?" Certes succinctly articulated the "what" question just above.

The other conversation is a "why" question: "Why is it happening this way now?" and the answer may have to do with technical issues concerning HTTP responses (how the internet handles moved pages), javascript, and Mediawiki software (Wikipedia runs on software created by the Wikimedia Foundation, which also supports Wiktionary, Wikiquote, and other sister projects).

Sidebar: As an aside on one technical point: the one "new bit" of info for me, was this: "A MediaWiki redirect is not a 'real' redirect." An HTTP 200 response is what your browser gets back when a page is FOUND on the internet; an HTTP 301 response is what you get when there is no content there, instead there is just a pointer to a page somewhere else. Let's say your browser asks for wikipedia's Georgeoia (i.e, the url in the browser address bar has the wikipedia domain address and that weird spelling at the end); instead of saying "NOT FOUND" and leave you staring at an error page, it could just send your browser an HTTP 301 and link you to the "Georgia" page instead. But apparently mediawiki "cheats", so to speak, and sends back a "HTTP 200" (FOUND!) even if the page is a redirect, and works out what page to show you on its own. The "cheating" part is related to the Phabricator ticket that Izno linked below.

But you don't need to know any of the technical stuff, which is basically about the "why-question", in order to participate here if you wish; just try to parse out which parts of it are about the "what-question", and just respond to that part. Hope this helps! Mathglot (talk) 21:14, 7 May 2022 (UTC)

Thank you Mathglot! This is helpful. Should I change anything on the article right now? Llmeyers (talk) 19:00, 8 May 2022 (UTC)

Hi Llmeyers, assuming you are talking about improving the Carey R. Dunne article, since this Village pump discussion is restricted to the topic of why a Wikipedia Talk page appears in search engine results, your question about the article is actually off-topic here, which may seem paradoxical, because it was your experience with the article that got this all started! So, I'd ask you to go to Talk:Carey R. Dunne, and ask your question there if you wish. Feel free to {{ping}} me or any user(s) you would like to invite to the discussion there.

If, on the other hand, you are asking about whether you need to change anything in the article in order to solve, or mitigate the Google Talk page indexing issue, then the answer is "no". Mathglot (talk) 19:53, 8 May 2022 (UTC)

I see. Thank you Mathglot! This clears it up. Llmeyers (talk) 13:20, 10 May 2022 (UTC)

@Llmeyers, was this "I can barely follow all this!..." meant to be a pun? I found it amusing. 73.127.147.187 (talk) 04:41, 9 May 2022 (UTC)

Sadly not a pun :D Llmeyers (talk) 13:21, 10 May 2022 (UTC)

For which the relevant task is phab:T53736. Izno (talk) 21:05, 7 May 2022 (UTC)

That's helpful, thanks. Mathglot (talk) 03:36, 8 May 2022 (UTC)

@Mathglot Right, I also thought that all talk pages had "noindex". (That's clear from my comment at the help desk (or TH).) After reading this, and the Phab ticket, I must have been wrong.

Are user pages noindexed, to discourage people from putting their autobiographies there? Somewhere, I know that we tell people not to bother putting autobios in user pages, or maybe it's in sandboxes. Thanks. 73.127.147.187 (talk) 09:41, 8 May 2022 (UTC)

I wonder how many indexed autobiographies lurk on unloved talk pages. Certes (talk) 11:16, 8 May 2022 (UTC)

@Certes: Here is a list of some google-indexed 'Talk' pages for biographies at Wikipedia. But this isn't a list of Talk pages whose mainspace page is not indexed, and I don't know a simple search to get that list. There appear to be about 233 of them indexed returned (at my default 50 results per page, SRP #5 shows 33 results). It's not at all clear to me what the common feature is of the Talk pages in that list. Mathglot (talk) 20:19, 8 May 2022 (UTC) (edit conflict) Dropping the WikiProject from the query string returns almost the identical number of results, but the result set is almost completely disjoint from the result set of the biography search, so clearly they are not surfacing all the results they have. Mathglot (talk) 20:26, 8 May 2022 (UTC)

Talk pages are not noindexed by default, but the presence of certain banners can mark the page as noindex without you being immediately aware. This occurs with, for example, {{BLP}}; and thus it also occurs with {{WikiProject Biography|living=yes}}. User pages are also not noindexed by default; as regards user sandboxes, see my post of 22:37, 6 May 2022 (UTC) above.

To check whether any given page is presently noindexed, click its "Page information" link in the left sidebar. In there, the first box (Basic information) should have an entry named "Indexing by robots", and this will show either "Allowed" or "Disallowed". --Redrose64 🌹 (talk) 20:23, 8 May 2022 (UTC)

@Redrose64 do you mean that the actual BLP articles are noindexed, or the talk pages for BLP articles are noindexed? I would expect BLP articles to be indexed by search engines. 73.127.147.187 (talk) 04:44, 9 May 2022 (UTC)

Edited to add: I do see experienced editors tell novice editors that it won't help to put autobios in user or user-talk pages because search engines won't see them. That's why I thought all user and user-talk (and, I was guessing, article talk) pages had noindex by default. I'll check a few, but that won't tell me the default... I don't want to beat this to death though... Thanks. 73.127.147.187 (talk) 04:51, 9 May 2022 (UTC)

The __NOINDEX__ magic word only affects the page on which it is used. Therefore, when used on a talk page (whether directly, or indirectly (by means of a template) it is the talk page that is noindexed. The subject page is not affected. --Redrose64 🌹 (talk) 19:47, 9 May 2022 (UTC)

Here is a count of noindexed pages for each namespace. Subtracting from total page counts gives a rough count of indexed pages. Certes (talk) 10:37, 9 May 2022 (UTC)

I try to ensure my scripts work on the mobile domains. Not always easy. I don't actually use the mobile domains outside of these tests. As I typically load my scripts locally I never bothered to look at preferences, common.js or whatever for this. But now I wanted to test loading a script on-wiki, and.. What.. the.. fuck..? There is no link to Special:Preferences anywhere on the mobile domain! The only "settings" link there is points to Special:MobileOptions which is utterly utterly worthless. Entering Special:Preferences by hand works (that's a step up from Special:Diff which just redirects to the worthless Special:MobileDiff), but it's clearly not intended to be used as there's a horizontal scrollbar in the tabs. Not to be defeated that easily, I made a URL using withJS. Surprise: it doesn't work! But on the desktop domain with Minerva it's fine. I must be missing something. Mobile can't be this worthless.. can it? No gadgets on mobile, no Special:Diff, no Special:Preferences, I'm surely mistaken. We wouldn't direct mobile devices to such unfinished garbage by default, that wouldn't make any sense. Tell me I'm mistaken. Tell me I completely overlooked the actual mobile preferences. — Alexis Jazz (talk or ping me) 18:06, 7 May 2022 (UTC)

You are not mistaken. You have not completely overlooked the actual mobile preferences. The mobile interface sucks. My understanding is that the developers think the mobile interface should be optimized for readers, not editors. Optimizing for readers leads them to eliminate things they don't think readers will need in favor of a sleeker looking, more aesthetically pleasing interface that allows people to just read the articles. ~ ONUnicorn^{(Talk|Contribs)}problem solving 18:10, 7 May 2022 (UTC)

@Alexis Jazz: If you try looking at the console, you will see a line that says Learn more about how we build our mobile site @ Extension:MobileFrontend. I had a look at it and have learnt that the extension provides replacements for special pages that are not mobile friendly: Special:History, Special:Contributions, Special:Watchlist, Special:Preferences, Special:MobileDiff; also, it is maintained by the Reading Web Team. NguoiDungKhongDinhDanh 18:18, 7 May 2022 (UTC)

This is why I have always been using User:Þjarkur/NeverUseMobileVersion.js. NguoiDungKhongDinhDanh 18:22, 7 May 2022 (UTC)

I warmly recommend that script, it has significantly improved my experience of using Wikipedia on my phone. —Kusma (talk) 20:06, 7 May 2022 (UTC)

Donald Trung, something for you? — Alexis Jazz (talk or ping me) 10:31, 8 May 2022 (UTC)

• Mobile support - a mostly OK reading experience these days - if you want to do any serious editing well you've seen the results. — xaosflux ^Talk 18:33, 7 May 2022 (UTC)
  • Xaosflux, ONUnicorn, being optimized for reading isn't entirely unfair, but many options for readers are also missing. Change my password? I don't see it. Maybe I was never supposed to log in anyway. Change the interface language? Nein. Change my notification settings? Forget it. Enable gadgets that aid reading like Wikipedia:Dark mode (gadget)? Mobile remains in the dark. Change search settings? Keep looking. Change banner types to display? Okay, no need for that because banners don't seem to work. (hmm.. do fundraising banners not show on mobile?) Okay, here's another question: is it possible to switch skin based on device/session so I could use different skins on my phone and my laptop on the same domain and without changing my preferences? — Alexis Jazz (talk or ping me) 19:15, 7 May 2022 (UTC)

    No idea. But Monobook in "responsive mode" is almost like having two different skins, one for small screens (my phone) and one for large screens (my laptop). Small-screen monobook can't deal with high indent levels, so I sometimes switch to large-screen by rotating my phone. Can the logic of the "responsive mode" be used to choose between two completely different skins? —Kusma (talk) 20:05, 7 May 2022 (UTC)

    No. Izno (talk) 21:03, 7 May 2022 (UTC)

    Timeless is another option, works well both on mobile on desktop for me. Galobtter (pingó mió) 21:54, 7 May 2022 (UTC)

    Oh, so Minerva would be completely unnecessary if Vector '10 never happened. Why does it always seem to work out this way? casualdejekyll 19:29, 8 May 2022 (UTC)

    The web browsing technologies to support Timeless's different appearance at different resolution were not supported by all the major browsers until IE9 released in 2011 and certainly not widely supported for some time even after in the various installations of everything out in the world in the early 2010s. In fact, just weeks ago, that browser version was finally removed from the basic support column for MediaWiki.

    You'll note also that the rise of mobile computing is actually fairly recent; even in July 2015 it accounted for only about a third of all requests, with of course the related prioritization. Now it accounts for almost two thirds.

    Vector 2022 is moving the direction of multiple resolution support, so at some point that may be the primary skin displayed on both desktop and mobile websites. Izno (talk) 19:45, 8 May 2022 (UTC)

• I just found out that while there's no Special:Preferences link on the mobile domain, if I enable Dark Mode it also becomes available on the mobile domain. So it seems gadgets can work after all, but not temporarily using withJS and to actually enable them you'll need to manually navigate to Special:Preferences or access it on the desktop domain. I created T307851 as a result of this topic. — Alexis Jazz (talk or ping me) 09:27, 8 May 2022 (UTC)

  withJS is defined in MediaWiki:Common.js, which is not loaded in mobile, because it’s likely to contain things not compatible with mobile. Either it needs to be copied to MediaWiki:Mobile.js (which is loaded only on mobile), or uses need to be migrated to the shiny new withgadget, which is defined in the Gadgets extension, and works on mobile as well. —Tacsipacsi (talk) 14:32, 9 May 2022 (UTC)

Most of our site didn't work on mobile at all ten years ago, so to be honest it's remarkable we have such a good reading experience there. Much of the work in Minerva, templates and then Timeless brought us to the place we are now. I have a lot of admiration for all the staff and volunteers that have got us to where we are today.

It's still a work in progress but if you go to the mobile settings page while logged in and chose advanced mode you will get almost feature parity with desktop (just a few new workflows to learn). The eventual goal I would imagine is to get advanced mode as the default and a lot of the work in mw:Desktop improvements has pushed us closer to that. WMF is investing more time in the advanced mode (and logged in experience) to push in the other direction and I am sure they would appreciate your feedback at mw:Moderator Tools/Content moderation on mobile web about where to focus. In fact they were only just recently looking into Special:Preferences (which is not shown btw as most of the preferences are desktop only and the page itself with all its tabs barely fits on a mobile screem.

In terms of gadgets if one is not working that is likely because it was built ten years ago using now deprecated code (importScript for example is deprecated but used all over the place) or the gadget developer intentionally disabled it on mobile.

I kindly suggest you take a little time to learn more about the mobile interface before making misinformed claims that it doesn't support anything. Am happy to help enlighten you in anyway I can if you have any concrete examples. Jdlrobson (talk) 17:04, 8 May 2022 (UTC)

I have to wonder why you're writing here as if you're not a major part of the "they" you refer to. A lot of the mobile stuff is your own work; by number of commits you're by far the most prolific non-bot contributor to the MinervaNeue and Vector skins and the MobileFrontend extension. Do you really need to "imagine" the WMF's eventual goals in the area? Given your experience and tenure at WMF on the teams working in this area I'd think you'd be directly involved in setting them. Anomie⚔ 18:44, 8 May 2022 (UTC)

Jdlrobson, I stand by what I said. I kindly suggest you take a little time to learn more about the mobile interface before making misinformed claims Hey, I took my time, ten times more than you can expect from your average user! You can't enable a gadget from within the mobile interface. When using the mobile interface there's no reason to think gadgets could work - or even know about their existence - at all. I found out by accident that if enabled somehow, they do load, but enabling them to begin with is another matter. chose advanced mode you will get almost feature parity with desktop Wow, did you seriously just say that? Almost feature parity? That's a low bar, and in what universe does it come even close to that? Good job on closing phab:T307851 because it's too hard for you and phab:T306737 because.. well fuck if I know. I've reopened them for you. — Alexis Jazz (talk or ping me) 09:06, 10 May 2022 (UTC)

Despite having edited Wikipedia for years I was also surprised to learn just how many fundamental workflows were missing or hidden on mobile web, and like you Preferences stood out as a glaring omission that should be accessible to everyone. My team is spending at least the next few months working on improvements to the mobile web interface with a focus on tools for experienced editors. We're currently working on some low-hanging fruit relating to mobile web's overflow menu (namely, adding a user Block button and considering making the menu available without turning on Advanced Mobile Contributions) while we explore potential UX changes for making Preferences available on mobile. I've just written a project page for the preferences work at Moderator Tools/Content moderation on mobile web/Preferences where I'd love to get input from folks who are interested in this. We want to spend a little time seeing what we can do to make Preferences less confusing and more mobile-friendly before adding a link to it. Samwalton9 (WMF) (talk) 08:56, 10 May 2022 (UTC)

Samwalton9, I strongly suggest you forget about the mobile interface in its current form, that's a waste of time. Don't try to serve readers and editors the exact same way: readers get annoyed by useless elements and editors get annoyed by missing essential elements. See phab:T307851#7911945. — Alexis Jazz (talk or ping me) 09:11, 10 May 2022 (UTC)

@Alexis Jazz: There are already differences in the mobile interface for logged-out and logged-in users, and our changes are, I think, only going to be for the interface displayed to logged-in users. If I understand your request, your issue is that Extension:MobileFrontend makes changes which you largely dislike, and therefore you'd prefer to use the MinervaNeue skin directly, without those changes. Is that right? If so could you elaborate on which elements of that extension you think need changes (or, rather, shouldn't be implemented)? Samwalton9 (WMF) (talk) 11:38, 10 May 2022 (UTC)

Samwalton9, I think MobileFrontend in its current form is, essentially, wishy-washy. It aims to please readers but also just had to include editing functionality. There are various good arguments for various possibilities and design choices, but delivering half an editing environment (consider WP:THEYCANTHEARYOU for example) isn't something to strive for. Special:MobileDiff for example is just useless. If you are interested in editing or, say, you at least know what a revision even is, you want the proper diff interface. If you're not interested, you don't need MobileDiff either. MobileFrontend just delivers a crippled editing experience. I'm not saying everyone has to use Vector and I would see tremendous value in a superclean reading mode as well as a fully featured Minerva. There is the argument of not wanting to scare off newcomers by revealing a million buttons when they decide to try editing. But that's still no excuse to deliver half an editing environment. I'll be thinking about how the presentation could be improved. — Alexis Jazz (talk or ping me) 12:36, 10 May 2022 (UTC)

@Alexis Jazz: That makes sense, and I share your view that there's a balance we haven't quite found yet between presenting an unobtrusive reading experience alongside an editing interface which has all the necessary features. I also agree with you on diffs, and in fact this is the direction I think we'll be going when we get deeper into looking at undoing edits. There's a plan (T117279), which I think we'll pick up, to remove Special:MobileDiff in favour of Special:Diff, albeit with the in-line view merged in. As you suggest, that gives us the features of the 'proper' diff interface without needing to invest additional work in new interfaces. Our current roadmap is to work on overflow menu (now), then preferences (design work underway), then diff/undo. I think there's a way for us to retain the good parts of MobileFrontend while tidying up unnecessary complications/simplifications like MobileDiff. Samwalton9 (WMF) (talk) 13:44, 10 May 2022 (UTC)

Samwalton9, Special:MobileDiff will be axed? So I can retire TakeAHikeMobileDiff? That would be a reason to celebrate! — Alexis Jazz (talk or ping me) 14:16, 10 May 2022 (UTC)

Hi all. I've tried to raise this at the RefToolbar talk page, but to no avail. I keep gettin blank parameters when using Microsoft Edge. Is there any fix/solution for this? Maybe it's the script I'm using or something else?

Thanks,--Tærkast (Discuss) 16:14, 8 May 2022 (UTC)

It might be one of your scripts, I am guessing reflinks? conflicting with it. Running RefToolbar only on Win10, Edge 101 works for me. Using versions of Edge lower than 79 would also cause the issue. On an unrelated note, some of your common.js is outdated, dispenser tools are dead and User:Ohconfucius/script/Sources.js spits out dozens of errors.--Snævar (talk) 05:43, 10 May 2022 (UTC)

Thanks, how would I go about updating my scripts? --Tærkast (Discuss) 17:15, 10 May 2022 (UTC)

Remember back in 2015, when we were younger and wilder? Anyway, back in 2015, {{Incorrect redirect template}} was upgraded to Lua with this edit. Now before that the template worked with switches, and those switches had a maximum capacity of one hundred parameters. When more than a hundred params were needed, we just embedded more switches. Worked fine.

Now, when we look at a template like {{College}}, we see one switch and several hundred params, and all the entries appear to work just fine. So my question is, what is the new maximum-parameter limitation (if any) for a switch? P.I. Ellsworth - ed. ^put'r there 13:55, 9 May 2022 (UTC)

@Paine Ellsworth I don't know if there is a limit, but according to Help:Switch parser function switch statements with 1,000 to 2,000 branches do work, though performance becomes a concern at those sizes. 163.1.15.238 (talk) 14:59, 9 May 2022 (UTC)

At present, the College template has more than 2,800 parameters/branches, and it seems to be working okay. The comparisons probably don't take nearly as long as in the past. I think that if no one else chimes in with helpful info, I'll nest a few more switches to help speed things up. Thank you, 163+ for your help on this! P.I. Ellsworth - ed. ^put'r there 15:19, 9 May 2022 (UTC)

@Paine Ellsworth I think I've found the limit.

Reading through the documentation on mediawiki there is no hard coded "maximum number of cases" limit in parser functions itself, so the standard template limits apply. I think the two most limits relevant limits here are the Preprocessor node count and the maximum expansion depth. As with all templates you can nest switch statments up to 40 layers deep. Each condion checked also adds two to the Preprocessor node count, which has a maximum value of 1,000,000. This means that a page which has nothing else on it could theoretically have up to 500,000 cases. 163.1.15.238 (talk) 15:37, 9 May 2022 (UTC)

Thanks again, 163+, very helpful info! Might go ahead and see if T.College can be Luafied to ensure top speed. P.I. Ellsworth - ed. ^put'r there 20:39, 10 May 2022 (UTC)

Hi is there some template I can use to block individual editors or automated messages for prods and AFDs etc? I have a bot blocker but nothing I can code to block individual editors. Like on Twitter there ought to be a block user option from posting on your talk page.♦ Dr. Blofeld 09:22, 5 May 2022 (UTC)

There is no way for you to turn off talk page messages from someone. You can turn off pings and emails, if you would like -- Guerillero ^{Parlez Moi} 12:20, 5 May 2022 (UTC)

@Dr. Blofeld: phab:T165124 is about a possible user control to block other users from your usertalk. While this could be invented, I don't expect it will ever be part of the English Wikipedia. But what are these "automated" messages you are getting? Are these really "edits" someone is maybe using scripts to help make, or is this some other process? — xaosflux ^Talk 12:35, 6 May 2022 (UTC)

I want something to block people with deletion prods and articles for deletion. So some sort of coding to block editors with "Proposed deletion" and "listing for deletion" notices from editing my talk page is probably possible.♦ Dr. Blofeld 12:44, 6 May 2022 (UTC)

@Dr. Blofeld right now the only way to do that would be with an edit filter, targeting your talk page - and that's not going to happen. Now, if perhaps you were only concerned with assisted edits that come from Twinkle (such as these) you could ask over at Wikipedia talk:Twinkle. Perhaps they could build a blacklist of "Users that do not want Twinkle assisted talk notices" in to that script. — xaosflux ^Talk 12:51, 6 May 2022 (UTC)

Is this one specific individual pestering you? Admins can set a WP:PBLOCK on a named individual that prevents them from editing certain pages. This is normally only done for a good reason, not "this user is annoying me". --Redrose64 🌹 (talk) 22:29, 6 May 2022 (UTC)

@Redrose64: It would make a considerable difference if I didn't get notices from User:Donaldd23. I have asked him in the past not to spam my talk page with messages.♦ Dr. Blofeld 09:20, 10 May 2022 (UTC)

I apologize for notifying you when I submit an article for PROD or AfD. I use TWINKLE and it automatically is set to notify the creator of the article. I do not recall you asking me not to notify you, but I will do my best in the future to uncheck the box and not have it notify you. Thank you. DonaldD23 talk to me 11:59, 10 May 2022 (UTC)

@Dr. Blofeld: See above. But if it resumes, consider requesting a WP:PBLOCK at WP:AN - but you need to make a strong case. --Redrose64 🌹 (talk) 22:07, 10 May 2022 (UTC)

Is there time calculator so we can sum up total lenght of songs from album? Eurohunter (talk) 22:31, 10 May 2022 (UTC)

@Eurohunter can you give an example of what you would expect the inputs (at least 3) and output to be for such? — xaosflux ^Talk 22:46, 10 May 2022 (UTC)

The documentation for {{Track listing}} mentions User:JPxG/TrackSum.js. Nardog (talk) 22:56, 10 May 2022 (UTC)

@Xaosflux: @Nardog: TrackSum.js has problem with Angel in the Night. There is no tool where I can type numbers and sum up? Eurohunter (talk) 23:14, 10 May 2022 (UTC)

LMGTFY ;) 1, 2 — xaosflux ^Talk 23:18, 10 May 2022 (UTC)

@Xaosflux: Yes I can use search function myself but I expected tool on Wikipedia (internal or external) or there is option to sum up time in Google search or Windows but I don't know how to activate it. Eurohunter (talk) 23:21, 10 May 2022 (UTC)

Short answer on wiki, pretty sure no. In windows, you prob could write something in powershell. Long answer on wiki, there are no tool to type things in, but a lua function could theoretically do this, but the input would need to be in the form of wikitext to a template. You should be able to do this in the browser if you write a javascript for it, I didn't see one as a ready to go userscript. Those websites I linked will let you "type numbers" and it will "sum up" them for you though. — xaosflux ^Talk 23:28, 10 May 2022 (UTC)

Hi, does anybody know a template to print specific line number of a long list when it gets transcluded? I'm using <noinclude> in Portal:Linux/News to avoid a long list in Portal:Linux but it seems not a best practice. — Labdajiwa (talk) 08:30, 11 May 2022 (UTC)

@Labdajiwa moving the noinclude is the 'easiest' way, you could also manually update something with Help:Labeled section transclusion, but that would be more work. I suppose you could write something with Lua (follow up at Wikipedia talk:Lua for more on options there). — xaosflux ^Talk 10:12, 11 May 2022 (UTC)

My use case is of a list of candidates in an election; as their party logos are of different height to width ratios, specifying their proportions by either, inevitably leads some being unduly rendered bigger than others. If only we could retrieve the height and width of the images in Commons... I could calculate new height and width for each to the same area size. Is there a trick for that? I couldn't find any documented or talked about. — Guarapiranga ☎ 05:10, 11 May 2022 (UTC)

This is not possible in wikitext. You could do it in Lua if you reallllllly needed. Izno (talk) 05:13, 11 May 2022 (UTC)

In lua it is mw.title.new(title, namespace).file.height. Width is called the same way.--Snævar (talk) 06:24, 11 May 2022 (UTC)

Thanks, Snævar and Izno. — Guarapiranga ☎ 00:10, 13 May 2022 (UTC)

While hovering over the From today's featured article, the link has political / world news commentary regarding the pending decision before the US Supreme court regarding abortion. It is not appropriate to use this hover box functionality to promote a given philosophical viewpoint. — Preceding unsigned comment added by 198.217.64.83 (talk) 17:41, 12 May 2022 (UTC)

Today's featured article is this one: Dispute between Darnhall and Vale Royal Abbey, which has nothing to do with what you're talking about. What are you seeing here? ThadeusOfNazereth(he/they)^{Talk to Me!} 17:43, 12 May 2022 (UTC)

@ThadeusOfNazereth (not the same IP as OP). The article was being repeatedly vandalised by an LTA earlier today, if you look in the page history you can see all of the deleted revisions. 192.76.8.71 (talk) 18:09, 12 May 2022 (UTC)

Oh, I see. I just assumed that featured articles were automatically protected from vandalism while they're linked on the front page. ThadeusOfNazereth(he/they)^{Talk to Me!} 18:11, 12 May 2022 (UTC)

@ThadeusOfNazereth They're automatically move protected, but not protected against editing. There was a trial with pending changes protection a while back but I don't think there was consensus to implement it. 192.76.8.71 (talk) 18:13, 12 May 2022 (UTC)

There have been several proposals to apply some form of edit protection to TFA, see for instance Wikipedia:Village pump (proposals)/Archive 183#RFC: Pending-changes protection of Today's featured article. They always fail as going against the "... that anyone can edit" part of the slogan displayed top of the main page. --Redrose64 🌹 (talk) 23:17, 12 May 2022 (UTC)

• Seems like there is nothing to do here from a technical perspective. Popups are not content aware, and have no filtering mechanism to only show certain types of content. — xaosflux ^Talk 18:59, 12 May 2022 (UTC)

  I think the issue might be that popups allow you to see the the content of edits that have been revdel'd. Nthep (talk) 21:11, 12 May 2022 (UTC)

  If you are an admin that can read that already, sure - but the OP is an IP, so certainly not to them. — xaosflux ^Talk 23:37, 12 May 2022 (UTC)

  I think there have been issues with popups and caching in the past, right? Could it be that the popup was using a cached version? If so, something should probably be added to force the cache to update if revisions are deleted. --rchard2scout (talk) 11:51, 13 May 2022 (UTC)

  For a logged out user, that seem to be "Page previews", and in combination with a vandalized page. We would need more details such as exactly what time the OP saw this to determine if there was possible technical issue. At the time of this posting the vandalism had already been removed for over 12 hours. — xaosflux ^Talk 12:53, 13 May 2022 (UTC)

During an investigation into links and transclusions, I find myself seeing many main namespace articles transclude themselves. For example, [15] shows that the page, Internationalization and localization, transcludes itself.

I was unable to reproduce that on my home wiki, zh.wikipedia; I wonder if this is caused by a software bug, or some template unknown to me. MilkyDefer 08:42, 14 May 2022 (UTC)

@MilkyDefer: It's because of one of our main citation modules; see this archived thread. Graham87 10:19, 14 May 2022 (UTC)

Hi, I just realised that on wiktionary:, one may create pages titled with lowercase first letter. But that is not possible here on Wikipedia, and we have to put hatnotes explaining to readers how this is all because of a mediawiki technical restriction. So, what exactly is this "mediawiki technical restriction" that doesn't apply on Wiktionary but applies to Wikipedia anyway? Thanks! —CX Zoom[he/him] ^{(let's talk • {C•X})} 11:31, 15 May 2022 (UTC)

IIRC, originally Wikitionary was also placed under the same restrictions, until they were lifted in a 2005/2006-ish patch. NguoiDungKhongDinhDanh 11:40, 15 May 2022 (UTC)

mw:Manual:$wgCapitalLinks. It's set to false for Wiktionary and a few Wikipedia languages in https://noc.wikimedia.org/conf/highlight.php?file=InitialiseSettings.php. With the current functionality, I think setting it to false would create far more problems than it solves for English. PrimeHunter (talk) 11:43, 15 May 2022 (UTC)

Hi, I just found that when I use {{WikidataCoord}} to create a coordinate link from Wikidata, and set |display= to title or inline,title, the page would be added to Category:Coordinates on Wikidata‎. I'm curious that:

1. The page has already fetched datas from Wikidata via {{WikidataCoord}}, and no coordinates datas were manually filled. Why did the page need to be tracked?
2. In line 650-657 of Module:Coordinates, only coordinates displayed in the title were tracked. Why don't track inline coordinates?

Thanks. --Tim Wu (talk) 15:46, 14 May 2022 (UTC)

That is because display=title is more than just an position, it pretty much ensures that the coordinate in question is the primary one. So, with lists with coordinates for example, you have a bunch of coordinates and it would not make any sense to check all of them in wikidata.--Snævar (talk) 22:42, 15 May 2022 (UTC)

Hi there! I'm having an issue with the article Auckland Domain. Recently a second mapframe started being generated in addition to the first, and I can't see any changes to the page or the Wikidata item that would be causing this. I can remove the original Infobox mapframe template from the infobox, but this doesn't tell me where the additional map is coming from (and how I'd change the zoom/size of the additional map. Can anyone help out? --Prosperosity (talk) 22:28, 15 May 2022 (UTC)

The additional map is the default map that appear unless |mapframe=no is specified. There are paramaters like |mapframe-zoom= to adjust it. It's all documented in the {{infobox park}}.MB 23:13, 15 May 2022 (UTC)

Hello!

Recently I've started trying to help a bit in the code section of MediaWiki. I've asked for the JenkinsBot to look after my patches and sometimes I get failure notices in its tests. I've followed the provided links for them but the output pages appear gigantic and noisy for my untrained eyes. I've asked around for help in "deciphering" them and even tried searching for tutorial videos on Jenkins but so far haven't been able to find much help. Is there anyone knowledgeable enough as to help me better understand 2-3 random specific failure notices I can provide, what's going wrong and how to fix them, so, hopefully, I can be overall better in understanding how to improve my patches in similar situations? - Klein Muçi (talk) 14:33, 15 May 2022 (UTC)

I'd be happy to help. One general bit of advice: the actual error is usually near the bottom of the output. Looking at the failure report for the most recent patch you uploaded, the relevant section of the error message is

14:25:08 ./pywikibot/logentries.py:375:1: W293 blank line contains whitespace
14:25:08 ./pywikibot/page/_wikibase.py:539:1: W293 blank line contains whitespace
14:25:08 ./pywikibot/page/_wikibase.py:946:1: W293 blank line contains whitespace
14:25:08 ./pywikibot/page/_wikibase.py:947:80: E501 line too long (81 > 79 characters)
14:25:08 ./pywikibot/page/_wikibase.py:1250:1: W293 blank line contains whitespace
14:25:08 ./pywikibot/page/_wikibase.py:1251:80: E501 line too long (81 > 79 characters)
14:25:08 ./pywikibot/page/_wikibase.py:1974:1: W293 blank line contains whitespace
14:25:08 ./pywikibot/page/_wikibase.py:2209:1: W293 blank line contains whitespace
14:25:08 ./pywikibot/site/_generators.py:1239:1: W293 blank line contains whitespace
14:25:08 ./pywikibot/site/_generators.py:1240:80: E501 line too long (80 > 79 characters)

That is, at the given line numbers, you have blank lines containing trailing whitespace or lines that are too long, both in violation of the style conventions of that repository. * Pppery * _{it has begun...} 14:41, 15 May 2022 (UTC)

@Pppery, thanks a lot! How would I be able to understand lines and file names from that? And what does "W293" mean? - Klein Muçi (talk) 14:52, 15 May 2022 (UTC)

"W293" is an internal error code from the tool being used to do that check and isn't particularly relevant here. I'm not sure what you mean by How would I be able to understand lines and file names from that?; ./pywikibot/page/_wikibase.py is a filename and :539 is a line number (meaning line 539 of that file). * Pppery * _{it has begun...} 15:17, 15 May 2022 (UTC)

@Pppery, yes, thank you, that's exactly what I meant. What does the next number after 539 (1) mean? - Klein Muçi (talk) 15:41, 15 May 2022 (UTC)

It means the character position within the line (that is :1 means the first character after the newline, :80 means the 80th character after the newline). * Pppery * _{it has begun...} 15:43, 15 May 2022 (UTC)

Thank you!

What about in these 3 other failure outputs I randomly selected from my patches:

1. https://integration.wikimedia.org/ci/job/trigger-wikispeech-mary-tts-pipeline-test/9/console
2. https://integration.wikimedia.org/ci/job/composer-php81-docker/8/console
3. https://integration.wikimedia.org/ci/job/tox-docker/25261/console

- Klein Muçi (talk) 15:49, 15 May 2022 (UTC)

All three of those seem to be some sort of pre-existing repository misconfigration and nothing to do with your patch, which is all I can say. I note that the third link appears to be a patch to Wikimetrics, which was shut down in 2018, so it's not clear why you are making changes to its codebase and expecting them to work. * Pppery * _{it has begun...} 16:24, 15 May 2022 (UTC)

@Pppery, I see, thank you. The reason I was doing those changes was because of T201491. I wanted to get myself accustomed with the general process and so I tried to fix as many typos as I could. (One of the easiest tasks I could find around.) That process helped me a lot but it was also accompanied with a lot of patches that had to be abandoned because of accidentally trying to fix upstream libraries or, as apparently was the case with what you just showed to me, old already shut down projects.

Thanks a lot for your help! The failure outputs make way more sense now for me. - Klein Muçi (talk) 22:39, 15 May 2022 (UTC)

• If this isn't about the English Wikipedia, perhaps mw:Project:Support_desk would be a better forum to follow up on this sort of thing. — xaosflux ^Talk 15:51, 15 May 2022 (UTC)

  @Xaosflux, hello! A bit of a naive question but is there a "memo" or a RFC done lately I might have missed in regard to topics that should be discussed here or something similar? This is the second time in less than 2 weeks that I get "bounced back" from here and it's starting to make me really insecure about writing again in the future. I've been lurking around in this page for around 6 years and in the meantime most of my questions have been off-topic from an EnWiki-only POV. So far I have never been told anything about it up until these days. Has anything changed? Maybe it's just a coincidence or maybe my requests themselves have changed lately but I wanted to ask about this because it's starting to really affect my confidence to be active in here. Even before I asked this I had to contemplate for quite some time if I should post it or not because of the last episode.

  Truth be told, I forgot about the MW:Support desk but I did search around a lot at MediaWiki/WikiTech for documentation related to Jenkins and after failing to find what I wanted to know, I ended up asking at the MediaWiki Discord channel. After being left without an answer for 1 week there, I tried my luck somewhere more familiar for me (here). - Klein Muçi (talk) 23:22, 15 May 2022 (UTC)

  @Klein Muçi at that top of this page is a banner that does say The technical section of the village pump is used to discuss technical issues about Wikipedia. ... Questions about MediaWiki in general should be posted at the MediaWiki support desk. As the largest project, we often attract all sorts of random questions; I usually try to point people to the most appropriate venue. Your question didn't seem to be about this Wikipedia. — xaosflux ^Talk 23:30, 15 May 2022 (UTC)

  @Xaosflux, no I do understand that and most likely it was just a coincidence and you just wanted to help me get my help faster and keep the place tidier. It's just that for me it just so happened that I had a similar experience not so long ago (actually the time just before this) and that forced me to ask if something had happened that things were made a bit stricter lately or maybe my requests have started becoming more off topic. I am of course prone to errors and biases so maybe the fault is in me. Feeling guilty I want to explain that I really do try to find a solution before coming here, reading all the possible documentation, checking the archives and even searching for tutorial videos elsewhere on the web. It is only after those steps have failed that I do try to ask here because in 90% of the cases someone has always been able to solve my problem. But I'll try harder to utilize the more suitable forums in other cases. - Klein Muçi (talk) 23:47, 15 May 2022 (UTC)

My advice for finding the important parts of Jenkins logs is to search for "error", "exception" and "fail", and then look at the preceding lines. Matma Rex talk 02:01, 16 May 2022 (UTC)

@Matma Rex, so far I've only searched for fail. Will update the mental list accordingly. Thank you! - Klein Muçi (talk) 03:02, 16 May 2022 (UTC)

In playing with MusikAnimal's scriptManager, I get a looooong list of scripts I want to play with on my left pane. I then started trying to make it more context sensitive, by separating them into different groups--history scripts, talk scripts, edit scripts, main scripts, etc (I might then use the same logic for always enabled scripts)--but using js' spread operator (...) to update the scriptsToManage object broke the script (commenting out the update portion, unbreaks it). What gives? — Guarapiranga ☎ 03:49, 16 May 2022 (UTC)

Yes, phab:T75714. Galobtter (pingó mió) 03:58, 16 May 2022 (UTC)

According to m:Help:URL and m:How to edit a page, all characters in URLs must be caught by [A-Za-z0-9:._\/~%-+&#?!=()@]. However:

• This URL is displayed correctly albeit having a comma in the middle:

  https://en.wikipedia.org/wiki/Diana,_Princess_of_Wales

• This URL is displayed correctly albeit having a semicolon in the middle:

  https://en.wikipedia.org/wiki/Diana;_Princess_of_Wales

• This URL avoid adding the trailing comma:

  https://en.wikipedia.org/wiki/Diana,_Princess_of_Wales, barfoo

• This URL avoid adding the trailing colon:

  https://en.wikipedia.org/wiki/Diana,_Princess_of_Wales: Foobar

In short, what exactly is the regex used by MediaWiki/Parsoid? NguoiDungKhongDinhDanh 13:22, 15 May 2022 (UTC)

Have you tried asking over at mw:Talk:Parsoid? Those meta pages seems to be out of date, for example https://ks.wikipedia.org/wiki/وِکیٖپیٖڈیا:اؠسَمبَلی_(تَکنیٖکی) works and it has all sorts of characters not in that list. — xaosflux ^Talk 01:13, 16 May 2022 (UTC)

Thanks! Asked there instead. NguoiDungKhongDinhDanh 06:18, 16 May 2022 (UTC)

How I can undone page moves? Eurohunter (talk) 08:58, 16 May 2022 (UTC)

@Eurohunter: Just move it back? NguoiDungKhongDinhDanh 09:04, 16 May 2022 (UTC)

@NguoiDungKhongDinhDanh: In most cases there is redirect left so I can't do that. Eurohunter (talk) 09:06, 16 May 2022 (UTC)

@Eurohunter: If the target page has only one revision and it redirects to the page you were moving, you will be able to delete that target page. NguoiDungKhongDinhDanh 09:10, 16 May 2022 (UTC)

As stated, if the redirect has one revision you can delete it by moving the page to that title. It the redirect has more than one revison or you can't move it for some other reason then you can list it at Wikipedia:Requested moves#Requests to revert undiscussed moves, assuming there was no discussion prior to the move. 163.1.15.238 (talk) 10:39, 16 May 2022 (UTC)

In the past few days my Chromebook keeps going to the mobile version - I suspect a Chromebook update.

Is there a way I can always go to the desktop version please?

Chidgk1 (talk) 14:39, 13 May 2022 (UTC)

In Special:Mypage/common.js, add the line

mw.loader.load( "https://en.wikipedia.org/w/index.php?title=User:%C3%9Ejarkur/NeverUseMobileVersion.js&action=raw&ctype=text/javascript" ); // User:Þjarkur/NeverUseMobileVersion.js

to automatically force any pageview of a mobile version page to reload the corresponding desktop page. —Kusma (talk) 14:49, 13 May 2022 (UTC)

I have that enabled, and it doesn't work when I'm editing on my mobile. ScottishFinnishRadish (talk) 14:50, 13 May 2022 (UTC)

Not working on my Chromebook either (and I don't have the twiddle on my keyboard so cannot work out how to sign this on mobile version) — Preceding unsigned comment added by 88.234.193.205 (talk) 14:57, 13 May 2022 (UTC)

When I do "open new tab" it stays on desktop like this but when I just click a link it goes to mobile like above Chidgk1 (talk) 15:01, 13 May 2022 (UTC)

Are you open to the mobile domain (en.m.wikipedia.org) or the normal en.wikipedia.org URL? — xaosflux ^Talk 15:29, 13 May 2022 (UTC)

Copied twiddles - lets see if I am logged in still 88.234.193.205 (talk) 15:06, 13 May 2022 (UTC)

OK so also I seem to have been logged out? — Preceding unsigned comment added by 88.234.193.205 (talk) 15:08, 13 May 2022 (UTC)

Works for me, just pulled out a Chromebook and made this reply. I'm on v101.0.4951.59, 64bit. Loading fine logged in, or in an incognito window. — xaosflux ^Talk 15:13, 13 May 2022 (UTC)

I've never had much luck with that script using chrome on my phone. Guess I'm just unlucky. ScottishFinnishRadish (talk) 15:14, 13 May 2022 (UTC)

@ScottishFinnishRadish That's because you're using ImportScript. ImportScript is deprecated and does not work on the mobile sites (I believe is slated for removal from the desktop site too at some point), see mw:ResourceLoader/Migration guide (users)#MediaWiki 1.16 and before. To get scripts to work on the mobile site you need to replace your ImportScript's with mw.loader.load's. 163.1.15.238 (talk) 16:41, 13 May 2022 (UTC)

Ah, thanks. Much appreciated. ScottishFinnishRadish (talk) 17:23, 13 May 2022 (UTC)

I don't have any issue like this. I'm making this reply on a CHromebook rn (I have no clue what the version is or if it's Chrome OS 32 bit or 64bit) ― Blaze Wolf^Talk_{Blaze Wolf#6545} 15:22, 13 May 2022 (UTC)

Thanks same version Powerwash Chromebook solved it Chidgk1 (talk) 15:36, 13 May 2022 (UTC)

Duh I thought so but now problem is back - will try Powerwash without reloadıng any of my stuff — Preceding unsigned comment added by 88.234.193.205 (talk) 15:44, 13 May 2022 (UTC)

It will only work when you are logged in. —Kusma (talk) 16:21, 13 May 2022 (UTC)

If anyone else has the same problem uninstalling the Wikpedia app from my Chromebook solved it for me. Chidgk1 (talk) 14:36, 16 May 2022 (UTC)

Moved to Wikipedia:Link rot/URL change requests

 – * Pppery * _{it has begun...} 15:54, 16 May 2022 (UTC)

Any idea why Santa Clara station (California) claims to transclude Module:Adjacent stations/MUNI and Module:Adjacent stations/SCVTA? As far as I can tell, the page does not include MUNI or SCVTA in the adjacent station list. Animal lover |666| (talk) 17:19, 16 May 2022 (UTC)

They are transcluded by {{Bay Area Rail Stations}}. PrimeHunter (talk) 17:40, 16 May 2022 (UTC)

@Animal lover 666 The templates are used in some of the navboxes at the bottom of the article, e.g. Module:Adjacent stations/MUNI is used in {{Bay Area Rail Stations}}. 163.1.15.238 (talk) 17:41, 16 May 2022 (UTC)

@Animal lover 666: It seems to have been indirectly transcluded through {{Bay Area Rail Stations}}, a navbox template. NguoiDungKhongDinhDanh 17:42, 16 May 2022 (UTC)

Hello! I'm wondering if someone could create a Wikibreak template for me (or direct me to a place I can request one). I'm wanting sort of a "scheduled wikibreak" template that will only display (or, if that's not possible say that the user will be on Wikibreak) after a specific start date and will go away once the end date is reached. It's similar to {{Vacation}} however I'm wanting to use this template specifically as a scheduled Wikibreak template since I won't be going on vacation at the start date (in fact my vacation will really only be a portion of the scheduled wikibreak). ― Blaze Wolf^Talk_{Blaze Wolf#6545} 17:24, 16 May 2022 (UTC)

@Blaze Wolf: You can specify that condition using {{#ifexpr}} and {{#time}}, like this: {{#ifexpr:{{#time:U|start date}} <= {{#time:U}} <= {{#time:U|end date}}|{{Wikibreak}}}}. NguoiDungKhongDinhDanh 17:47, 16 May 2022 (UTC)

@NguoiDungKhongDinhDanh: Ok...? Could you show me an example? I'm not sure I understand. ― Blaze Wolf^Talk_{Blaze Wolf#6545} 17:48, 16 May 2022 (UTC)

@Blaze Wolf: For instance, {{#ifexpr:{{#time:U|1 Jan 2022}} <= {{#time:U}} <= {{#time:U|1 Jul 2022}}|{{Wikibreak}}}} outputs (demo) {{Wikibreak}} at this very moment. NguoiDungKhongDinhDanh 17:50, 16 May 2022 (UTC)

@NguoiDungKhongDinhDanh: Ah alright. So it will display the template on the page if the it's within the time? ― Blaze Wolf^Talk_{Blaze Wolf#6545} 17:57, 16 May 2022 (UTC)

Yep. NguoiDungKhongDinhDanh 18:00, 16 May 2022 (UTC)

@NguoiDungKhongDinhDanh: Did I do something wrong? Cause it's displaying the template even though the start date hasn't happened yet. ― Blaze Wolf^Talk_{Blaze Wolf#6545} 18:08, 16 May 2022 (UTC)

@Blaze Wolf: Nope, I did it wrong. Fixed that for you by using double conditions. NguoiDungKhongDinhDanh 18:11, 16 May 2022 (UTC)

18:56, 16 May 2022 (UTC)

How are people here managing their global and local scripts (other than manually)? Has anyone crafted a global script installer yet? Enterprisey said he's not planning on expanding his script installer to global.js. Can common.js be transcluded to global.js (and common.js somehow disabled), so that the enwiki script installers be used to install to global indirectly? (clunky, I know, but that's all I could think of.)

Cheers. — Guarapiranga ☎ 02:26, 10 May 2022 (UTC)

Script-installer is quite short. I think I can try tweaking it, but am unsure if both common.js and global.js can/should be supported. #firstHeading already looks busy with the two, let alone a third. NguoiDungKhongDinhDanh 10:50, 10 May 2022 (UTC)

Here's a hacky way to get Enterprisey's installer to install scripts globally: in your common.js put window.scriptInstallerInstallTarget = "myglobal";
This will make the installer install scripts into a page called "myglobal.js" in your userspace (of course, you'd have to move your existing script installations there if you want to make them global). Then, in your global.js on Metawiki, put mw.loader.load("https://en.wikipedia.org/wiki/User:Guarapiranga/myglobal.js?action=raw&ctype=text/javascript");. I've tested this briefly and it seems to work as far as I can tell. Rummskartoffel 17:17, 10 May 2022 (UTC)

Nice workaround I must say, but it's not really comfortable: you will have to add every single myglobal.js to your real global.js. Imagine you have, say, 100 scripts scattering into 5 or 6 myglobal.js and suddenly a bug appears out of nowhere, the only way to check and uninstall a certain one is to find out where it hides first, go to that specific wiki to disable it, test things out, then restart the process and gets extremely confused. NguoiDungKhongDinhDanh 17:34, 10 May 2022 (UTC)

Oh yeah, I definitely wouldn't advise using this if you want to "globalise" more than one common.js. I understood OP's problem statement to mean "I want to use my en.wp common.js everywhere"; for anything more complex this kind of hack isn't adequate. Rummskartoffel 19:55, 10 May 2022 (UTC)

• I am not suggesting that my system is sensible for anybody else ... but I made my own system for sharing my user script setup across wikis. On the other wikis that are of interest to me, I have only common.js. The remote common.js is one line that just loads in the common.js from here. My local common.js then works out what user scripts should / should not be loaded. Putting all of my user scripts into a global.js would not be a good option for me, as not all of them will work on the other wikis — GhostInTheMachine ^{talk to me} 17:35, 10 May 2022 (UTC)

  Your common.js is the prettiest I've ever seen in my whole Wikimedia life. Looks neat. NguoiDungKhongDinhDanh 17:46, 10 May 2022 (UTC)

  ... I even have documentation! — GhostInTheMachine ^{talk to me} 17:58, 10 May 2022 (UTC)

  Definitely something I'd recommend to users who have a mess in their .jss. NguoiDungKhongDinhDanh 18:23, 10 May 2022 (UTC)

The most obvious solution would be to add

if (mw.config.get('wgWikiID') !== 'enwiki') {
	mw.loader.load('//en.wikipedia.org/w/index.php?title=User:Guarapiranga/common.js&action=raw&ctype=text/javascript');
}

to your global.js. Nardog (talk) 21:49, 10 May 2022 (UTC)

That's what I ended up going for; thanks, Nardog. I just found I needed to redefine importScript in common.js, though (as it's not deprecated in global, isn't it?):

function importScript(location) {
	mw.loader.load('//en.wikipedia.org/w/index.php?action=raw&ctype=text/javascript&title=' + location);
};

— Guarapiranga ☎ 00:21, 11 May 2022 (UTC)

importScript is not defined on mobile on any site but it's effectively a no-op on mobile here because it's defined in MediaWiki:Mobile.js. Nardog (talk) 04:46, 11 May 2022 (UTC)

Wait, so is that also an alt way of earmarking scripts for desktop only: mw.loader.load for all and importScript for desktop only? — Guarapiranga ☎ 05:06, 11 May 2022 (UTC)

There are much simpler ways, e.g. mw.loader.getState('mobile.init.styles') === 'ready'. Nardog (talk) 05:30, 11 May 2022 (UTC)

@Guarapiranga,

location

should be wrapped in

encodeURIComponent()

 ― Qwerfjkltalk 16:51, 16 May 2022 (UTC)

Works fine without it for me, Qwerfjkl (i.e. scripts load outside enwiki, even when stated with importScript). — Guarapiranga ☎ 23:44, 16 May 2022 (UTC)

@Guarapiranga, The problem would occur if the script page contained a space etc. (probably). ― Qwerfjkltalk 06:04, 17 May 2022 (UTC)

Right! I guess scriptInstaller conveniently already did the conversion, but I included the encoding in my common.js just in case. Cheers. — Guarapiranga ☎ 07:06, 17 May 2022 (UTC)

These are all excellent! Thank you. — Guarapiranga ☎ 23:21, 10 May 2022 (UTC)