Wikipedia:Village pump (technical)/Archive 175

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Contents

Pending changes

I would like to use this script when reviewing pending changes. However, when I see the pending changes, it only shows the diff, not the article with the changes implemented. Can an editor edit the my script so that it shows both the diff and article with the changes implemented? I don't know how to do it myself so I am asking for help. Interstellarity T 🌟 10:08, 21 June 2019 (UTC)

Not me, but DannyS712 can. Face-smile.svg --qedk (tc) 19:42, 21 June 2019 (UTC)
QEDK, Can you find someone else that can do it if DannyS712 can't do it? Interstellarity T 🌟 20:09, 24 June 2019 (UTC)
Interstellarity, Hi there i have fixed that issue. ___CAPTAIN MEDUSAtalk 13:14, 30 June 2019 (UTC)

Posting issues

I have just recently been having an issue: When I hit the preview button to check my edits then hit the publish button I get an edit conflict. When this first happened I treated it as such and it posted twice. After that I have reloaded and see it is already posted by only hitting the preview button. I have never had this issue, that was not a legitimate edit conflict, so am at a lose. Otr500 (talk) 16:09, 24 June 2019 (UTC)
Note: This has happened 4 times but when I previewed this edit then hit "publish changes" it worked fine. Otr500 (talk) 16:12, 24 June 2019 (UTC)
Apparently this is an issue only I am having but it is still ongoing. Otr500 (talk) 18:09, 28 June 2019 (UTC)
Wikipedia:Village_pump_(technical)#Incorrect_Edit_Conflicts related? Galobtter (pingó mió) 18:24, 28 June 2019 (UTC)
Very possible. Also whatever the issue is (I will have to look) it might be related to Wikipedia:Village pump (technical)#Block conflict that may just be another area where the edit conflict is occurring. Otr500 (talk) 12:19, 29 June 2019 (UTC)
I'm getting inexplicable edit conflicts today. Doug Weller talk 19:55, 30 June 2019 (UTC)
And again when I tried to post the above. Doug Weller talk 19:56, 30 June 2019 (UTC)
Again! Is it groundhog day? When this happens again I own't bother to mention it here. Doug Weller talk 19:57, 30 June 2019 (UTC)

Searching for old vandalization in a file

I'd like to know if there is any bot or tool that can help me finding old vandalizing editions in a WP file history. Thanks. --Jotamar (talk) 23:56, 19 June 2019 (UTC)

When I said WP files, I meant WP pages. Can someone at least tell me, where should I ask my question? --Jotamar (talk) 19:01, 26 June 2019 (UTC)
Yes, Jotamar, probably WP:BOTREQ, how many edits are you looking for? There will be many millions. Fist step might be to look for edits preceding those with an edit summary of "rvv". Another good place to look is the edits prior to User:ClueBot's edits.
All the best: Rich Farmbrough, 10:49, 28 June 2019 (UTC).
If you already know specific vandalized text in an article and want the edit which added it then click "Find addition/removal" at the top of the page history. It used WikiBlame until recently but the tool has problems and another is currently used. It's discussed at MediaWiki talk:Histlegend#Wikiblame replacement. PrimeHunter (talk) 11:09, 28 June 2019 (UTC)
What I have in mind is some sort of heuristic tool, capable of finding a short list of possible vandalazing editions that have not been reverted, in a group of pages, for instance, the pages under one category. In less popular, poorly maintained pages, it's not uncommon that such an edition can be easily reverted even after months or years, but first you have to find them, and that takes up a lot of time. --Jotamar (talk) 13:48, 1 July 2019 (UTC)

RefList falling in the wrong place

I need help getting a reflist to fall at the bottom of the article. It is falling between 2 tables. [[1]]

I would like to understand why this happening so I can fix it myself in the future.

Thank you. Lore E. Mariano (talk) 14:02, 1 July 2019 (UTC)

Fixed by [2]. PrimeHunter (talk) 14:10, 1 July 2019 (UTC)
Thank you so much! Lore E. Mariano (talk) 14:40, 1 July 2019 (UTC)

Cite error created by bot.

Apparently there is a new bot creating cite errors. Article: WZ-551 Tag: Rescuing 14 sources and tagging 0 as dead. #IABot (v2.0beta15)

Is there a review process for new bots/tools? I have encountered many repeated errors that I assume are created by them. e.g. "coauthors=", "DUPLICATE_date". User-duck (talk) 17:39, 1 July 2019 (UTC)

Communication failure between the bot owner and the community at WT:CS1. I fixed the WZ-551 page that Gog the Mild edited and will leave it to that editor to similarly repair any other error caused by the tool.
Trappist the monk (talk) 17:56, 1 July 2019 (UTC)
This is IABot via Oauth request by Gog the Mild. It was due to some miscommunications, my fault, iabot has been patched/rebooted and will look into fixing the errors added onwiki. -- GreenC 19:36, 1 July 2019 (UTC)
Edit conflict. I had just written:
Thank you Trappist the monk. That would have been from me clicking "Fix dead links" on the "Revision history" page and not checking the result thoroughly enough. I shall recheck my other recent clicks of that button.
GreenC, do I need to do anything, other than recheck previous uses of "Fix dead links", and/or cease using it? Thanks Gog the Mild (talk) 19:44, 1 July 2019 (UTC)
You are good, it's ok now. Looks like the bug lasted 3hrs and somewhere between 100-200 articles. I might script a quick fix or request something at AWB request wouldn't worry about manually repairing. -- GreenC 19:48, 1 July 2019 (UTC)

Tech News: 2019-27

21:22, 1 July 2019 (UTC)


Question re: new translations of articles linked out to other languages

Progression of events was:

  1. Editor created a link to de:Otto Kirn (in article Pandeism, correcting from wrong link to Otto Kern).
  2. Translated Otto Kirn added here.
  3. Wikidata updated for articles now in two languages.
  4. Tagged as an orphan here.

Question: Why doesn’t English addition to Wikidata automatically prompt changing of links previously made to point other languages? Hyperbolick (talk) 19:49, 1 July 2019 (UTC)

The edit said [[:de:Otto Kirn]]. This explicitly tells to link the German Wikipedia. {{Interlanguage link|Otto Kirn|de}}} could have been used instead to test for an English article called Otto Kirn. It would only have examined whether the page name exists and not whether it's in a Wikidata item. As far as I know we have no template for the latter. It is possible to pull information from Wikidata so maybe it could be added as a feature in {{Interlanguage link}}. I don't think it's possible for an English template to look up the Wikidata item for a German article so Q24529752 would probably have to be a parameter. A bot could be coded to automaticlly add the parameter when it's not supplied. PrimeHunter (talk) 21:12, 1 July 2019 (UTC)
Could a bot check whenever a Wikidata item is connected from here? Got a notification here when it was, so somebody’s telling this Wiki. Hyperbolick (talk) 21:41, 1 July 2019 (UTC)

Database issue

Could someone knowledgable comment here, centrally, on whether there are database issues beyond the apparently temporary ones outlined in the above Tech News, and if so, what are their extent and when do we think they will be resolved? It appears multiple bots have for some time not been running DB intensive tasks (such as certain Wikipedia:Database reports), and it is very difficult to parse through all the bot/report talkpage chatter to get a true picture of what is actually going on. Thanks in advance! UnitedStatesian (talk) 02:46, 2 July 2019 (UTC)

The database replicas are undergoing maintenance (see T222978). This involves taking one replica host out of service at a time. The other two hosts then have increased load, which leads to replication lag and increased query time (previously long queries could fail to complete). Maintenance is usually ongoing during the week and paused over the weekends. I would expect this to be an ongoing issue for a while. I don't know how long the maintenance will take, but the DBAs are reaching the end of the maintenance one the first replica. The database items in the Tech News are unrelated. — JJMC89(T·C) 05:29, 2 July 2019 (UTC)

Question, watchlist listing error & problem

Dear All,

initially I turned to administrator regarding the issue, but unfortunetly he could not give an idea for solution. The details may be read there...Shortly, if I set it to list the changes back to 7 or 30 days, it is not working, just listing the last 250 changes, not more and I have as well no (previous/next) buttons...I need a solution, Thank You(KIENGIR (talk) 20:21, 1 July 2019 (UTC))

@KIENGIR: This is Wikipedia:Village pump (technical)/Archive 174#did something break watchlist and make it too short again?. --Redrose64 🌹 (talk) 20:36, 1 July 2019 (UTC)
@Redrose64:,
Thank you it helped, I applied similar tweaks descibred there (in the detailed settings changing to 30 days and enabling 1000 entries as maximum). though, still I don't have 30 days, I assume mainly because of the 1000 entry limitation (I don't know where would be the url to tweak it higher). Thus practically I could go back two weeks, so my initial problem has been solved (going back between 4-7 days)...maybe as an important note for the others or the developers, even this worked only by unchecking the "Expand watchlist to show all changes, not just the most recent" in the Advanced Options...(initially at the first tweak attempt, I automatically checked this box assuming it is essential, but anything written above did not work until it was unchecked, ironically it had a contraproductive effect despite it's name...(KIENGIR (talk) 10:39, 2 July 2019 (UTC))

Issues with alerts, June 2019

Missing notification icons in MonoBook

I just spent ten minutes trying to figure out what was wrong on my end. If you're doing the same, it's not just you. See phab:T226503. Suffusion of Yellow (talk) 19:52, 25 June 2019 (UTC)

I'm getting it in MonoBook too. The appropriate CSS rules are present in the stylesheets:
.oo-ui-icon-bell, .mw-ui-icon-bell:before {
    background-image: url(/w/load.php?modules=oojs-ui.styles.icons-alerts&image=bell&format=rasterized&lang=en&skin=monobook);
    background-image: linear-gradient(transparent,transparent),url("data:image/svg+xml,%3Csvg xmlns=%22http://www.w3.org/2000/svg%22 width=%2220%22 height=%2220%22 viewBox=%220 0 20 20%22%3E%3Ctitle%3Ebell%3C/title%3E%3Cpath d=%22M16 7a5.38 5.38 0 0 0-4.46-4.85C11.6 1.46 11.53 0 10 0S8.4 1.46 8.46 2.15A5.38 5.38 0 0 0 4 7v6l-2 2v1h16v-1l-2-2zm-6 13a3 3 0 0 0 3-3H7a3 3 0 0 0 3 3z%22/%3E%3C/svg%3E");
}
.oo-ui-icon-tray, .mw-ui-icon-tray:before {
    background-image: url(/w/load.php?modules=oojs-ui.styles.icons-alerts&image=tray&format=rasterized&lang=en&skin=monobook);
    background-image: linear-gradient(transparent,transparent),url("data:image/svg+xml,%3Csvg xmlns=%22http://www.w3.org/2000/svg%22 width=%2220%22 height=%2220%22 viewBox=%220 0 20 20%22%3E%3Ctitle%3Etray%3C/title%3E%3Cpath d=%22M3 1a2 2 0 0 0-2 2v14a2 2 0 0 0 2 2h14a2 2 0 0 0 2-2V3a2 2 0 0 0-2-2zm14 12h-4l-1 2H8l-1-2H3V3h14z%22/%3E%3C/svg%3E");
}
Switching to Vector displays them properly, even though the CSS rules are virtually identical - the only differences are that the word "monobook" becomes "vector" in the first and third url(...) value. --Redrose64 🌹 (talk) 20:21, 25 June 2019 (UTC)
Um, did the fix also give a ton of scroll-space to the right of anyone else's window? I can now scroll for a very long time to the right, despite there being no content. Killiondude (talk) 23:42, 25 June 2019 (UTC)
@Killiondude: Yes, I see the same thing. (Firefox 67, Linux) Suffusion of Yellow (talk) 23:45, 25 June 2019 (UTC)
Ditto here, IE 11 in Windows. They were missing for a while, but now they've reappeared. I think they're blurrier than before, however. Could someone ping me and thank me for this edit, so I can see whether the number notifications look any different. Nyttend (talk) 23:53, 25 June 2019 (UTC)
@Nyttend: (ping) Suffusion of Yellow (talk) 00:06, 26 June 2019 (UTC)
Thank you. Things are somewhat different; the numbers looked normal, but when I clicked each one, it was momentarily surrounded by a little dark box. The same is true if I want to review past notifications and click either of the icons when I have nothing new. Nyttend (talk) 10:51, 26 June 2019 (UTC)
@Nyttend: You might be right about the extra blurriness, I'm not sure (I took some screenshots a few years ago: c:File:Vpt redrose64 alerts.PNG, c:File:Vpt redrose64 alerts2.PNG, c:File:Vpt redrose64 alerts3.PNG back when the car door was still in place, now replaced by the TV set icon). You're certainly right about the little dark box, it's blue and there are two for each icon, one enclosing the number and the other enclosing the icon.
@Killiondude: The super-wide scroll space was present for me on all pages until about an hour ago, it's now stopped appearing. --Redrose64 🌹 (talk) 13:06, 26 June 2019 (UTC)
You guys aren't getting the icons? I'm getting only the icons — not the actual pings. On the upside, I get all thanks twice. See below. (Using Monobook.) Bishonen | talk 21:38, 27 June 2019 (UTC).
@Bishonen: That's because this problem was fixed and the "fix" caused another problem. Try putting my "fix"-to-the-fix from the other thread in your monobook.css, and see if the links work as expected. Suffusion of Yellow (talk) 21:48, 27 June 2019 (UTC)
I'm sorry, Suffusion of Yellow, I don't see a fix-to-the fix in the other thread (you mean "Someone has broken Thanks", right?), and altogether, you're speaking a foreign language. Could you tell me what to do as if explaining to your mother? Bishonen | talk 21:59, 27 June 2019 (UTC).
@Bishonen: Sorry, there are too many threads about this right now. Try adding:
#pt-notifications-notice .mw-echo-notifications-badge, #pt-notifications-alert .mw-echo-notifications-badge {
	text-align: left;
}
to your monobook.css. Works for me, at least. Suffusion of Yellow (talk) 22:07, 27 June 2019 (UTC)
And it worked for me. Thank you very much, Suffusion of Yellow.
Re-pinging Suffusion of Yellow. Bishonen | talk 08:10, 28 June 2019 (UTC).
Suffusion of Yellow, I've just realized that my problem persists on Meta. Somebody pinged me, to test, and all I got was a three-year-old thanks. Can I put your magic code somewhere to fix that? (And hopefully Commons, Swedish Wikipedia, etc etc — I assume it's everywhere.) Bishonen | talk 19:30, 29 June 2019 (UTC).
@Bishonen: the problem on meta-wiki, (and most all other projects) should get cleaned up with the next release train. If it doesn't I'll put the hack on meta-wiki. If you need it urgently, you can hack your own monobook.css there (or just click a bit further to the left). — xaosflux Talk 19:38, 29 June 2019 (UTC)
@Bishonen: You can also put the same code in your meta:Special:MyPage/global.css. In theory this could cause display problems if you view some wikis in non-monobook skins, but I just tried in Vector and Timeless and I didn't see any problems. Suffusion of Yellow (talk) 19:42, 29 June 2019 (UTC)
@Bishonen: Wait, just realized that it's possible to have the fix only apply to monobook. Give me a few minutes to work it out. Suffusion of Yellow (talk) 19:45, 29 June 2019 (UTC)

@Bishonen: Ok, try putting:

.skin-monobook #pt-notifications-notice .mw-echo-notifications-badge, .skin-monobook #pt-notifications-alert .mw-echo-notifications-badge {
	text-align: left;
}

in your meta:Special:MyPage/global.css. Suffusion of Yellow (talk) 19:54, 29 June 2019 (UTC)

Suffusion of Yellow, now you're talking my language. It seems to work. Thank you. Bishonen | talk 20:20, 29 June 2019 (UTC).

Excessive width on monobook

So if you are using monobook, you may now constantly think there is something off the page to the right. See phab:T226597 for the report. Apparently this is a hack that the dev's put in to work around the notifications mess above. — xaosflux Talk 03:14, 26 June 2019 (UTC)

Merged to phab:T226594. — xaosflux Talk 03:41, 26 June 2019 (UTC)
Thank you. Just noticed this, and thought it was a broken ref spilling across the page I was on! Lugnuts Fire Walk with Me 06:54, 26 June 2019 (UTC)
Jeez. Hadn't noticed. Can't unsee now. Here's a temporary fix. —RainFall 07:13, 26 June 2019 (UTC)
#pt-notifications-notice .mw-echo-notifications-badge, #pt-notifications-alert .mw-echo-notifications-badge {
	text-indent: 0px !important;
}
Yesterday, when I responded to the thread above ("please ping and thank me"), I looked for this and it wasn't the case, but now it is. Nyttend (talk) 10:53, 26 June 2019 (UTC)
  • I've added RainFall's fix temporarily to MediaWiki:Monobook.css after testing locally, revert if any new issues are caused (I tested with both notification types as well). — xaosflux Talk 11:58, 26 June 2019 (UTC)
Does the temporary fix actually work? I've still got the excessive width. DuncanHill (talk) 12:00, 26 June 2019 (UTC)
@DuncanHill: it took a min to update the central css, try force refreshing a page. — xaosflux Talk 12:01, 26 June 2019 (UTC)
@Xaosflux: Now working, thank you. DuncanHill (talk) 12:05, 26 June 2019 (UTC)
@Xaosflux: Now, when I click on the "talk" link to the right of the notifications, I get the Special:Notifications popup instead. It looks like the screen-reader text, hidden by color:transparent, is overlapping with the talk link. Suffusion of Yellow (talk) 21:24, 26 June 2019 (UTC)
@Suffusion of Yellow, DuncanHill, Nyttend, Lugnuts, and RainFall: OK, I reverted the .css in monobook.css, give it a few and see if it fixes that problem (resulting in the original problem) - seems like I'm having to argue with the dev team to get them to understand that the change they made is making the final page worse than before :( — xaosflux Talk 21:37, 26 June 2019 (UTC)
OK Talk is back, but so is super-wide-mode :( — xaosflux Talk 21:38, 26 June 2019 (UTC)
@Xaosflux: Argue with the The Knights Who Say "OOUI!"? Good luck! Suffusion of Yellow (talk) 21:52, 26 June 2019 (UTC)
I'd like to laugh, but it's so annoying that breaking changes are just rolled out. If WMF want's to deprecate monobook they need to just say it - else stop breaking it.... — xaosflux Talk 22:31, 26 June 2019 (UTC)
"Quick - we need a distraction from Framgate, BREAK THINGS!" DuncanHill (talk) 22:32, 26 June 2019 (UTC)
please please please, don't feed to conspiracy theorists ... — xaosflux Talk 22:41, 26 June 2019 (UTC)
deprecate monobook: WP:BEANS! Suffusion of Yellow (talk) 22:33, 26 June 2019 (UTC)
"Deprecate" would be too strong a word, but the end of official support for MonoBook was announced about half a dozen years ago.[7] Whatamidoing (WMF) (talk) 06:31, 27 June 2019 (UTC)
I suppose I can put that code in my own css file, but I'd prefer that talk page link not to work over the wide screen space. I use trackpad shortcuts to move backward and forward through browser tab history a lot on Wikipedia. Having all the space to the right pretty much disallows moving forward in the history via that shortcut. Killiondude (talk) 22:35, 26 June 2019 (UTC)
If someone can come up with another hack for it that doesn't break things I'll happily force it back out there. — xaosflux Talk 22:42, 26 June 2019 (UTC)
If somehow this breaks the fundraising banner Seddon (WMF) is working on I bet it will get immediate attention...ijs... — xaosflux Talk 22:43, 26 June 2019 (UTC)
For any of my over-the-top complaining on this, some of it is frustration - but I really would like to thank Catrope for their continuing efforts to resolve this. Last update, the width problem is fixed, but now there is an alignment issue with the areas to click (you have to click a little further to the left then you used to right now) - this is already reported to phab. — xaosflux Talk 03:46, 27 June 2019 (UTC)
Ah, I was wondering about that. I was trying to get to my userpage from the link at the top, and kept getting info about notifications... Risker (talk) 04:16, 27 June 2019 (UTC)
Related xkcd. The initial "fix" that caused this seems to be very problematic. Can we not revert back and make a proper, tested patch instead of applying these small hacks repeatedly? —RainFall 05:15, 27 June 2019 (UTC)
Hi all. I don't know if this is related, but I can't click on the link to my talkpage from the very top bar, it always goes to my notifications. This is in Firefox. Lugnuts Fire Walk with Me 06:29, 27 June 2019 (UTC)
@Lugnuts: the 'talk link' problem should be fixed now (at least in monobook). If you are still seeing it in monobook can you gather some more details: hover over "log out" and look at what the link would be, then slowly move your mouse to the left (over contribus/wl/pref/ etc..) and see if you get sandbox, then your talk link. If it is out of alignment let us know? The link to the "user page" is somewhat overlapping with notifications (See above) but should work if you approach it from its left edge. — xaosflux Talk 14:27, 27 June 2019 (UTC)
Thanks Xaosflux, that seems to be OK now. Lugnuts Fire Walk with Me 14:29, 27 June 2019 (UTC)
I've just noticed that "Notices" now fills up most of the space between "DuncanHill" and "Talk", and "Alerts" partially overlaps "DuncanHill". I don't generally notice them unless I actually have an alert or a notice, as I use the blackscreen gadget and the words "Notices" and "Alerts" helpfully display in black text on a black background. Since these recent changes they have started shewing up in orange (like the other links at the top) but only when I point my mouse at them. DuncanHill (talk) 15:08, 27 June 2019 (UTC)
@Xaosflux: This fixes all the overlap issues for me, in FF67/Linux:
#pt-notifications-notice .mw-echo-notifications-badge, #pt-notifications-alert .mw-echo-notifications-badge {
	text-align: left;
}
I don't know why; I was just trying things at random. Might be worth trying in some other browsers. Suffusion of Yellow (talk) 21:33, 27 June 2019 (UTC)
This code fixes all the things for me. :) Before inserting this, I couldn't access "alerts" (the bell) only "notifications" (the inbox icon). Killiondude (talk) 22:00, 27 June 2019 (UTC)
I noted it at phab:T226594 to see if there will be an upstream fix before we start band-aiding again. — xaosflux Talk 22:18, 27 June 2019 (UTC)
@Suffusion of Yellow: That stops the overlap, but the text stays black when I point at it. Could someone thank and/or/ping me so I can see what it looks like then? Thanks, DuncanHill (talk) 22:24, 27 June 2019 (UTC)
User:DuncanHill, you annoy.---Sluzzelin talk 22:26, 27 June 2019 (UTC)
Thanks both, thanks and pings seem to shew up well and be clickable. Someday I'll get around to mentioning the incompatibility with the blackscreen gadget. I have to highlight the notification to read who it's from. But that's been like that for ever. DuncanHill (talk) 22:28, 27 June 2019 (UTC)
@DuncanHill: Ideally, that should go in Special:MyPage/monobook.css instead of Special:MyPage/common.css, not I think it will make a big difference. Suffusion of Yellow (talk) 22:34, 27 June 2019 (UTC)
Thanks again, have moved it over. Seems to be much the same effect. DuncanHill (talk) 22:40, 27 June 2019 (UTC)

