Talk:Main Page

From Patch Demo (601350,5)
Jump to navigation Jump to search

Archive subpages over 20 level deep[edit source]

I was looking at pages in all namespaces on this wiki with over 200 byte long titles when I found multiple pages which are archive subpages which are over 20 levels deep. One example is Talk:Clan Campbell/Archives/2018 1/Archives/2018 1/Archives/2018 1/Archives/2018 1/Archives/2018 1/Archives/2018 1/Archives/2018 1/Archives/2018 1/Archives/2018 1/Archives/2018 1/Archives/2018 1/Archives/2018 1/Archives/2018 1/Archives/2018 1/Archives/2018 1, which ClueBot created. See quarry:query/4320. User:Cobi is the botmaster. What happened here?--Snaevar (talk) 21:06, 30 January 2021 (UTC)[reply]

That's funny. Johnsoniensis added == == in the lead [1] before Template:Tlx which should be in the lead. Is it or isn't it in the lead afterwards? ClueBot III couldn't make up its mind. It's only a valid archive request if it's in the lead and ClueBot III apparently thought it was because it archived the page. It should only archive non-lead sections but it archived the "section" including the archive request.[2] In the next run it saw the archived archive request and thought it was a request to archive the archive so it dutyfully continued doing so recursively until it hit the 255-byte limit on page names. PrimeHunter (talk) 22:24, 30 January 2021 (UTC)[reply]
Funny bug. I fixed the intended archives, so all the extra archives can be deleted once Cobi doesn't need them for debugging any more. --mfb (talk) 09:55, 31 January 2021 (UTC)[reply]
Commuter town nesting. Scottish clan of archives. Here is a more creative variation: Template:Force wrap I'm cleaning these up and nominate them for deletion. That's all in the article namespace. There are many more in the user namespace, but that's up to these users. At least one of them has been cleaned up in the past, see HighKing cleanup (the deletion request appears in the same query because of its long name). --mfb (talk) 10:40, 31 January 2021 (UTC)[reply]
Update: The bug is not triggered by the empty section title, the other pages had filled section titles. Seems to be a general problem that the bot accepts archiving instructions in archivable sections. I realized Cobi has sysop rights so they can check the pages even after they are deleted, so I nominated all of them for speedy deletion. There are still user pages if others want to see examples. Found another archiving issue with Scottish articles in the process and fixed that as well. --mfb (talk) 13:05, 31 January 2021 (UTC)[reply]

I've found some additional messed-up pages; should these be MfD'd?

  1. User talk:Astroketh/Archives/2019/November/Archives/2020/February
  2. User talk:Astroketh/Archives/2019/November/Archives/2020/February/Archives/2020/May
  3. User talk:Astroketh/Archives/2019/November/Archives/2020/February/Archives/2020/May/Archives/2020/August
  4. User talk:Astroketh/Archives/2019/November/Archives/2020/February/Archives/2020/May/Archives/2020/August/Archives/2020/October
  5. User talk:Loksmythe/Archives/2020/August/Archives/2020/November
  6. User:ClueBot III/Master Detailed Indices/User talk:Loksmythe/Archives/2020/August/Archives/2020/November

jp×g 22:57, 4 February 2021 (UTC)[reply]

If the "real" content of these pages gets moved to the most appropriate true archive page, such that all that is left in the fake archive is a Template:Tlx or similar, then the fake archive can be tagged with Template:Tlx (there are not many valid uses for WP:CSD#G6, but this is one of them). --Redrose64 🌹 (talk) 23:57, 4 February 2021 (UTC)[reply]
Oh, chains that are still being formed. Move the archiving templates back to the parent talk page, make sure all the talk sections are in an archive, then nominate the nested archives for speedy deletion. G6, Db-error and G1, Db-nonsense both work. I wouldn't (and didn't) do this for user talk archives, however. It's best to ask these users first. If they want help with cleaning up, then U1, user request, is another possible deletion reason. For article talk pages there is no such concern. --mfb (talk) 00:28, 6 February 2021 (UTC)[reply]
I cleaned up all article talk page archives with the patterns "[month]/Archive", "1/Archive" and "2/Archive". The last one had just one instance and there were no accidental "3/Archive" or "4/Archive", so I didn't search beyond that (there are plenty of false positives in these searches, like Talk:Fallout 4/Archive 1). That's another 40 soon-to-be deleted edits. It makes Category:Candidates for uncontroversial speedy deletion look weird. --mfb (talk) 02:15, 6 February 2021 (UTC) --mfb (talk) 02:15, 6 February 2021 (UTC)[reply]
I don't see why user talk pages should be exempt - I can't think of a reason why the archive should itself be archived. Usually it's simply because the user concerned placed the archiving template in a section, Template:Diff, repeated Template:Diff. I think I fixed up the chain rooted at User talk:Sgubaldo - this involved eleven edits and thirty G6 deletions. And that's for just one user talk page which only ever had three threads posted to it that didn't originate with that same user.
Looking at the last 5,000 edits by ClueBot III in User talk: space (i.e. back to 15 December 2020), I have also found other chains rooted at User talk:Astroketh, User talk:Denisarona, User talk:Loksmythe, User talk:Mdriscoll03, User talk:Tessaracter, User talk:Tomcat7 and User talk:Trillfendi. --Redrose64 🌹 (talk) 14:58, 6 February 2021 (UTC)[reply]
What if I create User talk:Mfb/Archive 1/Archive 1/Archive 1 and archive things in it? Will you clean that up as well? I generally avoid changes in the space of other users unless it's clearly meant to be edited. I asked all active users with "endless" chains (one replied already), I skipped banned and completely inactive users. There are many additional users with a shorter archive nesting: Search 1, Search 2, Search 3 (similarly for the other months). By the way: The Cluebot subpages are irrelevant once their associated archive pages are deleted. There might be an automated clean-up script, I don't know. --mfb (talk) 15:13, 6 February 2021 (UTC)[reply]
I'm not talking about altering/deleting subpages that were deliberately created by the user, but fixing up archiving errors caused because the Template:Tlux was put in the wrong place - in a section of the talk page, instead of before the first heading of that page. If re-archiving like this is not stopped when detected, it will continue until the software limitations (which I believe are a limit of 255 characters after the "User talk:" part) cause the process to bomb out. --Redrose64 🌹 (talk) 20:51, 6 February 2021 (UTC)[reply]
I know the cause and I have fixed many of them in the past week in the article talk namespace. I still think it's up to these users to decide if they want this reverted or not. It's not breaking Wikipedia, it's just an odd place for the archived discussion. --mfb (talk) 06:02, 7 February 2021 (UTC)[reply]

