Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
On [https://noc.wikimedia.org/conf/dblists/group1.dblist many wikis] (group 1), the software to play videos and audio files on pages has now changed. The old player has been removed. Some audio players will become wider after this change. The new player has been a beta feature for over four years. [https://phabricator.wikimedia.org/T100106][https://phabricator.wikimedia.org/T248418]
Changes later this week
File:Octicons-sync.svg The new version of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2022-04-26|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2022-04-27|en}}. It will be on all wikis from {{#time:j xg|2022-04-28|en}} (calendar).
File:Octicons-sync.svg Some wikis will be in read-only for a few minutes because of a switch of their main database. It will be performed on {{#time:j xg|2022-04-26|en}} at 07:00 UTC ([https://noc.wikimedia.org/conf/highlight.php?file=dblists/s2.dblist targeted wikis]).
Some very old browsers and operating systems are no longer supported. Some things on the wikis might look weird or not work in very old browsers like Internet Explorer 9 or 10, Android 4, or Firefox 38 or older. [https://phabricator.wikimedia.org/T306486]
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? LizRead!Talk! 03:19, 25 April 2022 (UTC)
:In one of the [https://en.wikipedia.org/w/index.php?title=Special:Log&logid=130554329 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 {{u|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)
Watchlist notifications still appear after being dismissed
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. — xaosfluxTalk 19:10, 26 April 2022 (UTC)
How to write multiple OR in templates?
Hi, I want to create a template like this {{code|{{#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)
::::{{#switch:{{{letter}}}|A|B|C=true|false}}. That's all. PrimeHunter (talk) 22:14, 26 April 2022 (UTC)
Red links in talk pages
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)
::Great, thanks a lot! Vpab15 (talk) 23:06, 27 April 2022 (UTC)
Is there a Javascript date library we can load?
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 [https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.widgets.DateInputWidget mw.widgets.DateInputWidget] and [https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.widgets.datetime.DateTimeInputWidget mw.widgets.datetime.DateTimeInputWidget]. Nardog (talk) 04:45, 28 April 2022 (UTC)
::Thanks, but I wasn't looking for UI widgets. [https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.widgets.datetime.DateTimeFormatter 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)
:::[https://momentjs.com/ 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)
::{{ping|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)
Watchlist, email notifications
If you have email notifications for pages on your watchlist enabled then you receive emails that start {{tpq|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 [https://en.wikipedia.org/wiki/Special:AllMessages?prefix=enotif_&filter=all&lang=en&limit=50 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. — xaosfluxTalk 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 [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/ 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. — xaosfluxTalk 13:42, 28 April 2022 (UTC)
Move templates to bottom
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. — xaosfluxTalk 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)
If IP Template
{{resolved|GIGO. — xaosfluxTalk 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.
[https://zh.wikipedia.org/wiki/Template:If_IP The Chinese version of the template] works.
:{{ping|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 — xaosfluxTalk 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. — xaosfluxTalk 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)
Watchlist problems, some revisions that I go thru come back as unread, and other related matters
{{tracked|T218511}}
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 {{phab|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)
Is there any way to make language tag markup less breakable?
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 {{tl|lang}}, {{tl|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 {{em|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 {{em|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)
Anyone else experiencing "reply" adding nowiki to pings? or inability to preview
It's a pain. As is the occasional default to Visual with the inability to preview. Doug Wellertalk 11:07, 27 April 2022 (UTC)
:If you use the {{tl|Ping}} template in Visual it will nowiki it. Use the File:OOUI icon userAdd-ltr.svg 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 Wellertalk 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 @. — MusikAnimaltalk 16:49, 27 April 2022 (UTC)
::{{ping|Ahecht}} it works fine for me - I just used the ping template on you here. — xaosfluxTalk 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. — xaosfluxTalk 09:55, 28 April 2022 (UTC)
::::Probably. I presume "toast" means text? Doug Wellertalk 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. — xaosfluxTalk 12:55, 28 April 2022 (UTC)
::::::Lol! Of course! Doug Wellertalk 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)
Edge case actions with page titles
Hello! Is there any way we can do the following actions:
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.)
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)
:#There is no Wikipedia feature but it can be done in seconds with a Windows browser. Use {{keypress|Ctrl|A}} in the edit area to mark everything and {{keypress|Ctrl|C}} to copy it to the clipboard. Manually change the page name in the url and insert the copy with {{keypress|Ctrl|V}}
:#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 {{tq|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)
No cursor in the reply tool
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}} {{ping|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)? — xaosfluxTalk 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? — xaosfluxTalk 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 [https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(technical)?safemode=1#If_IP_Template safe mode]. Are you saying right now you only see this problem in Safari? — xaosfluxTalk 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)
Navigation popups - coder needed
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:
: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 [https://phabricator.wikimedia.org/T22581 since June 2019], with no substantive responses, other than support. The Wikidata request has been there [https://phabricator.wikimedia.org/T243820 since January 2020], with zero responses. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:19, 28 April 2022 (UTC)
Lighten up
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 [https://en.wikipedia.org/wiki/Help:Table#Color;_scope_of_parameters much] [https://www.w3schools.com/colors/colors_picker.asp 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)
:{{ping|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 [https://en.wikipedia.org/w/index.php?title=Help_talk:Table&oldid=1084013111#Remove_the_outlining_of_tables 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)
: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)
ProtectedTitles
{{tracked|T65318}}
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:
Allow ordering by level of protection and/or ending date of protection;
Show links beside entries for changing protection level ("similar" to what we get in Special:BrokenRedirects);
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? — xaosfluxTalk 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 — xaosfluxTalk 13:45, 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)
Changing the position of {{tl|DISPLAYTITLE}} creates an ugly gap, how to avoid it?
{{anchor|DisplayTitle}}
In this [https://en.wikipedia.org/w/index.php?title=Fujian_tulou&diff=next&oldid=1085284282&diffmode=source 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(TC) 15:56, 29 April 2022 (UTC)
:{{magic word|DISPLAYTITLE}} and {{tl|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. {{tl|DISPLAYTITLE}} creates an extra blank row while {{tl|Short description}} doesn't. If we place {{tl|DISPLAYTITLE}} under {{tl|Short description}} as per WP:LAYOUT, this blank row will appear. If we delete {{tl|Short description}} or place {{tl|Short description}} under {{tl|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 {{tl|Short description}} and {{tl|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)
Naturally I want to use {{tl|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)
Need help with image pixels
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!
:{{replyto|Mrbeastmodeallday}} You've set {{para||350px}}, which is against MOS:IMGSIZE and WP:THUMBSIZE, particularly since it's not in the lead section. Since there is no {{para|link}} option, the image may be clicked to enlarge it, should users so desire. --Redrose64 🌹 (talk) 21:43, 30 April 2022 (UTC)
[[:File:MerkelTS.jpg]] - can't be deleted as the only choice is undelete
And it needs deletion as a BLP violation, see [https://mythdetector.ge/en/georgian-facebook-users-spread-the-chemtrail-conspiracy-theory/]. Thannks. Doug Wellertalk 12:34, 1 May 2022 (UTC)
:Deleted at Commons as copyvio. Doug Wellertalk 13:43, 1 May 2022 (UTC)
Time-expired problem at Template:Centralized discussion
As noted at WP:Bureaucrats' noticeboard#The time allocated for running scripts has expired, something has gone wrong with {{tl|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 {{tl|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)
Map misspelling
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)
:{{ping|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)
::{{re|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)
:::{{ping|DuncanHill}} Oops, my bad. [https://www.openstreetmap.org/node/52231630 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)
Hiding Wikidata edits from watchlist
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)
Make working with templates easier: More improvements coming soon.
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 WolfTalkBlaze 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 WolfTalkBlaze 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)
Loading Watchlist very slow
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)
::I think parsing Tamzin's RfA every time might be causing it? I've tried [https://en.wikipedia.org/w/index.php?title=User:Amalthea/RfX/RfA_count&diff=1085632190&oldid=1068482713 this]; does this improve things? —Kusma (talk) 15:46, 1 May 2022 (UTC)
:::{{Ping|Kusma}} Back to normal for me. Kante4 (talk) 15:48, 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)
User talk page warning to flag up likely THEYCANTHEARYOU problem
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.
: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)
::::Thanks @Qwerfjkl — didn't even know such a place existed! :) Will try there... -- DoubleGrazing (talk) 11:55, 2 May 2022 (UTC)
Time spent on Mediawiki projects
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. — xaosfluxTalk 16:02, 27 April 2022 (UTC)
:@Klein Muçi This may not be exactly what you're looking for, but [https://xtools.wmflabs.org/ec/en.wikipedia.org/Klein_Mu%C3%A7i 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)
:{{u|Klein Muçi}}, you might find [https://sq.wikiscan.org/user/Klein+Mu%C3%A7i 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)
Does this template do anything?
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 FarmTalk 17:48, 2 May 2022 (UTC)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
On [https://noc.wikimedia.org/conf/dblists/group2.dblist all remaining wikis] (group 2), the software to play videos and audio files on pages has now changed. The old player has been removed. Some audio players will become wider after this change. The new player has been a beta feature for over four years. [https://phabricator.wikimedia.org/T100106][https://phabricator.wikimedia.org/T248418]
Changes later this week
File:Octicons-sync.svg The new version of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2022-05-03|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2022-05-04|en}}. It will be on all wikis from {{#time:j xg|2022-05-05|en}} (calendar).
Future changes
The developers are working on talk pages in the Wikipedia app for iOS. You can [https://wikimedia.qualtrics.com/jfe/form/SV_9GBcHczQGLbQWTY give feedback]. You can take the survey in English, German, Hebrew or Chinese.
Most wikis will receive an improved template dialog in VisualEditor and New Wikitext mode. [https://phabricator.wikimedia.org/T296759] [https://phabricator.wikimedia.org/T306967]
If you use syntax highlighting while editing wikitext, you can soon activate a colorblind-friendly color scheme. [https://phabricator.wikimedia.org/T306867]
Google translate shows login message for Wikipedia
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. — xaosfluxTalk 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. — xaosfluxTalk 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)
:{{ping|xaosflux}} Would the CSS in the collapsed bit would sort of show what it would look like if it were implemented? ― Blaze WolfTalkBlaze Wolf#6545 15:26, 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)
:::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 — GhostInTheMachinetalk 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 [https://en.wikipedia.org/wiki/Special:Preferences?useskin=vector-2022#mw-prefsection-gadgets 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. — xaosfluxTalk 20:00, 28 April 2022 (UTC)
Removing messagebox and standard-talk
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 {{tl|ombox}} and {{tl|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 {{em|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. {{tq|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)
:This is now done. Izno (talk) 21:35, 3 May 2022 (UTC)
Bug in Special:Contributions - lost checkboxes
{{tracked|T307530}}
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 {{button|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 Rextalk 22:32, 3 May 2022 (UTC)
::{{ty}} --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-File:Maple Leaf (Pantone).svg 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-File:Maple Leaf (Pantone).svg 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-File:Maple Leaf (Pantone).svg 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?/ [https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Accueil_principal full page view] Moxy-File:Maple Leaf (Pantone).svg 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) {{tq|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 {{phab|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 — GhostInTheMachinetalk to me 11:01, 3 May 2022 (UTC)
:::I guess you didn't get caught by the A/B testing {{u|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)
Is there a Vector-2022 talk page?
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)
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
:{{re|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. — xaosfluxTalk 15:26, 4 May 2022 (UTC)
: Note that the Date() constructor uses your browser's time zone. NguoiDungKhongDinhDanh 15:44, 4 May 2022 (UTC)
Dark mode
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)
::Thanks.Zao.♦ Dr. Blofeld 16:35, 4 May 2022 (UTC)
Dark mode by default to save energy (and the earth)
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)
::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)
ENGVAR in newcomer copyedit task
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:
::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)
:::::@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)
Chrome browser edit window fonts
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. — xaosfluxTalk 18:35, 4 May 2022 (UTC)
::{{ping|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 — xaosfluxTalk 20:40, 4 May 2022 (UTC)
::::{{ping|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)
Petscan
Why since 1-2 months [https://petscan.wmflabs.org/?outlinks_no=&only_new=on&edits%5Bflagged%5D=both&edits%5Bbots%5D=both&search_max_results=500&interface_language=en&edits%5Banons%5D=both&cb_labels_any_l=1&after=20210101000001&ns%5B0%5D=1&cb_labels_no_l=1&language=en&cb_labels_yes_l=1&categories=Bilateral%20relations%20by%20country&project=wikipedia&active_tab=tab_pageprops&max_age=3000&depth=1&doit= 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)
"Special pages"?
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! LizRead!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. LizRead!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. LizRead!Talk! 05:55, 5 May 2022 (UTC)
Gallery pictures look blurry on Edge and Chrome (Windows)
:I'm not exactly seeing the issue here. The images look perfectly fine. ― Blaze WolfTalkBlaze Wolf#6545 14:33, 4 May 2022 (UTC)
::On the top four picture thumbnails there is some weird phenomenon kinda like [https://techguided.com/wp-content/uploads/2019/01/Anti-aliasing-Example-750x420.jpg 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 WolfTalkBlaze 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)
{{clear}}
Movement Strategy Implementation Grant for the creation of an all-purpose file tool
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)
How to get/copy raw html content?
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
...
content in [https://ckb.wikipedia.org/wiki/%D8%AF%D8%A7%DA%95%DB%8E%DA%98%DB%95:%DA%BE%DB%86%DA%A9%D8%A7%D8%B1%DB%8C_%D8%A8%DB%95%DA%A9%D8%A7%D8%B1%DA%BE%DB%8E%D9%86%D8%A7%D9%86%DB%8C_%D9%86%D8%A7%D8%A6%D8%A7%D8%B2%D8%A7%D8%AF/doc?action=raw 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. — xaosfluxTalk 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)
::::::{{ping|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 {{tq|.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. — xaosfluxTalk 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)
{{od}}
{{re|Aram}} When you edit MediaWiki:Licenses the bulleted items work like this:
::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? — xaosfluxTalk 20:50, 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. — xaosfluxTalk 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.
{{collapse top|1=Content|indent=8em}}
// 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();
:::::Please notice that I changed the API source and it's "revids" to allow you try the the code (here: [https://test.wikipedia.org/wiki/Special:Upload 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)
{{od|5}} {{ping|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++) {