Message & notification icons in Modern skin

Modern skin icons.jpg

The message & notification icons in the modern skin seem to have been changed to something less than ideal. Any recent changes to the stylesheet that would have made this happen? FWIW browser is latest version of Firefox (67.0.4). Nthep (talk) 14:52, 27 June 2019 (UTC)

@Nthep: - so in summary - there is a bunch going on and this is coming from upstream not local styles. See phab:T226684 (and some of the discussion at phab:T226594) to catch up on the goings-on. — xaosflux Talk 14:57, 27 June 2019 (UTC)
Thanks. Nthep (talk) 15:10, 27 June 2019 (UTC)
@Nthep: Same as the monobook issues, should be fully fixed at the end of the week/next week depending on how they're doing deployments. Unless you don't like how we fixed it once it does change, in which case do please tell me. -— Isarra 15:55, 1 July 2019 (UTC)

Someone has broken Thanks

Now when I thank someone, instead of it happening all in the history page, it takes me to another page to ask me if I want to thank them, then to yet another page saying I have thanked them, and leaves me there and not where I was to start with and with no apparent way back. I expect it's an "improvement", but it makes life harder. DuncanHill (talk) 20:53, 27 June 2019 (UTC)

@DuncanHill: Works normally for me. What you are describing is the expected behavior if you have JavaScript disabled. It is possible that the JS for the "thanks" feature didn't load properly. Try WP:BYPASS, and see if it works again. Suffusion of Yellow (talk) 20:58, 27 June 2019 (UTC)
 Works for me - but the servers were just also having some hiccups, can you try again? — xaosflux Talk 20:59, 27 June 2019 (UTC)
I've been having intermittent weirdness of another type. On "Show preview", I've been getting a message that the servers are busy. If I refresh, it works fine. But the error has repeated numerous times today. I've been wondering if it's the new version of MediaWiki that Tech News mentioned would be on all wikis as of today. — Maile (talk) 21:00, 27 June 2019 (UTC)
(ec)I went back and in the page history it did not shew me as having thanked the person I had thanked. I tried again, nothing happened, then tried again and it behaved normally. I think there's a log somewhere where I can see if it went through, but can't remember where. DuncanHill (talk) 21:03, 27 June 2019 (UTC)
Hah! I found the thanks log, it's shewing me as having made the first thanks before I posted here, but not the second when I tried again. DuncanHill (talk) 21:06, 27 June 2019 (UTC)
This is not about thanks (I think), but I got first one, then two notifications today for apparently nothing. I mean, there's a little red "2" in the usual place, but when I look there's nothing new there. I think the second one may have been for AGK's mention of me here, since it turned up right as I was reading his motion, but I've no idea what the first one is. Anybody know what's going on? If an arb offers a motion to examine my conduct, and has as far as he knows pinged me about it, it would be nice to get that ping. Can I go somewhere to find it? Bishonen | talk 21:20, 27 June 2019 (UTC).
There's a Thanks log at this link. I don't think there's a ping log. People shouldn't rely on pings as 1) they don't always work at the best of times, 2) it's very rarely the best of times, and 3) I think you can turn notifications off. DuncanHill (talk) 21:26, 27 June 2019 (UTC)
There was a recent problem with notification (at least in Monobook) see here (look above), but I don't know whether there's a connection. I will henceforth thank and revert and ping users profusely and see how they react. ---Sluzzelin talk 21:27, 27 June 2019 (UTC)
Duncan, you better stop thanking me, or I will report you to ... ---Sluzzelin talk 21:31, 27 June 2019 (UTC)
(edit conflict) (edit conflict) (edit conflict) I use Monobook, Sluzzelin, I'm old school. You know what? I just realized that the little notifications digit — the red one — shows the thanks I've got, just like the blue digit does. So, I get thanks twice, and notifications never. Bishonen | talk 21:32, 27 June 2019 (UTC).
You can get a complete list of current and past notifications at Special:Notifications (which, frustratingly, works much better with javascript disabled). Doesn't help you realize there's new ones there if the main notice is broken, though. —Cryptic 21:57, 27 June 2019 (UTC)
@Sluzzelin: Wilco! DuncanHill (talk) 21:34, 27 June 2019 (UTC)
Bishonen, this happened to me (also a Monobook user) when someone replied to me in a topic which was archived in the time between their reply and when I saw the notification. Ever since then, whenever I go to a wiki project for the first time, there's a red number for notifications, even when there are none (because the default preference is to show cross-wiki notifications). On the bright side, I can always tell if it's my first visit to a project. BlackcurrantTea (talk) 07:48, 28 June 2019 (UTC)
@BlackcurrantTea:, my problem was solved by a kindly techy type in a thread above. I don't know if the same magic would help you, but it's probably worth trying. Bishonen | talk 08:06, 28 June 2019 (UTC)
Bishonen, thanks for the tip. That doesn't make a difference in my case, but it's not really a problem. BlackcurrantTea (talk) 08:36, 28 June 2019 (UTC)

Stuck alert/notification

At the top of every Wikipedia page I open are my control tabs: Username, Alerts, Notifications, Talk, Sandbox, Preferences, Beta, Watchlist, Contributions, Log out.

There is a red number over my Alerts tab, and the tab isn't working. When I click on it, it shows all the Notifications, as does the Notifications tab.

I can't get rid of that red number. It has worked fine until today. Help! -- BullRangifer (talk) 03:19, 28 June 2019 (UTC)

@BullRangifer: do you use Monobook for your skin? If so, see #Excessive width on monobook and specifically the last bit of code given that you can put into your css file to fix what the devs broke in the skin. Killiondude (talk) 03:23, 28 June 2019 (UTC)
Still a problem. -- BullRangifer (talk) 06:53, 28 June 2019 (UTC)
@BullRangifer: The problem is that although the bell and TV set icons are still links, their hotspots have shifted to the left by about their own width plus a bit more. So the TV set's hotspot is now where the bell is displayed. Therefore, to activate the bell, you click a little to its left - just over the letters "fer" should do it. --Redrose64 🌹 (talk) 11:05, 28 June 2019 (UTC)
Several patches for this were worked on and hopefully it will be fixed very soon! — xaosflux Talk 11:07, 28 June 2019 (UTC)
@Redrose64:, you're right! That's exactly what's happened. When will this be fixed? -- BullRangifer (talk) 14:18, 28 June 2019 (UTC)
@BullRangifer: My "fix" (developed using the tried-and-true XKCD method) should work, but you need to put it in your monobook.css, not your monobook.js. Isarra has submitted a patch which should fix this on all wikis, but it hasn't been reviewed yet and I don't know how long it will take to be merged. Suffusion of Yellow (talk) 17:45, 28 June 2019 (UTC)
I don't have that subpage, but I'll create it and give it a try there. Thanks. -- BullRangifer (talk) 20:11, 28 June 2019 (UTC)
That worked instantly! -- BullRangifer (talk) 20:14, 28 June 2019 (UTC)
I've worked out why the hotspots are overwide and overlapping. Whilst looking at DuncanHill's (unrelated) Blackskin problem with that gadget enabled, I happened to hover over the alerts icons - and behold! the text links "Alerts (1)" or "Notices (1)" become visible. It is those textual items that are invisibly appearing in front of the desired links. So to get the bell's link, you need to be to the left of the "N" of "Notices (1)". --Redrose64 🌹 (talk) 19:12, 28 June 2019 (UTC)
It'll be actually fixed here by the end of the week, or next week. Probably. Patch is merged; this is just the last place to get fixes when people aren't wildly swatting everything like lemurs. Mmm, lemurs. -— Isarra 15:50, 1 July 2019 (UTC)
  • @Suffusion of Yellow: I'm trying your css hack at testwiki:MainPage, it should be live in a few mins - just as another stopgap until the phab ticket is resolved - feel free to go look for bugs there before it gets promoted locally here. — xaosflux Talk 20:19, 28 June 2019 (UTC)

I'm being over-notified.

Somebody rid me of those dang notifications, which won't go away. GoodDay (talk) 20:49, 28 June 2019 (UTC)

@GoodDay: Are you using the MonoBook skin? If so, please visit the test wiki, WP:BYPASS your cache, and see if everything works as expected over there. Suffusion of Yellow (talk) 21:08, 28 June 2019 (UTC)
I went to my All notifications & 'unread' them. It seems to have worked. GoodDay (talk) 22:05, 28 June 2019 (UTC)

Hack added to monobook.css

I'm adding Suffusion of Yellow's hack to MediaWiki:monobook.css for now - revert if it causes trouble. — xaosflux Talk 22:33, 28 June 2019 (UTC)

Working for me, at least. Suffusion of Yellow (talk) 22:46, 28 June 2019 (UTC)

Deployment update

Thanks to User:Isarra's efforts on Friday, we now have full fixes for the notification badge issues in the Monobook and Modern skins. About 15 minutes ago (at 23:36 UTC) I deployed the fixes for Monobook, these are now live on all wikis. I didn't deploy the fixes for Modern because those are a little more complicated and that skin isn't used as much as Monobook is. If I get a chance, I may be able to deploy those 24 hours from now, and otherwise they'll come with next week's regular weekly deployment train on Thursday July 11 (there is no train this week due to the July 4th holiday). Thanks to User:Isarra for writing proper fixes for these bugs, and to User:Xaosflux for putting interim fixes in MediaWiki:Monobook.css in the meantime. And, again, my apologies for this disruption; I was the reviewer on the change that broke this, and I should have caught the fact that it changed the badge structure and the main badge CSS but did not update the Monobook CSS to match. --Roan Kattouw (WMF) (talk) 00:02, 3 July 2019 (UTC)

"Show preview" toolbar needs to be above the edit summary in the wikitext editing window

Or there needs to be a setting in preferences to allow this. Scrolling is a pain. Half the page has to be scrolled to click the "show preview" button.

Weird thing is that the edit window here does not have the "Edit summary (Briefly describe your changes)" toolbar. It only has the "common edit summaries" toolbar.

So look at an article edit window, or an article talk page edit window. -- Timeshifter (talk) 08:34, 1 July 2019 (UTC)

If you begin editing by using the "new section" tab, then no, you don't get an edit summary window. Instead, a standard edit summary is constructed for you, consisting of the name of the new section wrapped in /* ... */ markers plus the words "new section". The edit summary window only appears when editing an existing section, or the whole page. --Redrose64 🌹 (talk) 16:25, 1 July 2019 (UTC)
Thanks, Redrose64. I see now. -- Timeshifter (talk) 08:42, 2 July 2019 (UTC)

Edit window length is not remembered

A related problem is that the wikitext edit window length is not remembered. I can drag it up or down in length. But when I open another article or talk page, and then open an edit window, it is back to being a very lengthy edit window.

This exacerbates the previous problem of the "Publish changes" toolbar being separated by almost half a page of edit summary and terms of use stuff.

Lots of scrolling to do multiple previews. I am using Firefox on a 21-inch LCD monitor. --Timeshifter (talk) 08:24, 1 July 2019 (UTC)

This in your CSS sets the edit box height:
textarea {height:15em}
User:Js/ajaxPreview#Installation adds a small preview button above the edit box. It makes other changes. PrimeHunter (talk) 09:59, 1 July 2019 (UTC)
Or you can use alt+shift+p to preview. Galobtter (pingó mió) 10:14, 1 July 2019 (UTC)
Thanks, PrimeHunter. I installed both, and they both work great. They both should be preferences. -- Timeshifter (talk) 08:38, 2 July 2019 (UTC)
@Timeshifter: It has previously been suggested (see e.g. this thread)) that a setting such as the above rule textarea {height:15em} should be made a user pref. Unfortunately, this is not feasible since a value of 15em is not suitable for every user - we do not know how high anybody else's screen is. --Redrose64 🌹 (talk) 18:30, 2 July 2019 (UTC)
@Redrose64: Thanks. I see from that old thread that it was possible in the past to choose the size of the textarea. I vaguely remember that this existed at one time. You wrote in that old thread: "Each pref removed marginally improves page load time for logged-in users." Is it only prefs that are changed from default settings that effect page load time? If so, then the more preferences the better.
There should be a way to open up and activate a whole new set of preferences. That way newbs could start with a manageable set of preferences. Then over time, if desired, then people could look at other preferences. Without having to paste stuff into CSS and JS pages. People could make their own decision as to whether the marginal loss of page load speed was made up for by the improvements provided by the additional preferences. -- Timeshifter (talk) 02:53, 3 July 2019 (UTC)

Problem with CSD category counts, again

I wrote a query regarding CSD category counts being incorrect and SoWhy helpfully pointed me to archived threads on this board, like Category count wrong and several others with the same complaint going back to spring 2018. Editors responded by listing Phab tickets, like T200402, T195397, T221795 or T18036 (and there are probably more). I've checked all the different tickets that were mentioned in these threads on this common problem and they are either marked as a) closed, resolved, b) closed, duplicate or c) low priority. I don't see how this issue can be considered resolved when it continues to be a problem and it is disappointing to think that there is little to no chance that anyone will work on actually solving this problem. It's clear that a lot of work on this started last year, but then the ticket was mistakenly closed as resolved.

Is there any way to restart the process of review so that there is some investigation of this problem? Because as a "resolved, low priority" task, that means to me that it will never be examined again. Liz Read! Talk! 23:35, 2 July 2019 (UTC)

In Phabricator parlance "low priority" does not necessarily means the task is not important; quite the opposite at times. Phab:T195397 was closed as resolved because it was indeed resolved at the time, and when the problem resurfaces, it was not reopened since there are many other open tasks. Some were closed as duplicate, because they were what the label says; even here, I believe we don't like 'duplicate.' The main task now is at phab:T221795.
However, (for me to not be too evasive) I admit the problem is not given any sense of urgency from the technical side, but that's easily explainable. To be frank, there's nothing broken if category count is not correct. The problem has been noticed since 2008 or possibly earlier, and with adhoc fixes, everyone moves on until it returns and annoys another person. It's something obscure and which almost entire Wikipedia readers probably don't use nor care about. The editors who care for it (the count) are few, and even fewer know the problem exists. I don't know any way to speed up this, except (may be) to lobby the team working on it in the task, but keeping in mind, even if you think it needs immediate solution, others may not see it that way. – Ammarpad (talk) 06:37, 3 July 2019 (UTC)

Remove fbclid=... from all links

Hi all,

I happened to notice that hundreds of links in hundreds of articles include fbclid=longstringofrandomlookingletters parameters. According to what I read, Facebook adds these to track users' browsing behavior. It works like this:

  • Let's assume I discover something on www.example.com/cooltopic.html and share this URL with a friend on Facebook: "HEY CHEK THIS OUT!!!!!!!11"
  • Facebook automatically adds a unique FaceBook CLick ID (fbclid) to every link that is passed through them by adding &fbclid=... or ?fbclid=... to it. This doesn't change the destination of the link i.e. the URL still works the same.
  • The friend decides to add my URL as a reference/link to Wikipedia. Except, now the URL will read www.example.com/cooltopic.html?fbclid=xyz123.
  • Thanks to their Click ID Facebook can now track the URL: If the link is emailed to a 3rd person, who sends it to a 4th via Whatsapp, Facebook recognizes the (modified) link as the one I originally shared with my friend, thus gathering data about which persons are communicating with whom.
  • If the destination site of the link (example.com) has added a like-button to their page then Facebook even gets notified whenever anyone follows the link, i.e. they will know exactly which visits to www.example.com are a consequence of my original communication with my friend. (They use this to find out who is a valuable influencer.)

Long story short, IMHO all fbclid=... should be deleted from all (current and future) references and links on Wikipedia, because

  • Facebook has no business tracking Wikipedia contributors or readers.
  • The huge fbclid=... strings make references harder to read and edit.
  • The fact that an Wikipedia article's reference's URL was passed through Facebook's infrastructure earlier is not relevant to the topic the article covers, so this information need not be preserved.
  • The links work just the same after deleting the fbclid parameter.

So it would be great if some Wikipedia wizard could program and unleash a bot for this? Please?? Supposedly there are also Google Click IDs and others, however I haven't found their 'additions' in links. Maybe there is already a bot in place filtering them out? Then this bot would just need a little expanding.

I hope this is the right place to ask. Someone at the Teahouse was kind enough to point me here.

Thanks and regards, Jens (84.173.225.148 (talk) 20:27, 30 June 2019 (UTC))

I believe there's a bot that's removing them already, though in a gradual way as there's no immediate harm while they're here. I think the bot is also removing them not only from Facebook's URLs but similar ones from Amazon.com and the like. – Ammarpad (talk) 20:35, 30 June 2019 (UTC)
Yup, Wikipedia:Bots/Requests for approval/KolbertBot 4 was approved for this, but may be stalled/paused right now. User:Jon Kolbert is the operator, who may have more information. — xaosflux Talk 20:39, 30 June 2019 (UTC)
Template:Cite web#URL says "Remove tracking parameters from URLs". insource:fbclid currently gives me 1720 results in articles. The normal place for a request would be Wikipedia:Bot requests. PrimeHunter (talk) 20:42, 30 June 2019 (UTC)
(edit conflict) Hi Jens, looks like User:KolbertBot per Wikipedia:Bots/Requests for approval/KolbertBot 4 should be removing it, but the bot isn't running; ping Jon Kolbert. Galobtter (pingó mió) 20:44, 30 June 2019 (UTC)

I'll talk to him. Many thanks to all of you. --Jens (84.173.225.148 (talk) 21:14, 30 June 2019 (UTC))

Jens, thank you for bringing this to our attention! While we wait for him, I have begun (slowly) manually removing a lot of these trackers, if anyone wants to help, please do! TheAwesomeHwyh 22:59, 30 June 2019 (UTC)
There are 1700 pages, many of which will have several affected links (the article where this issue came to my attention has 8 of them). While I admire your diligence, I do think it's best to let the bot handle this. Please consider that doing such tedious work manually is very error-prone, if you accidentally remove a bit too little or too much the link won't work any more. Best regards, Jens (84.173.225.148 (talk) 23:54, 30 June 2019 (UTC))
Ah- I'm not planning on doing them all, just however many I can get to today (also, I check all the links before I upload), but yeah this is definitely something that's best suited for a bot once that gets running again. TheAwesomeHwyh 00:07, 1 July 2019 (UTC)
Hi there, I have been very occupied with a lot of other things - but I will make sure this task runs :-). Thanks for the note Jon Kolbert (talk) 18:14, 2 July 2019 (UTC)
Many thanks for your work. --Jens (84.173.228.245 (talk) 21:11, 3 July 2019 (UTC))

Piped link with lang template

It is easy to see that | is a permissible character to the right of the active | in a piped link. For example, [[red|green|blue]] produces the anchor text "green|blue" linking to the page red: green|blue.

In the lead sentence of the page Xiquets Copenhagen, however, the wikitext ([[Castell|{{lang|ca|castells}}]]) is obviously intended to produce the anchor text "castells" linking to the page Castell; but actually it does not produce a link at all, and most of the wikitext shows up as ordinary text in the article. If this is supposed to work as intended, perhaps someone can fix the bug. If it's intended not to work, perhaps someone can edit the article to do what is necessary to achieve the desired effect.

(If you have something to say, please say it here. I only came across the article via Special:Random, and don't expect to look at it again.) --76.69.117.113 (talk) 04:06, 3 July 2019 (UTC)

Fixed The problem is that {{lang}} not only marks the text as non-English, it also adds [[Category:Articles containing ...-language text]] - and wikilinks may not contain wikilinks. -- John of Reading (talk) 06:23, 3 July 2019 (UTC)
Ah, so it's intended not to work. Perhaps it would be helpful if there was some kind of error message, because the original construction looks legitimate until you know why not. --76.69.117.113 (talk) 02:57, 4 July 2019 (UTC)

Why can't I enable the 2010 editing toolbar along with the 2006 editing toolbar?

I would like to have both toolbars. Please make this possible. See: Wikipedia:Legacy toolbar.

See: Special:Preferences#mw-prefsection-editing. There one can enable this:

  • Enable the editing toolbar. This is sometimes called the '2010 wikitext editor'.

I can't enable it because I have the 2006 editing toolbar (plus extensions) enabled:

I have the following 3 gadgets enabled in the editing section of gadget preferences:

  • Enable the legacy (2006) editing toolbar. This will be overridden by the "Enable the editing toolbar" option in the Editing tab.
  • refToolbar: add a "cite" button to the editing toolbar for quick addition of commonly used citation templates
  • Add extra buttons to the old (non-enhanced) editing toolbar

They just add more buttons to the 2006 editing toolbar. -- Timeshifter (talk) 09:36, 1 July 2019 (UTC)

Anybody? Is this technically feasible? -- Timeshifter (talk) 02:56, 3 July 2019 (UTC)
No, it is not possible to have both the 2010 and 2006 toolbar. You could however ask for an script that adds the missing buttons to the 2010 toolbar, which would be the hidden comment, quote and horizontal line.--Snaevar (talk) 16:53, 3 July 2019 (UTC)
That's a good idea. I only want the 2 buttons for instant link brackets (no intermediary popup). One button for an internal link. And one button for an external link. -- Timeshifter (talk) 05:20, 4 July 2019 (UTC)

Discussion at Wikipedia:Teahouse#Two questions about the WMF's Android app

 You are invited to join the discussion at Wikipedia:Teahouse#Two questions about the WMF's Android app . Airbornemihir (talk) 04:32, 4 July 2019 (UTC)

VVVV I've posted the question asked by Airbornemihir in its own section directly below this section. VVV Orvilletalk 05:28, 4 July 2019 (UTC)

Two questions about the WMF's Android app

The following questions have been copied from the Teahouse. The editor below has technical questions we are unable to answer there, and I'm hoping editors here can provide Airbornemihir with assistance. Orvilletalk 05:21, 4 July 2019 (UTC)
I'm aware that it's a good practice to leave edit summaries, but I'm nonetheless curious about the official Android app apparently preventing an edit from going through if the edit summary is left blank. Is this an intended limitation of the app, or is there something I'm missing?

Tangentially related question: the list of Wikipedia mobile applications states that the Android app cannot open talk pages, but this doesn't seem to be true of the current version of the app which can open any page when looked up with the correct namespace. Is that something that should be updated? (Please ping when replying.) Airbornemihir (talk) 03:22, 1 July 2019 (UTC)

The above questions have been copied from the Teahouse. The editor above has technical questions we are unable to answer there, and I'm hoping knowledgeable editors here can provide Airbornemihir with assistance. Face-smile.svg Thank you Orvilletalk 05:21, 4 July 2019 (UTC)

@Airbornemihir: Uhm, are you sure you are using the latest version? I just published this edit without an edit summary using the official Wikipedia app for Android. Also, the app is technically able to show talk pages, but it treats them as "normal" articles. I think the article (List of Wikipedia mobile applications) is referring to the "View talk page" option placed at the bottom of every page—including talk pages... yep—which the app doesn't yet "handle." —RainFall 07:27, 4 July 2019 (UTC)
@RainFall: Thanks, I've noticed too that talk page links open by default in a different app, which is probably the intended meaning as you said. Regarding blank edit summaries, do you not get stuck during the edit at the place where it asks "How did you improve the article?" I can't seem to move on from there without either picking one of the canned edit summaries or writing one myself. Airbornemihir (talk) 07:46, 4 July 2019 (UTC)
@Airbornemihir: Yes, I did see the "How did you improve the article?" page; I tapped "Publish" leaving everything else untouched and it worked... again. —RainFall 07:52, 4 July 2019 (UTC)
@RainFall: OK, it looks like it worked for me too. I'm not sure what was going on before. I edited the smartphone apps page to better reflect what the app can do, as well. Thanks everyone for your help. Airbornemihir (talk) 08:08, 4 July 2019 (UTC)

Has syntax highlighting CSS just changed?

Resolved

I just noticed that the gap between lines in "Syntax highlighting" mode in the wikitext editor suddenly became wider. Was it a glitch of my browser not loading CSS properly, or did it actually change? —⁠andrybak (talk) 21:37, 3 July 2019 (UTC)

@Andrebak: can you be a bit more specific, Wikipedia:Syntax highlighting doesn't usually get used in .css pages, which use the code editor (not the source editor). Is this still occurring? Can you share the edit link you are using? — xaosflux Talk 22:28, 3 July 2019 (UTC)
I guess andrybak was not editing a CSS page but just speculating that styling from some CSS file was not working properly when editing a normal wikitext page. If you refer to the highlighter marker button Codemirror-icon.png to the left of "Advanced" in a toolbar then it doesn't change spacing for me in Google Chrome 75.0.3770.100. PrimeHunter (talk) 09:43, 4 July 2019 (UTC)
@PrimeHunter: Yes, but for me it has changed in the same mode (Codemirror-icon.png turned on), but between different pages. It changed between two different gap sizes since then, so I think that it was just some networking issue when loading CSS. —⁠andrybak (talk) 10:12, 4 July 2019 (UTC)

Strange google capitalization for Life

A user (Console.frog) noted that when searching for "life on earth" on Google, the Life article appears in the middle of page 1 under the title life on Earth. This expression appears several times in the article but I can't figure out why the correct title is not brought up, and more importantly why "life" is not capitalized properly. Do you think there is something on our side causing this? -- Luk talk 11:27, 4 July 2019 (UTC)

A datapoint: "life on Earth" appears four times in the preamble, "Life on Earth" appears once in the preamble. —⁠andrybak (talk) 11:59, 4 July 2019 (UTC)
linksto:Life insource:"life|life on earth" finds many articles saying [[life|life on Earth]]. Maybe Google prefers to display this link text when it matches the search. PrimeHunter (talk) 12:01, 4 July 2019 (UTC)
Situation confirmed; here's what I see with a US IP:
life on Earth - Wikipedia
https://en.wikipedia.org/wiki/Life
Evidence suggests that life on Earth has existed for at least 3.5 billion years, with the oldest physical traces of life dating back 3.7 billion years; however, some theories, such as the Late Heavy Bombardment theory, suggest that life on Earth may have started even earlier, as early as 4.1–4.4 billion years ago, and ...
Evolutionary history of life · ‎Timeline of the evolutionary ... · ‎Earliest known life forms
I'm using Internet Explorer, if that matters at all (or even if it doesn't). Nyttend backup (talk) 13:02, 4 July 2019 (UTC)