2FA[edit source]

Can I disable 2FA with scratch codes? ~~ CAPTAIN MEDUSAtalk 12:19, 6 February 2021 (UTC)[reply]

Template:Re Yes, according to Help:Two-factor_authentication#Disabling_2FA, which says you can use a normal code or a scratch code for disabling it. RudolfRed (talk) 17:59, 6 February 2021 (UTC)[reply]
BTW, as a PSA to everybody, if you have 2FA enabled, now is a good time to check to make sure you remember where you stashed your scratch codes and that you can still get to them. Actually, it's not a bad idea to burn one now to make sure you understand how to use them. There's nothing special about now that makes it a good time. But, "never" is most certainly not a good time. -- RoySmith (talk) 18:39, 6 February 2021 (UTC)[reply]
Warning - never get down to less than TWO scratch codes, if you are down to 2 or 1 , regenerate codes by disabling 2FA and reactivating it. — xaosflux Talk 23:42, 6 February 2021 (UTC)[reply]
In fact rather than rely on scratch codes, it might be a better idea to use an app like Authy that encrypts 2FAs and stores them on the cloud; you can then install the client on your phone, home laptop and work laptop. Then the only way to get locked out of your account (or be at the mercy of scratch codes) is if you lose all your devices. – SD0001 (talk) 17:21, 7 February 2021 (UTC)[reply]

Template determinism[edit source]

  1. Are templates defined to be evaluated in a specific order or are they defined to be evaluated an undefined order?
  2. During the template expansion of the page, can one template change the state of something so that another template can detect that change? — GhostInTheMachine talk to me 12:25, 6 February 2021 (UTC)[reply]
If they are nested then inner templates are evaluated first. If they are in parallel they should not depend on each other (but Lua can analyze the source code of the article, so in principle you can create trouble). --mfb (talk) 14:17, 6 February 2021 (UTC)[reply]
A Lua module can find where its template is in the source (see Template:Ml for one), but I assume that the source it sees is read-only? — GhostInTheMachine talk to me 16:56, 6 February 2021 (UTC)[reply]
Yes. There are numerous safeguards so that templates can not change other template transclusions (that is, other than subtemplates). In lua editing the source would be done with the internal os libary, which is intentionally blocked on all WMF projects.
There are two situations where templates are evaluated, one if the page is purged or edited, and the other if there is any change in the template itself. For the former the templates are evaluated from top to bottom (e.g./f.x. the lead first), for the latter see Wikipedia:Purge#Server_cache.--Snaevar (talk) 17:43, 6 February 2021 (UTC)[reply]
Template:U, I assume they're also re-evaluated if a new version of Lua is installed? -- RoySmith (talk) 18:55, 7 February 2021 (UTC)[reply]
Interesting point but I don't think Lua has ever been updated in Scribunto. Special:Version is saying Lua 5.1.5 which is the same as six years ago and probably longer. Johnuniq (talk) 22:15, 7 February 2021 (UTC)[reply]
Indeed, we have had 5.1(.x) since initial installation, with some 5.2 backports. (I am sad, because multi-line strings are directly supported in 5.2 but were not one of the backports.) I anticipate any upgrade to a newer version would have some amount of pre-upgrade linting work (apparently there is a fork in the community between LuaJIT and Lua >5.1, much the same as there was one between Python 2 and 3). --Izno (talk) 01:00, 8 February 2021 (UTC)[reply]

OK, in full — Templates (and their module children) are not strictly deterministic as they can output non-deterministic data (such as the time), but the evaluation is isolated and module code cannot write to anything outside of the evaluation of the current template. i.e. A template/module can only output HTML/wikitext and cannot alter any existing wikitext, cannot write to Wikidata, cannot write to any database anywhere and cannot alter any "global" or system variables. This means that a template/module cannot "pass" any information to another template/module other than the children being expanded within their own expansion. That right? — GhostInTheMachine talk to me 19:19, 8 February 2021 (UTC)[reply]

That's correct. One way to look at it is that devs want people to be able to edit any section on a page and preview the result, without needing to parse the whole page. Indeed, a dozen people could be simultaneously editing and previewing different sections and each works in complete isolation. An enterprising editor found they could muck around with refs to break the isolation model, but that was regarded as a bug and the system patched to prevent it. It is possible to have a loadData module which does calculations and returns a fixed table of data. I would recommend against it, but such a module could read the page and decide what to do based on what it finds. Once loaded, subsequent accesses to the module would get a cached table. Johnuniq (talk) 22:20, 8 February 2021 (UTC)[reply]

RefToolbar and Cite button[edit source]

Hi. Why is this function so intermittent? I added it via the gadgets page in my preferences, and it works from time to time. But quite a lot of the time, clicking the button just sends it off spinning and doesn't do anything. Clicking cancel gives the "Error: Citations request failed". I'm using the latest version of Firefox. Anyone else having the same issues? Thanks. Lugnuts Fire Walk with Me 16:14, 6 February 2021 (UTC)[reply]

Been hit-and-miss for the last two days now. Lugnuts Fire Walk with Me 10:12, 8 February 2021 (UTC)[reply]
maybe check Wikipedia:RefToolbar/2.0#Troubleshooting Gfigs (talk) 12:07, 8 February 2021 (UTC)[reply]
That error message is from MediaWiki:Gadget-citations.js.--Snaevar (talk) 18:46, 8 February 2021 (UTC)[reply]
Thanks both. Looked at both of them, but still the same. The cite tool worked fine yesterday, but isn't working (for me) right now. I reckon it's good for maybe 50% of the time during any given day. Lugnuts Fire Walk with Me 12:54, 10 February 2021 (UTC)[reply]
And now back to working fine...! Lugnuts Fire Walk with Me 15:43, 10 February 2021 (UTC)[reply]

checking screen sizes[edit source]

is there any way on Wiki, Chrome (mobile), or Android phone, to view what a mobile article page looks like in various custom screen sizes ? Gfigs (talk) 08:16, 7 February 2021 (UTC)[reply]

as @Aklapper posted in phab:T271288Gfigs (talk) 15:06, 7 February 2021 (UTC)[reply]
Template:Re If you use a PC, you can view an article on Google Chrome, Microsoft Edge or some other Chromium-based web browser. In such browsers, you can use the DevTools, which can be opened using F12 button on keyboard. You can emulate various screen sizes by following the instructions here: [3] The steps mentioned in the link can be used in Google Chrome or any other Chromium-based web browsers also. Hope it helps! CX Zoom (talk) 20:33, 7 February 2021 (UTC)[reply]
Template:U, thanks Gfigs (talk) 22:50, 7 February 2021 (UTC)[reply]

Disabling the reply button[edit source]

Is there a way to disable that obnoxious [[[:Template:Blue]]] button, preferably one that doesn't require logging in? I've been using the preview mode workaround but it's really getting old. (talk) 12:39, 7 February 2021 (UTC)[reply]

#reply-link-wrapper {display: none;} in the css should do the job. Without login you would need to do that in your browser, logged in you can use the custom css page. mfb (talk) 13:02, 7 February 2021 (UTC)[reply]
Are any IP's getting it here at the English Wikipedia or is the post about another wiki? mw:Talk pages project/Replying#Deployment says it's only deployed as opt-out at the Arabic, Hungarian and Czech Wikipedia, e.g. at hu:Wikipédia-vita:Segítség. If you have an account then you can disable it at the bottom box at hu:Special:Preferences#mw-prefsection-editing. The CSS to remove it is .dt-init-replylink-buttons {display: none !important;}. The class reply-link-wrapper is used by User:Enterprisey/reply-link which is loaded in User:Mfb/monobook.js. It's not targeted with #reply-link-wrapper but with .reply-link-wrapper {display: none;}. PrimeHunter (talk) 14:24, 7 February 2021 (UTC)[reply]
That solved the issue, thank you! And to answer you, the question was indeed about the English Wikipedia. (talk) 18:27, 7 February 2021 (UTC)[reply]
I don't see it whether logged in or out. I guess they are running an A/B test and you are in the group which gets the tool. PrimeHunter (talk) 23:22, 7 February 2021 (UTC)[reply]

Vandalized Article[edit source]

I'd like to report that an article is heavily vandalized. Please help to restore its initial form. It is: The Three Fools. Thanks in advance for the help!--MrPanyGoff (talk) 20:21, 7 February 2021 (UTC)[reply]

Template:Re are you having a technical problem? You should be able to go to the article, select history, select any old version, click edit, then publish that old version again. — xaosflux Talk 21:19, 7 February 2021 (UTC)[reply]
Anyway, thanks everybody who help to fix that issue!--MrPanyGoff (talk) 08:29, 8 February 2021 (UTC)[reply]

Logins bounced[edit source]

Typically I log in direct to my watchlist, then click through to any interesting-looking pages. Recently, when I begin to say edit an article, I sometimes find that I am no longer logged in and my edit is recorded under my IP address. This has begun to happen quite often. Is it a known issue, and if so is it more likely to be a server or browser bug? — Cheers, Steelpillow (Talk) 16:01, 8 February 2021 (UTC)[reply]

Me too, actually. Trying to hit watchlist first has been a losing proposition of late. It usually happens to me on a mobile device though. --Izno (talk) 18:33, 8 February 2021 (UTC)[reply]
Now I am noticing I a tooltip-style popup, top right: " Central login You are centrally logged in as Steelpillow. Reload the page to apply your user settings." It's appeared twice already this session. If this is signed by my IP address, we are homing in on the culprit. (talk) 19:02, 8 February 2021 (UTC)[reply]
Ha! See that! It bounced me off and I have had to log in a second time to sign this. — Cheers, Steelpillow (Talk) 19:05, 8 February 2021 (UTC)[reply]
This sounds like Wikipedia:Village pump (technical)/Archive 187#Why is Wikipedia logging me out?. --Redrose64 🌹 (talk) 22:09, 8 February 2021 (UTC)[reply]
Yes it does, thank you. However no mention was made there of the little popup. That popup suggests to me that the service knows there is an issue; presumably it remembers that you are logged in but has lost some of your session credentials. The fact that the problem is affecting/annoying multiple users and has only begun recently suggests to me that Something Needs To Be Undone. — Cheers, Steelpillow (Talk) 11:08, 9 February 2021 (UTC)[reply]

Tech News: 2021-06[edit source]

<section begin="technews-2021-W06"/>

<section end="technews-2021-W06"/> 17:40, 8 February 2021 (UTC)

Textarea not always monospaced[edit source]

In User:Redrose64/monobook.css I have the rule