Switching phrases in masse

Is there a bot or tool that can replace the phrase Kingdom of Hawaii to Hawaiian Kingdom across Wikipedia without having to edit each page and switch it over? This is just a logistical inquiry before a request for consensus for such a change. KAVEBEAR (talk) 21:01, 3 July 2019 (UTC)

AWB can do this. It shows up 54 pages, so it should be quite feasible, with about 10 seconds per page to allow manual check it could take 10 minutes. Graeme Bartlett (talk) 23:07, 3 July 2019 (UTC)
This is not so much a VPT matter as a question for WP:BOTREQ - and I see that an identical thread has been posted at WT:BOTREQ, contrary to WP:MULTI. --Redrose64 🌹 (talk) 23:09, 3 July 2019 (UTC)
To answer the technical question KAVEBEAR, no - assuming this phrase appears in the source text it would require creating another version of the source text for each page (which yes a bot could do, but that is how it would do it). The only way around that would have been if the name was actually a template that could be changed once. — xaosflux Talk 13:19, 4 July 2019 (UTC)

Stuck tooltips

Not sure if this is the correct venue but the tooltip (hovertext) that logged-out readers see for Antananarivo stampede is stuck on an old incorrect version with the wrong date. This has been repeatedly pointed out at main-page errors but no one there knows how to fix it. The article was corrected on 28 June [8]. Any help appreciated as this is currently on the main page in the In the News section. Espresso Addict (talk) 23:34, 4 July 2019 (UTC)

@Espresso Addict: It's not just that one page. In fact, I'm not sure that the preview has updated for any page since June 28. See phab:T227033. Suffusion of Yellow (talk) 23:48, 4 July 2019 (UTC)
Thanks. At least someone is hopefully looking into the issue. Espresso Addict (talk) 23:52, 4 July 2019 (UTC)

Google Maps template not displaying accessdates

Resolved

Why isn't {{Google maps}} displaying the access date in, for example, the first ref at Bussell Highway? The use of accessdate in the article seems fine ... and I'm not that good with templates. Thanks for any help! Graham87 14:02, 5 July 2019 (UTC)

Fixed the parameter as told in the documentation of the template. Stryn (talk) 14:18, 5 July 2019 (UTC)
Ta muchly ... oops, didn't notice the underline there! One of the perils of not paying attention to punctuation with my screen reader ... but seemingly an easy mistake to make, whether you're sighted or not! Graham87 14:47, 5 July 2019 (UTC)

Should be able to set DESKTOP to be DEFAULT on a laptop computer, right?

I hope this is an appropriate place to describe this concern. If not, please advise me where to express it. On my laptop I'd like to be able to set desktop to be my wikipedia preference, so it would be my permanent default view, and mobile view never come up on it. I am using Firefox 67.0.4 (64-bit) browser on Windows 8.1. The problem I encounter is that when using my laptop computer and searching for something via google, sometimes when I click on a wiki search-find I get a presentation of a wiki article which I have discovered to be a MOBILE wiki presentation, which I don't want. I now finally understand that I can go to the bottom of such an article and click on 'desktop', and I'll get a desktop view, and that setting will also obtain for other wiki articles until I turn my laptop off. But the next time I turn my laptop on, mobile views can again present from google searches, and I have no use for mobile style views. I would think desktop view should be able to be set in Preferences. If that can't be made available in Preferences, is there some other way that I could set DESKTOP to be my wikipedia permanent default view? UnderEducatedGeezer (talk) 23:22, 4 July 2019 (UTC)

As far as I know, Wikipedia can't automatically switch you from the mobile view to the desktop view. If you're on a phone, and go to the desktop version (en.wikipedia.org), you can be switched to the mobile version (en.m.wikipedia.org), but the other way around doesn't work. Therefore, if you click on a link from somewhere else on the internet to the mobile version (en.m.wikipedia.org), you stay on the mobile version. The easiest way to change this is to remove the .m from the URL. rchard2scout (talk) 10:13, 5 July 2019 (UTC)
That does not work. Trying to remove ".m" without using the appropriate option will redirect you back to the mobile view. The opposite is not true and from the desktop view (without the ".m") accessing the mobile view by simply adding .m is possible. Now, the easiest way to flip the views is to go to the footer of the page and click "Desktop view" or "Mobile view" as you want it. It's cookied, so it sticks for a while, but once the cookie expires, it will reset back to mobile view (if on mobile) and desktop view (if on desktop). Note that these options are incompatible with browser-provided "Enable desktop view" options and will not work on Wikipedia. --qedk (tc) 12:25, 5 July 2019 (UTC)
"It's cookied, so it sticks for a while" is a key bug for me. I made that explicit "Desktop view" setting because I wanted it that way, and it might be a pretty long page I have to scroll through to get to the bottom to (re)change it. My request is that either the cookie have a much longer expiration or that it can be handled by a site (rather than browser) pref. DMacks (talk) 16:47, 5 July 2019 (UTC)
You can make a JS script and add it to your MySkin.js, all you need to do is detect the current URL and if it contains, ".m" and go to the URL + "&mobileaction=toggle_view_desktop", essentially forcing the desktop view. --qedk (tc) 17:20, 5 July 2019 (UTC)
That doesn't quite match my experience: for me, just removing the m. is all it takes. On a desktop, that is. But if someone drops a link from the mobile site (like in a diff) and you click on it, then you get the mobile version. I like the script idea. Ivanvector (Talk/Edits) 17:27, 5 July 2019 (UTC)
Yep, if the default view is desktop (as in, how the page first loads), that is how it will work, but instead if your default view is mobile, it will not work. --qedk (tc) 18:36, 5 July 2019 (UTC)
I have a bookmark on my mobile phone that does not have the m. It sometimes takes me to the mobile site, and then I can click the Desktop-site link at the bottom of the page to switch to desktop mode. From then on, for a while, the bookmark takes me to Desktop. But then sometimes it (that same bookmark, with no m) reverts to mobile mode, and I have to click Desktop-site switch it, and then it will again stay that way but only for a while. DMacks (talk) 18:53, 5 July 2019 (UTC)
That's how it works for me too. Not a bookmark, but any wikipedia URL I try to load will initially (if I haven't clicked the Desktop link in some time) automatically redirect to the mobile page. Then clicking on the Desktop link will keep me in desktop mode for ... some time, two weeks or a month or so, unless I click on another mobile URL. This is the case whether I check the "always request desktop version" setting in my mobile browser. Above, I was referring only to desktop behaviour, and I have no idea about setting "default view", I didn't know that was a thing. Ivanvector (Talk/Edits) 18:58, 5 July 2019 (UTC)
@DMacks: Try bookmarking "https://en.wikipedia.org/w/index.php?title=Main_Page&mobileaction=toggle_view_desktop" and using that. --qedk (tc) 19:07, 5 July 2019 (UTC)
  • I often edit from my phone, but dislike the mobile view because it does not show all items on the page (specifically templates) and the incompatiblity with user scripts (none work). Therefore, I wish for pages to always display in desktop view. Senator2029 “Talk” 10:55, 5 July 2019 (UTC)
  • I often edit on my tablet, and occasionally for no apparent reason it will go to mobile view. This can happen even if I am currently looking at a page in desktop view and click a link on the page. It's very annoying. As DMacks said, sometimes it's a long page and not that easy to scroll to the bottom of the page. I'd love to have a preference (or even a js hack) that would disable mobile view while I'm logged in regardless of what device or browser I'm using. olderwiser 19:04, 5 July 2019 (UTC)
  • @DMacks, Ivanvector, Bkonrad, and Senator2029: Hey guys, so I hacked together a script since a lot of you said it was an issue, which should work, {{subst:lusc|User:QEDK/forcedesktop.js}}. Just paste this into your Special:MyPage/common.js and it should work. I've tried it on my mobile (Android 8.1, Chrome 75) and Desktop (Windows 10, Firefox 67) and it works alright. If you run into any issues, I can try to fix it, but my focus is on AI/ML which is kinda far from web development, but I will surely try to fix it. Hope I could help. Also please note, if the script works ideally, you will not be able to access the mobile site at all, until you remove the script (and purge your cache). --qedk (tc) 08:57, 6 July 2019 (UTC)
Updates and stuff
  • Missed a few: @UnderEducatedGeezer and Rchard2scout:. --qedk (tc) 09:00, 6 July 2019 (UTC)
    Working on desktop browsers, working on a fix for mobile browsers. --qedk (tc) 09:05, 6 July 2019 (UTC)
    Fixed --qedk (tc) 09:25, 6 July 2019 (UTC)

There is some interesting chatter on a related topic at phab:T214998. --Izno (talk) 15:42, 6 July 2019 (UTC)

Page preview discrepancy for an ITN item

Resolved: Thanks for pointing out the post above; closing this due to derpiness –Deacon Vorbis (carbon • videos) 21:29, 6 July 2019 (UTC)

The page preview for final item (as I'm writing this) on the "In the News" list on the main page (the Antananarivo stampede) mentions it occurred on 26 July, despite the article (correctly) saying it was 26 June. Looking at mw:Page Previews, it just says it uses a portion of the opening paragraph, so I have no idea what's causing the discrepancy. Does anyone know why this is happening and/or how to fix this? Thanks, –Deacon Vorbis (carbon • videos) 20:50, 6 July 2019 (UTC)

User:Deacon Vorbis, see #Stuck tooltips above. Over at Phabricator, it has an "Unbreak Now!" status, which means "drop everything you're doing and fix this". Nyttend (talk) 21:21, 6 July 2019 (UTC)

RfC: Alteration of Account Creation Limits/Account Creator Rights

Currently, one of the most backlogged processes is Request an Account (ACC) , which exists mainly (though not entirely) for helping with 3 purposes: Those having trouble completing CAPTCHA; enabling the choosing of a username that is too similar to an existing username under certain circumstances & creating an account for those hindered by a rangeblock.

The current backlog on pending requests is 4 months.

In the last couple of months multiple editors have signed up to be ACC tool users, Tool users are signed up to the confidentiality agreement and meet various other criteria.

Currently here are limits, however, on both their ability to create accounts. Two options could ease their work.

  1. Raise the local account creation rate limit from 4 to 10. The new limit only to extended-confirmed users to prevent any abusive behaviour from IPs.
  2. Automatically grant account creator permission, on request, to new ACC tool users. This would allow them both to bypass the limit entirely, but would also let them ignore the antispoof and title blacklist when making accounts.

Pinging all participants in the local chat discussion: @Ajraddatz, FlightTime, Xaosflux, TheSandDoctor, AfroThundr, QEDK, and Oshwah: Nosebagbear (talk) 13:11, 14 June 2019 (UTC)

  • NOTE: Option 2 is broader than Option 1, however they do not completely overlap. Option 1 would allow any EC-confirmed editor to create up to 10 accounts per IP address, option 2 is specifically targeted at ACC-users. Thus participants can !vote for either/both/none of the options.

Survey: Account creator rights

  • Support for option 1 only. Speaking as an ACC administrator, I believe that automatically granting all new ACC tool users the account creator user right (option 2) would open the door for new tool users to potentially handle requests incorrectly and without limitations before it's caught and identified - which would not be a good thing at all. We need to have a limit for how many accounts that new tool users can create per day by default. When a tool user shows proficiency with handling requests correctly, they can apply for and (after approval by an ACC admin via a comment made to the request) be granted the account creator flag in order to remove those limits. Option 2 would remove the need for an ACC tool administrator to give their approval before an admin can grant the user rights to the requesting user. This approval is still necessary and absolutely needed. Raising the current limit of 4 creations per day to 10 creations per day would loosen the restrictions so that users can help take care of the current backlog of requests at ACC, while still being on a set limit during the time that they're learning and demonstrating their knowledge and proficiency with ACC tool user interface. This option is the best way to resolve the concerns expressed. :-) ~Oshwah~(talk) (contribs) 13:25, 14 June 2019 (UTC)
  • Support for option 1; encourage ACC admins to quickly work with new ACC volunteers to get them trained and empowered with additional flags as soon as feasible. — xaosflux Talk 13:43, 14 June 2019 (UTC)
  • Support option 1 Per above. Also, as all rights on Wikipedia are, it is granted on the basis of need for the right, inherent oppose for point 2. --qedk (tc) 13:59, 14 June 2019 (UTC)
  • Support option 1 as per my comment in the previous discussion. I also agree with Oshwah on automatically granting new users the ACC bit. The current method of granting the right after a couple weeks of activity allows the team to gauge the user's performance and whether or not they have learned the policies and procedures properly. Lowering the barrier further could lead to a problematic user potentially causing a lot more damage (no rate-limit, anti-spoof override, username title blacklist override) than they otherwise could if we had to manually grant those rights. On the other hand, when all is in order, granting them the right is usually quick and painless anyway. — AfroThundr (u · t · c) 14:04, 14 June 2019 (UTC)
  • Support alternate option where an group named Account creation helper is formed, which would contain only the noratelimit right.--Snaevar (talk) 14:38, 14 June 2019 (UTC)
I appreciate the idea, but I just don't see how this implementation would be useful here, or how it would resolve any issues that the account creator flag wouldn't already resolve. If an ACC admin user can trust an ACC tool user enough to have no account creation limit, that admin user should also trust the tool user enough to be able to correctly and properly handle requests that tripped the antispoof extension and require a flagged user to override (and vice versa). ~Oshwah~(talk) (contribs) 14:45, 14 June 2019 (UTC)
  • Support 1. After thinking about this a bit more, I'm not sure if tying the rate limit to extendedconfirmed would be possible. If not, I still think we should raise the limit, but maybe to 6 like it was before instead. The limit was lowered mainly for projects without 300 active local sysops who couldn't instantly respond to mass account creation. -- Ajraddatz (talk) 15:16, 14 June 2019 (UTC)
    Rights like PMR have increased limits for certain flags (in that case, page moves), this would just mean adding a flag like that to EC right holders. --qedk (tc) 15:23, 14 June 2019 (UTC)
    Yes, most ratelimits are determined on a per-account basis (or per IP for anonymous users). But I seem to remember account creations being different, and being specifically tied to the IP. I assume/hope that a defined higher ratelimit for extendedconfirmed would override that. And no need to tie it to a specific permission; it can be done for the group itself. -- Ajraddatz (talk) 22:58, 14 June 2019 (UTC)
    Yep, but that's a non-issue as far as devs are concerned. Delving into the issue of newer technical changes, from my experience talking to people on SRE/Deployment (and Anomie, TheDJ), technically unfeasible things are pretty rare and I have not seen requests getting turned down (rarely, if ever) with "MediaWiki does not support this", if it's a feature change, or some irreproducible bug, it's a different thing but for example, during the RfC for Template editor rights, a lot of people were worried about the tecnical changes but eventually it was done, with no big deal at all. That's how it is for most new things (and TE rights had a new protection level as well), so I would say a change would be technically feasible until a dev says exactly otherwise. --qedk (tc) 07:50, 16 June 2019 (UTC)
    With dev time almost anything is possible; my concern would be if the current software doesn't support the change, then we should be looking at easier options like raising the max number to 6 / IP as it used to be. Adding a new protection level is easy to do through the software. Fundamentally changing the account creation throttle might be more difficult. But agreed that we should ask rather than muse about things we know little about :-) -- Ajraddatz (talk) 01:03, 18 June 2019 (UTC)
  • (ACC admin comment) I'm pretty sure option 1 isn't possible without development, i.e. it is not a simple configuration change. AFAICT, IP account creation limits can only be set as a count per interval with the noratelimit right being the only way for a user to bypass that limit. (mw:Manual:$wgAccountCreationThrottle) Oppose option 2 for the reasons outlined by Oshwah. Support returning the daily IP limit to 6 unless the Security Team provides a good reason that it needs to remain at 4. — JJMC89(T·C) 05:50, 15 June 2019 (UTC)
    The Security Team doesn't have a problem with bumping the IP limit from 4 to 6 or even 10, as originally proposed. SBassett (WMF) (talk) 21:32, 21 June 2019 (UTC)
    @SBassett (WMF): thanks for the note, is this really something we need to worry about at a per-project level then? — xaosflux Talk 21:52, 21 June 2019 (UTC)
    @Xaosflux: - see my response to JJMC89 starting here: https://phabricator.wikimedia.org/T212667#5274787. SBassett (WMF) (talk) 12:39, 22 June 2019 (UTC)
    @JJMC89:, @Xaosflux: - just following up here, the account creation throttle revert was deployed today. SBassett (WMF) (talk) 21:47, 24 June 2019 (UTC)
  • Comment. My preference would be to at least be granted access to the tool. I've waited for a week or so now. :/ –MJLTalk 16:04, 18 June 2019 (UTC)
  • Oppose I think 6 is the highest we should go with general limits on account creation per IP. Given that changing IP is rather trivial, the higher we go the greater the risk of abuse. If we raised the limit from 4 to 10, and a bad actor switches from their laptop to their cellular data network when they hit a limit, that is an additional 12 accounts they would be able to create. I think 4 was fine, 6 is okay, but anything higher I am not in favor of. I am not in support of option 2 for the reasons above. Wugapodes [thɑk] [ˈkan.ˌʧɹɪbz] 19:05, 29 June 2019 (UTC)
  • Support option 1 I'm not sure what option 2 is, so I can't support it. Option 1 seems fine, though. I think we should prioritize clearing up the backlog, though. InvalidOS (talk) 23:13, 6 July 2019 (UTC)

Discussion: Account creator rights

  • @Nosebagbear: regarding your proposed options, and since this is VPT, can you explain the specific technical changes you are proposing - or is this more of a "let some developer figure it out" type of request? Is the "automatic" granting you are asking some sort of technical change you are proposing, or is it a procedural/policy change? — xaosflux Talk 13:24, 14 June 2019 (UTC)
    Xaosflux - If option 1 were to reach consensus, it would be corrected by filing a phab ticket to have this done. See phab:T212667. ~Oshwah~(talk) (contribs) 13:27, 14 June 2019 (UTC)
    Thanks. — xaosflux Talk 13:29, 14 June 2019 (UTC)
    (edit conflict) @Xaosflux: - changing the rate limit is obviously possible. Whether it can be changed "in bands" to different protection levels is, I'm afraid, I query for those more technically savvy than me. If they say that's impossible (or akin), then this would need to be rethought. Nosebagbear (talk) 13:29, 14 June 2019 (UTC)
  • For the problem that is trying to be solved - is overriding anti-spoof the normal resolution, or is getting them to pick a new username? — xaosflux Talk 13:25, 14 June 2019 (UTC)
    Xaosflux - For instances where similar usernames exist and are caught by anti-spoof, it depends. See this section of the ACC guide for the policy on when ACC tool users with the account creator flag can override the antispoof flag and proceed with creation. ~Oshwah~(talk) (contribs) 13:30, 14 June 2019 (UTC)
    @Oshwah: thanks, option 1 above won't fix the antispoof ones, is that a significant part of the backlog? Just asking so we don't spend time getting something done that won't help. — xaosflux Talk 13:33, 14 June 2019 (UTC)
    Xaosflux - No. Requests that have tripped the anti-spoof extension make approximately 3.5% of all total requests at this time. Of those, users without the account creator flag can still see if the similar accounts are active, and decline the request if any of them are. The only time that a request requires a user with the account creator flag is when a request trips the antispoof extension and the similar accounts are all inactive. This means that the antispoof needs to be overridden, the request approved, and the account created. ~Oshwah~(talk) (contribs) 13:37, 14 June 2019 (UTC)
  • Why not grant Wikipedia:Event coordinator to new members of ACC? EVC will give them ability to bypass 4 account limit and it also doesn't allow overriding antispoof/title ban restrictions. ‐‐1997kB (talk) 16:36, 14 June 2019 (UTC)
    1997kB - Not a bad thought, but event coordinators can set new accounts as 'confirmed' using Special:UserRights, which is an ability that they don't need. Essentially, we'd be trading apples and oranges here if the concern is over access to some user rights they shouldn't have. As I said above, I believe that if an ACC admin can trust an ACC user to create accounts with no limit, they should also trust them to properly handle requests that tripped the antispoof extension and require a user with the account creator permissions to override and create (and vice versa). :-) ~Oshwah~(talk) (contribs) 16:42, 14 June 2019 (UTC)
    @Oshwah: - I realise I agree with you, but to run with the Event-Coordinator compromise theory a bit further, it would be clearer cut - the damage possible is pretty tiny. Even if they made every account they created confirmed, it wouldn't cause a great uptick in carnage. Nosebagbear (talk) 22:36, 14 June 2019 (UTC)
    Fair point. ~Oshwah~(talk) (contribs) 02:31, 15 June 2019 (UTC)
    @Oshwah: what is the expected amount of accounts to be created by "new" ACC volunteers per period? (i.e. would 6 or 8 be enough?) since the "rights they don't need" here to ECC users is expected to be way more than is needed by the relatively minuscule ACC team. — xaosflux Talk 16:59, 14 June 2019 (UTC)
    Xaosflux - Honestly, any increase from 4 would be beneficial. Even if the increase is just by a few... :-) ~Oshwah~(talk) (contribs) 17:41, 14 June 2019 (UTC)

New bot

I think we should have a bot or some kind of tool check for accounts which are hitting the account creation limit but do not hold the rights event coordinator, account creator and are also not ACC tool users. The account creation limit was lowered for a reason and increasing it without keeping a check in place would be a gross violation of WP:BEANS imo. Thoughts, @Nosebagbear, JJMC89, Xaosflux, and Oshwah:? --qedk (tc) 14:19, 14 June 2019 (UTC)

A recurring database report may be able to solve this for you. — xaosflux Talk 14:27, 14 June 2019 (UTC)
If this is a major issue, the report would have to be run quite frequently, and viewed frequently by patrolling users. Otherwise, this method might not be effective enough at stopping abuse and quickly enough... ~Oshwah~(talk) (contribs) 14:30, 14 June 2019 (UTC)
(edit conflict) QEDK - Doesn't sound like a bad idea to me. How would this new bot alert others that an account is hitting a limit and isn't within one of those groups? Who would this bot alert? Where? This is something that we should figure out if we're going to consider an idea like this... :-) ~Oshwah~(talk) (contribs) 14:29, 14 June 2019 (UTC)
It can function the same way AnomieBot handles WP:TPERTABLE, there's no annoying notifications involved and interested people can simply watch the page and report when they find anyone suspect. --qedk (tc) 14:33, 14 June 2019 (UTC)
QEDK - Nice... I like it. :-) ~Oshwah~(talk) (contribs) 14:36, 14 June 2019 (UTC)
Functionally, a bot wouldn't be able to work "that way". Also, bot's wont be able to see "that you got denied by the limit" , but a bot could periodically generate a report of "accounts created per user over some time period" and could either filter out members of certain groups or just report the groups as well. — xaosflux Talk 14:38, 14 June 2019 (UTC)
Why not? The logic is pretty simple, you would need to check creation logs iterating a certain period (maybe an hour) and track accounts which create another account for 24 hours at minimum and more if they somehow meet the limit each day (hence, suspect). Wikipedia accounts which do not have a similarly authorized account in ACC (or the other account creation rights as well) have demonstrably no reason to carry out actions like this, hence red-flagging them almost immediately. --qedk (tc) 14:49, 14 June 2019 (UTC)
A bot could create a report, technically it won't be able to tell if you actually got stopped by the limit, just that you hit it or approached it. It wouldn't work "the way" of the protected edit requests in that those don't mine logs, they make use of what links here/category memberships. But the output could still be made. Have a bot periodically (say hourly) ingest the user account creation log and make a report. I think it may even be helpful to have it report on everyone, or everyone with say 3+ creations - and also to identify accounts made by coordinators, etc - so they can be coached as needed. — xaosflux Talk 14:54, 14 June 2019 (UTC)
Yeah, I mean, technically not. But I'm saying it like the logic is clear that an account cannot make more than 10, so an account which makes 10 accounts can be construed to have hit the limit, what's important is identifying if anyone is trying to make a large number of accounts in a short period of time, hitting the actual limit is more of a formality. --qedk (tc) 15:06, 14 June 2019 (UTC)
Something like quarry:query/36938? It can't tell if they're an ACC tool user, obviously. If this query is correct, there's not a whole lot of ACC activity going on. MusikAnimal talk 19:46, 14 June 2019 (UTC)
@MusikAnimal: thanks for the query, even including everyone with 3+ creations over the last whole 10 days (quarry:query/36941). I haven't checked their groups, but the impact here seems to be very small. — xaosflux Talk 20:07, 14 June 2019 (UTC)
Almost all ACC users in that 10+ range, minus the one event coordinator. Unfortunately I won't be appearing in that query anytime soon due to a certain rangeblock with "account creation disabled" set. Really puts a damper on ACC work... — AfroThundr (u · t · c) 01:51, 15 June 2019 (UTC)
@AfroThundr3007730: - I thought individual accounts could be exempted from rangeblocks? If so then ACC tool users would be a priority Nosebagbear (talk) 14:32, 15 June 2019 (UTC)
@AfroThundr3007730: this is a known issue, even effects admins: phab:T189362. — xaosflux Talk 15:16, 15 June 2019 (UTC)
@Nosebagbear: Besides IPBE, I'm not aware of any (current) facility to exempt an individual user from the effects of a rangeblock, at least not the account creation part.
@Xaosflux: - thanks, suspect it was one of those merging of facts I got while swinging around the policy pages. Clearly, I'd made a terrible nerd Nosebagbear (talk)
@Xaosflux: Yep, definitely tracking that one, and if they do get around to implementing it, I would be first in line to request IPBE so I can get back to helping in ACC. — AfroThundr (u · t · c) 18:37, 15 June 2019 (UTC)
Could use an abusefilter for this - something along the lines of Special:AbuseFilter/527. Galobtter (pingó mió) 15:33, 15 June 2019 (UTC)

Event Coordinator Rights

The idea of granting (permanent) Event Co-ordinator rights to any ACC tool user who didn't possess Account Creator rights was mooted as a compromise. The right waives the account creation limit, and also allows accounts to be made confirmed. Obviously the latter isn't needed, but as I noted above, even if a tool-user went rogue, the maximum potential damage is significantly smaller (than the additional rights of Account Creator). It makes a good halfway house between nothing and Account Creator, and if Option 1 turns out to be inviable, then it might be the only way to significantly help with their task. Nosebagbear (talk) 18:46, 17 June 2019 (UTC)

  • Oppose The event co-ordinator right will allow the ACC team to grant confirmed right to new users. And the new users will start to create articles in the mainspace, which will cause more damage. Masum Reza📞 10:20, 29 June 2019 (UTC)
  • Oppose We (ACC tool admins) want new ACCers to be rate limited, so that we can easily monitor adherence to the ACC Guide. — JJMC89(T·C) 17:29, 29 June 2019 (UTC)

Back to 6 per day

So, the prior "temporary" reduction has been lifted and the setting is back to 6 accounts per day for all projects; that being said is anything really needed now? I think that it is reasonable for volunteers working with the ACC team to get account creator access after a short warm-up/training period - and having the team communicate the plan to new members and getting those swiftly processed (say within a fortnight of actively working with ACC) is a good thing. — xaosflux Talk 13:16, 25 June 2019 (UTC)

I haven't personally noticed any issues with ACC members requesting and getting the bit granted — after they have demonstrated continuous good judgment for a few weeks, that is. I still think it might make sense to raise the limit to 10 for enwiki, being the largest userbase, and with that query and edit filter from above, we can continue to monitor non-ACC users with high creation rates. — AfroThundr (u · t · c) 15:49, 25 June 2019 (UTC)
  • Comments: I am new to this, support account creation, and was appalled at the backlog. A note that 2-3 days may be needed, may take weeks or even months, and a backlog of 4 months seems to point to a possible loss of good editors at worse, those legitimately seeking an account to lose interest or maybe just not actively seeking an account. Maybe I am looking at this wrong but a backlog of 4 months seems to indicate "is anything really needed now?" a strange question. I understand the need to limit account creation abuse and possible vandalism, but if what is in place seems to be a horrible failure then why not an increase to maybe the 10 suggested instead of back to the statue-quo? I haven't looked at this, just read over some of the above, but has there been a problem with "trusted user" abuse to cause the decrease in the first place? Otr500 (talk) 08:55, 29 June 2019 (UTC)
    The backlog doesn't have anything to do with the rate limit. Almost everyone working at ACC has noratelimit (from accountcreator or sysop), so the limit doesn't apply to them. The backlog is from a shortage of volunteers willing to devote time to working at ACC. — JJMC89(T·C) 17:28, 29 June 2019 (UTC)
  • If it's back up to 6, then I don't think further changes are needed. New volunteers can get the accountcreator bit once they have a bit of experience. The biggest issue is number of volunteers. -- Ajraddatz (talk) 01:11, 1 July 2019 (UTC)

IPvandal links with ranges

WP:ANI#Unknown attack on me contains some {{IPvandal}} links to individual IPv4s, individual IPv6s, and IPv6 ranges. Here are three of them, plus a totally unrelated IPv4 range:

You'll see that the template doesn't do well with some of the range code. Is there a way we could fix this, either by instructing the template to drop the "http" link if it's not a simple IP, or by otherwise rearranging something? Nyttend (talk) 20:13, 6 July 2019 (UTC)

This will prevent the "http" link from appearing if the input is neither a IPv4 nor IPv6, although it might be a bit kludgey. Nardog (talk) 20:39, 6 July 2019 (UTC)
Thank you. Would you advise that I seek to gain consensus before copying your new code into the module, or should I just go ahead and make the change immediately? Nyttend (talk) 21:26, 6 July 2019 (UTC)
I'm not sure either. Let's ask Mr. Stradivarius and Anomie, who are responsible for the module. Also there might be a better way to prevent it than return ''. Nardog (talk) 21:38, 6 July 2019 (UTC)
Seems sensible to me. Anomie 01:07, 7 July 2019 (UTC)

Global count tool now limited?

Seems that "Global User Contributions" (at => https://tools.wmflabs.org/guc/?by=date&user=Drbogdan , for instance) once gave truly "total contribution results", but now seems limited to "20 results per wiki"? - QUESTION: is there a way to again obtain truly "total contribution results" with this wiki tool (or some other related one) - and *Not* be so limited (to some number of results per wiki)? - in any case - Enjoy! :) Drbogdan (talk) 00:52, 4 July 2019 (UTC)

Drbogdan, Hey, at least it's working now (it was down for a while). There is an alternate tool at https://xtools.wmflabs.org/globalcontribs which may work better for you. --AntiCompositeNumber (talk) 01:21, 4 July 2019 (UTC)
AntiCompositeNumber - Thank you for your reply - and suggestion - the newly suggested counter seems limited to english and english-related wikis - and not wikis from other countries as the https://tools.wmflabs.org/guc/?by=date&user=Drbogdan counter seemed to be - at least at one time - hopefully, the old counter will be back up - and work like it seemed to at one time - in any case - Thanks again for your reply - and - Enjoy! :) Drbogdan (talk) 01:39, 4 July 2019 (UTC)
@Drbogdan: It's not limited to English wikis, rather it's just listing global edits chronologically. If you paginate through you'll find edits you made elsewhere, e.g. here are your edits from before July: https://xtools.wmflabs.org/globalcontribs/Drbogdan/all//2019-07-01.
FYI there is still some database maintenance going on, so both GUC and XTools may experience occasional slowness. MusikAnimal talk 02:26, 4 July 2019 (UTC)
This tool will also give you your total edit count by wiki. bd2412 T 01:40, 4 July 2019 (UTC)
Hello. @Drbogdan: the GUC tool was down at the beginning of June, then it has been repaired with Phabricator:T224930, with the limitation that you have seen. But in the Phabricator task, Krinkle said "I'm gonna land the patch now, although it only works for recent changes right now. Not for "All contributions". [...] I'll fix that in a separate change, but closing this for now." so I am convinced that, after the next fix, GUC will show again the "total contributions count" (for all projects) and the "project contributions count" (for each project). Regards --NicoScribe (talk) 21:59, 4 July 2019 (UTC)
@Drbogdan: The GUC tool has always limited the number of results from a single wiki to 20. This has been the case since the tool's creation by Luxo for Toolserver in 2014. However, there are two things that did change since 2014:
  1. In May 2018 (last year), I added the text "20 results per wiki" so as to reduce confusion for users not aware of this previously (phab:T167524).
  2. In June 2019 (last month), I switched the default grouping logic from "per wiki" to "per day" (chronological globally, instead of per-wiki). This has not made any change to which results are shown, merely in which way they are grouped. Both grouping options are still available as before, and can be selected in the form, or by url. This was requested by several users (phab:T193896).
As always, if you are interested in seeing more results from a specific wiki, use the "contribs" link next to the user name to continue for more results (which links to Special:Contributions on the relevant wiki).
Regarding the "global edit count" (as a number, not the list of actual edits), this can be better retrieved from Special:CentralAuth.
--Krinkle (talk) 17:57, 5 July 2019 (UTC)
@Krinkle: Thank you for your reply - and comments - yes - using "https://en.wikipedia.org/wiki/Special:CentralAuth/Drbogdan", my total counts is currently 69,212 - however - for some reason - seems, until somewhat recently, my total counts with "https://tools.wmflabs.org/guc/?user=Drbogdan" were almost always about 1000 counts more (should be, with the earlier program-tool, about 70,200+/?) - an example => based on an old copy (June 2018) of my User:Drbogdan Wiki-Page - at => "https://web.archive.org/web/20180622155402/https://en.wikipedia.org/wiki/User:Drbogdan" - in the right-hand userboxes (down the middle of the page) - the total counts at that time were noted as 59,000 (using "https://en.wikipedia.org/wiki/Special:CentralAuth/Drbogdan") and 60,000 (using "https://tools.wmflabs.org/guc/?user=Drbogdan") - perhaps I was misreading/misunderstanding something in some way? - or perhaps - something changed in the meanwhile? - in any case - Thanks again for your reply - and - Enjoy! :) Drbogdan (talk) 18:51, 5 July 2019 (UTC)
@Krinkle:
  • When writing my message above, I knew about "20 results shown per wiki". That's why I focused my message on something else: the "total contributions count" (for all projects) and the "project contributions count" (for each project). These 2 types of count are necessary (for me) to follow several long-term cross-wiki abusers. When you wrote "I'm gonna land the patch now, although it only works for recent changes right now. Not for "All contributions". [...] I'll fix that in a separate change, but closing this for now." in the Phabricator task, you were not talking about these 2 types of count?
  • CentralAuth is great for many uses but is unable to show the "project contributions count" and the list of recent edits side to side (for each project). GUC was able to do that, before. Moreover CentralAuth does not work for IP users.
@Drbogdan: CentralAuth considers the deleted edits and ignores the imported edits, whereas GUC ignores the deleted edits and considers the imported edits. For instance:
37 + 956 = almost 1000: it explains the difference between your old GUC "total contributions count" and your CentralAuth total count. --NicoScribe (talk) 17:39, 7 July 2019 (UTC)

Small tags and mobile view

In the mobile view, <small>..</small> has no effect on the size of the displayed font. This appears to be implemented in the different style sheets used in mobile view. I assume this was a deliberate design decision – perhaps it was thought that making already potentially small font on a mobile device even smaller wasn't a good idea.

Up until February 2018, {{small}} was a wrapper for <small>..</small>. It was then changed to be a wrapper for <span style="font-size:85%;">..</span>. This is obeyed in mobile view, so does generate smaller text.

If it was a deliberate decision not to display smaller text in mobile view, then the change to {{small}} should be undone. Comments, please. Peter coxhead (talk) 12:50, 8 July 2019 (UTC)

Finding distinct pages edited by a user?

When I'm looking to see what a user has been up to, looking at their contributions page is usually way to verbose, because it shows every edit. What I usually want is to just see the distinct pages. In pseudo-sql, I want something like, "select distinct page_name from contributions". Is such a thing possible, short of using Quarry?

Even better, a way to do this for both contributions and deleted contributions and fold the results together into a single list of distinct pages. -- RoySmith (talk) 14:29, 5 July 2019 (UTC)

Sounds like the same idea as the "Group changes by page in recent changes and watchlist" option in Special:Preferences#mw-prefsection-rc, but that does not seem to affect Special:Contributions lists. DMacks (talk) 14:38, 5 July 2019 (UTC)
@RoySmith: It is not sorted chronologically, but maybe XTools' Top Edits would help? For example [9]. This intentionally does not reveal deleted contributions. MusikAnimal talk 17:21, 8 July 2019 (UTC)

Tech News: 2019-28

20:12, 8 July 2019 (UTC)

Wanted - someone to adopt a discontinued bot

Wikipedia:WikiProject Women in Red is looking for someone who'd be prepared to run a bot, the owner of which has recently retired. The bot is described at d:Wikidata:Requests for permissions/Bot/Emijrpbot 6, which points to code here. The function of the bot is to add new wikidata items for new en.wiki biographies and/or to add human and/or gender statements to existing wikidata items, based on articles found on Special:UnconnectedPages. WiR bases all of its metrics (& these) on wikidata records for en.wiki articles, and since end April the project's stats have become increasingly hard to compile. We'd be more than grateful if someone would consider picking up this thankless task; thx. --Tagishsimon (talk) 17:33, 3 July 2019 (UTC)

@Tagishsimon: if you haven't already, try WP:BOTREQ Headbomb {t · c · p · b} 05:16, 9 July 2019 (UTC)

Wikipedia:Welcoming committee/members

Resolved

--qedk (tc) 07:05, 6 July 2019 (UTC)

I'm not sure what the best venue is to ask this question, but I was at Wikipedia:Welcoming committee/members and in these edits, I purged a bunch of sock operators, some unregistered users, a bunch of redlinked users who hadn't edited in forever, and without looking at the rest of the list, I can only wonder how many people there are actually active. Is there any technical way to purge the list of duds? I also noticed there were tons of green-linked names, which typically represents users who have changed their handles.

Side question: I remember tweaking a setting that turned redirect links green (see above) but I can't remember where it was. I looked through my prefs and common.js file and can't find it. Help? Cyphoidbomb (talk) 02:35, 6 July 2019 (UTC)

@Cyphoidbomb: Try this: User:Anomie/linkclassifier. To use only the redirect green color, copy User:Anomie/linkclassifier.css to your .css and comment out the ones you don't need. --qedk (tc) 04:35, 6 July 2019 (UTC)
@Cyphoidbomb and QEDK: Better yet, install User:BrandonXLF/GreenRedirects. 10/10 user script for that. –MJLTalk 05:41, 6 July 2019 (UTC)
@QEDK and MJL: I'll gladly install whatever anybody strongly recommends. Since the redirects already show up as green for me, I was trying to figure out what I already clicked in my prefs/gadgets/whatever, so if anybody has any idea, please let me know. Also, I'm still curious about purging the Welcoming committee members page, although it's a low priority on account of it being an indiscriminate user list. Cyphoidbomb (talk) 06:46, 6 July 2019 (UTC)
[Thank you for the ping] Cyphoidbomb, you're a real treat. lol –MJLTalk 06:51, 6 July 2019 (UTC)
@MJL: You are awesome. I can't keep track of the various common files and most of my changes have been to common.js, so I am much appreciative for your sleuthing. I come to the tech board so I don't have to walk in circles aimlessly like an asshole. Face-smile.svg Thanks, mate. Cyphoidbomb (talk) 06:57, 6 July 2019 (UTC)
...so I don't have to walk in circles aimlessly like an asshole. But that's all I do on Wikipedia! 718smiley.svg Glad to hear you resolved it. --qedk (tc) 07:05, 6 July 2019 (UTC)
@Cyphoidbomb: It was nothing! It was just a quick check of your subpages. As for the pruning, I'm afraid I don't know much that could be of service. Maybe a bot to clerk the list would be of service, but I am not the one to program such machinations. Cheers! Face-smile.svg (edit conflict)MJLTalk 07:05, 6 July 2019 (UTC)
User:Cyphoidbomb and User:MJL, you might consider using the Wikipedia:WikiProject X tools, which come with a bot to archive inactive members. User:Harej can probably point you in the right direction if you get stuck. Whatamidoing (WMF) (talk) 21:02, 9 July 2019 (UTC)

logout slow and failed due to http

I was trying to log out one day but the step was slow. It said, "You are being logged out, please wait". Then it said, "Cannot log out now: http". Eventually I was logged out. Why so long? Does it mean that I must have been using a slow network? If I close my browser while waiting, is that good enough? Nick Levinson (talk) 20:26, 6 July 2019 (UTC)

You say 'one day' and you were eventually logged out, that means the issue may no longer be there. Have you tried logging out again to see if the issue persists up to now?. – Ammarpad (talk) 05:12, 7 July 2019 (UTC)
Preventing a logout is a security concern, thus I asked, even if it doesn't repeat for me. I agree the issue may be gone but it may not be, which is why I said "one day" and then posted. It did not recur on another day but that doesn't mean it was resolved. I think I had another well-known site open under my login during the same session; if so, I had no problem logging out from there. I assume the two strings I quoted (minus "http") can be searched for in MediaWiki software or the Wikipedia implementation to find what causes them to display, but I can't do those searches and I don't know how to test for recurrence of the problem, because if the cause was network slowness I don't know how to slow a network that I don't control and most networks I use are likely fairly robust.
Does the problem come from network slowness or something else? If anything was done to resolve it, that's different and please tell us.
Nick Levinson (talk) 23:39, 8 July 2019 (UTC) (Corrections: 23:46, 8 July 2019 (UTC))
@Nick Levinson: I've filed a task at phab:T227621 for it to be looked at. Thanks for reporting. Quiddity (WMF) (talk) 21:52, 9 July 2019 (UTC)

Null edit needed