/* monospace font for input boxes */
textarea.oo-ui-inputWidget-input {
  font-family: monospace;
  font-size: 13.3333px;

and this works for most multi-line text input boxes, such as the one that I used to type this in. But it's ignored in the large text input box at Special:EmailUser/Oversight (or any other recipient name), where I'm getting a PS font. How might I get a monospace font there also? --Redrose64 🌹 (talk) 21:43, 8 February 2021 (UTC)[reply]

You can try adding the following class selector:
/* monospace font for input boxes */
.oo-ui-textInputWidget .oo-ui-inputWidget-input
  font-family: monospace;
  font-size: 13.3333px;
isaacl (talk) 21:56, 8 February 2021 (UTC)[reply]
That worked for the textarea concerned - but it also matched all text input boxes, such as the subject line on that page, the edit summary below this box, and others. So I used an id instead:
/* monospace font for input boxes */
#mw-input-wpText .oo-ui-inputWidget-input {
  font-family: monospace;
  font-size: 13.3333px;
which works. But I'm still puzzled as to why the first selector wasn't matched. --Redrose64 🌹 (talk) 22:50, 8 February 2021 (UTC)[reply]
Template:Re I see a default CSS rule setting font-family: inherit; for .oo-ui-textInputWidget .oo-ui-inputWidget-input, which will have precedence over your rule. — The Earwig ⟨talk⟩ 23:12, 8 February 2021 (UTC)[reply]
I saw the same rule as The Earwig (using my browser's developer tools to examine which rules applied to the HTML element in question), thus my suggestion. Rules that match with greater specificity take precedence over those that match with less specificity. So something that matches by matching two classes, or one ID and one class (for a total of two selectors) takes precedence over a match on just one class. isaacl (talk) 23:43, 8 February 2021 (UTC)[reply]

Extra newlines when copypasting[edit source]

Template:Tracked If I go to a page with the CSS content model, highlight two or more lines, copy to clipboard and paste those elsewhere, there are two linefeeds (U+000A) after each line instead of one, the result being a blank line between consecutive "real" lines. This appears to be a recent change: how may I restore the old behaviour? --Redrose64 🌹 (talk) 21:51, 8 February 2021 (UTC)[reply]

Template:Re This is a Gecko-specific issue and has been fixed for 1.36.0-wmf.28 (phab:T271614). I wonder why it hasn't been deployed here though; Tech News doesn't say. I guess you could override the CSS until then if you want it fixed now. Nardog (talk) 00:43, 9 February 2021 (UTC)[reply]
I am pretty sure I saw WAID say elsewhere that our train got stopped for wmf.28. I assume it will come this week. --Izno (talk) 01:05, 9 February 2021 (UTC)[reply]

Talk:Hezbollah - Military History Project not showing in mobile view[edit source]

So, while investigating how to trim the banner spam, I noticed on mobile a blank section between two project notices (Lebanon and Organizations)

Switched over to desktop mode and found the page renders correctly with "Military History" being listed between the two.

A look at the wiki markup doesn't show any obvious reason this project wouldn't render on mobile. Though as I cut and paste I notice the importance field is missing.

{{WikiProject Lebanon|class=GA|importance=High}} {{WikiProject Military history|class=GA|Middle-Eastern=y|Post-Cold-War=y}} {{WikiProject Organizations|class=GA|importance=High}}

Slywriter (talk) 22:29, 8 February 2021 (UTC)[reply]

Is there a way to collapse selected rows of a table?[edit source]

In IBM System/370#Architecture details I have a table with several long sections. There is a heading row showing bit positions, and I want cells in subsequent rows to align with those headings, so I don't want to put those sections in nested tables. I would like to make each of Control Registers and General Registers separately collapsible. Is there a way to do that? Shmuel (Seymour J.) Metz Username:Chatul (talk) 22:55, 8 February 2021 (UTC)[reply]

It is possible to collapse each row seperatly, with an class="mw-collapsible" in the tr, and class="mw-collapsible-content" in all of the subsequent td's. Mw-collapsible is the Mediawiki collapsible code, it differs from NavFrame collapsible by not having an autocollapsible function.--Snaevar (talk) 18:23, 10 February 2021 (UTC)[reply]
It is not NavFrame that provides autocollapsible. Anyway, 'autocollapse' is shimmed to function based on mw-collapsible on en. --Izno (talk) 23:34, 10 February 2021 (UTC)[reply]

Wikitable help; space between columns and rows?[edit source]

I'm trying to get this wikitable format to look more like this div style one. In making a new project page for Wikipedia:WikiProject Classical music I was advised to not use divs since they leave a huge white space when the window is decreased and are not optimal on many devices. I figured the best way would to put this in a table format but I'm having trouble finding a way to have it not looked so crammed; is there a way to put space between columns and rows? Best - Aza24 (talk) 23:04, 8 February 2021 (UTC)[reply]

Template:Ping I have taken the liberty of editing your sandbox directly, as it makes it really easy to try things out directly. Please feel free, of course, to revert my edit. My quick test was successful, if I measure it against your "look more like this" criterion; I'd say it does. It is not particulary responsive to changes in display size, which I don't much like, but then, your "div style" version isn't either.
I used two different methods to simulate the divider lines, the upper one (between rows 1 & 2) uses CSS border properties, which is cleaner (I believe) than using <hr>. The lower dividers, between rows 2 & 3, use <hr>. The border version has a small break between cells, but maybe that doesn't disturb you much.
Perhaps you can see where I set widths, so you can then adjust and try out your changes as suits you. — JohnFromPinckney (talk) 00:39, 9 February 2021 (UTC)[reply]
Whoever told you that about divs is wrong. That would be the preferred mechanism to do what you are trying to do. --Izno (talk) 01:48, 9 February 2021 (UTC)[reply]
Agreed, the content Aza24 has is not tabular. That's why I added role="presentation" to my sample code, as it's purely for layout. The div sample might be improved by relaxing some of the constraints on it. As it is now, it can't resize either larger or smaller to adapt to various display sizes. — JohnFromPinckney (talk) 01:56, 9 February 2021 (UTC)[reply]
Thanks a lot Template:U, that's exactly what I was looking for, I've opted for the version without the vertical spacing. Template:Ping, I don't really know what to do—a user on the talk page was insisting I remove them. As I understand it, it's because of the white space it leaves by the section simply moving downwards rather than minimizing when a window is minimized. I don't know how much better this is, but at least it kind of addresses that issue? Aza24 (talk) 02:09, 9 February 2021 (UTC)[reply]
This is what they said, if that helps:
Template:Tq So I've interpreted this as I should be using a Wiki Template, not pure HTML and a Wikitable seemed the only possibility...? Aza24 (talk) 02:15, 9 February 2021 (UTC)[reply]
Template:Tq This is more or less reasonable. The word that we are looking for there is responsive, that is, a page design is responsive when it can change to fit the screen on which it is viewed. (Tangent: In reality the best way to test different resolutions is actually to test different resolutions by increasing or decreasing the width of the browser viewport. Zooming, which I assume is what is meant by increase/decrease scale, is usually secondary to that assessment.)
Your understanding that you should use wikitables is incorrect and in fact result in a much Template:Em design on the responsive axis, as tables do not act like you might prefer at small widths. Moreover, they are wrong from a semantic point of view.
Template:Tq Is more or less reasonable when dealing with article space because article space can be changed often, and where simplicity/wikitext is preferred anyway so that it is easy to use there (see WP:MOS#Use simple markup; especially, these reasons are not really the reasons proffered). It becomes unreasonable in a non-reader facing area, which usually do not change and where you might prefer to be fairly creative. Go hogwild!
What you definitely should do is use WP:TemplateStyles e.g. in Wikipedia:WikiProject Classical music/styles.css (you will need someone to start that page and change the content model; feel free to ping me), and put all of what are now inline styles in one place. It will make it easier to test and adjust for different resolutions and text sizes, and most importantly, it makes CSS media queries available to you, which will help make your wikipage design responsive. What I would also recommend is to avoid position relative, etc., in favor of display: flex, which will also help make your design responsive. --Izno (talk) 02:50, 9 February 2021 (UTC)[reply]
Template:Ping Fresh ping since I failed on the previous. --Izno (talk) 23:35, 10 February 2021 (UTC)[reply]

plugin error message[edit source]

I keep getting this type of message popping up, "You are importing User:Lupin/popups.js into common.js" and to remove it as it's unmaintained. I am not sure why I started getting it today, and how to get rid of it. Any help? Govvy (talk) 12:27, 9 February 2021 (UTC)[reply]

Template:Ping The code is in User:Govvy/monobook.js. You can remove the first 9 lines. Enable "Navigation popups" at Special:Preferences#mw-prefsection-gadgets if you want a replacement. PrimeHunter (talk) 13:56, 9 February 2021 (UTC)[reply]
Template:Reply I removed the first 9 lines and left importScript('User:Lightmouse/monobook.js/script.js'); there, you know, I forgot that page existed! Cheers. Govvy (talk) 14:24, 9 February 2021 (UTC)[reply]
I tweaked the prompt at User:Lupin/popups.js to try to make this a little clearer. — xaosflux Talk 14:35, 9 February 2021 (UTC)[reply]

Temporary watchlist[edit source]

I just made a post on a user talk page, and somehow this was added to my watchlist for only 28 days. I did not select 28 days, I always leave it at the default permanently. What is occurring? DuncanHill (talk) 17:55, 9 February 2021 (UTC)[reply]

Template:Ping It is the default for Twinkle. You can adjust your preferences at WP:TW/PREFS MusikAnimal talk 18:05, 9 February 2021 (UTC)[reply]
Template:Re Thanks, I had no idea there was such a page. DuncanHill (talk) 18:17, 9 February 2021 (UTC)[reply]

Did Thursday come early this week?[edit source]

I'm seeing drop-down menus (More, TW, etc) getting stuck open. Any idea what's going on? -- RoySmith (talk) 18:25, 9 February 2021 (UTC)[reply]

Thursday came late, actually. Template:U has a fix for the bullet points issue in Twinkle that should be deployed soon. As for the hover states being broken, that's due to a bug in MediaWiki that has since been fixed but not scheduled to go out until the next deployment train (Thursday). See phab:T273143#6812849. MusikAnimal talk 18:28, 9 February 2021 (UTC)[reply]
Ah, I can tell Template:U nevermind.[10]. davidwr/(talk)/(contribs) 18:32, 9 February 2021 (UTC)[reply]
Template:Ping The issue with the MoreMenu submenus is separate, by the way, and that should be fixed now too. I only pushed that update a few minutes ago so it may take a few more minutes for it to show up on your end. MusikAnimal talk 18:34, 9 February 2021 (UTC)[reply]
MoreMenu is fixed for me. Multi-bug day, I blame it on being squeezed between Patch Tuesday and WP:THURSDAY. Template:Smiley davidwr/(talk)/(contribs) 18:44, 9 February 2021 (UTC)[reply]
Template:U, Hmmm, 90-ish minutes later, it's still happening for me. I tried restarting Chrome and emptying my browser cache, to no avail. Maybe I just need a larger value of "a few more minutes" :-) -- RoySmith (talk) 19:52, 9 February 2021 (UTC)[reply]
Template:Ping Are you talking about the issue with MoreMenu submenus, or the broken hover states (where you have to click on "Page" or "User" to make the menu appear)? If the latter, that won't be fixed until the wmf.30 train arrives, which is scheduled for this Thursday.
If the former, I'm confused why it's still broken for you. I'm guessing you installed MoreMenu via the gadget. Maybe try turning the gadget off and then on again? Or try installing globally, which is the preferred route anyway because it works on all wikis. MusikAnimal talk 20:29, 9 February 2021 (UTC)[reply]
Template:U, Ah, I guess I'm talking about the later (i.e. the screenshot I posted above). Thursday, then. -- RoySmith (talk) 20:36, 9 February 2021 (UTC)[reply]
Twinkle fix now pushed; sorry all, had planned to put it up later today but didn't realize it was gonna come early this week. ~ Amory (utc) 18:46, 9 February 2021 (UTC)[reply]
Also heads up about [11]. Release Engineering (with good reason) will now halt the train if any new errors show up. This should mean fewer errors will make their way to English Wikipedia, but as a consequence we may see more erratic train schedules like this, where the new version arrives on Monday/Tuesday/etc. instead of the usual Thursday. MusikAnimal talk 19:01, 9 February 2021 (UTC)[reply]
Is there a way for us to get a notice here when the software is updated, perhaps with a link to release notes, or is there a page we can add to our watchlists to know about changes? The tech news that is posted here is forward-looking, so things listed there do not always happen on time, and the link to the new version always leads to a blank page when the news posting is added here. – Jonesey95 (talk) 20:37, 9 February 2021 (UTC)[reply]
I think the ecosystem is too big to have a fully comprehensive release notes for weekly trains. But anything notable should go through Tech News. Bugs like the broken hover states of dropdown menus are of course not announced in advance because they were not intentionally introduced.
As for when the train arrives, you can check toolforge:versions to see the current status, and wikitech:Deployments to see the current schedule. Whenever the train is delayed, an email is sent to the wikitech-l mailing list. You can also see if anything is currently blocking the train by checking toolforge:train-blockers. That redirects you to the corresponding Phab task for the upcoming train, and blockers there are listed as subtasks. At the time of writing there are no subtasks, so wmf.30 should hopefully come as planned on Thursday.
The recent policy change around deployments may actually improve the situation, as developers might get in the habit of reverting problematic changes, rather than holding up the train to fix them. Time will tell. MusikAnimal talk 21:21, 9 February 2021 (UTC)[reply]

Mildly irritating orange box[edit source]

Hi, this might have been answered before, but I cant find it.

Whenever I visit an XfD page, I get a popup orange box in the top right hand corner of my screen saying "XFDcloser is now a gadget! Please upgrade to the gadget version." The thing is, I *have* upgraded to the gadget version. The box goes away if I click on it, but it's still slightly annoying. Can I stop it from appearing? (Firefox 85.0, Win10) Black Kite (talk) 21:51, 9 February 2021 (UTC)[reply]

In User:Black Kite/vector.js, remove importScript('User:Mr.Z-man/closeAFD.js');. By the way, if you follow the link "upgrade to the gadget version", it should tell you to do this. — The Earwig ⟨talk⟩ 22:15, 9 February 2021 (UTC)[reply]
Doh! Of course, thank you - I only glanced at it and it mentions common.js first - forgetting I was using vector. Black Kite (talk) 22:18, 9 February 2021 (UTC)[reply]

There seems to be a problem with your login session...[edit source]

I had an interesting thing happen to me this evening. My main machine was down, so I dug out an old laptop and tried to use that. Trying to log in to wikipedia, I got, "There seems to be a problem with your login session; this action has been canceled as a precaution against session hijacking. Please resubmit the form. You may receive this message if you are blocking cookies".

To make a long story short, if you ever get that, take a look at what version browser you're running. If it's something ancient, try updating your browser :-)— Preceding unsigned comment added by RoySmith (talkcontribs) 23:59, 9 February 2021 (UTC)[reply]

I've seen this at least once in the last week or so. I'm using up-to-date software. davidwr/(talk)/(contribs) 00:12, 10 February 2021 (UTC)[reply]
I've seen this message when I've had the login page up but didn't login for a while; I've always assumed this corresponded to the login page timing out (one approach to mitigate the risk of a person-in-the-middle attack). If your old laptop had an old, cached version of the login page, then it would be a stale login session. isaacl (talk) 01:13, 10 February 2021 (UTC)[reply]
Template:U, I was able to login via an incognito window, but clearing the browser cache in the main browser window didn't help. I don't remember if I cleared my cookies or not, but it's unclear why updating to a newer version of chrome would make a difference if it was a stale cookie problem. -- RoySmith (talk) 17:45, 10 February 2021 (UTC)[reply]
I got that same message a couple of days ago, maybe at the same time. I am using the latest version of Firefox supplied with my Linux distribution. I retried a couple of times and got the same message but then left it for an hour or so and could log in perfectly well. It looks to me that this may be a timeout of some kind, caused by something running slowly on the client or server or network. Phil Bridger (talk) 09:48, 11 February 2021 (UTC)[reply]
I have been getting this message occasionally, for quite some time. More recently, see the discussion above on Logins bounced. — Cheers, Steelpillow (Talk) 09:54, 11 February 2021 (UTC)[reply]
This issue is a bit different, where an attempt to login fails, as opposed to already being logged in and then being logged out unexpectedly. isaacl (talk) 18:27, 11 February 2021 (UTC)[reply]
Superficially, yes. But I began experiencing them both within a fairly similar timescale and they are both login bounces. How strong does a coincidence need to get before it isn't one? I'd hate to be dogmatic either way. — Cheers, Steelpillow (Talk) 19:28, 11 February 2021 (UTC)[reply]
While anything is possible, logging in is a distinct function from maintaining a logged-in session. So I wouldn't a priori tie these two symptoms together. isaacl (talk) 20:07, 11 February 2021 (UTC)[reply]
Template:Replyto Once is happenstance, twice is coincidence, the third time it's enemy action. Ian Fleming, Goldfinger. --Redrose64 🌹 (talk) 20:38, 11 February 2021 (UTC)[reply]
I had both issues. I was logged out unexpectedly and then got the message described above when I tried to log back in. Phil Bridger (talk) 21:11, 11 February 2021 (UTC)[reply]

Need some technical help[edit source]

Template:Resolved Hey all, looking at this request from Template:U, they appear to have moved an article into Talk space, and yet the talk page has gone missing. Anyone have any ideas for where it could have gone and how to restore the pages to their original locations where they can be safely moved? Much appreciated. Cyphoidbomb (talk) 04:11, 10 February 2021 (UTC)[reply]

Template:U The issue has been resolved by Template:U. Thanks to both of you. Yashthepunisher (talk) 05:12, 10 February 2021 (UTC)[reply]

Political party color using nowiki[edit source]

I was inspecting the output produced by a module (not relevant here, but see "UNIQ--nowiki" at permalink if wanted). That output included strip markers from nowiki tags resulting from the module expanding color templates for political parties. For example:

Why is the nowiki used? If someone puts Template:Tlf on a page in normal wikitext, the nowiki stops # from being interpreted as a numbered list item. However it looks like these templates are being used in wikitext or HTML to generate a table. The resulting HTML gives a table cell like the following:

<td style="background-color:?'"`UNIQ--nowiki-00000001-QINU`"'?"></td>

which is transformed to

<td style="background-color:#DDDDDD"></td>

Are those nowiki really desirable? Johnuniq (talk) 04:34, 10 February 2021 (UTC)[reply]

On the template, and maybe in the transclusion (I don't remember exactly), those pound signs would otherwise be interpreted as an ordered list item. --Izno (talk) 04:53, 10 February 2021 (UTC)[reply]
I think I've mishandled some of the {{Election box metadata}} set-ups before in my time and the consequences have been a bit messy. I think something about the election results boxes - of which there are a smattering of different designs for FPTP, STV, AMS etc - goes wonky if the color section isn't bracketed by the nowiki tags. doktorb wordsdeeds 05:10, 10 February 2021 (UTC)[reply]

Last call for projects[edit source]

Wikimedia is applying as a mentoring organization for Google Summer of Code 2021 and Outreachy Round 22. We're currently gathering project ideas for the application. If you have ideas for projects, share them here: -- The Wikimedia GSoC & Outreachy Organization AdministratorsTemplate:Pb --qedk (t c) 15:01, 10 February 2021 (UTC)[reply]

Upon creating an article[edit source]

Template:Resolved When creating an article, is there any way to suppress or collapse or otherwise hide the box that says, "Before creating an article, please read Wikipedia:Your first article. We recommend that new editors ..." etc.? If there isn't, could a way to suppress that box be added to Preferences? Abductive (reasoning) 16:46, 10 February 2021 (UTC)[reply]

Template:Re you can add this line:
.mw-newarticletext {display: none}
To your Special:Mypage/common.css or Special:Mypage/skin.css file. — xaosflux Talk 16:59, 10 February 2021 (UTC)[reply]
Great, it works! Hidden. Thanks. Abductive (reasoning) 17:25, 10 February 2021 (UTC)[reply]

Maintenance categories[edit source]

Just noticed that Category:Astronomy templates is not hidden at Solar radio emission and is displayed alongside encyclopedic categories (more fresh eyes than mine are needed). Btw, could we run a bot that will detect all unhidden maintenance categories and hide them? Brandmeistertalk 20:56, 10 February 2021 (UTC)[reply]

Template:U, this was caused by incorrect categorization wikitext at Template:The Sun and has been fixed. —⁠andrybak (talk) 21:42, 10 February 2021 (UTC)[reply]
Thanks, I thought it had to do with the category itself. Brandmeistertalk 21:51, 10 February 2021 (UTC)[reply]
Template:Replyto Template:Diff - the category was placed outside the Template:Tag when it should have been inside, ideally placed in the documentation page (see WP:CAT#T). Template:Cl is not a maintenance category, and there should be no reason to hide it - otherwise it wouldn't be shown at Template:The Sun, where its display is highly appropriate. --Redrose64 🌹 (talk) 14:19, 11 February 2021 (UTC)[reply]
Unhidden maintenance categories is a very rare problem in my experience and not something we really need a bot for. A more common problem is that the category doesn't exist and shows up red which looks worse. I have thought about making a Phabricator request for a MediaWiki message with regex for category names which should be treated as hidden categories if they don't exist. A feature similar to MediaWiki:Spam-blacklist. The numerous template-added maintenance categories with names like Category:Articles with dead external links from April 2020 would be easy to target with regex. Some wikis might choose to hide all red categories. The feature could also have a setting to automatically hide the category if it does exist. PrimeHunter (talk) 21:07, 11 February 2021 (UTC)[reply]

Reverted tag missing[edit source]


I cannot see the useful "reverted" tag in some contributions that were reverted. Examples of mw-reverted are in recent changes but what about these:

Am I missing something or is this hopefully a temporary glitch? Johnuniq (talk) 03:06, 11 February 2021 (UTC))[reply]

Template:U, TIL tags are applied asynchronously. For example, when I first looked at Special:Contributions/Cheekyrascal, only the first two edits had the Reverted tag. Now all three do. See meta:Help:Reverting#Reverted edits: Template:Tq -- RoySmith (talk) 03:47, 11 February 2021 (UTC)[reply]
That makes sense, thanks. I've never seen a lag before and would guess that something unusual is holding up the process. I hope it gets back to a fast response because the point of the tag is to see which edits need to be checked/reverted on encountering a problematic editor. Johnuniq (talk) 04:06, 11 February 2021 (UTC)[reply]

Uploads disabled vs. Permission error[edit source]

I have come across both versions of messages attempting to upload files on other wikis. The first one says “Permission error” and then says “The action you have requested is limited to users in the group: Administrators.” See wikt:Special:Upload. The first one isn’t quite hard to understand. However, the second title says “Uploads disabled.” Then it says “Local file uploads are disabled. Please upload to Wikimedia Commons.” See d:Special:Upload. I have a question about the second message: Does the second message mean that not even administrators can upload images on that wiki? If so, then who can upload? I always thought that administrators could do “everything” on the wiki; by everything I don’t mean literally everything, but something like uploading images should be available to sysops or at least someone on every wiki. 54nd60x (talk) 04:58, 11 February 2021 (UTC)[reply]

Regular admins can do many things, but not everything. The system administrators can disable features directly in the software so that no one can perform them. That is what you're seeing in the "Uploads disabled" case: that's what happens when $wgEnableUploads is set to false in MediaWiki. Wikidata doesn't need any locally hosted files, so it's disabled there. — The Earwig ⟨talk⟩ 05:25, 11 February 2021 (UTC)[reply]

Wikidata notices[edit source]

Is there any way to turn off the endless stream of Wikidata notices? It's rendered my "inbox" useless. Maury Markowitz (talk) 12:03, 11 February 2021 (UTC)[reply]

By "inbox" do you mean e-mail, onwiki notifications or watchlist? There are settings at Special:Preferences#mw-prefsection-echo, Special:Preferences#mw-prefsection-watchlist, wikidata:Special:Preferences#mw-prefsection-echo. PrimeHunter (talk) 14:01, 11 February 2021 (UTC)[reply]
It is an icon of an inbox. Actual messages to me show up in the bell icon. Thanks for the pointer, I did find the (hopefully correct) option. It is very odd that it is on another web site. Maury Markowitz (talk) 14:49, 11 February 2021 (UTC)[reply]
This is a consequence of how the various WMF sites interact. At one level, every wiki (the various language wikipedias, wikidata, commons, etc) is a seperate site, with its own set of preferences. For example, I might want to be notified when somebody links to a page I've created on enwiki, but not on wikidata. On the other hand, all (well, most) of these projects share a common authentication system, so you don't have to create a new account on each site. One of the things that gives you is that notifications generated on any of the sites are visible on all the others via your inbox. It's actually a very handy feature, but I can see how it could be surprising and/or confusing. -- RoySmith (talk) 15:52, 11 February 2021 (UTC)[reply]

Minor rendition problem[edit source]

I know this is incredibly minor but it's bugging me. Take a look at Arithmetic mean, in the example as part of the definition. The first, fourth and 7th plus (+) signs not properly formed. my initial thought was that it was an artifact of my monitor or some temporary rendition problem, I believe it persists, and I can reproduce it in other browsers.

I created:

Note that the problem does not exist an example 2 but does an example 1 and example 3.

I think that suggests that it has something to do with the header, But I can't think why that would be.--S Philbrick(Talk) 16:17, 11 February 2021 (UTC)[reply]

Template:Ping didn't actually describe what problem you are having, but given how you managed to talk around it, I believe you're suffering from this issue. --Izno (talk) 16:33, 11 February 2021 (UTC)[reply]
Template:U, I don't think so, though I can't really exclude that as a possibility. It isn't that the + is missing, it's that simple pixel's are missing and it's not a crisp pair of lines. would be interested to know whether any others see exactly what I see. when I look at example 2, the plus signs are crisp and well-formed, but in examples one and three, the + doesn't look quite right. I just tried an experiment changing the font size. If I increase or decrease the font everything looks fine; the only issue is that the default size. S Philbrick(Talk) 17:42, 11 February 2021 (UTC)[reply]
Template:U, if you aren't seeing it I can create a screen shot. S Philbrick(Talk) 17:42, 11 February 2021 (UTC)[reply]
Indeed, I am not seeing it. Some other things for you to add: What skin, what browser(s), what operating system, and what is your math display setting at the bottom of Special:Preferences#mw-prefsection-rendering? --Izno (talk) 18:30, 11 February 2021 (UTC)[reply]
I'm seeing it as well. Curiously, on the article page, it's the 1st, 4th, and 7th plus signs, but if I open the image in a new tab, it's the 2nd, 4th, and 6th signs. I'm using Vector on Chrome 88.0.4324.150, and math display is set to "MathML with SVG or PNG fallback". Here are some screenshots.
In the article
In a new tab
--rchard2scout (talk) 07:07, 12 February 2021 (UTC)[reply]
Template:U, thanks for the screenshots, procrastination bails me out yet again:) S Philbrick(Talk) 12:58, 12 February 2021 (UTC)[reply]

New articles from specific category[edit source]

How I can see new articles from Category:Bilateral relations by country and its subcategorieres? Eurohunter (talk) 16:21, 11 February 2021 (UTC)[reply]

Template:Re you can use the PetScan tool. Here is an example set of parameters: PetScan query. — xaosflux Talk 16:49, 11 February 2021 (UTC)[reply]
Template:Re Thanks Eurohunter (talk) 17:35, 11 February 2021 (UTC)[reply]

User default sandbox[edit source]

Why default user sandbox isn't capitalised as any other namespace? So we should have User:Example/Sandbox instead User:Example/sandbox. Eurohunter (talk) 18:01, 11 February 2021 (UTC)[reply]

If you mean the 'Sandbox' link in the user menu bar at the top, it actually leads to 'user:example/sandbox'. Ruslik_Zero 20:11, 11 February 2021 (UTC)[reply]
The namespace is the part before the colon, in this case "User". The first character after the namespace is automatically capitalized, in this case "E". The default /sandbox is a user subpage. Subpages are fully case sensitive like any other part of a page name after the first character. I don't know how the case was chosen but all skin subpages are also lowercase: /common.js, /common.css, vector.js, vector.css (and the skin name is Vector), /monobook.js, monobook.css (skin name MonoBook), and so on. PrimeHunter (talk) 20:18, 11 February 2021 (UTC)[reply]

resizing parts of an Infobox in mobile view[edit source]


am doing this comparison from Chrome (mobile). please toggle the width entries, in above code, to see if you can change sizes of parts of the Infobox, in both desktop and mobile views. the only width entry seems to be functioning for me (in desktop view) is "bodystyle" and "titlestyle". I cannot change headerstyle, labelstyle, or datastyle widths in desktop. and none of width entries seem to have any effect in mobile view. please check for errors in above code. is this expected behaviour ? or should it be reported, if so, where (or to whom) ? Gfigs (talk) 08:51, 12 February 2021 (UTC) Template:Infobox[reply]

Template:Ping A cell cannot be displayed with two different widths so there are dependencies: body width = header width = label width + data width. If you specify conflicting widths then they cannot all be satisfied. body width is 22em by default if you don't override it. The second infobox has body 4em, label 2em, data 2em. The data field is widened to fit the widest word "consectetur". Use Template:Tl if you want to permit word breaks to get a more narrow column. Don't make an article infobox this narrow. PrimeHunter (talk) 10:01, 12 February 2021 (UTC)[reply]
Template:U, hope, everything adds up on mobile.. Gfigs (talk) 12:28, 12 February 2021 (UTC)[reply]
Template:U, I'll also point out that these are not just tables, they are inboxes. Infoboxes have a whole set of custom CSS especially on mobile (on mobile we render them as a flex box grid). Also you probably should know about max-width and min-width for instance, which generally are better to be used if you want to set a certain limit, as opposed to a 'starting' position to calculate the width to be actually used. —TheDJ (talkcontribs) 14:55, 12 February 2021 (UTC)[reply]
Template:U, seems to be ok..just a few glitches in understanding here..Gfigs (talk) 16:53, 12 February 2021 (UTC)[reply]