Can someone with the right permissions null edit the fully locked page User:NQ/nqup.css (the user hasn't edited for 2 & 1/2 years) so as to clear the redirect Category:Potentially illegible userboxes? This one is causing strange errors for the redirect bot. Timrollpickering (Talk) 14:24, 9 July 2019 (UTC)

Wow that page is a mess, looking at it. — xaosflux Talk 14:53, 9 July 2019 (UTC)
 Done @Timrollpickering: should be good now, is using the 'fake css' permission hack to make a protected user page. — xaosflux Talk 14:56, 9 July 2019 (UTC)
It's cleared - thanks. Timrollpickering (Talk) 15:03, 9 July 2019 (UTC)
Rather than null edit it, it should be nullified - there isn't a single valid CSS rule in the whole thing. --Redrose64 🌹 (talk) 19:44, 9 July 2019 (UTC)
@Redrose64: it is a self-protection hack used by non-admins (c.f. Wikipedia:User_pages#Protection_of_user_pages). — xaosflux Talk 22:16, 9 July 2019 (UTC)
Why do we encourage this? --Redrose64 🌹 (talk) 22:34, 9 July 2019 (UTC)

Template conditional syntax quesiton

What is the correct syntax to set the inline parameter conditionally in this template? It is embedded in the London Overground article thus: {{Overground RDT|inline=yes}}, which should be able to set the inline to 1 or true. The aim is to hide the top bar of the template when embedded in an infobox but not elsewhere.

I attempted this but it didn't work, so clearly I'm not getting the conditional syntax right:

|<includeonly>|inline={{#if: {{{inline|}}}|1|0}}</includeonly>

What's the correct way of doing it? Thanks. — Preceding unsigned comment added by Cnbrb (talkcontribs) 20:38, 9 July 2019 (UTC)

@Cnbrb: You're overcomplicating it. Just do this that way you can use {{Overground RDT|inline=1}}. BTW the documentation for {{Routemap}} shows |inline=1 but |inline=yes might work, I'm no Lua expert. --Redrose64 🌹 (talk) 22:32, 9 July 2019 (UTC)
Ah! Someone has stepped in and fixed it. The answer was (of course) obvious:
|inline={{{inline|}}}
Thank you! Cnbrb (talk) 00:26, 10 July 2019 (UTC)

Headerbar doing v-t-e and hide

{{Navbar-collapsible}} is a good utility (showing both V-T-E links and the Hide/Show button). Now IIRC, there was a similar template for (wiki)table headers. Cannot find it any more, did anything bad happen? If someone could give me a hint/link, +appreciated. -DePiep (talk) 20:37, 9 July 2019 (UTC)

You recall incorrectly. No such template exist, or can exist. Headbomb {t · c · p · b} 23:10, 9 July 2019 (UTC)
You can make a collapsible table, but the v/t/e won't be able to reliably target just the table for editing (see User:Xaosflux/sandbox76). — xaosflux Talk 00:35, 10 July 2019 (UTC)
Indeed, Xaosflux, but I will apply it in a templated table.
Discovered how to make this work:
{| class="wikitable collapsible" (adds the Hide/Show button, right)
! colspan=4 | {{navbar-collapsible|1=Title text|2=Template:Foo}} (adds the v-t-e links, left)
-DePiep (talk) 09:48, 10 July 2019 (UTC)
@DePiep: do you have this sandboxed? I'm assuming the edit link still goes to a "page" not somehow only edits "the table" right? — xaosflux Talk 13:00, 10 July 2019 (UTC)
@Xaosflux: I only use this in a table that is in a template page (see {{Decay modes}} edit), that is what I meant to say with "in a templated table". I do not aim to use this in an in-article coded table; as you pointed out that won't work. -DePiep (talk) 13:06, 10 July 2019 (UTC)

Preloading edit summary?

Hey! is it possible to preload an edit summary like we can do with page content? and if yes whats the code? thanks in advance.--▸ ‎épine talk 21:50, 9 July 2019 (UTC)

@Épine: &summary= ! ;-) Example link. Quiddity (talk) 21:56, 9 July 2019 (UTC)
URL is [https://en.wikipedia.org/w/index.php?title=Wikipedia:Sandbox&action=edit&summary=foo%20bar Example] -DePiep (talk) 11:47, 10 July 2019 (UTC)
Épine, also see the documentation mw:Manual:Creating pages with preloaded text. —TheDJ (talkcontribs) 13:36, 10 July 2019 (UTC)

Sorting broken?

Take a look at List of Governors of Alabama - errors of "Script error: No such module "Date table sorting"." all over the place. --Golbez (talk) 14:25, 10 July 2019 (UTC)

It's fixed now. --Golbez (talk) 14:26, 10 July 2019 (UTC)

Android app login generic error

Screenshot: https://pasteboard.co/ImS2y8j.jpg

hello,

I can successfully log into the web browser version of Wikipedia, but I cannot log into the Android app using the same credentials. I received a generic error that only states that an error has occurred.

I have also tried using the same automatic input of credentials from the same source and mechanism on the same device to control for my user error. Again, browser version login works, app no :(

Any ideas gratefully received!

Thank you — Preceding unsigned comment added by Rrubix44 (talkcontribs) 12:17, 7 July 2019 (UTC)

Did you try uninstalling and reinstalling the app? There may be an issue with the app itself. -- Luk talk 19:55, 7 July 2019 (UTC)
  • @Luk: The same issue bugs me to no end. I'm not even using an Unicode username, which has been an issue in the past. All that I could think of was that either my password - 32 character sequence of random ASCII characters - somehow triggered the bug, or that the Pie autofill API weren't accepted. I wasn't using VPN either. There is only a very slim chance I could log into the Android App without problem. Is there an phabricator on this? Tsu*miki* 🌉 16:31, 10 July 2019 (UTC)

WHOIS broken

Whois returns either a blank page, or a 500 internal server error. Been going on for a few hours already. DuncanHill (talk) 21:26, 10 July 2019 (UTC)

  • I just posted this in a section above, but moving it here. The last couple of days, I've been getting 500 - Internal Server Error Here is one from WP:AIV I've tried multiple times just now 1. Here is one from a different IP 2. — Maile (talk) 21:02, 10 July 2019 (UTC)
Note: This might not be isolated to Wikimedia or Tools. I just got the identical error message at Find A Grave. On second try, Find a Grave loaded. — Maile (talk) 23:26, 10 July 2019 (UTC)

XTools

I use two XTools - edit counter and article counter, both of which have stopped working for me as I have over 350,000 edits. Any idea how this can be resolved? GiantSnowman 15:27, 10 July 2019 (UTC)

@GiantSnowman: The limit is there to prevent long-running queries that likely wouldn't finish, and would unnecessarily slow down XTools for everyone else. I can try increasing it a little bit, but we have to have some sort of sane limit. phab:T182182 is about analyzing the most recent 350,000 edits, but I suspect this wouldn't really help because in theory we'd still have to scan all of your contributions to get the most recent 350,000. The issue with Pages Created, specifically, is tracked at phab:T207959. One idea is to use the page creation log (phab:T221730), which is fast, but it would only produce pages you created going back to June 2018.

It's a tough problem to solve. We have to balance satisfying the needs of our users, such as yourself, while protecting stability and preventing unrealistic queries from being ran. This is compounded by more general issues with the replica databases, such as the inability to estimate how slow queries will be (phab:T188677) and more recently, general slowness following recent schema changes (phab:T226050). In the meantime, you could try using tools that don't have any limits (or the scalability problems that XTools has), such as Sigma's Pages created tool. Sorry for the inconvenience! MusikAnimal talk 16:19, 10 July 2019 (UTC)

I have increased the edit count limit to 400,000. It seems right now, the replicas are going fairly fast. Both Pages Created and Edit Counter didn't time out for your account. I can't promise it will stay that way, though. As an FYI, you can make the Edit Counter go faster by asking only for the data you need, using the checkboxes at https://xtools.wmflabs.org/ec. Best, MusikAnimal talk 16:27, 10 July 2019 (UTC)
Thanks! GiantSnowman 16:36, 10 July 2019 (UTC)
@MusikAnimal: can you do an 'simple counter' for article creations, which just shows the number rather than a full list? GiantSnowman 08:23, 11 July 2019 (UTC)
Good idea. I'll look into it! MusikAnimal talk 17:50, 11 July 2019 (UTC)

Request bot for auto archiving

Resolved

For talk page. See https://en.wikipedia.org/wiki/Talk:Nicotine_marketing QuackGuru (talk) 03:00, 12 July 2019 (UTC)

Alerts and alarms

Is there some facility within Wikipedia for me to receive a reminder when, for example, a block that I have made or a page protection that I have added has expired, or a deletion discussion that I have initiated has run its full time? Moreover, is there some facility within Wikipedia to create reminders generally? If not, can such a thing be created? bd2412 T 22:52, 10 July 2019 (UTC)

While this would be a godsend, e.g. for checking back on a talk page in 7 days or so, or allowing a 24-hour 3RR to expire, I am not sure it is MediaWiki's job to be tracking our reminders. That seems to present unnecessary load to the servers for something that individual editors would best be equipped to track locally. I have used Google Calendar and assorted alarm-clock apps to do this, so far. Elizium23 (talk) 23:06, 10 July 2019 (UTC)
@BD2412: this may be incorporated in the existing feature request: phab:T88781. — xaosflux Talk 23:12, 10 July 2019 (UTC)
Note though, this is related to phab:T2582 - which has been pending for 10 years. — xaosflux Talk 23:13, 10 July 2019 (UTC)
@Elizium23:, I don't know how big a server load this would necessarily represent. I already get all sorts of notices for things like being mentioned in a discussion or a link being made to a page I created. Obviously some system event is occurring when a block or a page protection expires, because the system knows to lift the block or unprotect the page. I suspect that implementing such a thing is much more a matter of prioritizing it than any effect on the servers. bd2412 T 23:16, 10 July 2019 (UTC)
  • A JS tool can be made to log certain temporary actions (and/or any kind of reminder you want) to an userspace subpage and serve you reminders based on that. Noting that, the JS datetime implementation is... almost nonsensical, at best. So, kudos to anyone who does. Alternatively, and this is easier, you can use Siri/Assistant, does seem like a better choice, but it'll mix your onwiki/offwiki life. --qedk (tc) 05:49, 12 July 2019 (UTC)

JSON error on Template:Infobox book series

Not sure what's going on, but I can't even make a dummy edit to Template:Infobox book series since it has a JSON error somewhere. I want to make an improvement to the template, but can't due to the error. Can anyone help? Steel1943 (talk) 21:48, 11 July 2019 (UTC)

I think I fixed it. --Gonnym (talk) 22:28, 11 July 2019 (UTC)
@Gonnym: Yep, I can at least do dummy edits now, so it's probably good. Thanks! Steel1943 (talk) 01:42, 12 July 2019 (UTC)
I'm pretty sure there was some backend change sometimes not long ago, as I had a lot of templates I could edit without that error that one day started blocking me. --Gonnym (talk) 06:47, 12 July 2019 (UTC)
If you aren't used to JSON, you can use this site to check for errors. Also useful in cases where you know JSON syntax but cannot find the error (lots of parameters, etc.) --qedk (tc) 08:03, 12 July 2019 (UTC)

Extracting the ToC list

Is there a way (via template or lua) to extract the ToC headers so they can be presented in a different style? What I mean by that is using a ToC style such as {{Horizontal ToC}} but without the ridiculously awful need to manually write each header, and later update it if it's changed. --Gonnym (talk) 14:19, 10 July 2019 (UTC)

@Gonnym: {{Horizontal ToC}} is a recent template. We already have {{Horizontal TOC}}, mentioned at Help:Section#Horizontal TOC. The names are confusingly similar. I have added a see also link [15] but more should probably be done. __TOC__ places the table of contents. It can be wrapped in styling like {{Horizontal TOC}} does. PrimeHunter (talk) 09:01, 12 July 2019 (UTC)
Yeah, I just found it by accident. There really is no reason to have the newer template. If a manual list of entries is somehow needed (and I really can't even see one valid reason why it would), that could added to the better template. --Gonnym (talk) 09:04, 12 July 2019 (UTC)

Minor edits

It's annoying that everytime one needs to check the "This is a minor edit" box. I would recommend making it the other way round and checking after making large edits instead. THE NEW ImmortalWizard(chat) 16:40, 10 July 2019 (UTC)

@ImmortalWizard: There was a user preference "Mark all edits minor by default". This was removed eight years ago following a discussion in which it was determined that the option was often misused. See Help talk:Minor edit/Archive 1#Should we remove the Preference setting to "Mark all edits minor by default" ? and phab:T26313. On that matter, this edit, which was the last one that you made before posting here, should not have been marked minor. Further information at WP:MINOR. --Redrose64 🌹 (talk) 15:33, 11 July 2019 (UTC)
Thanks Redrose64. I have now read the information page. THE NEW ImmortalWizard(chat) 16:50, 12 July 2019 (UTC)

Interwikilink

Hi, the interwiki link on article Aún soltera takes me to the Spanish article on Ian Fleming which does not seem correct...GrahamHardy (talk) 17:11, 12 July 2019 (UTC)

@GrahamHardy: it takes you to the main page of eswiki, and their TFA is Ian Fleming --DannyS712 (talk) 17:21, 12 July 2019 (UTC)
@GrahamHardy: Fixed it by removing the incorrect {{SPATRAcite}}. -- John of Reading (talk) 17:24, 12 July 2019 (UTC)

Some users think that youtube-dl is not notable enough for having its own article !

Can any user help to stop the speedy deletion request ? Thanks (https://github.com/ytdl-org/youtube-dl) -- Voldemort (talk) 11:49, 12 July 2019 (UTC)

This isn't the right forum for such a request; next time(it has already been deleted) try the Help Desk. 331dot (talk) 11:51, 12 July 2019 (UTC)
Voldemort, this is not the place to ask these questions, please ask this question on Teahouse. ___CAPTAIN MEDUSAtalk 11:52, 12 July 2019 (UTC)
There is a page at User:widefox/Youtube-dl if you want to help improve it to show WP:GNG. Wikipedia:Articles for deletion/Youtube-dl was the last formal debate. Graeme Bartlett (talk) 02:10, 13 July 2019 (UTC)

Fake edit conflicts when I edit talk pages

Pretty much most of the time for several days. On my iPad and my Windows laptop. they aren't real as my edits still appear. Doug Weller talk 16:57, 2 July 2019 (UTC)

@Doug Weller: didn’t you return back to edit form (in the browser) after saving an edit? Incnis Mrsi (talk) 17:02, 2 July 2019 (UTC)
@Icnis Mrsi: I'm not sure what you mean by edit form, but it's the nature of an edit conflict that you can't save. I can't save but my edit appears. Note that I just had a normal edit conflict with you and had to repost it in the upper text field as usual and save. Doug Weller talk 17:41, 2 July 2019 (UTC)
I should fix my ping. @Incnis Mrsi: thanks. It keeps happening, sometimes even on non-talk pages. Doug Weller talk 16:23, 6 July 2019 (UTC)
Are you double-clicking or double-tapping when you save? Sometimes the system can be confused into thinking that the save button has been hit twice. bd2412 T 17:42, 6 July 2019 (UTC)
This has been happening to me too on Windows with Chrome browser. It is new behavior, but I also remember seeing it in the past. I can't see any pattern for when it will happen and when it won't. Last time I saw these behaviors, it quietly stopped happening on it's own. ~Kvng (talk) 15:44, 12 July 2019 (UTC)
I had this for a few weeks, thinking it was maybe some server issue that would solve itself. It didn't. Before destroying my computer I reset my settings in the preferences and it solved itself. It must be a conflict with one of those, but I have no idea which one. --Gonnym (talk) 15:57, 12 July 2019 (UTC)
I haven't changed my preferences since before this started. Maybe there's a dodgy setting in there but not one that I've made recently. ~Kvng (talk) 16:01, 13 July 2019 (UTC)
I didn't either, but resetting it worked. You just have to bite the bullet if it annoys you as much as it did me. --Gonnym (talk) 16:17, 13 July 2019 (UTC)

Old revisions of image missing, but not deleted

At File:Dave_Carlascio_and_Family_Force_5.jpg, some old revisions of the image give a 404 error message. Thumbnails of those revisions are still included by the HTML page, and it links to where the old revisions would have been. From the revision notes, it looks like they were non-free, so probably should be deleted, but, well, they weren't deleted.

By comparison, here is what old deleted revisions of a file look like: File:City_of_Spokane_Seal.svg — "No thumbnail" note, and no broken links or images. So, the problem with Dave_Carlascio_and_Family_Force_5.jpg appears to be a software bug, disk corruption, or similar.

Could someone properly delete the old versions in this case, and investigate the cause of this to ensure other files (that shouldn't have been deleted) aren't corrupted, restoring the revisions from backup as needed? Thanks! —{{u|Goldenshimmer}} (they/their)|TalkContributions 22:12, 13 July 2019 (UTC)

watchlist inaccuracies again

My watchlist is again showing pages and diffs I have already seen, even though I have it set to show only unseen changes. Bolding of these pages in the list is also inconsistent. Anyone know why this exceptionally fun behaviour has returned? —Joeyconnick (talk) 22:50, 13 July 2019 (UTC)

Citation generator in Visual Editor not working for PMID or PMC numbers

Screencap of Wikipedia page.png

It works, most of the time, when you insert the doi number or the article title, but not at all for PMID or PMC numbers. Not sure where I should report this. --Anthonyhcole (talk · contribs · email) 05:05, 9 July 2019 (UTC)

It's a known issue involving the tool labs DNS being blocked or something, see T226088. @AManWithNoPlan: could probably explain in more details what the issue is. Headbomb {t · c · p · b} 05:13, 9 July 2019 (UTC)
Thanks Headbomb. Seems from this Phabricator discussion that no one knows what the problem is. It's been 3 weeks now, and I can't see that anyone has taken this on as their task - but perhaps I just don't understand how WMF technical people work. --Anthonyhcole (talk · contribs · email) 05:35, 9 July 2019 (UTC)
Anthonyhcole, there are literally 2 people discussing and analysing network traffic in that ticket... What more are you looking for ? A fix before understanding the cause of the problem is not possible. —TheDJ (talkcontribs) 07:26, 9 July 2019 (UTC)
As I say, I don't know how that Phabricator process works. If this is normal, fine. Seems a bit sluggish, though. --Anthonyhcole (talk · contribs · email) 08:23, 9 July 2019 (UTC)
Citation bot noticed it a month ago. It was mistakenly thought to be a DNS firewall problem in the Phab ticket. I determined that it was an issue with data sizes exceeding 4K within DNS messages, then someone else determined it was only a problem with secure dns. In summary, there are all sorts of standards and extensions to DNS and pubmed sends something that we don’t handle. Side note: from what I read, handling split messages over 4K makes some attacks easier. AManWithNoPlan (talk) 12:57, 9 July 2019 (UTC)
Thanks, man. I'm in awe of and grateful for what you tech guys can do, but impatient. It's a comfort knowing that this issue is firmly on your radar. --Anthonyhcole (talk · contribs · email) 04:36, 10 July 2019 (UTC)
This issue is now fixed. Thanks for reporting. —TheDJ (talkcontribs) 19:30, 10 July 2019 (UTC)
Thank you, TheDJ. --Anthonyhcole (talk · contribs · email) 07:15, 14 July 2019 (UTC)

Template:Documentation

There is a problem with tables which occurs while using template {{Documentation}} with parameter |content= (also known as inline documentation). Documentation breaks when it reaches {|. Could this be fixed with a change of Module:Documentation? Thank you! --  Gzhegozh talk 11:00, 14 July 2019 (UTC)

This is normal behaviour for templates: you cannot pass a Wikimarkup table through a parameter. I suggest that you make the documentation into a subpage, as is done with the majority of templates. If you state which template, I can carry out the appropriate edits. --Redrose64 🌹 (talk) 14:10, 14 July 2019 (UTC)
Well, is it possible then to make a subtemplate for inline documentation? Because I have got a following problem in the Ukrainian Wiki: few months ago I discovered that many templates there still contained old, Russian-style inline documentation translusions (Russians use their own documentation style, and there is a special template for inline documentation). So I replaced all those inline documentation transclusions with {{Documentation}} and the parameter |content=, but there were some cases with tables. Despite solving this problem by creating subpages, I think that it would still be helpful if a special inline documentation template is created. For example, in that link from a user's sandbox you can see a situation where it can be very useful to have such an option, as you don't need to create an extra docpage. That Russian template enables this option. --  Gzhegozh talk 15:03, 14 July 2019 (UTC)
So, this is not a technical issue with the English Wikipedia at all then. --Redrose64 🌹 (talk) 16:43, 14 July 2019 (UTC)
No, the same problem exists also in the English Wikipedia. --  Gzhegozh talk 17:03, 14 July 2019 (UTC)
Template parameters can contain pipes if they are written as {{!}} per mw:Help:Magic words#Other. The source will look ugly if it's done for all pipes in a whole table, but it works as shown below. See also the second bullet at Help:Template#Usage hints and workarounds. The Russian Wikipedia does not appear to have {{Wikitable}}. {{!}} is not a template but part of MediaWiki and works in all wikis. PrimeHunter (talk) 18:32, 14 July 2019 (UTC)
Hmm, this looks like a solution. Thank you! --  Gzhegozh talk 19:10, 14 July 2019 (UTC)
Documentation
Header text Header text Header text
Example Example Example
Example Example Example
Example Example Example

Page titles in italics

Hi. I've just noticed that all article page titles are suddenly showing in italics. Must have happened in the last ~5 minutes or so. Do a null edit on a page to see, if it's not rendering in italics already. I take it this is some temp. glitch? Thanks. Lugnuts Fire Walk with Me 12:51, 13 July 2019 (UTC)

It seems to be connected to {{Infobox}}, as the italics disappear when the infobox in an article removed. —Nizolan (talk · c.) 13:00, 13 July 2019 (UTC)
The culprit appears to be this edit by Gonnym, which is causing italic titles to show up all over the place. —Nizolan (talk · c.) 13:03, 13 July 2019 (UTC)
Thanks for letting me know. I didn't see anything while testing but I'll revert myself while I figure it out. --Gonnym (talk) 13:05, 13 July 2019 (UTC)
@Lugnuts: could you let me know what page you were looking at? --Gonnym (talk) 13:07, 13 July 2019 (UTC)
Hi. I noticed it at Hodan Nalayeh, but that seems to be fixed now. Lugnuts Fire Walk with Me 13:09, 13 July 2019 (UTC)
@Gonnym: I saw this on many pages - in fact every article I looked at, for example, 1337x. In many cases it also displayed this error in red at the top of the page: "Warning: Display title "<i>1337x</i>" overrides earlier display title "1337x" (help)." -- zzuuzz (talk) 13:21, 13 July 2019 (UTC)
@Zzuuzz: Could you give me a page where you had the conflicting displaytitle issue? --Gonnym (talk) 13:29, 13 July 2019 (UTC)
As above, 1337x (which is still in italics). Another was definitely xHamster (still displaying the error). -- zzuuzz (talk) 13:31, 13 July 2019 (UTC)
Thanks! (the just refresh the page as the code was reverted ~30 mins ago). --Gonnym (talk) 13:34, 13 July 2019 (UTC)
Testing the reported pages Hodan Nalayeh, 1337x and xHamster in preview with the infobox set to /sandbox produces no italics or errors (Just to be clear, I've made changes to the code, hopefully fixing the issue). --Gonnym (talk) 13:37, 13 July 2019 (UTC)
Also reported, Northern Paiute people[16] (but now fixed). I get no errors for 1337x and xHamster in preview without changing anything, but they still display as reported. -- zzuuzz (talk) 13:45, 13 July 2019 (UTC)
OK, a purge got rid of those errors. -- zzuuzz (talk) 13:54, 13 July 2019 (UTC)
Lugnuts and Zzuuzz, please see File:Holy Cow That's Weird.png and the WP:VPT archive where it appears. This report really strongly reminds me of that incident :-) Nyttend (talk) 23:09, 14 July 2019 (UTC)
Hehe, nice! Lugnuts Fire Walk with Me 06:47, 15 July 2019 (UTC)

Special:SuffixIndex

There is a page Special:PrefixIndex which is showing all pages starting with a certain name, but can someone create a similar page which would show all pages ending with certain characters? It would be a very useful tool. --  Gzhegozh talk 09:49, 15 July 2019 (UTC)

There is an old request at phab:T12808: "Introduce Special:Suffixindex". PrimeHunter (talk) 10:07, 15 July 2019 (UTC)

PHP7 details

See my latest ten contributions: some of the edits are tagged with PHP7, and others aren't, although I used the same browser on the same computer to make those edits, and all of them were done with my home wireless network. Any idea why three are tagged as PHP7 and seven aren't, instead of all ten being tagged or all ten not being tagged? The PHP7 page says Replacing the Beta Feature, since March 2019 a percentage of all production traffic has been randomly assigned to use PHP instead of HHVM. I would assume that this means that some of my sessions would use PHP7 and some wouldn't, but you can see that seven of those edits came in one session, yet exactly two of the seven edits used PHP7. Is every single edit randomly assigned or randomly not-assigned to use PHP7? Nyttend (talk) 21:10, 14 July 2019 (UTC)

Nyttend, a percentage of your requests, not of your sessions indeed. —TheDJ (talkcontribs) 07:24, 15 July 2019 (UTC)
What's a request? Is it an edit, or a page request (i.e. my computer asks the server to send a page), or something else? Nyttend (talk) 10:44, 15 July 2019 (UTC)
Nyttend, any communication your browser makes with the servers. For a page, that is usually dozens of requests (each image is a separate request for example). For an edit, it is a single request. —TheDJ (talkcontribs) 11:15, 15 July 2019 (UTC)

Whist marker - such a popular article!

See Talk:Whist marker, for the views this trifling monograph has attracted over time - i.e. very few until suddenly 100,000 in one day! Do we have any ideas why this might happen? (I have seen previous hadwavey "bot" explanations, of similar phenomena, do we have anything concrete?)

All the best: Rich Farmbrough, 21:34, 14 July 2019 (UTC).

@Rich Farmbrough: the additional view stats report this is from "mobile web" user clients. It certainly could be some sort of "bot" (not a wikipedia bot, a web bot) that is not presenting as a bot. For a few reasons (primarily privacy) detailed reader information is not available except to developers. — xaosflux Talk 21:59, 14 July 2019 (UTC)
It's not merely mobile web. Mobile app and desktop had similar jumps, although smaller:
Date Mobile web Mobile app Desktop Total
1 July 1 0 0 1
2 July 0 0 4 4
3 July 2 0 1 3
4 July 2 0 3 5
5 July 5 0 4 9
6 July 94,411 529 13,246 108,186
7 July 36,762 371 5,309 42,442
8 July 1,799 52 512 2,363
So whatever's going on is presenting itself with all sorts of platforms. Nyttend (talk) 22:39, 14 July 2019 (UTC)
Just Reddit helping people figure out what their random junk is: [17]. Top comment links the Wikipedia article. Modulus12 (talk) 22:51, 14 July 2019 (UTC)
Ah, this is the modern equivalent of being slashdotted! Thanks! All the best: Rich Farmbrough, 14:49, 15 July 2019 (UTC).

How is the "Number of page watchers who visited recent edits" calculated?

Just curious. Neither Help:Page information nor Help:Watchlist say. Nardog (talk) 15:44, 10 July 2019 (UTC)

@Nardog: not sure, but the API docs describe it further as the number of watchers of each page who have visited recent edits to that page. — xaosflux Talk 15:54, 10 July 2019 (UTC)
Looking at the code, it seems that it skips watchers where the "updated since your last visit" indicator on the history page would show for revisions more than 180 days older that the most recent revision of the page. For example, if the most recent revision of a page is 1 April 2018, it'll skip any watchers who would see the marker on revisions from 3 October 2017 or earlier. Anomie 13:48, 11 July 2019 (UTC)
@Anomie: Thanks. Could you point to where that code is ? I don't know jack about PHP but it seems to me InfoAction.php and the variable "RCMaxAge" have something to do with it, but I could be far off. Nardog (talk) 16:37, 12 July 2019 (UTC)
@Nardog: You're in one of the right files. The actual database query happens at WatchedItemStore.php lines 366–382, called from InfoAction.php line 775 and ApiQueryInfo.php line 927 with a cutoff time based on $wgWatchersMaxAge. $wgRCMaxAge is involved in counting the number of "recent" edits, for a different threshold of "recent". Anomie 11:31, 13 July 2019 (UTC)
Thanks, edited Help:Page information. Nardog (talk) 15:41, 15 July 2019 (UTC)

Watchlist

Is there an easy way to remove all pages which I did not create from my watchlist? Thank you, DuncanHill (talk) 10:21, 14 July 2019 (UTC)

@DuncanHill: - no. You could use Special:EditWatchlist/raw to get a dump of your watchlist, then get a query of pages you created and use an offwiki utility to subtract them, then replace the list with your new list. — xaosflux Talk 19:52, 15 July 2019 (UTC)
Seems like the data from this would be useful, but downloading a CSV seems to only give me a partial list. Eman235/talk 19:53, 15 July 2019 (UTC)

Editing News #1—July 2019

Read this in another languageSubscription list for this multilingual newsletter

VisualEditor-logo.svg

Did you know?

Did you know that you can use the visual editor on a mobile device?

Every article has a pencil icon at the top. Tap on the pencil icon OOjs UI icon edit-ltr.svg to start editing.

Edit Cards

Toolbar with menu opened

This is what the new Edit Cards for editing links in the mobile visual editor look like. You can try the prototype here: 📲 Try Edit Cards.

Welcome back to the Editing newsletter.

Since the last newsletter, the team has released two new features for the mobile visual editor and has started developing three more. All of this work is part of the team's goal to make editing on mobile web simpler.

Before talking about the team's recent releases, we have a question for you:

Are you willing to try a new way to add and change links?

If you are interested, we would value your input! You can try this new link tool in the mobile visual editor on a separate wiki.

Follow these instructions and share your experience:

📲 Try Edit Cards.

Recent releases

The mobile visual editor is a simpler editing tool, for smartphones and tablets using the mobile site. The Editing team has recently launched two new features to improve the mobile visual editor:

  1. Section editing
    • The purpose is to help contributors focus on their edits.
    • The team studied this with an A/B test. This test showed that contributors who could use section editing were 1% more likely to publish the edits they started than people with only full-page editing.
  2. Loading overlay
    • The purpose is to smooth the transition between reading and editing.

Section editing and the new loading overlay are now available to everyone using the mobile visual editor.

New and active projects

This is a list of our most active projects. Watch these pages to learn about project updates and to share your input on new designs, prototypes and research findings.

  • Edit cards: This is a clearer way to add and edit links, citations, images, templates, etc. in articles. You can try this feature now. Go here to see how: 📲Try Edit Cards.
  • Mobile toolbar refresh: This project will learn if contributors are more successful when the editing tools are easier to recognize.
  • Mobile visual editor availability: This A/B test asks: Are newer contributors more successful if they use the mobile visual editor? We are collaborating with 20 Wikipedias to answer this question.
  • Usability improvements: This project will make the mobile visual editor easier to use.  The goal is to let contributors stay focused on editing and to feel more confident in the editing tools.

Looking ahead

  • Wikimania: Several members of the Editing Team will be attending Wikimania in August 2019. They will lead a session about mobile editing in the Community Growth space. Talk to them about how editing can be improved.
  • Talk Pages: In the coming months, the Editing Team will begin improving talk pages and communication on the wikis.

Learning more

The VisualEditor on mobile is a good place to learn more about the projects we are working on. The team wants to talk with you about anything related to editing. If you have something to say or ask, please leave a message at Talk:VisualEditor on mobile.

PPelberg (WMF) (talk) and Whatamidoing (WMF) (talk) 21:24, 15 July 2019 (UTC)

Tech News: 2019-29

15:29, 15 July 2019 (UTC)

Don't waste your time trying to give feedback on the Android item; the "leave feedback" page doesn't let you add a new section and doesn't even have an edit button. Nyttend (talk) 21:43, 15 July 2019 (UTC)

WP:Dashboard on sidebar

I had an idea that the Dashboard should be on the sidebar below the Community Portal. I don't know how to add it locally, and I feel it should be sitewide anyway. Thoughts? Remagoxer (talk) 09:19, 16 July 2019 (UTC)

An administrator can add it to MediaWiki:Sidebar but I see no good reason. The first link in Wikipedia:Community portal is Wikipedia:Dashboard and it's linked twice more. PrimeHunter (talk) 10:04, 16 July 2019 (UTC)
You can add a Dashboard link below "Community Portal" for your own account with the below in your common JavaScript. PrimeHunter (talk) 12:13, 16 July 2019 (UTC)
mw.loader.using(['mediawiki.util'], function () {
  mw.util.addPortletLink(
    'p-interaction',
    mw.util.getUrl( 'Wikipedia:Dashboard' ),
    'Dashboard',
    'pt-dashboard',
    'Wikipedia Dashboard – Discussions and requests',
    null,
    '#n-recentchanges'
  );
});

Reward for a task!

There's a bounty of 50$ for anyone who manages to solve T27471 which concerns with adding a "delete associated talk page" checkbox to the delete form. The commit must be shepherded through code-review and merged to the master-branch; customized java-script based fixes are disallowed. ~ Winged BladesGodric 05:58, 17 July 2019 (UTC)

If anyone is interested, but no idea how to proceed, take a look at mw:How_to_become_a_MediaWiki_hacker. Some knowledge of LAMP is necessary. --qedk (tc) 06:37, 17 July 2019 (UTC)
I have made a related suggestion at MediaWiki talk:Confirmdeletetext#Add link to delete an associated talk page. PrimeHunter (talk) 10:08, 17 July 2019 (UTC)

"Publish changes"

Some time ago, the save button was replaced with a "publish changes" button. I work with an awful lot of new editors both on-wiki and off-wiki, and it is perhaps the most frequent source of confusion (after maybe why VE doesn't work on talk pages -- but that's a whole other deal with technical constraints). The awkward language choice of part of the interface shouldn't be something I have to bring up in every introduction to editing session I run (and shouldn't be something that confuses so many people even after bringing it up). Specifically, it comes up when new users are starting to edit in their userspace, in a sandbox, in a draft, etc. -- people see "publish changes" and hesitate because of the implications of "publish".

I'm sure there have been threads about this in the past, but I'm not sure the best way to search for this. Has this change been well-received otherwise? — Rhododendrites talk \\ 17:44, 11 July 2019 (UTC)

IIRC this change was made by WMF legal and is non-negotiable; they wanted to make it clear to editors that the moment one clicks that button, whatever is in your edit window becomes publicly available for anyone to view and not saved to a private userspace inaccessable to others, whatever the namespace being edited. It was a global change, so the discussions will I assume be on Meta. The announcement was here, so the discussions if there were any will be shortly before that. ‑ Iridescent 17:49, 11 July 2019 (UTC)
I recall seeing some discussion on Phabricator; I'll see if I can find links. JoJo Eumerus mobile (talk) 18:44, 11 July 2019 (UTC)
Actually the save button was changed to "publish changes" because of newbies. In UX testing newbies did expect the save button to work more like drafts. There was a need to change the text of the button to be more decisive. The bug behind this change is T131132, which explains this further.--Snaevar (talk) 19:32, 11 July 2019 (UTC)

Thanks all. From the sound of it, it seems like it makes most sense to use "publish changes" in most namespaces, but switch back to "save changes" for draft and userspace? Might be too much of a hassle to change, though (other than on a per-user basis with a script, of course, but that sort of defeats the point). — Rhododendrites talk \\ 16:32, 12 July 2019 (UTC)

Rhododendrites, I've been asking around about this since the change was made a few years back. So far, with one exception, the editathon folks tell me that the problem is that new users actually do understand this, and are intimidated by making their creations available to the general public. They want to clean it up and try to make it "perfect" before anyone else can see it. (That is, they're looking for a save button that doesn't publish their edits, which is not how our big blue button works.) I'd be very interested in hearing whether your users express similar sentiments.
Draft space and userspace are just as published as the mainspace. Whatamidoing (WMF) (talk) 23:27, 15 July 2019 (UTC)
@HJ Mitchell, Pigsonthewing, and RexxS: You often teach new users, but I don't know if you watch this page; please can you supply some feedback for Whatamidoing? --Redrose64 🌹 (talk) 23:44, 15 July 2019 (UTC)
OK, if there was such a hoo-hah about calling it "Save" then why does the ephemeral popup dialog still read "Your edit was saved." Should it not be changed to "Your edit was published!" for consistency? Won't someone be confused about whether the edit was saved or published, when she pressed "Publish" but it was "Saved" instead? Also, the ephemeral dialog is annoying to me: it covers screen real-estate, can't be dismissed early, and goes away without being acknowledged, as if we had time to spot and read it. Not a good experience at all. (EDIT: It apparently can be dismissed early, if your reaction time is FPS-trained enough to hit the tiny "X" before it fades and disappears (~5 seconds.) Elizium23 (talk) 14:03, 13 July 2019 (UTC)
Good point, Elizium23. I filed a bug report about that. Whatamidoing (WMF) (talk) 23:23, 15 July 2019 (UTC)
@Redrose64 and Whatamidoing (WMF): I've not found it an issue for new editors at editathons and workshops. I almost always guide new editors through their first edit, which is normally to their user page to say what topics they are interested in. I make a point of explaining that publishing it makes it visible to the whole world and caution against writing anything that they wouldn't want everyone to see. After that I use "publish" and "save" interchangeably and I don't believe I've ever found anyone confused by that. Hope that helps. --RexxS (talk) 15:08, 16 July 2019 (UTC)
I concur with the OP; it's a point of confusion, as happened with the last event i ran, earlier this month. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:28, 17 July 2019 (UTC)

Request to fix uw-paid1 and uw-paid2

Is there an easy way, perhaps a module or template, to add a "unregistered"/"registered" differentiation to {{uw-paid1}} and {{uw-paid2}}?

These important templates currently give wrong advice to IP editors; see Template talk:Uw-paid1#"User page" disclosure for IP addresses. ~ ToBeFree (talk) 14:00, 17 July 2019 (UTC)

I do not think those templates should be used to warn "IP addresses" as they're not meant for that. Paid editing is done with accounts that's why the disclosure is needed on userpages. If an IP address is persistently making promotional or suspicious editing, they should be reported to the appropriate noticeboard not be asked to disclose their client on their "IP userpage" which does not make sense. – Ammarpad (talk) 18:36, 17 July 2019 (UTC)

Can't edit caption

Timeline and map of the Seven Wonders of the Ancient World, including the Village pump (technical)/Archive 175

Hi. In our Colossus of Rhodes article is a timeline/map of the 7 wonders, which inadvertently implies that there were 8 of them (by referring to the Colossus "and the other 7" wonders).

I cannot find this caption in the text of the page, nor at File:Ancient seven wonders timeline.svg. Where is it? --Dweller (talk) Become old fashioned! 11:33, 17 July 2019 (UTC)

The image is called as a template Template:Ancient seven wonders timeline.svg. The wording is generated from the title of the page using it, and that in the template. DuncanHill (talk) 11:38, 17 July 2019 (UTC)
Ahhhh! Thanks. Fixed it. --Dweller (talk) Become old fashioned! 11:47, 17 July 2019 (UTC)
Glad to have helped. The curly brackets were the clew. {{This is a template, not a file}} DuncanHill (talk) 11:56, 17 July 2019 (UTC)
I missed that, because I'm a newbie technical buffoon. --Dweller (talk) Become old fashioned! 12:50, 17 July 2019 (UTC)
In your defense, it's a little confusing to include ".svg" in the template name. A search finds around 50 such templates. All the examined were created by Cmglee. A few of them have been moved to avoid confusion, e.g. [20]. PrimeHunter (talk) 13:49, 17 July 2019 (UTC)
Hi PrimeHunter, Apologies for confusing editors with the extension. I think having it is useful as it informs editors that, unlike other templates, it's purely an image thumbnail. Furthermore, it gives the image type (extension). Finally, the exact filename of the image is there, should anyone want to go directly to the image page. Thanks for helping out Dweller, regardless. cmɢʟeeτaʟκ 17:07, 18 July 2019 (UTC)
My ego thanks you for giving it a nice excuse. --Dweller (talk) Become old fashioned! 14:20, 17 July 2019 (UTC)
--> the caption on the image on the right here is hilarious. --Dirk Beetstra T C 13:26, 17 July 2019 (UTC)
I'm so bad with tech, I feel like a wonder of the ancient world myself --Dweller (talk) Become old fashioned! 13:44, 17 July 2019 (UTC)
Put the template on your userpage then! DuncanHill (talk) 13:48, 17 July 2019 (UTC)
 Done --Dweller (talk) Become old fashioned! 14:25, 17 July 2019 (UTC)

Edit filter to address Visual Editor bug (or common user error)

When a user drafts content with references in a sandbox, if using the Visual Editor it is necessary to enter edit mode before copying in order to retain the references. If the user doesn't copy from edit mode, the superscript links will be retained, but they will be links back to the original page (where the footnote anchor would be) without the reference itself. You can see an example of this in my sandbox:

This sandbox shows the first paragraph from the body of Wikipedia copied from edit mode.

This sandbox shows the same paragraph copied without entering edit mode.

It would be useful to have an edit filter or some other way to indicate when this happens. This is something I always tell new users, but which people very regularly forget about, just to introduce improperly formatted content into an article when trying to copy out of a sandbox. It seems like this could be easily detected by looking for superscript tags around a link to a different page. (Another common sign this happened is that "[edit]" appears inside a heading). Ideally, this would notify the user when they try to save, but an edit filter could be useful, too. — Rhododendrites talk \\ 18:25, 17 July 2019 (UTC)

@Rhododendrites: I suggest you move this to Wikipedia:Edit filter/Requested - where the volunteers that write filters can better asses it. It is possible to just make a "warn" filter as well. — xaosflux Talk 17:19, 18 July 2019 (UTC)

Template transclusion check down

Is it only for me or it is down? Here I get errors, and when trying to change language too. Please ping me, I don't want this page in watchlist because there are many changes... --Obsuser (talk) 21:58, 18 July 2019 (UTC)

Replacement of character references with actual characters

Beland (talk · contribs) has been replacing HTML character references with the actual characters they represent, using JWB. Is there a consensus or justification for this?

The replacements are concerning to me especially given they include characters in Private Use Areas, which IMHO are best left as references (frankly I don't think they should ever be used in articles in the first place, but still). And even if it was justified, wouldn't it fall under WP:COSMETICBOT? Nardog (talk) 21:50, 18 July 2019 (UTC)

Greetings! I was actually wondering whether I should be keeping Private Use Area HTML entities as they are. In my browser, I can see the Unicode point number of characters I don't have fonts for, but I'm not sure about other editors. This began as part of a spell checking and Manual of Style compliance project. I'm trying to bundle HTML entity cleanup with any punctuation cleanup on the same articles, so there aren't a bunch of minor commits. Right now I'm working on a list of only about 5,000 articles; in some cases, the HTML entities represent breakage so there's reader-visible cleanup to do, but you're right it's often only editor-visible. I've been getting occasional thanks for the entity cleanup, though; where done right it makes the wikitext a lot more readable, especially to editors who don't know HTML. (For example, café is a lot easier to read and edit than caf&#xC9;.) I had a conversation with some MOS editors before starting this, and there was a strong consensus in favor of converting numeric HTML entities where possible, unless the result would be confusing, and I made a list of confusing situations to exclude. Unfortunately, Unicode is a huge place and no one thought about potential problems with combining characters (I'm leaving those alone after editors on some Arabic-langugage-related pages rightfully complained) or the private use area or a handful of other things where I'm trying to building bottom-up consensus. I'm leaning toward PUA characters being too confusing to convert, so I'll add them to my exclusion list unless someone here would much rather see real characters than numeric entities? Ah, I see Template:PUA actually says not to convert them; that's also a page that will probably give a comprehensive list of articles they are used in, if anyone wants to go around pruning any unnecessary ones. -- Beland (talk) 23:14, 18 July 2019 (UTC)

Phantom edit: notifications and watchlist not updating

Greetings, I just discovered that an edit to a page I have watchlisted (Special:Diff/906832193) is apparently a phantom, as it did not appear on my watchlist and the ping did not trigger a notification. I already checked that the ping was done correctly, my preferences enable me to be notified by said ping, and that the page is indeed on my watchlist. Also, my watchlist has updates later than this edit, and I got notifications as recently as yesterday and have not knowingly changed any settings since. None of this explains the conspicuous absence of this edit from both my watchlist and notifications.

I therefore ask: has anyone else experienced such a problem, and is there a solution that either I have overlooked or can be implemented by a "reset" of preferences? Thanks, ComplexRational (talk) 18:58, 18 July 2019 (UTC)

Addendum: The edit in question is also not listed in the project's recent changes feed, probably suggesting that the problem is not on my end. ComplexRational (talk) 19:43, 18 July 2019 (UTC)
For the watchlist, I believe it is the same issue that was resolved earlier in January at phab:T211849, but I believe it still occur sporadically. I've experienced that some weeks ago but didn't have time to report the issue. You can report it again. For the ping, I am not sure why it didn't work. – Ammarpad (talk) 05:05, 19 July 2019 (UTC)
What you're describing sounds like phab:T225199. I'm looking into it. Legoktm (talk) 07:23, 19 July 2019 (UTC)

If you wonder how the servers work

Computer-kitten.jpg

https://www.youtube.com/watch?v=i0FTcG7PxzI has some information about how code gets deployed, if anyone's interested in learning more about Wikipedia's back end. Whatamidoing (WMF) (talk) 01:11, 16 July 2019 (UTC)

I'm honestly just a little disappointed the video actually had information on how code gets deployed, rather than footage of hamsters running over a keyboard. Someguy1221 (talk) 01:20, 16 July 2019 (UTC)
Nice! SD0001 (talk) 18:42, 20 July 2019 (UTC)

File Upload Wizard bug

In the File Upload Wizard, the radio boxes in Step 3 are invisible on my system. –LaundryPizza03 (d) 00:30, 20 July 2019 (UTC)

What is your system? Ruslik_Zero 08:27, 21 July 2019 (UTC)

Official website gives a 500 error

This isn't necessarily Wikipedia-related, but look at the Official website under "External links". After you click on the official website, the URL at the top of the screen is correct but there is a 500 error. When I go to the site and click on the correct link there, everything is fine. So I have changed the official website so it will work. — Vchimpanzee • talk • contributions • 16:59, 13 July 2019 (UTC)

@Vchimpanzee: from some testing, it looks like their website is just having an intermittent outage right now (got it on the 'new link' as well) - in any case I updated the offical website property on wikidata and set the template to use the WD value. — xaosflux Talk 17:16, 13 July 2019 (UTC)
I've had the problem for several days. Sometimes the link works and sometimes it doesn't.— Vchimpanzee • talk • contributions • 17:49, 13 July 2019 (UTC)
Xaosflux this is at least the third straight day with a 500 error from the link in the article. If there is going to be a link, it should work. From the site itself, a link to Dear Abby does work.— Vchimpanzee • talk • contributions • 18:24, 15 July 2019 (UTC)
@Vchimpanzee: you are not seeing a Wikipedia issue, you are seeing an issue with their web pages. To test I typed the URL in to a broswer, then opened and closed it 5 times, it failed three times. This is occuring for both the 'dearabby.com' link, and the 'uxpress.com' link. There is nothing we can do to fix their broken website. — xaosflux Talk 18:30, 15 July 2019 (UTC)
I don't have the problem when I go to Dear Abby from the uexpress site. I did contact them to tell them what is going on with me.— Vchimpanzee • talk • contributions • 18:50, 15 July 2019 (UTC)
Just got there, and refreshed my page 10 times, half of them failed. They could have some broken load balancer. — xaosflux Talk 19:03, 15 July 2019 (UTC)
I didn't try that many times but it worked for me both clicking on the link in the article and typing "dearabby.com".— Vchimpanzee • talk • contributions • 20:05, 15 July 2019 (UTC)

Just got this. Even though I used my real name in the request, I just happened to have used this name in my email address.

Hello Vchimpanzee,
We're aware of this issue, and the developers will correct as soon as they are able.
Please let us know if you have any other questions.
Thank you,
Andrews McMeel Universal Support
GoComics.com
PuzzleSociety.com
Uexpress.com

Vchimpanzee • talk • contributions • 20:20, 15 July 2019 (UTC) I'm still sometimes getting that 500 error but I have to wonder what would be wrong with just switching to the URL which that other site sends us to.— Vchimpanzee • talk • contributions • 17:49, 20 July 2019 (UTC)

@Vchimpanzee: I don't think you understand the technical problem - it isn't a problem with one of those domain names vs the other, it is a problem with the connection between the second domain name and the actual web server - as confirmed by the server owners in your response above. We've demonstrated that this happens with both URL's. This is not a problem with the English Wikipedia or with the mediawiki software in general. There is literally nothing else for us to do here. — xaosflux Talk 17:52, 20 July 2019 (UTC)
I was watching to see if I got any kind of response from the people fixing the software. My suggestion was that if the other URL does nothing but what is called "redirect" on Wikipedia, why not just bypass that?— Vchimpanzee • talk • contributions • 17:55, 20 July 2019 (UTC)
Sometimes website are broken and there is nothing to do but wait and hope. We could try to change all URLs to the redirect and/or adding archive links for non-working links. But since they said they are working on it, we should wait. -- GreenC 18:07, 20 July 2019 (UTC)
If the only problem were with the websites first 'redirect' page, then yet it would be fine to just bypass this - but please see above - the problem is not with the first link, it is with where they redirect it to. — xaosflux Talk 17:37, 21 July 2019 (UTC)

Template linking and transclusion check tool

Hello, does anybody know how/who can fix the Template linking and transclusion check tool JMHamo (talk) 11:51, 21 July 2019 (UTC)

Maybe author? (If he's active). MarMi wiki (talk) 18:04, 21 July 2019 (UTC)

Tech News: 2019-30

13:07, 22 July 2019 (UTC)

Transclusions with hashes at the beginning

I have recently become confused by some transclusions on sports seasons articles such as 2019–20 UEFA Europa League, which under the "third qualifying round" header just has the following code to produce the fixtures table, with no edit button as is usual on templates:

{{#lst:2019–20 UEFA Europa League qualifying phase and play-off round|Q3}}

I cannot find the corresponding template or module for this anywhere, can anyone give me a hand?

Thanks – filelakeshoe (t / c) 🐱 14:42, 22 July 2019 (UTC)

It is not a template, but a page - 2019–20 UEFA Europa League qualifying phase and play-off round. --Gonnym (talk) 14:46, 22 July 2019 (UTC)
(edit conflict) #lst, or more readably #section isn't actually a template but instead a magic word. The text it produces is stored at 2019–20 UEFA Europa League qualifying phase and play-off round, delimited by <section begin=Q3 />...<section end=Q3 />. * Pppery * it has begun... 14:47, 22 July 2019 (UTC)
(edit conflict) @Filelakeshoe: that is the abomination of mw:Extension:Labeled Section Transclusion - I really hate that extension, but some people like it! — xaosflux Talk 14:48, 22 July 2019 (UTC)
Thanks everyone! Yeah it's not very user friendly - an "edit source" link would be useful, but I guess not practical for all cases. – filelakeshoe (t / c) 🐱 14:55, 22 July 2019 (UTC)
Is there a better way? I've used it to transclude chunks of appropriate help text from Help:CS1 errors into the various error category pages in Category:CS1 errors. It's worked well for that. One source page so only one page to maintain. But if there's a better way, ...
Trappist the monk (talk) 15:01, 22 July 2019 (UTC)
@Trappist the monk: reusable text/markup is what birthed templates :D — xaosflux Talk 15:02, 22 July 2019 (UTC)
The real solution for tables will always be 1 data source, that you call from whatever page you are on and get the results placed into the table. That was supposed to be Wikidata but it seems that won't happen. Anything else is just a backwards way of trying to handle tabular data. See any TV award, which is written and independently sourced in the TV article, season article, actor article, the TV award itself and if the character that actor played has an article, that article as well. /off-topic rant --Gonnym (talk) 15:15, 22 July 2019 (UTC)
(edit conflict)
Oh, aye? But don't we, at en.wiki, proscribe article text in template space? Not my creation but the documentation for the cs1|2 templates is primarily handled by Template:Citation Style documentation and a plethora of sub-templates. It is a pain to maintain and that, in my mind, disqualifies it as a 'better way' than labeled section transclusion. So no 'better way' than templates?
Trappist the monk (talk) 15:20, 22 July 2019 (UTC)
Well "template documentation" isn't really "article text" is it? :D — xaosflux Talk 15:32, 22 July 2019 (UTC)
It's not, but the OP provided an example where labeled-section-transclusion is used in article text which avoids the no-article-text-in-template-space proscription. My csdoc example is intended to show that were article text allowed in template space, such use of templates can be unwieldy. So am I to understand that while you consider labeled-section-transclusion to be an abomination, you don't have a better solution?
Trappist the monk (talk) 16:11, 22 July 2019 (UTC)

Convert button in visual editor: is this new?

I noticed today that when you click on a reference which is a bare URL in Visual Editor, the edit box has a bottom section that says, This reference consists of just an external link. You can use the "Convert" button below to generate a properly formatted reference. Is this new, or have I just never noticed it before? -- RoySmith (talk) 22:54, 19 July 2019 (UTC)

No, this convert button message is not new. It was added at November 1, 2015. It is part of the citoid extension, which is bundled with VisualEditor.--Snaevar (talk) 09:16, 21 July 2019 (UTC)
Interesting, but weird that I've never noticed it before. Has something changed to make it more obvious? My usual process has been to copy the URL, create a new Automatic citation, then delete the old reference. It's just odd that I've never noticed the Convert button before, which does all that with so much less effort. -- RoySmith (talk) 16:45, 22 July 2019 (UTC)

Template help

Requesting help updating some wiki templates (non-Lua). I don't know how to do it. Can you help? Template_talk:Vcite_book#Support_for_archive-url_vs._archiveurl. Cross posted to Wikipedia:Requested_templates#Vcite_template_updates. -- GreenC 16:12, 22 July 2019 (UTC)

This is done, though {{vcite book}} could still use support for |archiveurl= and |archivedate= in case anyone wants to add it, examples in other vcite templates. -- GreenC 17:45, 22 July 2019 (UTC)

English Fundraising Tests

Dear all,

As I noted at the end of June, through the summer we will be running systems tests in preparation for the end of year fundraiser on the English Wikipedia.

This weeks test is scheduled for 1500 UTC Wednesday 17 July.

  • If you need to report a bug or technical issue, please create a phabricator ticket.
  • If you see a donor on a talk page, OTRS or social media having difficulties in donating, please refer them to donate@wikimedia.org.
  • If you have specific ideas to share, please feel invited to add them to our fundraising ideas page.

You can also send feedback regarding the fundraising campaign directly on my talk page.

Thank you in advance for your support. Seddon (WMF) (talk) 22:26, 16 July 2019 (UTC)

Just to bump this thread that we will be testing again 1500 UTC Wednesday 24 July. Many Thanks. Seddon (WMF) (talk) 20:28, 23 July 2019 (UTC)

Help with color overlap problem

Hello. On my talk page Mnnlaxer asked about a situation with the collapsed tables at the Israel men's national lacrosse team article. Because they are blue readers can't see the "show/hide" command. I think I've seen tables where they are highlighted in white but I have no idea how to make the change. Any help that can be provided will be appreciated. MarnetteD|Talk 18:41, 24 July 2019 (UTC)

MarnetteD, would it be okay if someone changed the background of the title from blue to green? You can do that by replacing all "#274da9" with "Green"--SharabSalam (talk) 19:01, 24 July 2019 (UTC)
I don't know SharabSalam. I have posted this this message Wikipedia talk:WikiProject Lacrosse#Input help to see if that wikiproject has any guidelines about the color of the tables in their articles. Thanks for the suggestion. MarnetteD|Talk 19:57, 24 July 2019 (UTC)
So many issues with that page... MOS:DONTHIDE, MOS:SMALLFONT, MOS:LINKCOLOR, MOS:HEADINGS - just from one section. --Gonnym (talk) 20:16, 24 July 2019 (UTC)
The color is blue because of the Israeli national flag color. It can change, but white "show/hide" would be better. If anyone can do some clean up on the MOS issues, please jump right in! Thanks, MarnetteD. --- Mnnlaxer | talk | stalk 04:27, 25 July 2019 (UTC)
{{hidden begin}} can replace | bodystyle = background:#FFFFE6; with | style = color:white; | bodystyle = background:#FFFFE6; color:black; as the below example. The style parameter also applies to the collapsed text so it's returned to black with bodystyle. I don't know whether this can cause issues for some users trying to replace normal black text with another color for themselves. The gadget "Use a black background with green text" appears to work as normal. PrimeHunter (talk) 09:24, 25 July 2019 (UTC)
Current code

Body text.

Suggested code

Body text.

Thanks PrimeHunter for figuring out the code and Gonnym for fixing MOS issues, including removing the hidden tables. Onward and upward with the arts! --- Mnnlaxer | talk | stalk 17:44, 25 July 2019 (UTC)

Request bot for auto archiving

For two talk pages. See https://en.wikipedia.org/wiki/Talk:Juul and see https://en.wikipedia.org/wiki/Talk:Pax_Labs QuackGuru (talk) 18:51, 25 July 2019 (UTC)

@QuackGuru: see Help:Archiving_a_talk_page#Automated_archiving for some code snippet you can put on a page to request bot archiving functionality. — xaosflux Talk 19:02, 25 July 2019 (UTC)

Local en.wp gadget "Allow navigation menus to be collapsed" causes sidebar items to be indented

Hi, i am Monniasza, and I have found bug in "Allow navigation menus to be collapsed" gadget. It causes sidebar to get malformed by icorrectly indenting its contents.

Steps to Reproduce

Go to preferences

Open "Gadgets" tab

Scroll to "Appearance"

Enable "Allow navigation menus to be collapsed"

Save changes

Open a new browser tab with Wikipedia and view it

Actual Results

Sidebar gets malformed on non-special pages

Expected Results

Navigation menus can be collapsed

Monniasza talk edits 08:54, 26 July 2019 (UTC)

What is your browser? What is your skin at Special:Preferences#mw-prefsection-rendering? It's indented but collapsing works for me in Google Chrome and Internet Explorer. I guess the indentation is intentional and wouldn't call it malformed. Are you saying that it doesn't work for you, or that you just don't like the indentation? The code is in MediaWiki:Gadget-CollapsibleNav.js and MediaWiki:Gadget-CollapsibleNav.css. Example without enabling the gadget in preferences: https://en.wikipedia.org/wiki/Example?withJS=MediaWiki:Gadget-CollapsibleNav.js&withCSS=MediaWiki:Gadget-CollapsibleNav.css. Example with the JavaScript but not the CSS (don't enable the gadget): https://en.wikipedia.org/wiki/Example?withJS=MediaWiki:Gadget-CollapsibleNav.js. Does that work better for you? PrimeHunter (talk) 09:44, 26 July 2019 (UTC)
I used Google Chrome browser, Vector skin. Monniasza talk edits 17:41, 26 July 2019 (UTC)

Undo script

mobileUndo script is an userscript created for mobile. It basically adds a button to revert the latest revision of an article while previewing a diff on the mobile website. Currently there isn't any undo feature in mobile version of the mediawiki software (as far as I know). It meets the general criteria for gadgets and I have the original creator's permission. Therefore I am proposing this script to be approved as a gadget. Should we approve of this script as a gadget? Masum Reza📞 12:01, 28 June 2019 (UTC)

Source codeHere (maintainer's copy, probably outdated)
Authormeta:User:FR30799386
FeaturesmobileUndo#Features
Note – The original creator of this script is blocked on en-wiki for sockpuppeting. But it is possible to reach him on meta-wiki.
Maintainer on en-wikiUser:DannyS712
My statement – I am a regular user of this script and have been using it since January, 2019. I can assure you that it possesses no threat to sensitive data of it's user. This is a very useful script for both editing and counter-vandalism. Making it a gadget will benefit many users editing on on mobile devices.

Questions

A list of questions and answers I believe would be useful.

1 Does it work if just included with no further configuration?
Yes. It works with no further configuration.
2 Is it configurable via personal common.js?
No. The current maintainer and the original script creator can provide more information.
3 Is it compatible with all major browsers in other words, cross-browser compatibility?
Yes. It is compatible with most major browsers on mobile except Opera mini. So far I've tested it's compatibility myself with Mozilla Firefox, Chrome, Chromium and Microsoft Edge.
4 Does it have any duplicates?
No, not on en-wiki except the current maintainer's copy. I've copied the script to my userspace on test wiki and meta wiki for performing tests. I am willing to delete those copies if necessary.
5 Does it require any special permission?
No. It even works with very new accounts. But I think we should not give its access to non-autoconfirmed editors to prevent misuse.
6 Which skins are compatible with this script?
Minerva Neue obviously as this is the only skin available on the mobile website.
7 Does it have cross-wiki compatibility?
Yes it has. I've tested this script myself on meta, Japanese Wikipedia, Wikidata and test wiki. It even generates edit summary in other languages on other wikis.

Discussion

I am willing to answer any questions you may have about this script (please ping me when you reply). Thanks. Masum Reza📞 12:01, 28 June 2019 (UTC)

@Masumrezarock100: Noting that I have synced my version with FR's on meta - I plan to make some optimization tweaks, but otherwise it should be good to go --DannyS712 (talk) 15:44, 28 June 2019 (UTC)
@DannyS712: Thanks Danny. What do you think the suggestion in my answer to the 5th question. Masum Reza📞 20:48, 28 June 2019 (UTC)
@Masumrezarock100: That can be set very easily if the script is a gadget (see mw:Extension:Gadgets) - but as just a user script, its harder to implement. I think its fine to leave it as it is, with the understanding that if it is enabled as a gadget it should, like twinkle, require autoconfirmed. --DannyS712 (talk) 20:50, 28 June 2019 (UTC)
@DannyS712: I see. Since it has cross-wiki compatibility, I highly suggest we make this a global gadget, what do you think? Masum Reza📞 20:59, 28 June 2019 (UTC)
@Masumrezarock100: well, I don't think those exist yet. --DannyS712 (talk) 21:06, 28 June 2019 (UTC)
@Masumrezarock100: Please observe how this RfC is currently listed at WP:RFC/TECH, and include a brief, neutral statement of or question about the issue immediately below the {{rfc}} tag, in accordance with WP:RFCST and WP:RFCBRIEF. --Redrose64 🌹 (talk) 12:08, 29 June 2019 (UTC)
@Redrose64: Done. I am very new in this RfC stuff. Thanks for pointing out my mistakes.Masum Reza📞 12:59, 29 June 2019 (UTC)
It's now worse, in that nothing is now displayed other than the link. You need a timestamp (if not a full signature) after the statement so that Legobot knows where to stop parsing: WP:RFCST does state "Failing to provide a time and date will cause Legobot to remove your discussion from the pages that notify interested editors of RfCs." and that is precisely what has happened here. At the moment, the first timestamp that it encounters is the one at the start of this "Discussion" subthread, by which time the statement is no longer neutral and certainly not brief. --Redrose64 🌹 (talk) 13:33, 29 June 2019 (UTC)
To @Alsee, Izno, North8000, DannyS712, Killiondude, and RainFall:, who participated in this discussion, How about importing this script to Mediawiki:Minerva.js or Mediawiki:mobile.js as only JavaScript that gets executed on mobile is at Mediawiki:Minerva.js and Mediawiki:mobile.js. Both of them are almost empty, so I don't see a problem here. Masum Reza📞 08:45, 13 July 2019 (UTC)
Fixing ping Rutilant Masum Reza📞 08:49, 13 July 2019 (UTC)
I don't have the knowledge of those things/terms to respond. North8000 (talk) 21:13, 13 July 2019 (UTC)

User survey

Please state your vote using '''Support'' or '''Oppose'''. Explain why if you choose the latter option. Masum Reza📞 05:07, 29 June 2019 (UTC)

I'm a bit baffled by your second sentence. By nature of this being an addition, the onus is on the supporters to explain why it should be added. However, in discussions like these, explanations from both sides would be useful to all. Killiondude (talk) 19:53, 29 June 2019 (UTC)
I meant that one must add a reason if they oppose it. Explanation from Support side is helpful as well but I am not explicitly asking them to state their reason. Masum Reza📞 22:15, 29 June 2019 (UTC)
To support: say "aye"; to oppose: rehash the Bible. —RainFall 08:07, 1 July 2019 (UTC)
  • Support - This would be really helpful, whenever I want to undo on my mobile I have to go to desktop view which is just a pain. SSSB (talk) 09:51, 7 July 2019 (UTC)
  • Instead we should ask the Foundation to Undo their removal of Undo from mobile. Creating a gadget to put Undo back is pretty absurd, unless it is the only way to get this fixed. I don't use mobile, and while I know the Foundation has badly crippled basic functionality on mobile I had no idea that they removed the undo link. That's pretty bad. If/when there's a clear majority here to ask the Foundation to fix this, give me a ping and I'll be happy to open a phabricator task and push for action. Alsee (talk) 13:27, 7 July 2019 (UTC)
    There's never been an undo button in mobile, basically, so I do not know why you think they removed it. See phab:T87609. --Izno (talk) 13:52, 7 July 2019 (UTC)
  • Weak support (invited by the bot) I favor simplicity vs. trimming seconds off of the "revert" time, but it looks like its inclusion is optional, and that lots of good work has been done. North8000 (talk) 13:04, 10 July 2019 (UTC)
  • Support as a non-default gadget. SD0001 (talk) 16:59, 21 July 2019 (UTC)
  • Well, it would be nice if jQuery or something was used instead of constructing long HTML strings directly. See also Musik's comments on his talk page, which I think should probably be addressed. Gadgets do run on the mobile skin, right? Enterprisey (talk!) 08:54, 27 July 2019 (UTC)

6 million articles already?

According to the Wikimedia Statistics page, we already have over 6 million articles. However, the main page says we're over 100,000 short. It seems to me these two values should be the same. Discuss? Samsara 09:25, 28 July 2019 (UTC)

Counter on the main page should be updated after every refresh. Why it isn't (in 2019)? Eurohunter (talk) 09:43, 28 July 2019 (UTC)
The main page counter uses {{NUMBEROFARTICLES}} which says 5,980,511 when this is rendered. It is updated several times daily. Samsara's link does not claim over 6 million. The vertical axis has no number at the top. It shows a small horizontal line when the axis ends but this is not at 6 million. It is around 5.9 million. Hovering over the right side of the graph says 2019-06-01 Content 5.884.993 for me. PrimeHunter (talk) 10:13, 28 July 2019 (UTC)
It has a tick mark on the left. If the tick mark does not indicate 6 million, it should not be there at all. Samsara 10:58, 28 July 2019 (UTC)
I agree but it's not something we can change here. The horizontal axis has the same issue. There is a mark at the end but it's not at 2020. In that case it's currently easier to see that the last interval is shorter than between the other marks. PrimeHunter (talk) 12:21, 28 July 2019 (UTC)

FWIW - perhaps to keep track of the number of Articles (and more) - is the following template => {{User:Dbogdan/WikipediaOverview}} - hope this helps in some way - if otherwise - *entirely* ok with me to rv/rm/mv/ce the template of course - in any case - Enjoy! :) Drbogdan (talk) 12:41, 28 July 2019 (UTC)

This template contains clickable links

WIKIPEDIA – The Free Encyclopedia

WIKIPEDIA – The 5th most popular site on the Internet, was launched on January 15, 2001 (1st edit by co-founder Jimmy Wales), is currently published in over 300 languages, has been freely available worldwide for 18 years, 10 months and 25 daysWikipedia has 51,542,106 total articles (5,980,511 in English (stats); 151,656 in Simple English) – *VITAL ARTICLES*: 101001000; *BEST ARTICLES*: 30,362; *POPULAR ARTICLES*: Last 24 hours; Last Week: Top25; Top5000 – and has (for the English version) 1,147 administrators and 135,647 active editors – as of 13:55, December 10, 2019 (UTC).

Estimated size of a printed version of Wikipedia (August 2010).
Click here for updated image using Encyclopædia Britannica volumes.

Code to access templates between Wikis?

QUESTION: Is there some code that can access a template residing on the English Wikipedia - from another Wikipedia like, for example, the Simple Wikipedia? More specifically, the template {{ScienceNews}} resides on the English Wikipedia - Question: Can this {{ScienceNews}} template be accessed from the Simple Wikipedia (without recreating/duplicating the template on the Simple Wikipedia)? If so, what code may be used? - tia - Enjoy! :) Drbogdan (talk) 16:01, 28 July 2019 (UTC)

Drbogdan, Interwiki templates are not currently supported on WMF wikis, mostly for performance and usability reasons. There's been some interest in developing the software to do this well for a long time (including in the 2015 Community Wishlist Survey where it was a top-10 wish), but nothing has developed out of it. --AntiCompositeNumber (talk) 16:18, 28 July 2019 (UTC)
@AntiCompositeNumber: Thank you *very much* for your comments - they're *greatly* appreciated - at least I'm now better informed about this - has my vote in developing this software if helpful - in any case - Thanks again - and - Enjoy! :) Drbogdan (talk) 17:00, 28 July 2019 (UTC)

Unable to edit my watchlist?

Problem: For some reason, I'm unable to edit my watchlist (via "View and edit watchlist" or "Edit raw watchlist" in https://en.wikipedia.org/wiki/Special:EditWatchlist ) - even after restoring all default settings in my "Preferences" - and regardless of the browser used (latest versions of "Brave"; "Chrome"; "Firefox" used; Windows10/1903; Dell-XPS 8900) - seems earlier, all was *completely* ok with editing the watchlist - but now the listing in my watchlist (in edit mode) seems to appear very, very briefly - and then disappears? - any help with this would be appreciated - in any case - Enjoy! :) Drbogdan (talk) 15:16, 27 July 2019 (UTC)

@Drbogdan: do you have a large (many thousand+) number of entries on your WL? Can you see if you can edit it using this safemode link? — xaosflux Talk 15:37, 27 July 2019 (UTC)
@Xaosflux: Thank you for your reply - and suggestions - seems I have => "You have 8,108 pages on your watchlist (excluding talk pages)." - is there a maximum limit for all to be ok? - also - the https://en.wikipedia.org/wiki/Special:EditWatchlist/raw?safemode=1 - seems to work ok at the moment - anything I should/could do to be ok again in "normalmode" (not "safemode") - in any case - Thanks again for your reply - and - Enjoy! :) Drbogdan (talk) 16:03, 27 July 2019 (UTC)
I've got 18,314 pages. I was over 25,000 a couple of weeks ago, and was able to edit it. DuncanHill (talk) 16:09, 27 July 2019 (UTC)
@Drbogdan: while there isn't a limit (well there probably is some super giant limit but you're not at it) WL's tend to get wonky over 5000 entries, so I really suggest you trim it if possible. Perhaps you have a bunch of old User:IPADDRESS ones from old feedback/warnings that you can remove. Also the safemode link disables scripts, such as the ones you have enabled in User:Drbogdan/common.js and User:Drbogdan/vector.js - you could try turning these user scripts off to see if there are any conflicts being caused. — xaosflux Talk 16:43, 27 July 2019 (UTC)
@Xaosflux: Thanks for your reply - it's appreciated - yes - trimmed some entries in "safemode" - but this did not work - remmed script in User:Drbogdan/common.js - as follows => <!---mw.loader.load('//meta.wikimedia.org/w/index.php?title=User:Hedonil/XTools/XTools.js&action=raw&ctype=text/javascript'); importScript('User:SD0001/oldSearchHistory.js');---> - not clear if this script is important for anything I'd miss at the moment - but yes - this worked *very well* and the WatchList edit seems to be *entirely* ok (in regular "normalmode") at the moment - Thanks again for your help with this - and - Enjoy! :) 17:17, 27 July 2019 (UTC)
@Drbogdan: .js pages use a slightly different comment code (I edited YOUR page with the right comment type - feel free to revert or do anything you want with it now) You can try turning those lines on back one at a time if you want them, then contact whomever's script you are loading if you would like them to work on it. — xaosflux Talk 17:21, 27 July 2019 (UTC)
@Xaosflux: Thanks for updating the js code with the right comment code(s) - it's appreciated - all now seems ok - Thanks again for all your help with this - and - Enjoy! :) Drbogdan (talk) 17:27, 27 July 2019 (UTC)
@Xaosflux: - BRIEF Followup - after several tests - seems the particular problem script line in the "User:Drbogdan/common.js" file is => /*importScript('User:SD0001/oldSearchHistory.js');*/ - the other script line seems ok - and somewhat useful at the moment - hope this helps in some way - in any regards - Thanks again - and - Enjoy! :) Drbogdan (talk) 17:51, 27 July 2019 (UTC) [NOTE: corrected code - Drbogdan (talk) 21:12, 27 July 2019 (UTC)]
@SD0001: - want to take a look? — xaosflux Talk 18:00, 27 July 2019 (UTC)
@Xaosflux and SD0001: FWIW - rm related CSS line from the "User:Drbogdan/common.css" file as well - /*@import url("//en.wikipedia.org/w/index.php?title=User:SD0001/oldSearchHistory.css&action=raw&ctype=text/css");*/ - see => "Wikipedia:Village_pump_(technical)/Archive_173#Hideous_history_page" section for more if interested - Enjoy! :) Drbogdan (talk) 18:13, 27 July 2019 (UTC) [NOTE: corrected code - Drbogdan (talk) 21:12, 27 July 2019 (UTC)]
@Xaosflux: In this edit you used the wrong format, it's either
/* ... */
or it's
// ...
the latter extending to the end of the line. --Redrose64 🌹 (talk) 18:38, 27 July 2019 (UTC)
@Redrose64: thanks, fixed though syntactically it worked (would interpret the same since it was on each line) :D — xaosflux Talk 20:01, 27 July 2019 (UTC)
Drbogdan, problem script fixed. SD0001 (talk) 16:27, 28 July 2019 (UTC)
@SD0001: Thank you *very much* for your comment - and help with this - may try the fixed script at my next opportunity - iac - Thanks again - and - Enjoy! :) Drbogdan (talk) 17:07, 28 July 2019 (UTC)
@SD0001: Checked the new fixed script - and the "WatchList Edit" now seems to work *very well* - Thank you for your help and efforts with this - they're *greatly* appreciated - Enjoy! :) Drbogdan (talk) 17:53, 28 July 2019 (UTC)

Popups - little white box above the link

When I point my cursor at a link, as well as the usual popup preview thingy, I also get a little white box appearing above the link. I think it started in the last hour or so. Is this a new feature? It doesn't appear to do anything useful, or indeed at all. DuncanHill (talk) 23:01, 28 July 2019 (UTC) Sorry should have said, monobook, Edge, Win10. DuncanHill (talk) 23:01, 28 July 2019 (UTC)

Template's FULLPAGENAME in documentation

Resolved

I'm looking for a template to produce the pagename of a template on both template's main page and template's doc subpage? That is, a template equivalent to following code:

{{#ifeq:{{SUBPAGENAME}}|doc|{{NAMESPACE}}:{{BASEPAGENAME}}|{{FULLPAGENAME}}}}

I could not find it in Category:Pagename manipulation templates, Category:Namespace manipulation templates. Template:Subpage other could be used, but only for root page templates — it won't work for userspace userboxes. And it will still require writing out the branches of the if. Is there such a template? —⁠andrybak (talk) 00:58, 29 July 2019 (UTC)

Maybe you can use {{TEMPLATENAME}}. It also removes other things. PrimeHunter (talk) 01:11, 29 July 2019 (UTC)
Thanks, that's exactly what I was looking for. Added the template to Category:Pagename manipulation templates. —⁠andrybak (talk) 01:51, 29 July 2019 (UTC)
@Andrybak: You may have been looking in the wrong place, since these are not templates - they are variables. --Redrose64 🌹 (talk) 08:13, 29 July 2019 (UTC)
{{TEMPLATENAME}} is a template. Its name is just chosen with all uppercase like magic word variables. PrimeHunter (talk) 09:07, 29 July 2019 (UTC)

Biography - authority control

On the biography for Paul Ricœur, the authority control box has the following text in red font: The RERO id 02-A000137666 is not valid. Can someone fix it? Thanks! 2607:FEA8:1DE0:7B4:F81D:4C1A:755A:7B9F (talk) 03:20, 29 July 2019 (UTC)

The ID itself is valid but actually all RERO IDs were categorized as invalid and I could not find what's causing this in Module:Authority control. Pinging Tom.Reding who added them today. – Ammarpad (talk) 07:25, 29 July 2019 (UTC)
@IP & @Ammarpad:  fixed.   ~ Tom.Reding (talkdgaf)  10:51, 29 July 2019 (UTC)

Google Maps can't find some decimal coordinates

Not a Wikipedia problem, as it occurs even when Wikipedia is not involved, but affects a lot of articles so it's worth raising here. Maybe somebody knows something about this, and in any case editors need awareness of the problem.

Google Maps says it "can't find" some, but not all, geo coordinates in decimal format. Example 53.111,-2.245, a location near Manchester UK. ―Mandruss  20:00, 27 July 2019 (UTC)

@Mandruss: Hmm, while "53.111, -2.245" isn't working, "53.11100, -2.24500" is. — xaosflux Talk 20:07, 27 July 2019 (UTC)
Hmm, indeed. ―Mandruss  20:10, 27 July 2019 (UTC)
That's interesting. I also played around with the precision and 53.11100, -2.24500 doesn't work for me. Killiondude (talk) 20:11, 27 July 2019 (UTC)
For an example of an actual affected article, see 2014 Isla Vista killings. Google Maps takes you to Isla Vista but displays the error and fails to place a marker. Appending one zero to the end of either lat or long fixes it.
At this link is a place to report errors in Google Maps, but it requires a Google sign in. I don't have a Google account and I don't care to create one for this purpose. Perhaps someone else could report this error and return any feedback here.
If we can't get this error fixed soon, we should start thinking about a change to the software we control to work around it. Accepting this for the indefinite term is out of the question in my opinion. ―Mandruss  12:20, 29 July 2019 (UTC)

{{collapsible option}} works incorrectly

I used this template correctly, but it doesn't work. Look at my signature, it contains afromentioned template. Monniasza talk Initial visibility: currently defaults to autocollapse

To set this template's initial visibility, the |state= parameter may be used:

  • |state=collapsed: {{Village pump (technical)|state=collapsed}} to show the template collapsed, i.e., hidden apart from its title bar
  • |state=expanded: {{Village pump (technical)|state=expanded}} to show the template expanded, i.e., fully visible
  • |state=autocollapse: {{Village pump (technical)|state=autocollapse}}
    • shows the template collapsed to the title bar if there is a {{navbar}}, a {{sidebar}}, or some other table on the page with the collapsible attribute
    • shows the template in its expanded state if there are no other collapsible items on the page

If the |state= parameter in the template on this page is not set, the template's initial visibility is taken from the |default= parameter in the Collapsible option template. For the template on this page, that currently evaluates to autocollapse. 10:25, 29 July 2019 (UTC)

@Monniasza: usage of templates in signatures is forbidden. —⁠andrybak (talk) 10:29, 29 July 2019 (UTC)
Template still works incorrectly .Monniasza talk 10:37, 29 July 2019 (UTC)
{{Collapsible option}} is designed to be used on template documentation pages. It outputs text that describes how the state parameter works in those other templates. It doesn't do any collapsing itself. And, as Andrybak said, you may not use any template in your signature. -- John of Reading (talk) 10:43, 29 July 2019 (UTC)
Yes, this is like wrapping your beer in a refrigerator manual and complaining it doesn't get cold. PrimeHunter (talk) 13:10, 29 July 2019 (UTC)

Tech News: 2019-31

21:42, 29 July 2019 (UTC)

Colors of class=wikitable?

Quick question, but I can't find the answer. What are the color codes for the default wikitable? For the grey background and the darker grey header? Thanks, Renata (talk) 02:33, 30 July 2019 (UTC)

#eaecf0
#f8f9fa

border:1px solid #a2a9b1; -- Begoon 02:40, 30 July 2019 (UTC)

Title italics magazines

So, see how the title Poetry (magazine) is italicized on the article page only in the magazine title, Poetry, how do I get the title for British Vogue to read British Vogue in the article title (again only italicizing the magazine's actual name)? Alanscottwalker (talk) 17:16, 30 July 2019 (UTC)

See this edit. -- WOSlinker (talk) 17:22, 30 July 2019 (UTC)
Thanks. Alanscottwalker (talk) 17:38, 30 July 2019 (UTC)

Signature with unclosed font colours

I need help working out how to fix the signature of Oddbodz (talk · contribs · deleted contribs · logs · edit filter log · block user · block log) (inactive since May). There is a black font at the end which renders following text black, and therefor invisibly to users of the green-on-black gadget. There are other font colors in the signature which, if the black is removed, then bleed over into following text. I tried to fix it here, but somehow buggered it up in another way. Help! Thanks, DuncanHill (talk) 15:43, 30 July 2019 (UTC)

done. * Pppery * it has begun... 15:47, 30 July 2019 (UTC)
Thanks - I'll point Oddbodz to that. Is it generally considered acceptable to apply the fix on pages where I see it causing problems? I don't like to edit another chap's signature, but I like not being able to read all the following comments even less. DuncanHill (talk) 15:49, 30 July 2019 (UTC)
@DuncanHill and Pppery: if that is coming from a signature, that isn't a good fix, since you wont be able to insert that closing font tag after the timestamp in a signature. That last font tag needs to be completely removed, and the others should be closed as a quick fix, see User:Xaosflux/sandbox75 - really font is deprecated and there are much better fixes if this person is still editing. — xaosflux Talk 15:52, 30 July 2019 (UTC)
DuncanHill, there are some bots that can fix this if it is on a lot of pages, you can ask at WP:BOTREQ. In general if you see one fix it, unless it is on a user_talk page you are other wise editing (as it will cause "new message" flag for the page owner). — xaosflux Talk 15:53, 30 July 2019 (UTC)
A search [29] finds around 740 cases. This is a job for a bot or AWB. It's always OK to close open tags in signatures. I would also merge the nested font tags to get Oddbodz - (Talk) (Contribs). If deprecated font tags stop working later then it's no big loss if old signatures are rendered as normal text. PrimeHunter (talk) 16:12, 30 July 2019 (UTC)
Thanks all - I don't know how to explain things in bot request terms. I mean, I could tell them what I told you here, but I wouldn't understand what I was on about if I tried to explain how your fix works or how it would be applied. DuncanHill (talk) 16:15, 30 July 2019 (UTC)
@DuncanHill: plain speak is fine there, something like "can one of the Linter signature fixing bots clean up Oddbodz's bad font tags?" with an example or 2. — xaosflux Talk 17:50, 30 July 2019 (UTC)
@DuncanHill: Based on Xaosflux's sandbox, I'm filing a BRFA now --DannyS712 (talk) 18:35, 30 July 2019 (UTC)
Thank you, much appreciated. DuncanHill (talk) 19:35, 30 July 2019 (UTC)

Connecting between pages

Hello everyone, how to connect between a template and a CSS page? Thanks! ⇒ AramTalk 12:04, 31 July 2019 (UTC)

@Aram: see Wikipedia:TemplateStyles. — xaosflux Talk 13:15, 31 July 2019 (UTC)
Also Category:Templates using TemplateStyles has lots of reusable examples. — xaosflux Talk 13:16, 31 July 2019 (UTC)

'Fun' with external link 'marks'

"Discovered" at Wikipedia talk:Principle of Some Astonishment#Random thing I noticed when somebody accidentally "nested" italic marks. The "nesting" obviously doesn't work, and is an error, because the italics are effectively 'closed' before the link text and 'opened' again after it, so you don't get italic text, but check out the funky "extra" link mark which gets added on the left of the link text...

  • ''[https://www.google.com ''normal text'']'' = normal text

These "variants" also produce similar "results":

  • '''[https://www.google.com '''''italic text''''']''' = italic text
  • ''[https://www.google.com '''''bold text''''']'' = bold text

-- Begoon 23:21, 29 July 2019 (UTC)

''[https://www.google.com ''normal text'']'' produces the html <i><a rel="nofollow" class="external text" href="https://www.google.com"></a></i><a rel="nofollow" class="external text" href="https://www.google.com">normal text<i></i></a>. The link is split in two links to the same target. The first arrow belongs to the first link which has no link text. PrimeHunter (talk) 14:48, 30 July 2019 (UTC)
Yeah, I'd looked at the html source and seen that. It's an oddity that this "error" produces a double-link like that, as I said at the talk page it's something I've never seen happen before in 10 years, but an odd "bug" nonetheless... Looks as though the wikitext 'parser' is somehow seeing both <i>...</i> 'portions' as separate 'entities' that each need linking, yet using the single href target address... -- Begoon 22:22, 30 July 2019 (UTC)

The wikitext parser produces misnested HTML: <i><a rel="nofollow" class="external text" href="https://www.google.com"></i>normal text<i></a>. HTML5 specifies that that "tag soup" be corrected in a manner that produces the empty link, and thus that's what RemexHtml does. Firefox 68 does the same if given that misnested HTML, BTW, and other modern browsers should as well.

Parsoid, on the other hand, seems to interpret that wikitext to produce <i><a rel="mw:ExtLink" href="https://www.google.com" class="external text"><i>normal text</i></a></i>, i.e. it doesn't recognize "misnested" apostrophe markup and link markup in the first place. Anomie 13:31, 31 July 2019 (UTC)

Switch transclusion on/off depending on how recently a template/subpage has been edited?

Do we have a template/magic word combination that can achieve the following? I would like Portal:Germany to display Portal:Germany/Germany news whenever that page has been recently edited, and not display it when it is too embarrassing (say, when the last edit is more than a month ago). Is there some easy way to achieve this? —Kusma (t·c) 10:01, 31 July 2019 (UTC)

{{#ifexpr:{{#time:U|{{REVISIONTIMESTAMP:Portal:Germany/Germany news}}}} > {{#time:U|-30 days}} | {{Portal:Germany/Germany news}}}} PrimeHunter (talk) 10:42, 31 July 2019 (UTC)
PrimeHunter, that's brilliant, thanks! —Kusma (t·c) 11:12, 31 July 2019 (UTC)
@Kusma: keep in mind, that dynamic page content is not guaranteed, especially for non-logged in users; rendered pages are cached and simply viewing the page as a reader does not force re-evaluation of templates. — xaosflux Talk 13:28, 31 July 2019 (UTC)
That's okay, the worst things that can happen here are that the portal wrongly doesn't display a refreshed "news" section or displays an outdated one that I would rather hide. Neither causes any serious problems. But it is a good point that we shouldn't rely on re-evaluation of templates/magic words for anything critical. —Kusma (t·c) 14:08, 31 July 2019 (UTC)

Connecting to wikidata?

What's the fastest way to see if there's an existing wikidata entry for an article? What I do now is open another window, navigate to wikidata.org, and copy-paste the article title into the search box. Surely there's a more streamlined (one-click?) way to do this? -- RoySmith (talk) 14:43, 30 July 2019 (UTC)

You can add a "Wikidata search" link for the page name under Tools with the below in your common JavaScript. PrimeHunter (talk) 15:18, 30 July 2019 (UTC)
mw.loader.using(['mediawiki.util'], function () {
  mw.util.addPortletLink(
    'p-tb',
    '//www.wikidata.org/wiki/Special:Search?search=' + encodeURIComponent( wgPageName ),
    'Wikidata search',
    't-wikidatasearch',
    'Search the page name in Wikidata',
    null,
    '#t-wikibase'
  );
});
You can also have a small box single line display under an article's title linking to the Wikidata entry (if one exists) by adding this script to your common.js. StarryGrandma (talk) 15:50, 30 July 2019 (UTC)
 // d:User:Yair rand/WikidataInfo.js
 mw.loader.load( '//www.wikidata.org/w/index.php?title=User:Yair_rand/WikidataInfo.js&action=raw&ctype=text/javascript' );
There should be a built-in "Wikidata item" link under Tools in the left sidebar, shown only if an item exists. @PrimeHunter: Do you not see this link? MusikAnimal talk 19:13, 31 July 2019 (UTC)
I know the link. I may have misunderstood the question. I thought it was about an easy way to search for a possible Wikidata entry to add the article to if it doesn't already have one. PrimeHunter (talk) 19:45, 31 July 2019 (UTC)
MA, yes, I think the question is whether an (other) item exist covering the same topic as an article, not whether the article is connected to a Wikidata item. --Izno (talk) 22:02, 31 July 2019 (UTC)
Thanks, and sorry for the noise. I read "existing wikidata entry for an article" as being a connected one. Furthermore many people don't even know about the links under Tools, so I wanted to make sure that didn't go unnoticed. MusikAnimal talk 15:08, 1 August 2019 (UTC)
The link is getting moved, but that's just an aside. --Izno (talk) 16:26, 1 August 2019 (UTC)

Broken template messing up page formatting

User:Paine Ellsworth, can you or someone please revert this edit at Template:Sidebar with collapsible lists? It is badly breaking *some* pages that transclude it. See Catholic Church and homosexuality. Mathglot (talk) 08:58, 1 August 2019 (UTC)

Wait, that's a hidden text-only change, so how could that possibly be the cause? But what else has changed, that would break dozens of older versions of the article, that were definitely not broken this morning? Here's version 861002525 from 500 edits ago; just as broken. I can't understand what's happened, here. Mathglot (talk) 09:03, 1 August 2019 (UTC)

The problem is (was) in {{Catholic Church sidebar}}, not {{Sidebar with collapsible lists}}. It was this edit by Royalistandlegitimist that broke the template. I advise Royalistandlegitimist to take advantage of the sandbox and testcases before making changes to the template. Nardog (talk) 09:11, 1 August 2019 (UTC)
Thanks, Nardog, for the fix! (Apologies to Paine; not only weren't they the cause of the problem, but that edit was (nearly exactly!) a year ago. I was too tired and in too much of a hurry to see clearly.) Mathglot (talk) 17:41, 1 August 2019 (UTC)

The notification button

Resolved: Fixed in the last update of MediaWiki. Nardog (talk) 05:45, 2 August 2019 (UTC)

Hi, so I am using my mobile.

  1. Just 1 hour ago, an editor posted a comment in my talk page.
  2. I got a notification.
  3. I didn't click on the notification,
  4. I went to the watchlist and see what triggered the notification. (I didn't click on the notification button.)
  5. I saw the comment diff.
  6. I went to another site, returned to Wikipedia again and saw that the notification button is still red,
  7. I clicked on it, surprisingly, I didn't see the comment that was posted to my talk page, I saw old notifications.
  8. I refreshed the page and the notification button returned red. I clicked on it and the red button disappeared and I refreshed it appeared again.
  9. Cleared the cache it didn't help still red.

So can someone help me to fix this? Thanks.--SharabSalam (talk) 21:52, 22 July 2019 (UTC)

  • Something I haven't tried; which is to trigger the notification again. I will ping a wrong random editor and see. This usually triggers a notification saying: “the ping was not sent because the user doesn't exist”. agsbshsisbsidsb.--SharabSalam (talk) 21:57, 22 July 2019 (UTC)
  • I got a notification, I clicked, read it, refreshed, the notification button returned red so it didn't help.--SharabSalam (talk) 21:59, 22 July 2019 (UTC)
    @SharabSalam: if you go to Special:Notifications is it there? Also, I have no idea who User:agsbshsisbsidsb is, will assume you just typed random characters for some reason? — xaosflux Talk 22:00, 22 July 2019 (UTC)
    I went there saw your ping. I returned here refreshed the page and the red button is still red.--SharabSalam (talk) 22:05, 22 July 2019 (UTC)
    Yes, it was random I tried to get a new notification and I got a new notification but the red button is not disappearing even after I saw the notification.--SharabSalam (talk) 22:09, 22 July 2019 (UTC)
What does clicking on the blue circle on the new notification do? Nardog (talk) 21:59, 22 July 2019 (UTC)
As I said I am using the mobile version of Wikipedia. I tried that too. I changed to desktop version clicked on the red button and the blue button. The blue button shows me old notifications like "user thank you" or something like that. Both the blue and the red button shows old notifications.--SharabSalam (talk) 22:04, 22 July 2019 (UTC)
No, I'm talking about the blue circle at the upper right of each notification. It toggles the read/unread status of the notification. If there's no blue circle and only empty circles then click on them a few times. Nardog (talk) 22:10, 22 July 2019 (UTC)
I had no idea about the blue circle. I had never clicked on it since I joined Wikipedia. I have lots of notifications that I didn't click on their blue circle but I haven't got an issue like this before. It's gonna take a while to make all the circles empty? Is that what I should do? Make the circles empty or blue? Thank you for this information about the blue circle. I had no idea about it.--SharabSalam (talk) 22:17, 22 July 2019 (UTC)
Thanks Nardog, the problem was fixed. I made all the circles empty. I always wondered why I get the number "+99" all the time on the notification button when I get one notification LOL today I learned.--SharabSalam (talk) 22:28, 22 July 2019 (UTC)
In the future, you can use "Mark al