Wikipedia:Village pump (technical)/Archive 173

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

Internet Archive link

The Internet Achive link at Martin Luther#External links returns 18 271 results. Adding |birth=1483|death=1546|sopt=t only reduces them to 18 265. Is there a way to reduce the results returned?

A direct link to the IA page with relevant filters  didn't work, maybe because the brackets in the link messed it up:

Jonund (talk) 16:22, 19 March 2019 (UTC)Reply[reply]

(I fixed the broken link by copying the URL (and link label) from Martin Luther#External links. --Pipetricker 18:40, 19 March (UTC))
Why do you want fewer results? --Pipetricker (talk) 19:09, 19 March 2019 (UTC)Reply[reply]
I wanted to exclude results like Martin Luther King, but now, as I scroll down the results, these do not apppear to turn up. Books in foreign languages do, however, turn up, and I think they should be excluded. Jonund (talk) 15:48, 20 March 2019 (UTC)Reply[reply]
@Jonund: As indicated in the sidebar, it is possible to filter the results by language. Jc86035 (talk) 15:55, 20 March 2019 (UTC)Reply[reply]

@Jonund:, cases like this are difficult because it is a common 2-word name who is popular. About the only way is to build a custom search that filters other known Martin Luthers. Because Internet Archive now uses an infinite scroll it's impractical to scroll to the end to see what might be there. The site Internet Archive Classic Search allows paged viewing to get deeper into the results. Looks like filtering out "luther king" helps a lot: 6,012. BTW I don't think we should filter English language because end-users can easily do that through the side bar. I've added this custom search to the template. -- GreenC 16:49, 20 March 2019 (UTC)Reply[reply]

CSD categories

Hi! Can anyone explain (or even fix?) this: {{CSD-categories}} shows 7 candidates for speedy deletion as "Abandoned drafts/AfC submissions"; Category:Candidates for speedy deletion as abandoned drafts or AfC submissions is empty. It's been this way for several days at least. Thanks, Justlettersandnumbers (talk) 18:56, 20 March 2019 (UTC)Reply[reply]

phab:T200402, phab:T202833, phab:T18036 - take your pick @Justlettersandnumbers: - category counts aren't reliable. — xaosflux Talk 19:14, 20 March 2019 (UTC)Reply[reply]

Infobox map tooltips

I noticed something in the infobox on the England, Wales, Northern Ireland, and Scotland articles (tho it might be on more). When you hover hover the the biggest "zoomed in" part of the map, the tooltips have some css in them (eg, Scotland's is Location of  .mw-parser-output .nobold{font-weight:normal}Scotland  (dark green) – in Europe  (green & dark grey) – in the United Kingdom  (green)). I tried poking around the wikitext used in the templates, but I can't seem to find the cause (might be due to how templatestyles injects Template:Nobold/styles.css, but that would probably require a phab ticket). --Terra (talk) 06:57, 18 March 2019 (UTC)Reply[reply]

It's due to the usage of {{nobold}} in {{Infobox_country_UK}}. I'm not a fan of adding templatestyles to inline and 'style only' templates like that. It makes no sense, because the CSS belongs with the template USING nobold, and the nobold template should be removed from a template that is using it really. —TheDJ (talkcontribs) 07:35, 18 March 2019 (UTC)Reply[reply]
I agree that in another template it makes sense for the surrounding template to take the entirety of the styling. That said, no one seems to have been interested when I tried to discuss how we should deal with CSS for metatemplates. So... --Izno (talk) 01:11, 21 March 2019 (UTC)Reply[reply]

WikiProject Yorkshire clean up list

Hello all, sorry about this but I am a complete novice when it comes to this stuff, hence why I am asking for help..... The clean-up list for WP Yorkshire has been going to a blank page with 502 Bad Gateway error for about five days now; anybody any ideas how to resolve this? Is it as simple as repointing the link? Help! *Clean up list is here. Thank you and regards. The joy of all things (talk) 19:33, 18 March 2019 (UTC)Reply[reply]

This has been sorted. Thanks anyway. Regards. The joy of all things (talk) 06:29, 21 March 2019 (UTC)Reply[reply]

Is there a way to have a vertical 'no wrap'

If you have something like

  • Header1
    • Item 1
    • Item 2
    • Item 3
    • Item 4
    • Item 5
  • Header 2
    • Item 1
    • Item 2
  • Header 3
    • Item 1
    • Item 2
    • Item 3

and you zoom at different levels, you will often have lists broken up over multiple columns. Is there a way to have everything on Header 1/Header 2/Header 3 kept together, much like {{nowrap}} prevents things from spilling over multiple lines, so you have something like

  • Header1
    • Item 1
    • Item 2
    • Item 3
    • Item 4
    • Item 5
  • Header 2
    • Item 1
    • Item 2
  • Header 3
    • Item 1
    • Item 2
    • Item 3


  • Header1
    • Item 1
    • Item 2
    • Item 3
    • Item 4
    • Item 5
  • Header 2
    • Item 1
    • Item 2
  • Header 3
    • Item 1
    • Item 2
    • Item 3

depending on your zoom level. Headbomb {t · c · p · b} 14:26, 21 March 2019 (UTC)Reply[reply]

I think using Template:No col break should do it. Galobtter (pingó mió) 14:36, 21 March 2019 (UTC)Reply[reply]
Doesn't seem to work. Headbomb {t · c · p · b} 14:52, 21 March 2019 (UTC)Reply[reply]
Actually, it works in Chrome, but has some issues in Firefox. Does the nocolbreak class need tweaking in MediaWiki:Common.css? Headbomb {t · c · p · b} 15:01, 21 March 2019 (UTC)Reply[reply]

Request for testing and feedback: Automated article section recommendations

The Wikimedia Research team is developing a new method for automatically recommending sections to add to stub articles. This method uses machine learning to suggest sections that could be added to an article, based on the sections that exist in other articles on similar topics.

We think this method could be useful for helping new editors find useful onboarding tasks to do. But before we build anything, we need to test the quality of the recommendations.

We are looking for experienced editors to evaluate these recommendations and provide feedback to help us improve them. We have built a testing tool that makes it easy to provide quick, survey-style feedback on the quality of the recommendations, and we are also interested in more detailed feedback on the project feedback talkpage.

If you are interested in giving us feedback, please get started by reading the instructions here and then start rating articles!

If you have questions about the project or more general feedback, you can reach us here.


Jonathan Morgan & Diego Saez-Trumper, Wikimedia Foundation Research

Jmorgan (WMF) (talk) 15:05, 21 March 2019 (UTC)Reply[reply]

List of pages using multiple infoboxes

Is there any list of pages using multiple infoboxes? What does the Wikipedia policy say about that? Capankajsmilyo(Talk | Infobox assistance) 15:33, 19 March 2019 (UTC)Reply[reply]

@Capankajsmilyo: I don't know of such a list. Normal wikitext searches won't work for this because most child infoboxes also have names beginning with "infobox".
I don't think there are any policies that would directly affect infoboxes in this way. Wikipedia:Manual of Style/Infoboxes does not have any guidance on this, and the language implies (but does not explicitly say) that one infobox is the default. Regardless, as you've probably noticed, in practice there are a number of pages which include more than one infobox, often to describe multiple topics or entities covered in the same article (e.g. Great Belt Fixed Link), or to separate information into groups (e.g. Georgetown University). Jc86035 (talk) 14:35, 20 March 2019 (UTC)Reply[reply]
This search which times out (for probably obvious reasons) is a short list of some multi-infobox pages. --Izno (talk) 01:16, 21 March 2019 (UTC)Reply[reply]

BRFA for Xinbenlv_bot

Dear Technical Wikipedians

I would like to ask for your opinion on a BRFA I am applying for User:Xinbenlv bot.

(by the way, should I use {{rfc}} instead?)

Xinbenlv (talk) 22:46, 21 March 2019 (UTC)Reply[reply]

Bug in timestamps - messages from the future :D

See File:Future - Bug in MediaWiki timestamps.png Posts available at my talk page for review (perm diff). Lol. I have time-travelling students :D --Piotr Konieczny aka Prokonsul Piotrus| reply here 10:15, 22 March 2019 (UTC)Reply[reply]

Piotrus, this is not in the wikisource though. Are you using the Comments in local time-gadget ? —TheDJ (talkcontribs) 10:37, 22 March 2019 (UTC)Reply[reply]
But the UTC time in the source is in the future. It's from a new user. I guess they haven't learned to sign with four ~~~~ which adds a time stamp. They probably wrote the time manually in their own time zone and copied "(UTC)" from another post without knowing the meaning. Maybe their teacher is to blame :D PrimeHunter (talk) 10:51, 22 March 2019 (UTC)Reply[reply]

Template:Popular pages

The Template:Popular pages does not appear to be generating monthly reports on Wikipedia:WikiProject Civil Rights Movement in the Statistics section. User:Mr.Z-man does not appear to be active. Does this bot continue to operate? If yes, then how do I generate monthly reports. Mitchumch (talk) 12:52, 22 March 2019 (UTC)Reply[reply]

@Mitchumch: Mr.Z-man's system has been superseded by meta:Community Tech/Popular pages bot. I have added WikiProject Civil Rights Movement with Special:Diff/888984428. Note there is also toolforge:massviews, e.g. [1]. MusikAnimal talk 17:36, 22 March 2019 (UTC)Reply[reply]

Behavior of settlement infobox

I noticed that the Template:Infobox settlement has two population fields: population_total, and population_density_km2. A person asked a related question at the help desk and when trying to answer the question, I noticed that these aren't text fields, and so you can't put a year in parenthesis ex: (2019) after the values, in case they are from different years. I tried to add citations after the numbers, and population_total allows it, but if I try to put a citation after population_density_km2, the field disappears. Is this the intended behavior? The article I tested this with is Jeju City if you want to see if you can duplicate this. TimTempleton (talk) (cont) 00:34, 22 March 2019 (UTC)Reply[reply]

Template talk:Infobox settlement is active. You can ask questions there. Some numeric infobox parameters are used for calculations, e.g. conversion between km2 and sq mi, or density = population/area. This requires pure numbers (commas may be stripped but not always). If they are not numbers then calculations may be omitted or produce errors, or the parameter may be ignored. If population_density_km2 is set to auto then it's calculated from population_total and area_total_km2 so those parameters cannot have a reference in this case. population_note can be used for a reference. If the infobox cannot convert density between km2 and sq mi then it appears to omit the field. I suppose it could be coded to just output whatever was put in and hope it makes sense. PrimeHunter (talk) 10:14, 22 March 2019 (UTC)Reply[reply]
Thanks PrimeHunter. Good explanation. 15:11, 22 March 2019 (UTC)TimTempleton (talk) (cont)Reply[reply]
@Timtempleton: This is why the |population_as_of= parameter was provided. There is also |population_footnotes= for the reference, and |population_note= should additional text be necessary. --Redrose64 🌹 (talk) 15:50, 22 March 2019 (UTC)Reply[reply]
Some recent examples of fixing population problems can be seen at Template talk:Infobox settlement#Merge problems. Johnuniq (talk) 23:05, 22 March 2019 (UTC)Reply[reply]

Tech News: 2019-12

19:43, 18 March 2019 (UTC)

About the "Partial blocks": My team isn't involved, so my information may be out of date, but this is supposed to let admins block someone from ≤10 specifically named pages, or from one namespace (e.g., no direct editing of articles or templates), so it might be useful for enforcing some types of TBANs in software. If the English Wikipedia wants to try this out, then I believe that the team will need proof of community consensus, and that if you don't specifically request it, then it won't be offered here until most of the other wikis have tried it out first (because scale). Whatamidoing (WMF) (talk) 19:34, 22 March 2019 (UTC)Reply[reply]
Being able to block editing based on one or more categories would be absolutely aces for topic bans.--Jorm (talk) 19:37, 22 March 2019 (UTC)Reply[reply]
That team has talked about it, but hasn't figured out how to make it happen yet. I suggested once that they consider planning for hidden cats like "Category:Pages covered by ArbCom case Example", rather than a regular content cat such as "Category:Cancer" (which might be added or removed by people who didn't understand the related effects). Of course, it wouldn't be perfect (for example, if you're banned from editing about a subject, then you're banned from creating pages on that subject, too, even though those new pages won't be in any category yet), but it might be helpful overall. Whatamidoing (WMF) (talk) 19:50, 22 March 2019 (UTC)Reply[reply]
Another danger is someone adding or removing the category to screw around with what someone else's block covers. True, in most cases that would lead to a swift block for the user/IP doing the screwing-around, but we do have plenty of wikilawyers around who might take "broadly construed" pretty broadly... Anomie 02:14, 23 March 2019 (UTC)Reply[reply]

Changes not being marked as read immediately

Seems to have started a few days ago. If I view a diff for a change made on whatever page, it still shows up as bold in my watchlist. Amaury (talk | contribs) 13:26, 22 March 2019 (UTC)Reply[reply]

Looks like it's taking 6 or 7 minutes for the read marker to be applied. Amaury (talk | contribs) 13:39, 22 March 2019 (UTC)Reply[reply]
See also § Green watchlist bullets do not turn blue. It's definitely been going on for days now. —Joeyconnick (talk) 18:48, 22 March 2019 (UTC)Reply[reply]
@Amaury: I find that if you remove the affected article from your watchlist temporarily (remove it, then add back ... with that "star" by the read, edit and view history tabs), it will clear the bold. Still annoying, but that's one workaround. MPFitz1968 (talk) 07:02, 23 March 2019 (UTC)Reply[reply]

New Tool: Whodunnit

I just threw together a git blame-like tool to help visualize who the text on a page came from. It could be useful for cleaning up after problematic editors, or just for the curious. It's still fairly WIP, but it works well enough. It's available at toolforge:whodunnit; the source is here. Gaelan 💬✏️ 06:57, 23 March 2019 (UTC)Reply[reply]

Don't we already have WP:WIKIBLAME for this? It's linked from each page history. --Redrose64 🌹 (talk) 15:09, 23 March 2019 (UTC)Reply[reply]
Redrose64, not quite the same thing—WikiBlame searches for a specific phrase, while my tool displays the text of the page, color-coded by the user that added it (and lets you hover over a piece of text to see the specific edit). Gaelan 💬✏️ 15:25, 23 March 2019 (UTC)Reply[reply]
Gaelan, See wikiwho. Galobtter (pingó mió) 15:32, 23 March 2019 (UTC)Reply[reply]
Galobtter, I hadn’t seen that before, but it does look fairly similar. I’ll give it a try when I get a chance in a few hours. Gaelan 💬✏️ 16:05, 23 March 2019 (UTC)Reply[reply]

ScienceDirect not correctly formatted by cite tool

Wikipedia:RefToolbar isn't interpreting ScienceDirect links correctly. For example, isn't being resolved or resolved to a "cite web" template when it should make "cite journal". Jo-Jo Eumerus (talk, contributions) 20:27, 23 March 2019 (UTC)Reply[reply]

Sounds like something to bring to WT:RefToolbar. Headbomb {t · c · p · b} 20:34, 23 March 2019 (UTC)Reply[reply]
Relayed there. Jo-Jo Eumerus (talk, contributions) 20:43, 23 March 2019 (UTC)Reply[reply]

Twinkle (redux)

xaosflux Talk 23:07, 23 March 2019 (UTC)Reply[reply]

Further customizing comments in local time

 – I cross-posted this at Wikipedia talk:Comments in Local Time‎ because I wasn't sure where I would get a response faster. I've gotten help there as well, and since that's the more appropriate venue, I'm going to close this to keep discussion to one place. Special thanks to PrimeHunter for responding here. Amaury (talk | contribs) 20:21, 23 March 2019 (UTC)Reply[reply]

I have the following in my vector.js: LocalComments = { dateDifference: false, dateFormat: 'mdy', timeFirst: false, twentyFourHours: false, dayOfWeek: false, dropDays: 0, dropMonths: 0 };

This changes signature display for me from 2:21 pm, 9 March 2019, Saturday (12 days ago) (UTC−8) to March 9, 2019, 2:21 pm (UTC−8). I want to further customize it to capitalize the AM/PM and remove the time zone (UTC -X), since I know that all times are in my time zone of Pacific. Is that possible? CC: Redrose64. They directed me here after I asked them on their talk page here here. Amaury (talk | contribs) 05:38, 23 March 2019 (UTC)Reply[reply]

The gadget uses MediaWiki:Gadget-CommentsInLocalTime.js which loads User:Gary/comments in local time.js. You could disable the gadget in preferences, copy the code to User:Amaury/comments in local time.js with a few changes, and load it with mw.loader.load(''); in your vector.js. It looks like the only needed changes are ' am' : ' pm' to ' AM' : ' PM', and remove two + ' (UTC' + utcOffset + ')'. You would not get future changes to the gadget. PrimeHunter (talk) 10:19, 23 March 2019 (UTC)Reply[reply]
Three minutes is extremely short to wait before cross-posting a non-urgent issue. You got the same code change in both places.[5] PrimeHunter (talk) 00:25, 24 March 2019 (UTC)Reply[reply]
@Amaury: Yes, I suggested you could ask at Wikipedia talk:Comments in Local Time ... if the gadget's talk page isn't fruitful, you may get better luck posting at WP:VPT. Comments in Local Time isn't on my watchlist, so at first I didn't realise that you had posted in both places. --Redrose64 🌹 (talk) 10:47, 24 March 2019 (UTC)Reply[reply]

Numbers OK in "Desktop View" - but Very Low in "Mobile View"?

Question: Numbers added to the "Template:NFPA 704 diamond" are *entirely* OK in the usual "Desktop View" (see, for example, the noted diamond and added numbers in the "Ammonia" article) - HOWEVER - the added numbers are all *significantly lower* in the noted diamond in the "Mobile View" of the same "Ammonia" article (esp with Windows 10/Dell8930/Chrome-Firefox-Opera Browsers) - Thanking you in advance for your help with this - Enjoy! :) Drbogdan (talk) 20:08, 24 March 2019 (UTC)Reply[reply]

(Downgraded caps, in GF and in good understanding with Drbogdan). -DePiep (talk) 20:30, 24 March 2019 (UTC)Reply[reply]
I guess you mean it varies whether the numbers are centered in the squares or appear in the lower part. I see the same. Alignment like this can be tricky. I posted the example {{NFPA 704 diamond|F=1|H=3|R=0|S=-}} above. Special:ExpandTemplates shows the complicated code it produces with an image map:
<div style="width:100%; background:transparent;"><div id="container" style="margin:0 auto; width:82px; font-family:sans-serif"><div id="on_image_elements" class="nounderlines" style="background:transparent; float:left; font-size:20px; text-align:center; vertical-align:middle; position:relative; height:80px; width:80px; padding:1px;">
<div id="diamond_image_and_mw_ImageMap" style="position:absolute; height:80px; width:80px;"><imagemap>
File:NFPA 704.svg|80px|alt=NFPA 704 four-colored diamond
poly 300   0 450 150 300 300 150 150 [[NFPA 704#Red|Flammability code 1: Must be pre-heated before ignition can occur. Flash point over 93 °C (200 °F). E.g., canola oil]]
poly 150 150 300 300 150 450   0 300 [[NFPA 704#Blue|Health code 3: Short exposure could cause serious temporary or residual injury. E.g., chlorine gas]]
poly 450 150 600 300 450 450 300 300 [[NFPA 704#Yellow|Reactivity code 0: Normally stable, even under fire exposure conditions, and is not reactive with water. E.g., liquid nitrogen]]
poly 300 300 450 450 300 600 150 450 [[NFPA 704#White|Special hazards (white): no code]]
desc none
</imagemap></div><div style="width:12px; text-align:center; position:absolute; top:12px; left:35px;">
[[NFPA 704#Red|<span style="color:black;" title="Flammability code 1: Must be pre-heated before ignition can occur. Flash point over 93 °C (200 °F). E.g., canola oil">1</span>]]</div><div style="width:13px; text-align:center; position:absolute; top:31px; left:15px;">
[[NFPA 704#Blue|<span style="color:black;" title="Health code 3: Short exposure could cause serious temporary or residual injury. E.g., chlorine gas">3</span>]]</div><div style="width:13px; text-align:center; position:absolute; top:31px; left:54px;">
[[NFPA 704#Yellow|<span style="color:black;" title="Reactivity code 0: Normally stable, even under fire exposure conditions, and is not reactive with water. E.g., liquid nitrogen">0</span>]]</div></div></div></div>
PrimeHunter (talk) 20:46, 24 March 2019 (UTC)Reply[reply]
Image shows the issue indeed. My thoughts: the creator (could be me ;-) ;-) ) used css styles that are discarded when in mobile view. -DePiep (talk) 20:51, 24 March 2019 (UTC)Reply[reply]
@PrimeHunter and DePiep: Thanks for your comments - is there some easy way of centering the numbers in both, the "Desktop View" and "Mobile View"? - or maybe - it may be too difficult - and - perhaps best - to leave well enough alone at the moment - iac - Enjoy :) Drbogdan (talk) 20:57, 24 March 2019 (UTC)Reply[reply]
I'd say: rebuild css/style from scratch, but don't distrust <imagemap> for now. It's these pesky little 'style=""' details mobile view ignores, per my first suspicion. -DePiep (talk) 21:05, 24 March 2019 (UTC)Reply[reply]

Tech News: 2019-13

18:04, 25 March 2019 (UTC)

Template Hadith-usc is broken because the source website is defunct

Template:Hadith-usc generates a URL pointing to a website at USC, but the USC website is permanently defunct since at least Oct. 2018. seems to have a complete archive of the USC website, and I suggest to modify the template to generate a URL based on, unless there are better sources. --Happyseeu (talk) 19:50, 25 March 2019 (UTC)Reply[reply]

@Happyseeu: Following up at Template talk:Hadith-usc#It's time to modify the defunct USC website with a functional website -- GreenC 06:06, 26 March 2019 (UTC)Reply[reply]

Almaty mislocated on map


Please see Talk:Bids for the 2022 Winter Olympics#Map issue. 2607:FEA8:1DE0:7B4:1426:377C:72E2:A4B6 (talk) 07:59, 26 March 2019 (UTC)Reply[reply]

Broken infobox

Hi! I see in the infobox of this article erroneous text "include" and "back to article". I can't figure it out, can you? 2001:14BA:980E:7700:0:0:0:8EA (talk) 12:48, 26 March 2019 (UTC)Reply[reply]

 Fixed, like this. --Redrose64 🌹 (talk) 12:59, 26 March 2019 (UTC)Reply[reply]
Thank you Redrose64, much improved! :) 2001:14BA:980E:7700:0:0:0:8EA (talk) 13:29, 26 March 2019 (UTC)Reply[reply]

Editing Wikipedia pages with vi

What is the keystroke sequence to initiate editing a Wikipedia page with vi? Michael Hardy (talk) 19:46, 23 March 2019 (UTC)Reply[reply]

@Michael Hardy: vi as in the *nix text editor? We don't have a 'edit in vi' mediawiki hotkey. You could install text editor extensions in to your browser. What browser are you using? — xaosflux Talk 20:08, 23 March 2019 (UTC)Reply[reply]
@Xaosflux: You're mistaken. It exists. I know it exists because I've entered it accidentally several times. Michael Hardy (talk) 21:07, 23 March 2019 (UTC)Reply[reply]
@Michael Hardy: lately? There used to be an option in Special:Preferences#mw-prefsection-editing for "use external editor", but that was removed 5+ years ago. See mw:Manual:External editors. This still required you to configure such an editor (such as vi) in your browser it didn't force a specific application on your computer to launch. You certainly could still have a browser extension for something similar. If anyone else has an idea, hopefully they will chime in and add or correct this below! — xaosflux Talk 21:15, 23 March 2019 (UTC)Reply[reply]
@Xaosflux: Within the past couple of days. And a bunch of other times within the past couple of years. One was maybe about a month ago. Michael Hardy (talk) 21:32, 23 March 2019 (UTC)Reply[reply]
See also Help:Text editor support (though again, these all look like they are on your browser client). — xaosflux Talk 21:40, 23 March 2019 (UTC)Reply[reply]
@Xaosflux: I'm using Google Chrome. I can't say I've ever thought about browser extensions. Is there a quick way to tell whether I have such a thing? Michael Hardy (talk) 21:47, 23 March 2019 (UTC)Reply[reply]
I've never seen it but there is a browser extension known as "it's all text" which I believe can be configured to use whatever editor you like when normally a browser edit window would open. Google that phrase for information. I just copy from the browser edit window to my editor, then copy back if I want to post what I edited. Johnuniq (talk) 21:49, 23 March 2019 (UTC)Reply[reply]
(edit conflict) (multiple) This feature was at Preferences → Editing, under the "Advanced options" heading, and was titled "Use external editor by default (for experts only, needs special settings on your computer)". It was always disabled for new and logged-out users, I'm guessing that Michael Hardy must have enabled it at some point after registering. It was removed from Preferences with the deployment of MediaWiki 1.22/wmf2 to English Wikipedia on 22 April 2013; AFAIK the removal of this preference also disabled it for all users who had previously enabled it. --Redrose64 🌹 (talk) 21:52, 23 March 2019 (UTC)Reply[reply]

@Redrose64: @Johnuniq: I'm using a laptop that I bought in 2016. I've never configured it for anything like this nor enable any such features. Michael Hardy (talk) 00:51, 24 March 2019 (UTC)Reply[reply]

To see whether any extensions are installed in Chrome: Click the three vertical dots at the top right, then "More tools" and "Extensions". PrimeHunter (talk) 01:25, 24 March 2019 (UTC)Reply[reply]
@PrimeHunter: ok, I've done that, and I see no such extension. But the fact remains: I've accidentally stumble into editing a page with vi several times. Michael Hardy (talk) 17:29, 26 March 2019 (UTC)Reply[reply]
@Michael Hardy: so just for reference, how do you launch vi normally? (Are you on a *nix variant machine)? Is it pure vi, or vim? — xaosflux Talk 01:34, 24 March 2019 (UTC)Reply[reply]
@Xaosflux: This laptop runs MS Windows, and I've installed vim. Michael Hardy (talk) 01:38, 24 March 2019 (UTC)Reply[reply]
I've been using lately; seems to work fine for this purpose. Enterprisey (talk!) 15:39, 25 March 2019 (UTC)Reply[reply]
I have played around with a few external editors tied to browsers, but -- at least to me -- cutting and pasting the source into an external editor, editing (and saving a copy -- occasionally having a copy comes in handy) and pasting it back works really well. Getting off-topic here, but for anyone using Vi or Vim, I highly recommend NeoVim.[10] (In particular. read the section "The Codebase".) [11][12] --Guy Macon (talk) 16:06, 25 March 2019 (UTC)Reply[reply]

Finding active Wikipedians by language

It's not possible to easly check which user in these categories was recentlty active. Is there list with users speaking certain language by activity? Eurohunter (talk) 18:47, 26 March 2019 (UTC)Reply[reply]

Strange Memory Behavior on Toolforge with Java

Hi all, when I run the following command on toolforge:

jsub -once -mem 2g -quiet -j y -o a.txt java -Xmx1G -version

And view the log file:

$ cat a.txt
Error occurred during initialization of VM
Could not allocate metaspace: 1073741824 bytes

I see an error related to (lack of) memory. Changing the memory values to something crazy seems to yield the desired output.

For example:

$ jsub -once -mem 8g -quiet -j y -o a.txt java -Xmx4G -version
$ cat a.txt

results in the desired output

openjdk version "11.0.2" 2019-01-15
OpenJDK Runtime Environment (build 11.0.2+9-Debian-3bpo91)
OpenJDK 64-Bit Server VM (build 11.0.2+9-Debian-3bpo91, mixed mode, sharing)

That leaves me with the following questions

  1. Is this a bug or the expected behavior?
  2. Is the latter example the best practice on toolforge these days (i.e. set crazy memory values)?

Thanks in advance. -FASTILY 00:23, 27 March 2019 (UTC)Reply[reply]

@Fastily: I have created phab:T219351 to investigate this issue.
Thank you to TheDJ for pointing this question out on irc. Broadly speaking bug reports and technical questions about Toolforge should be made via the cloud mailing list, the #wikimedia-cloud connect channel on Freenode, or Phabricator. The various wiki village pumps are not monitored for such reports because of lack of staff to watch pages in 800+ Wikimedia wikis. --BDavis (WMF) (talk) 01:26, 27 March 2019 (UTC)Reply[reply]
Sounds good, thanks! -FASTILY 03:38, 27 March 2019 (UTC)Reply[reply]

Problem with editing text after inline citation in Visual Editor (in Microsoft Edge)

There seems to be another bug in the Visual Editor (people tell me there are so many bugs in it). If you have an inline citation you cannot set the insertion point to edit any text to the right of the citation. Has anyone else noticed this? (talk) 11:01, 27 March 2019 (UTC)Reply[reply]

works in my browser.. Which browser and version of that browser do you use ? If you know how to, maybe make a screen recording that shows your problem ? —TheDJ (talkcontribs) 12:00, 27 March 2019 (UTC)Reply[reply]
If I open Equinox in the Visual Editor and try to edit the words after inline citation [7] the insertion point appears between "[7]" and "It" and refuses to move. This is on Microsoft Edge. I don't have the problem on Google Chrome or Firefox. (talk) 12:43, 27 March 2019 (UTC)Reply[reply]

The thing that makes things look like a paper letter

I remember fairly recently seeing Wikipedia newsletters with a background that looked like a page with a folder corner on the top left. I'm trying to find them again, and I've been searching for half an hour without much luck. Does someone know the CSS class that makes this happen, or failing that, an example of such a newsletter? Headbomb {t · c · p · b} 15:10, 27 March 2019 (UTC)Reply[reply]

@Headbomb: Are you looking for {{Letterhead start}}, {{Letterhead end}}, and Template:Letterhead start/styles.css? --DannyS712 (talk) 15:22, 27 March 2019 (UTC)Reply[reply]
That's the one, yes thanks! Headbomb {t · c · p · b} 15:28, 27 March 2019 (UTC)Reply[reply]

Typing consecutive spaces in the Wikipedia iOS app editor causes NBSPs, which can break templates

What happened here? Some spaces seem to be replaced by spaces of a different kind. After this edit, the items type and fatalities are no longer displayed in the infobox. --FredTC (talk) 07:54, 15 March 2019 (UTC)

Those were "raw" (meaning not encoded like &nbsp; or &#160;) non-breaking spaces (NBSP), and those don't work as separators in template parameter assignments like regular spaces do, hence the disappearing items – same thing happens if you replace those spaces with &nbsp;. --Pipetricker (talk) 10:22, 15 March 2019 (UTC)
But how did such spaces get there? I have no way to detect that they are there. When I edit the version I mentioned, and select/copy (ctrl-C) the code for the infobox, then paste it to a notepad.exe file, I cannot see a difference. Can I produce it by accident? How? --FredTC (talk) 11:13, 15 March 2019 (UTC)
Per the tag of the edit you linked to, in this case the culprit was the official Wikipedia iOS app.
If you want to report this as a bug in the iOS app, go to mw:Wikimedia Apps/Team/Bug reporting.
Some text editors highlight NBSPs (for example LibreOffice Writer) or have an option to do so (the Show all formatting marks, ¶, option in Microsoft Word). There are feature requests for MediaWiki at Phabricator:
--Pipetricker (talk) 15:10, 15 March (UTC), 23:27, 22 March 2019 (UTC)
I found another occurrence of this (another iOS app edit) and have submitted a bug report:
--Pipetricker (talk) 14:25, 22 March 2019 (UTC)Reply[reply]
I replied to "Can I produce it by accident? How?" at WP:VPM. --Pipetricker (talk) 16:48, 27 March 2019 (UTC)Reply[reply]
The translation tool also inserts the 160 nbsp character which I have removed several times while cleaning another of its bizarre habits, most recently at diff. Johnuniq (talk) 23:01, 22 March 2019 (UTC)Reply[reply]

Clickable button template on Slovak Wikipedia

Hi, can you please look at this? Thanks a lot, --Luky001 (talk) 18:59, 27 March 2019 (UTC)Reply[reply]

Pageviews error

The current featured article is William Matthews (priest). Clicking Pageviews on its history goes here. That displays "Error querying Pageviews API - Unknown". I don't recall using this tool before. Is that a known issue which clears up in due course, or should I hassle its devs? Johnuniq (talk) 02:06, 28 March 2019 (UTC)Reply[reply]

@Johnuniq: It works for me. Do you by chance have a privacy or adblock browser extension, such as Privacy Badger? That is a common cause for this tool failing. Otherwise, please share which browser and version you are using. Better, follow the steps at WP:JSERROR, which will give us even more debugging info. Best, MusikAnimal talk 02:43, 28 March 2019 (UTC)Reply[reply]
Sorry about the noise. I normally check unexpected issues in another browser and when I did that just now it worked. I have NoScript but I thought I had disabled it. There is some issue here, thanks. Johnuniq (talk) 03:09, 28 March 2019 (UTC)Reply[reply]


Hey, fails now, has failed for a day or two at least. Is there something wrong with wmflabs? I am totally out of it, tech-wise, but I like to check on my wp:AFDSTATS. --Doncram (talk) 01:09, 28 March 2019 (UTC)Reply[reply]

Explained above in #User interaction analyzer not working by the ever-excellent TheDJ. Basically, a thing that tools were running on changed and not everybody running tools changed yet. ~ Amory (utc) 01:19, 28 March 2019 (UTC)Reply[reply]
Seems fixed. (Thanks, Sigma!) Enterprisey (talk!) 05:45, 28 March 2019 (UTC)Reply[reply]

Page move fail

I tried to move Template:Civil Rights Movement-stub to Template:Civil-Rights-Movement-stub in order to correct a format issue. However, none of the contents of the old page was moved to the new page. Not sure what happened. Mitchumch (talk) 17:34, 28 March 2019 (UTC)Reply[reply]

@Mitchumch: may have been caching or job lag, it appears to be done now - are you still seeing a problem? — xaosflux Talk 17:36, 28 March 2019 (UTC)Reply[reply]
Yes, I do. Mitchumch (talk) 17:40, 28 March 2019 (UTC)Reply[reply]
@Mitchumch:  fixed the content moved, but the stub template ({{asbox}}) has some special rules - Special:Diff/889896029 solved it. --DannyS712 (talk) 17:36, 28 March 2019 (UTC)Reply[reply]
Thank you. Mitchumch (talk) 17:40, 28 March 2019 (UTC)Reply[reply]

Is there a string template/module that 'counts' the number of times a specific character/combination of characters in a string?

For example, if there something that could check

{{character count|\*|
Lorem ipsum
{{character count|e|
Lorem ipsum
{{character count|G|
Lorem ipsum

and return 3 in the first instance, 1 in the second instance, and 0 in the third instance? Headbomb {t · c · p · b} 13:42, 28 March 2019 (UTC)Reply[reply]

{{#invoke:Text count|main|text=|pattern=}} where pattern is a Lua pattern, not regex
{{#invoke:Text count|main|text=Lorem ipsum
* HIJ|pattern=%*}}
Script error: No such module "Text count".
{{#invoke:Text count|main|text=Lorem ipsum
* HIJ|pattern=e}}
Script error: No such module "Text count".
{{#invoke:Text count|main|text=Lorem ipsum
* HIJ|pattern=G}}
Script error: No such module "Text count".
Trappist the monk (talk) 14:03, 28 March 2019 (UTC)Reply[reply]
Thanks, that works. Headbomb {t · c · p · b} 18:08, 28 March 2019 (UTC)Reply[reply]

How to move to the new Debian Stretch job grid?

Greetings - On 23 March,I posted a notice here about enwp10 tool being down. Wondering if anyone here knows how to do this move? It's totally beyond my knowledge. Regards, JoeHebda (talk) 00:29, 26 March 2019 (UTC)Reply[reply]

Documentation is at wikitech:News/Toolforge Trusty deprecation, but migrating tools requires maintainer intervention. Pinging Kelson. The other maintainer listed is "tmoney" but I'm not sure what their username is here.
Just FYI, there are a LOT of tools that were not migrated to Stretch and probably broke today. Maintainers should have received numerous emails about this over the past two months. MusikAnimal talk 02:53, 26 March 2019 (UTC)Reply[reply]
Thx JoeHebda, things are under control on our side. Let us know if not. Kelson (talk) 05:04, 26 March 2019 (UTC)Reply[reply]
Today is the day (for the first time since the toolserver migration 5 years ago), where we will find out how many tools are not being used (broken but no complaints) and how many are not being maintained (complaints but no one to fix them)... —TheDJ (talkcontribs) 08:13, 26 March 2019 (UTC)Reply[reply]
 Done - Thanks to audiodude for completing this. Details here. Cheers! JoeHebda (talk) 19:37, 28 March 2019 (UTC)Reply[reply]

Is there a way to automatically collapse a table on mobile?

WP:CRAPWATCH displays fine on the desktop view, but loading up the mobile website seems to lose the collapsible tables (class="mw-collapsible mw-collapse"). One of the big reasons to make these tables collapsible is to make the mobile view more manageable, so it's a bit annoying that this doesn't work. Headbomb {t · c · p · b} 18:11, 28 March 2019 (UTC)Reply[reply]

If you are referring to the navbox, which is the only collapsible thing that I see on the page and which is not a table, the navbox class is not displayed on mobile. See WP:NAVBOX. – Jonesey95 (talk) 19:00, 28 March 2019 (UTC)Reply[reply]
@Jonesey95: do you not see "All 106 MDPI-related entries" in the very first row of the table (Rank 1, MDPI) ? Headbomb {t · c · p · b} 19:52, 28 March 2019 (UTC)Reply[reply]
Yeah, I suppose I should have searched the page for "show" and "hide" like a smart person. Sorry about that. Anyway, I think your question will need an answer by someone more familiar with the interface configuration files like MediaWiki:Common.js and the other files listed at Template:CSS and JS MediaWiki messages. My guess is that the collapsible show/hide stuff is not rendered on mobile for some reason. – Jonesey95 (talk) 21:12, 28 March 2019 (UTC)Reply[reply]
It's mostly to display automatically collapsible article content in articles for phones that have old browsers / browsers without javascripts. Wondering if there's a way to bypass that, and support collapsible tables for modern mobile browsers, which do support collapsible tables. Headbomb {t · c · p · b} 21:25, 28 March 2019 (UTC)Reply[reply]

Template:More citations needed section is a talk page?

Am I going crazy? Why is Template:More citations needed section a talk page? It's transcluded in a bunch of pages. Eman235/talk 17:46, 28 March 2019 (UTC) On a closer look I think it's because Anthony Appleyard messed up a page move. Eman235/talk 17:48, 28 March 2019 (UTC)Reply[reply]

@Eman235: Because of a page move by @Anthony Appleyard - I reverted the move, but now the prior template needs to be undeleted. I blanked the page, so for now it shouldn't show up on pages when it is transcluded. --DannyS712 (talk) 17:49, 28 March 2019 (UTC)Reply[reply]

Warning: Authority control with VIAF, and also double identities

While editing the article Henry Moskowitz (activist), a "Warning: Page using Template:Authority control with "VIAF", please move this to Wikidata if possible (this message is shown only in preview)." displayed on the screen. Also, there are two Template:Authority control assigned to this article and both have this warning message. I don't know how to fix this issue. Mitchumch (talk) 22:32, 28 March 2019 (UTC)Reply[reply]

This might be better asked at Template talk:Authority control. However, the issue is that the article contains {{Authority control|VIAF=190653772}} (and a second) and the warning is saying it should just be {{Authority control}} and the VIAF value should be placed at Wikidata. To do that, click "Wikidata item" in the toolbox on the left and play around with the VIAF setting. Problem: Wikidata already has VIAF=21135876 with a claim that it was imported from enwiki. Some checking of the VIAF values needs to take place to determine what's going on. There should be only one VIAF, and it should be at Wikidata. Johnuniq (talk) 22:57, 28 March 2019 (UTC)Reply[reply]
Both VIAFs are unfortunately valid. VIAF needs to be contacted. --Izno (talk) 03:30, 29 March 2019 (UTC)Reply[reply]
Izno, Mitchumch can also be documented at Wikipedia:VIAF/errorsTheDJ (talkcontribs) 08:47, 29 March 2019 (UTC)Reply[reply]
I added entry on Wikipedia:VIAF/errors to section "Two or more VIAF identities for the same article". The two VAIFs were added to article by blocked User:Richard Arthur Norton (1958- ) on 18:56, 28 January 2015. Mitchumch (talk) 11:37, 29 March 2019 (UTC)Reply[reply]
It looks like the bot that maintained that page no longer runs and stopped right around the time Wikidata started, but I don't see if a similar automated process was set up on Wikidata. --Izno (talk) 13:01, 29 March 2019 (UTC)Reply[reply]
That would be d:Wikidata:Database reports/Constraint violations/P214 - the equivalent exists for every Wikidata property. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:06, 29 March 2019 (UTC)Reply[reply]
The page exists, but it does not indicate any automatic provision of duplicate IDs to VIAF. --Izno (talk) 13:50, 29 March 2019 (UTC)Reply[reply]
Both VIAF and ISNI are federated databases. A close look at the two VIAF records or at the corresponding two ISNI records shows that they originate from different national libraries. One identity [13][14] comes from US and Israel, while [15][16] comes from the Netherlands, Ireland, and France. Each attributes a different birth year (1878 vs. 1880), which may have delayed ISNI in recognizing and resolving the duplication. A simple heuristic of referring to the lowest-numbered VIAFid (the former) will avoid having a duplicate Q number in such cases, and when the VIAF and ISNI deduplicates are eventually done, that lowest number will either be used or redirected. A more challenging problem arises when the VIAF or ISNI records conflate identities, as is almost unavoidable for common names, but this too is well understood by librarians.LeadSongDog come howl! 16:43, 29 March 2019 (UTC)Reply[reply]

Talk page button on Kindle gone

I often browse WP from my Kindle eBook reader, including Talk pages. Up until a few days ago, at the bottom of each article page there was a button to link to the Talk page (it does not appear on my desktop in Chrome). The Kindle browser does not display the usual WP top-of-page menu (talk history &c) so this was very handy. Now the <Talk> button no longer appears. Was this a recent WP change, or do I assume it was a Kindle update? --D Anthony Patriarche (talk) 12:11, 29 March 2019 (UTC)Reply[reply]

D A Patriarche, are you still logged in ? The button only shows if you are logged in. —TheDJ (talkcontribs) 15:20, 29 March 2019 (UTC)Reply[reply]
D A Patriarche I also happen to do that sometimes. Best solution could be to use desktop view by going to the very bottom in mobile view (I think it uses that by default) and pressing "Desktop". SemiHypercube 15:35, 29 March 2019 (UTC)Reply[reply]
Aha, that's it! For some reason I've been getting logged out recently despite checking "Keep me logged in". Thanks. --D Anthony Patriarche (talk) 18:07, 29 March 2019 (UTC)Reply[reply]


I forgot the password for my account and there's no email attatched, is it possible to put an email onto my account?Muur (talk) 18:28, 29 March 2019 (UTC)Reply[reply]

Muur as described here: Help:Logging in#What if I forget the password?TheDJ (talkcontribs) 20:02, 29 March 2019 (UTC)Reply[reply]

Broken clickable map

Something appears to have broken the {{Indian states and territories image map}} clickable map, and a quick check shows that this 2011 edit now throws up a "Invalid coordinate at line 61, must be a number." and subsequent versions don't render (prior versions still work; example). I am assuming this is a recent issue unrelated to an edit made to the particular template, since the error otherwise would surely have been spotted sooner. Anyone have an idea what the issue could be and how to resolve it?

Pinging @Begoon and RaviC: who have been involved with the template and are currently active. Abecedare (talk) 22:25, 28 March 2019 (UTC)Reply[reply]

Honestly I'm not too sure. The last time I edited the template was back in 2014, and it was working well back then. Looking at the revision history in 2011, the map was edited to add the shapes of states as polygons as opposed to before, when just a rectangle for a link was present for each state. That could be where the problem lies. I recall adding more polygons to the map using ImageMapEdit. --RaviC (talk) 22:34, 28 March 2019 (UTC)Reply[reply]
Ok. It was the "x.y" coordinate format that was causing the problem (don't ask me why!). Changing it to "x y" seems to have resolved the issue. Abecedare (talk) 22:54, 28 March 2019 (UTC)Reply[reply]
Is it working properly, even after that change? Hovering my mouse over various parts displays two different pointers - an arrowhead for non-sensitive areas, and a finger for sensitive areas. The sensitive areas do not cover the whole map, missing out the southern portions. Clicking on a sensitive area displays a criss-cross tangle of blue lines covering a roughly rectangular shape, before going to the article for the relevant state. --Redrose64 🌹 (talk) 23:14, 28 March 2019 (UTC)Reply[reply]
I think it is working "as written". The issue you point to is due to the fact that not all states have a clickable area defined by their polygonal boundary corresponding to their borders. Many states (eg, 7, 15 etc) have a clickable area defined by a much smaller rectangle that covers only (approx) the numerical index in the image. The way to resolve this would be for someone to trace the boundaries of the latter group of states and update the template code. The current version is non-ideal but functional. Abecedare (talk) 23:37, 28 March 2019 (UTC)Reply[reply]
It doesn't seem to be working properly for me as it used to before. I'm not sure why, but the polygons for some states (e.g. Maharashtra, Tamil Nadu) aren't there any more. Clicking near Gujarat brings up a hyperlink for the Siachen Glacier. Something has happened to the template and it probably needs to be rewritten now. --RaviC (talk) 00:01, 29 March 2019 (UTC)Reply[reply]
You are right! What I was interpreting as "x.y" coordinates, seems to be just the x- or y-coordinate to two or three decimal places. My converting them to "x y" made the result acceptable syntactically, but completely mucked up the location of the polygons. So undoing that edit.
It's possible that for some reason 'poly' now accepts only integer parameters; but would be good to know that defnitively before someone puts in the effort to repair or rewrite the template. Abecedare (talk) 02:13, 29 March 2019 (UTC)Reply[reply]
I think your guess was correct. It wasn't much effort to round all the poly co-ordinates to integers using a perl command on a text file of the wikitext - perl -i -pe 's/(\d*\.\d*)/int($1+0.5)/ge' filename, so I've done that. There's this recent gerrit commit that's probably related. -- Begoon 02:56, 29 March 2019 (UTC)Reply[reply]
@Begoon: Thanks for nailing down the diagnosis and the quick fix. Abecedare (talk) 03:36, 29 March 2019 (UTC)Reply[reply]
Abecedare, See also phab:T217087. A change in the behaviour of the php parser, caused these numbers to throw errors. Because of this, the sanitisation was changed to become more strict and instead of implicitly ignoring the floating part, it now creates errors. This also makes our image maps aligned with HTML behaviour of image maps. —TheDJ (talkcontribs) 09:19, 29 March 2019 (UTC)Reply[reply]
Thanks. Fwiw, I agree with your comment there that the rounding/typecasting should ideally happen after the scaling. Abecedare (talk) 14:35, 29 March 2019 (UTC)Reply[reply]
Yes, that loss of precision was my concern with rounding the co-ordinates to integers as I did - but since that was all the extension currently accepts I didn't have much option if we wanted the template to work at all. I've added those thoughts to the phab ticket. -- Begoon 01:27, 30 March 2019 (UTC)Reply[reply]
@Begoon: You clearly chose the right and only available option, and the extra decimal places most likely represented false-precision in this instance. My comment was more of a pedantic quibble over 'poly' (unlike 'rect') accepting only integer parameters, which makes the graphics less scalable in theory. Of course this would matter only for scale values >> 1 and I'd be hard-pressed to find examples on wikipedia where it makes a practical difference. Abecedare (talk) 01:42, 30 March 2019 (UTC)Reply[reply]
PS: Read Begoon's comment at phabricator and realized that we here are already on the same page and just preaching to the choir :-). Abecedare (talk) 01:44, 30 March 2019 (UTC)Reply[reply]
  • Note that, per the phabricator ticket, floating point co-ordinates now work again, so I've reverted to the version before any changes concerning this issue. -- Begoon 05:18, 30 March 2019 (UTC)Reply[reply]

Template banner illegible

Hi, Can someone amend Template:Assyrian Democratic Movement to make the banner at the top legible (or is it just my eyes/browser/weather conditions)... Thanks GrahamHardy (talk) 08:08, 30 March 2019 (UTC)Reply[reply]

 Done ‑ Iridescent 08:30, 30 March 2019 (UTC)Reply[reply]

Workarounds for a glitch in {{#time}}

Template:XFD backlog uses {{#time}} to derive the names of preceding months.

This has worked fine since I created the template two weeks ago, but now it is miscalculating the previous month.

  • {{#time: M Y |now}} → Sep 2022
  • {{#time: M Y |now - 1 month}} → Aug 2022
  • {{#time: M Y |now - 2 months}} → Jul 2022
  • {{#time: M Y |now - 3 months}} → Jun 2022

The second result, for now - 1 month, is wrong: it should be Feb 2019.

This looks to me like a bug in {{#time}}, probably connected to March being longer than February. If so, similarly glitches will occur at the end of several other months?

Please can someone suggest an elegant workaround? --BrownHairedGirl (talk) • (contribs) 17:21, 30 March 2019 (UTC)Reply[reply]

@BrownHairedGirl: so yes its a bug, but its not really a mediawiki bug, its a php bug, but it's also not really a "bug" but a "feature". Month math only operates on the "month value" so in this case it takes 2019-03-30 and sets it to 2019-02-30, then the php date fixer comes and "fixes" that to 2019-03-02. If you want to do month math, you have to program for it. — xaosflux Talk 17:40, 30 March 2019 (UTC)Reply[reply]
More, this is also because the #time parser uses entire datetimes, your filter doesn't lower the precision it just doesn't display that part of the output. — xaosflux Talk 17:42, 30 March 2019 (UTC)Reply[reply]
You might try this to lower the precision:
{{#time: M Y |{{#time:M Y|now}} - 1 month}} → Aug 2022
Trappist the monk (talk) 17:44, 30 March 2019 (UTC)Reply[reply]

Many thanks, @Xaosflux and Trappist the monk. That quick and elegant workaround does the job nicely. --BrownHairedGirl (talk) • (contribs) 18:12, 30 March 2019 (UTC)Reply[reply]

XFD backlog
V Jun Jul Aug Sep Total
CfD 0 0 0 14 14
TfD 0 0 0 2 2
MfD 0 0 0 0 0
FfD 0 0 0 2 2
RfD 0 0 2 25 27
AfD 0 0 0 0 0

Here's the fix implemented: [17].
And thanks to @Pipetricker: for fixing my typos above. --BrownHairedGirl (talk) • (contribs) 18:59, 30 March 2019 (UTC)Reply[reply]

Alignment issue at the signpost

If you write something like

{{Wikipedia:Wikipedia Signpost/Templates/Signpost-block-start-v2}}
{{Signpost series|type=sidebar|tag=openaccess|seriestitle=Open Access}}
{{Lorem ipsum|2}}
{{Wikipedia:Wikipedia Signpost/Templates/Filler image-v2|image=File:Circle.svg|size=300px|caption=An image!}}
{{Lorem ipsum|3}}
{{Wikipedia:Wikipedia Signpost/Templates/Signpost-block-end-v2}}

This gives the very crooked/bad looking/misaligned (and how bad it is depends on the zoom level)

An image!

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Curabitur pretium tincidunt lacus. Nulla gravida orci a odio. Nullam varius, turpis et commodo pharetra, est eros bibendum elit, nec luctus magna felis sollicitudin mauris. Integer in mauris eu nibh euismod gravida. Duis ac tellus et risus vulputate vehicula. Donec lobortis risus a elit. Etiam tempor. Ut ullamcorper, ligula eu tempor congue, eros est euismod turpis, id tincidunt sapien risus a quam. Maecenas fermentum consequat mi. Donec fermentum. Pellentesque malesuada nulla a mi. Duis sapien sem, aliquet nec, commodo eget, consequat quis, neque. Aliquam faucibus, elit ut dictum aliquet, felis nisl adipiscing sapien, sed malesuada diam lacus eget erat. Cras mollis scelerisque nunc. Nullam arcu. Aliquam consequat. Curabitur augue lorem, dapibus quis, laoreet et, pretium ac, nisi. Aenean magna nisl, mollis quis, molestie eu, feugiat in, orci. In hac habitasse platea dictumst.

Fusce convallis, mauris imperdiet gravida bibendum, nisl turpis suscipit mauris, sed placerat ipsum urna sed risus. In convallis tellus a mauris. Curabitur non elit ut libero tristique sodales. Mauris a lacus. Donec mattis semper leo. In hac habitasse platea dictumst. Vivamus facilisis diam at odio. Mauris dictum, nisi eget consequat elementum, lacus ligula molestie metus, non feugiat orci magna ac sem. Donec turpis. Donec vitae metus. Morbi tristique neque eu mauris. Quisque gravida ipsum non sapien. Proin turpis lacus, scelerisque vitae, elementum at, lobortis ac, quam. Aliquam dictum eleifend risus. In hac habitasse platea dictumst. Etiam sit amet diam. Suspendisse odio. Suspendisse nunc. In semper bibendum libero.

Could someone take at a look at {{Signpost series}} and tell it to behave nicely with Wikipedia:Wikipedia Signpost/Templates/Filler image-v2 and other v2 templates? Headbomb {t · c · p · b} 22:31, 29 March 2019 (UTC)Reply[reply]

If you're talking about openaccess sidebar adding padding-left:5em to Lorem, then use sidebar-v2 as a type. Too bad that it isn't mentioned in template documentation (or maybe it is in some other place?). --MarMi wiki (talk) 23:47, 30 March 2019 (UTC)Reply[reply]
@MarMi wiki: fantastic, that works! Headbomb {t · c · p · b} 23:51, 30 March 2019 (UTC)Reply[reply]

Capitalisation of module names

I am currently working on creating required modules and templates in Wikipedia Incubator. I would like to know the mechanism through which the name of a module is being converted into uppercase. Take for example, the template Template:View. In that template, the code actually invokes the module navbar. But when checking the list of modules being used from the option 'Templates used', I am able to see the module with the name 'Navbar'. When I checked the redirects present on the 'Page Information' of the module Module:Navbar, I didn't find anything. If anybody know that mechanism, please comment. Adithyak1997 (talk) 10:26, 31 March 2019 (UTC)Reply[reply]

MediaWiki automatically converts the first character to upper case in wikis where mw:Manual:$wgCapitalLinks is true, except if mw:Manual:$wgCapitalLinkOverrides overrides it for the namespace. [[example]] produces example which links directly to with no redirect. It's the same with transclusions and module invokations. It isn't even possible to create a redirect at the lowercase title because page names cannot start with a lowercase letter. There is a related feature where automatically redirects to but such redirects are not the same as wiki redirects and they are not used by wikilinks and transclusions. sets wgCapitalLinks to true for all Wikimedia wikis except jbowiki (Lojban Wikipedia) and Wiktionary. PrimeHunter (talk) 10:51, 31 March 2019 (UTC)Reply[reply]
But will that work for those projects in Incubator as well? Adithyak1997 (talk) 10:57, 31 March 2019 (UTC)Reply[reply]
It only works for the first character in the whole page name. Incubator uses subpages like incubator:Template:Wp/khw/Navbar for the Navbar template in the khw (Khowar) Wikipedia. At Incubator it can be called with {{Wp/khw/Navbar}} or {{wp/khw/Navbar}}, but not {{Wp/khw/navbar}} unless a redirect exists like at incubator:Template:Wp/khw/navbar. PrimeHunter (talk) 12:06, 31 March 2019 (UTC)Reply[reply]
Thanks a lot. Adithyak1997 (talk) 12:11, 31 March 2019 (UTC)Reply[reply]

Template:Percentage bar and Template:Notice interactions

 – {{Percentage bar}} has been fixed, so the 2nd of the below bars doesn't show the problem anymore.

The percentage bar, on its own, displays fine


However, if you put it in a notice box/mbox, it doesn't

If works fine if you don't use a relative value for width however


Can someone help? Headbomb {t · c · p · b} 15:04, 30 March 2019 (UTC)Reply[reply]

Wrap bar in div (<div style="position:relative">{{Percentage bar...}}</div> - inspiration):
--MarMi wiki (talk) 01:20, 31 March 2019 (UTC)Reply[reply]
MarMi wiki, Headbomb like thisTheDJ (talkcontribs) 13:26, 31 March 2019 (UTC)Reply[reply]

Magic word for the user's image size setting?

Is there a magic word or similar for a user's image size setting? What I'd like to do is set the size of the images in a gallery to the user's default. Hawkeye7 (discuss) 19:25, 30 March 2019 (UTC)Reply[reply]

No, because content cannot vary on potentially 'infinite' things (sizes), it's bad for caching. —TheDJ (talkcontribs) 13:36, 31 March 2019 (UTC)Reply[reply]

templatetransclusioncheck (on Toolforge) needs a new maintainer

Seems {{Squad maintenance}} in not working. See Template:Real Madrid CF squad "Check completeness of transclusions" and it says "404 Not Found". Pelmeen10 (talk) 12:13, 31 March 2019 (UTC)Reply[reply]

Pelmeen10, the maintainer of this tool is Chameleon222 a user who seems to have stopped editing in 2015. —TheDJ (talkcontribs) 12:55, 31 March 2019 (UTC)Reply[reply]
The source code of the tool is available at [Github]. If anybody is interested, they can adopt that tool and thus become a maintainer of that tool. Adithyak1997 (talk) 13:43, 31 March 2019 (UTC)Reply[reply]

User interaction analyzer not working

 – Amaury (talk | contribs) 01:08, 27 March 2019 (UTC)Reply[reply]

"503 Service Unavailable" Amaury (talk | contribs) 15:19, 26 March 2019 (UTC)Reply[reply]

Probably because Toolforge moved to new servers. User:Σ is this yours by any chance? GreenC 15:28, 26 March 2019 (UTC)Reply[reply]
In the more general, why does toolslab have to be so slow and/or crap? Every other day it's giving 404s and 501s etc. Can't the WMF spend just a percentage of its hard-earned (read: given), and provide us with the tools we need to actually improve the encyclopedia? I assume that's what the donations are given towards, rather than merely allowing various unnamed yet by no means unknown characters pissing about in Lear Jets Transatlantic Stylee [/RANT] ——SerialNumber54129 15:37, 26 March 2019 (UTC)Reply[reply]
Serial Number 54129, because we editors do crazy stuff ;) Seriously though, what people don't realise is that keeping things working requires investment by people. All maintainers of these tools received several emails over the last 4 months that they needed to do something because their software was running on 5 year old operating systems that had been deprecated for 3 years. And really in most cases the maintainers didn't have to do much, other than follow several instructions. They did nothing at all however and thus those tools are now down. I don't see how to fix that problem. If anything, this is a result of WMF continuously giving maintainers of tools maximum liberty, while they should have been more forceful 3 years ago to get people to put in the work of upgrading their software. —TheDJ (talkcontribs) 16:20, 26 March 2019 (UTC)Reply[reply]
Not to say there isn't a lot wrong with toollabs that can be improved, there most definitely is (but this is also happening, and if you are a toolcmaintainer it is notable noticeable). At the same time, there are many tools that haven't seen their official maintainer log in for several years, yet being used by thousands of people. The WMF is not an adoption agency for that code just because it runs on their servers. —TheDJ (talkcontribs) 16:22, 26 March 2019 (UTC)Reply[reply]
I'm glad to hear that you appreciate my work. I'm sorry if you feel that I have been shirking my duties, but I must clarify that I am not tech support at the WMF's beck and call.
The WMF is not an adoption agency for code, but the flip side of that coin is that we editors and tool maintainers have no obligation to do any more work than we want to. Personally, I'll keep doing what I've been doing. But as it is right now, priorities list wise, this will always sit comfortably below doing what it takes to put a roof over my head and keep the lights on. Which should give you one hint to "fix the problem", in my case at least. I hope this helps. Σσς(Sigma) 17:32, 26 March 2019 (UTC)Reply[reply]
Σ, oh don't get me wrong, that wasn't a value judgement of your work, far from it, it is an observation of how this works. This is exactly why often when Wikipedians say "we need more time", "you should give better announcements" etc etc. I note that it is pointless to do so, because volunteers won't do 'low prio' things until stuff starts breaking. Most volunteers just don't have the bandwidth to handle much of this and neither do I personally as a fellow volunteer expect them to (my hiatuses often stretch for months). Within the tech circles of Wikimedia this is also pretty much universally recognized. But that's also what makes these services completely different from the production level services. Having these tools unavailable once in a while is a sacrifice that needs to be made simply because WMF can't go and hire every tool developer fulltime to turn it into a production level service (although they have hired a sizeable portion of them through the years). Simply respecting things for what they are and then working from there to see how to improve them within those constraints is probably more fruitful than passing around blame. The fact is that our tools can virtually grow infinite in number, but our maintainers of them are not, nor usually have access to the tools of those who left. And after 5 years there is now a moment where that became unavoidably visible. —TheDJ (talkcontribs) 19:07, 26 March 2019 (UTC)Reply[reply]
+1 to TheDJ. The 404s/502s/whatevers are usually because of maintainer neglect. WMF Cloud Services merely provides the infrastructure for volunteers to host their tools. They are not and should not be responsible for maintaining code they didn't write. Yes the platform has problems, many of them, but all things considered it is in my opinion a pretty phenomenal service for being free. From my data, actual percentage uptime (at least on VPS) is somewhere between 3 to 4 nines. Many for-profit websites don't come close to that.
@Amaury: There is also toolforge:interaction-timeline which provides similar functionality. MusikAnimal talk 17:52, 26 March 2019 (UTC)Reply[reply]
Another one three. -- GreenC 18:43, 26 March 2019 (UTC)Reply[reply]
Thanks for all the answers, and apologies if it sounded like I was digging anyone out or being particularly unappreciative  :) I was not. If anything, it's the WMF I am unappreciative of, as although WP:VOLUNTEER is a sound enough principle for crowd-sourcing an encyclopaedia, it sounds like they could start putting some bloody money into what yous all do. If not by direct payments (although I don't see why not, since the tools directly affect WMF income) then at least with support. Imagine an employee of Google getting 404 when they need to check a copyright status! We might be smaller, but the principle applies, as many of these tools are fundamental to the structure we operate within. Buy the bloody techies a drink for X's-sake! ——SerialNumber54129 19:07, 26 March 2019 (UTC)Reply[reply]
Serial Number 54129, I note that several tools services over the last years have been upgraded to production services over the last year based on prioritization by the Community wishlist surveys. From advanced search, to xtools, maps, page view stats etc etc. Please contribute again next year in those surveys to continue that effort and celebrate the goals they are achieving. —TheDJ (talkcontribs) 19:15, 26 March 2019 (UTC)Reply[reply]

Thanks for all the answers - no harm at all. Things should be back up now. Σσς(Sigma) 21:18, 26 March 2019 (UTC)Reply[reply]

While you are here; prep for database changes!

While many tool developers/maintainers are paying attention.. Because of the size of Wikimedia websites and in prepping for future development, several major changes to the core of MediaWiki have been made over the past two years and will be made in the upcoming year.

If your tool talks to the database replicas and does things with editsummaries or log files, usernames, and/or revisions (yes that is a like 90% of what you use that database access for most likely), you should check out the new comment table, the actor table and probably the Slots table if you do a lot with the contents of revisions. At some point in the future, some of the columns that you rely on right now will likely have moved their contents into these new tables and their backwards compatible view will at some point disappear.

For that reason, you should definitely subscribe to the cloud-announce@ mailinglist to keep up to date about the deadlines for such eventual changes.. The one for comments just happened for instance, and since new services on jessie were just made impossible, if you currently run on jessie, now is the time to think about when in the next 1,5 year you are updating your tool, so that when the time comes in 2020, you won't have the same problem as the tools that broke today. —TheDJ (talkcontribs) 19:43, 26 March 2019 (UTC)Reply[reply]

All of the database reports (except for lists of edit counts) generated by the Bernstein Bot haven't updated in five days when they are typically updated daily. TheDJ, are you saying that it is likely they won't be updated ever again in the future? Because they are necessary for maintenance of the project. I've contacted the bot operator but a fellow editor said on his talk page that this was a WMF issue of deprecation. Liz Read! Talk! 18:57, 29 March 2019 (UTC)Reply[reply]
Liz if a tool is not maintained, then at some point it might stop working. Maybe if a new volunteer maintainer can be found, the bot can be handed over and brought up to date ? —TheDJ (talkcontribs) 19:58, 29 March 2019 (UTC)Reply[reply]
TheDJ, would you recommend posting a request on the bot request page? I'd wait a few days to see if the tool is updated. Liz Read! Talk! 20:32, 29 March 2019 (UTC)Reply[reply]
Liz, seems like a suitable place yes —TheDJ (talkcontribs) 20:34, 29 March 2019 (UTC)Reply[reply]
Is PetScan affected by this? I've tried to run some queries today, but they all spin for several minutes before throwing a "502 Bad Gateway nginx/1.13.6" error. --Redrose64 🌹 (talk) 14:57, 31 March 2019 (UTC)Reply[reply]

Noprint and metadata classes

I noticed that amboxes have the "metadata" class in their code, so I'm trying to find out the differences between that class and the "noprint" class. Also, where can I find the CSS rules for those classes? --CaiusSPQR (talk) 01:05, 30 March 2019 (UTC)Reply[reply]

noprint is do not print, metadata means not part of the main content and what happens with such blocks can depend on the medium, the usecase and the transformation or the user. 14:05, 30 March 2019 (UTC) — Preceding unsigned comment added by TheDJ (talkcontribs)
noprint is in Mediawiki:mobile.css (curiously--I would expect it in print.css :]) and metadata is in Mediawiki:print.css. Example search. --Izno (talk) 14:51, 30 March 2019 (UTC)Reply[reply]
Izno, there are many more places where they are listed. Our CSS is generally not 'defined in a single location' as our usecases tend to be very complex. CSS targets classnames, it does not define classnames. Our CSS rules are then delivered when needed. noprint doesn't have to be in MediaWiki:print.css, because it is defined by the core 'print only' CSS style rules, which are only downloaded and activated when you actually print. —TheDJ (talkcontribs) 13:31, 31 March 2019 (UTC)Reply[reply]
@TheDJ: I chose deliberately not to comment on the use versus definition--only where it was currently used. Naturally, yes, there must be other locations targeting these classes given that their uses in the above are not sufficient to get us to a print-worthy state. In that regard, .metadata is not used in core and .noprint is used in mediawiki.legacy/commonPrint.css. --Izno (talk) 15:51, 31 March 2019 (UTC)Reply[reply]

Permission to see history of deleted '.css'

I get a strange error message now I have deleted a .css in my Bot's userspace, and try to see the history of said deleted page through

Permission error
You do not have permission to view a page's deleted history, for the following reason:
The action you have requested is limited to users in one of the groups: Administrators, Oversighters, Researchers, Checkusers.

I am sure that this has to do with me not being an interface administrator (though my limitation here is not that I am not administrator ..). However, I do object to the fact that I am not allowed to see the deleted history/content, but I am allowed to see the history and current content when the page exists, and allowed to delete it (though it is fully understandable and correct that I am not allowed to restore the file). --Dirk Beetstra T C 18:34, 31 March 2019 (UTC)Reply[reply]

This is a known issue; phab:T202989. The permission message itself has a problem due to some hardcoding and assumptions about administrators group; phab:T203083. – Ammarpad (talk) 18:46, 31 March 2019 (UTC)Reply[reply]
@Beetstra: for what it's worth that isn't rally a .css page, it contained one line # placeholder for list. If you would like it restored drop a note at WP:IANB. — xaosflux Talk 19:16, 31 March 2019 (UTC)Reply[reply]
@Xaosflux: nah, I don't need it, thanks. I was merely interested whether there was a history which I was blocked from and resulted in above sentiment. I agree with the phab ticket that we should be able to investigate history, and that real abuse should be handled by oversight. --Dirk Beetstra T C 19:34, 31 March 2019 (UTC)Reply[reply]

Tech News: 2019-14

16:28, 1 April 2019 (UTC)

Assessment and tagging bot

I'm trying to set-up a bot to perform assessment and tagging work for Wikipedia:WikiProject Civil Rights Movement, but I'm not sure how to get this started. Mitchumch (talk) 02:44, 1 April 2019 (UTC)Reply[reply]

@Mitchumch: What specifically do you want tagged and assessed? I may be able to help - Wikipedia:Bots/Requests for approval/DannyS712 bot 21 is an open brfa that would assess pages that are already tagged as stubs as stub class, and I previously did a bot run to tag pages for another wikiproject. --DannyS712 (talk) 03:55, 1 April 2019 (UTC)Reply[reply]
The project needs a bot to detect and alert the project of any article, draft, etc. that may be related to the WikiProject. The articles or draft may not have a project stub on it. The project already has Inception bot running, but we need a bot that can review older stuff on Wikipedia. Mitchumch (talk) 04:21, 1 April 2019 (UTC)Reply[reply]
@Mitchumch: oh, thats a lot harder. I can generate lists from categories and tag the articles in those, but I don't think I'm the right user to help you out with the rest. --DannyS712 (talk) 04:23, 1 April 2019 (UTC)Reply[reply]
I tried looking at "Article tagging tools" listed at Wikipedia:WikiProject Council/Guide#Use bots to save work, but I don't posses enough experience to determine which one would be useful. Mitchumch (talk) 04:37, 1 April 2019 (UTC)Reply[reply]
@Mitchumch: If you want to discuss more how I can (try to) help, feel free to post on my talk page, because I ~may~ be able to help, but I don't really know what you are asking for. --DannyS712 (talk) 05:03, 1 April 2019 (UTC)Reply[reply]
You shouldn't need to choose a bot yourself. A number of bots are already approved for this kind of task, and a request at WP:BOTREQ will draw the attention of their operators; one who is willing to take the task will usually step forward fairly soon. What they will want to know are the criteria for tagging - "pages in categories X and Y but excluding pages already tagged for WikiProject Z" is the kind of thing. Please be specific about the categories - avoid saying "... and all their subcategories", since in the past this has led to a lot of mistagging and a great deal of work to undo again. --Redrose64 🌹 (talk) 08:25, 1 April 2019 (UTC)Reply[reply]
Thanks. I added a request on Wikipedia:Bot requests § WikiProject Civil Rights Movement. Mitchumch (talk) 18:42, 1 April 2019 (UTC)Reply[reply]

Importing an image from the Icelandic Wikipedia

Hi, I'm trying to add this image [19] to this article Logi Már Einarsson. I searched the English Commons but it doesn't exist there. Is there a quick way to import the image to the English Commons? I can use google translate to transfer the Icelandic text to English. -- Somedifferentstuff (talk) 22:27, 28 March 2019 (UTC)Reply[reply]

@Somedifferentstuff: There is no such thing as "Icelandic Commons", nor is there any such thing as "English Commons". The image is:Mynd:Logi Einarsson.jpg is hosted at Icelandic Wikipedia. --Redrose64 🌹 (talk) 23:11, 28 March 2019 (UTC)Reply[reply]
Looking at the original image, it's taken from the Alþingi website, and appears to be under copyright. Therefore, to use it on English Wikipedia, you need to satisfy all ten of the non-free content criteria; and straight off, I can say that it will fail criterion 1 since the subject is still alive, and so there is a reasonable chance that a free image may be created - perhaps when making a public speech. --Redrose64 🌹 (talk) 23:25, 28 March 2019 (UTC)Reply[reply]
Redrose64, according to the copyright section on the photo, it says "Höfundaréttshafi hefur veitt leyfi fyrir að nota myndina - The copyright holder has granted permission to use the image." I assume that is because the person in the picture is an active politician and the Alphing is the Iceland government website. -- Somedifferentstuff (talk) 00:22, 29 March 2019 (UTC)Reply[reply]
That being in the template is:Snið:Leyfi-rétthafa. Have they granted permission to Icelandic Wikipedia alone, or to all Wikimedia projects? If the former, they also need to grant permission here (see Wikipedia:Donating copyrighted materials) before we can use it. If the latter, where may the permission be examined?
It's not "Alphing", it's "Alþingi". The letter "þ", known as "thorn", is pronounced like "th" as in "thing". --Redrose64 🌹 (talk) 00:41, 29 March 2019 (UTC)Reply[reply]
From Google translate: The copyright holder has granted permission to use the image. It may not be used for marketing or reproduction unless otherwise stated. To the person who uploaded the image: Specify the type of use allowed. All images that can be used for marketing purposes and make reproductions transfer to the Commons. Explanation of fair use. Downloaded wikipedia with informed consent of editor; "Portrait photographs of members of the Althingi taken in 2016 and later marked as photographers and with the following text on their permission for re-publishing: The re-use of this photograph is free, provided that the name of the photographer appears where it can be found. In addition, the copyright rights of the author must be respected so that re-use does not improve or alter the author's work to impair his or her authorship or identity." --- Is there a way to tell if this is only for Icelandic Wikipedia? -- Somedifferentstuff (talk) 00:54, 29 March 2019 (UTC)Reply[reply]
That sounds like a no-derivative licence.Nigel Ish (talk) 13:35, 29 March 2019 (UTC)Reply[reply]
The files from Althingi where discussed awhile ago at the Icelandic Village pump. One of the users there emailed Althingi, which along with the rights organization of photographers in Iceland decided that the pictures of the congressmen where under an Non-Commercial licence. Their response is quoted in the linked discussion in a comment on November 11 2009, at 23:20 by Jabbi. There is no Icelandic Wikipedia specific restriction on those files, but obviously the Non-Commercial clause does stop them from being transferred to Wikimedia Commons.--Snaevar (talk) 17:22, 29 March 2019 (UTC)Reply[reply]
Snaevar, so a government photo can be used on the Icelandic Wikipedia but not the English Wikipedia? I am not well versed on Commons, copyright, etc., but I find that strange. Is it to protect the rights of the photographers? -- Somedifferentstuff (talk) 20:07, 29 March 2019 (UTC)Reply[reply]
What? No. It is perfectly fine to use the image on the English Wikipedia, given that it passes the rules here. Maybe I did not make that clear enough.--Snaevar (talk) 14:11, 31 March 2019 (UTC)Reply[reply]
Ok, thanks. So how do I import it? I'm new to working with images in this way. -- Somedifferentstuff (talk) 13:13, 1 April 2019 (UTC)Reply[reply]
@Snaevar: You claim it is perfectly fine to use the image on the English Wikipedia, given that it passes the rules here - in what way does it pass all of the WP:NFCC criteria, particularly criterion 1 No free equivalent? --Redrose64 🌹 (talk) 18:56, 1 April 2019 (UTC)Reply[reply]
  • So, this isn't a "technical issue". @Somedifferentstuff: there is no "import" process for media from iswiki, assuming it is available under a non-free exemption, you can just download it, then upload it here - and credit the source. If it was actually a free image, you could move it to commons and use it anywhere. Keep in mind, we take image use seriously here (see the comments above) and if the upload violates our rules it will be deleted. — xaosflux Talk 19:35, 1 April 2019 (UTC)Reply[reply]

Seen changes not marked as such in the watchlist

Today is Thursday. And now when I visit a link from my watchlist, and then go back to the watchlist, the green bullet stays green instead of turning blue. This problem occurs even for deleted redlinked pages. GeoffreyT2000 (talk) 23:36, 14 March 2019 (UTC)Reply[reply]

Wow, you just beat me here by like 3 minutes. I've noticed this a couple times today, but in both cases, my watchlist had green bullets for articles in which I had made the most recent edit. If I actually go back to the article, the bullet will go back to blue. –Deacon Vorbis (carbon • videos) 23:40, 14 March 2019 (UTC)Reply[reply]
(Well, now that I say that, a couple of them are now insisting on staying green, even though some have gone back to blue, so I dunno). –Deacon Vorbis (carbon • videos) 23:46, 14 March 2019 (UTC)Reply[reply]
They change to greyish cyan (specifically,   #638c9c) for me. But then I use MonoBook skin. --Redrose64 🌹 (talk) 23:56, 14 March 2019 (UTC)Reply[reply]
I've been having this problem on other wikis too, including en.wiktionary and en.wikivoyage. —Granger (talk · contribs) 00:54, 15 March 2019 (UTC)Reply[reply]
They look OK to me in monobook and in vector. Do you have "Use non-JavaScript interface" set in your prefs? — xaosflux Talk 01:24, 15 March 2019 (UTC)Reply[reply]
(e/c) GeoffreyT2000, there have been some changes in the watchlist logic this week. Can it be that they work, but are not updated as quickly as you are used to ? —TheDJ (talkcontribs) 13:48, 15 March 2019 (UTC)Reply[reply]

I'm a monobook user and have "unseen changes" set as a filter and "expand watchlist to show all changes" set in preferences. Until recently, if I viewed a change and returned to the watchlist, that change would no longer be showing. Now the item remains stuck in the watchlist. This would seem to be the same problem as above. I think they might clear on browser restart, but I'm not sure on that point – I'll try that in a moment and report.SpinningSpark 13:13, 15 March 2019 (UTC)Reply[reply]

I'm finding that on all the WMF wikis where I'm active, pages are only inconsistently marked as read after I look at the changes. I'm pretty sure this problem started less than 48 hours ago. It's really frustrating and makes my watchlist hard to use. —Granger (talk · contribs) 14:22, 15 March 2019 (UTC)Reply[reply]

@TheDJ: If this is a timing issue, then it is persistent for an extraordinarily long time. Yesterday, I had items in my watchlist that hadn't cleared after several hours. I eventually dealt with it by "mark all pages visited" nuclear option. There does seem to be some inconsistency - I was looking at the possibility that it was connected with the number of unseen edits on an individual page or whether one viewed the page or the diff, but for the last couple of hours it been somewhat better behaved and I didn't get anywhere with that. SpinningSpark 14:41, 15 March 2019 (UTC)Reply[reply]

I now think the way it works is this: if there are multiple unseen edits on a page and the one you look at is not the first one made, then that edit will get stuck on your watchlist, even if you then go back and view the first one, which will also stay stuck. Those who don't have their watchlist expanded to show all edits don't have a choice; they are going to view the last edit and it will stick on the watchlist unless it was the only one made. If you actually make an edit to the page it's taken off the watchlist. SpinningSpark 19:13, 15 March 2019 (UTC)Reply[reply]
To me it seems much more random and inconsistent than that. Sometimes editing the page doesn't even solve the problem—I just edited wikivoyage:Wikivoyage:Travellers' pub, and my own edit (along with the other recent edits to the page) is still displaying on my watchlist as if I haven't yet visited it. —Granger (talk · contribs) 00:04, 16 March 2019 (UTC)Reply[reply]
I'm seeing my own edits that I've just made show up on my watchlist too, whereas previously they hadn't. I often can't clear those pages from the watchlist, even if I visit the current incarnation of the page or view the last diff. Has been happening since 10am Pacific for me. —Joeyconnick (talk) 03:26, 16 March 2019 (UTC)Reply[reply]

I suspect this might be fixed with this change. It is a followup change that is part of phab:T188801. Hopefully it can be deployed asap. —TheDJ (talkcontribs) 14:36, 18 March 2019 (UTC)Reply[reply]

I'm having the same problem. If I visit a page any way other than by clicking on it on my watchlist, it's not marked as read. TheDJ, Neither of those links are working for me. Is that broken too? Natureium (talk) 18:59, 18 March 2019 (UTC)Reply[reply]

There's an issue at the moment with, among other things, phabricator. ~ Amory (utc) 19:09, 18 March 2019 (UTC)Reply[reply]

Also an issue: if there's a long list of unseen changes, and I compare the oldest unseen and the subsequent, say, 3 changes (but there are more than 3 changes unseen after that), then return to the article History, it lists all revisions as seen. Definitely not what should be happening, because I haven't seen those other revisions. —Joeyconnick (talk) 02:41, 19 March 2019 (UTC)Reply[reply]

I've noticed this issue too. It doesn't interfere with my workflow, so I haven't brought it up, but I can imagine it might bother other editors. —Granger (talk · contribs) 13:53, 19 March 2019 (UTC)Reply[reply]

It seems they overfixed this, as I now have the opposite: a page which is marked as "visited" now stays marked as "visited" even after new edits have been made to it (I don't use the green and blue, I use the blue circle / filled blue circle version, FWIW). Fram (talk) 14:58, 21 March 2019 (UTC)Reply[reply]

Looking at this further, it seems as if a page stays "read" until a new section is posted, while in the past it changed to unread as soon as anything was posted. I don't know if this change was deliberate or not, but I prefered the old way, certainly since there is no per section watchlisting. Fram (talk) 16:21, 21 March 2019 (UTC)Reply[reply]

For me this issue seems to be solved. I haven't encountered the new problem Fram describes. —Granger (talk · contribs) 01:23, 29 March 2019 (UTC)Reply[reply]

Seems over for me too, thank goodness!!! —Joeyconnick (talk) 18:44, 29 March 2019 (UTC)Reply[reply]

I have the opposite problem: after refreshing my watchlist, there are new diffs marked as having being visited, even though I have not. If I go to the history page then they are correctly marked as unread. Has anyone seen this problem? isaacl (talk) 21:21, 29 March 2019 (UTC)Reply[reply]

JS loads are insanely slow

Am I the only one suffering from painfully slow JS load times? This started today out of nowhere. Everything is slow to load.Cp678 (TCGE) 23:23, 1 April 2019 (UTC)Reply[reply]

Generating a page log

What mechanism is responsible for generating a log entry for a given page or action? In particular: why does this command show an entry for the adding of an {{unreferenced}} tag whereas this command does not, even though both articles are tagged with an unreferenced template? More specifically, what would need to happen in order to cause the action of adding a {{PROD}} tag to an article to also generate a log entry for said action? Thank you.--John Cline (talk) 07:19, 23 March 2019 (UTC)Reply[reply]

@John Cline: the logging of adding maintenance tags, deletion tags, etc is a part of the page curation system (see WP:NPR for more) while just adding the template manually (or semi automatically using twinkle) does not. --DannyS712 (talk) 07:29, 23 March 2019 (UTC)Reply[reply]
(edit conflict) Those log entries are created by new page reviewers (and admins) using mw:Page Curation (Special:Log/pagetriage-curation, Special:Log/pagetriage-deletion). — JJMC89(T·C) 07:33, 23 March 2019 (UTC)Reply[reply]
@John Cline: See [20] for the code that actually adds the log entry --DannyS712 (talk) 07:33, 23 March 2019 (UTC)Reply[reply]
Thank you both for this information. I am not sure how to use it to reach the end I desire which is an effective method of ascertaining whether or not an article has ever survived the proposed deletion process, effectively retiring that process for the given topic. Right now the determination is entirely too cumbersome to glean yet there are situations where policy stipulations mandate that it must be considered in concert with other pending or contemplated actions. I would like to see this problem solved. Can it be resolved? Thanks again.--John Cline (talk) 09:20, 23 March 2019 (UTC)Reply[reply]
Addition of PROD probably should tag the edit as attempted proposed deletion, which is possible with an edit filter I believe. You will need to leave a request at WP:EFN to see. --Izno (talk) 14:03, 23 March 2019 (UTC)Reply[reply]
Alternatively, it might be good if Twinkle did it at runtime and that would probably take care of the majority of PROD taggings. --Izno (talk) 14:08, 23 March 2019 (UTC)Reply[reply]

Personally, I would find it very helpful if there was a way of finding out a page's entire move history. Special:Log/move is tied to the title rather than the page itself, so it would only show moves that originated at the current title. -- King of ♠ 18:56, 23 March 2019 (UTC)Reply[reply]

I agree. As it stands, an idea to incorperate a bot to assist with this is being pursued here. I recall seeing it mentioned that it would be helpful if evaluating iterations of the page being discussed, where it may have existed under a different title, was part of the bot tasking. King of Hearts it would be great if you look in on that discussion to help ensure that we endeavor a best effort in this regard; I know you have a surplus of insight regarding XfD. Anyone else interested in seeing this done right is not only welcome, as well, they are entreated to help, if they so kindly will. Sincerely.--John Cline (talk) 02:26, 24 March 2019 (UTC)Reply[reply]
@King of Hearts: Regarding a true move log, it is unclear to me if Mediawiki even retains the information you would need. When researching all previous names, I usually have to do detective work. Diffs in the history don't even seem to remember what article name they were originally diffs of. They proudly announce they are diffs of the current article name, whatever if happens to be at the moment. EdJohnston (talk) 16:03, 25 March 2019 (UTC)Reply[reply]
@EdJohnston: page moves are currently recorded in the history of both source and target title (e.g. if you move Foo to Bar, this action is recorded in the history of both titles) but this was not always the case and such a note was only left in the history of the old title (Foo in this example). I think the changed happened circa 2006. Thryduulf (talk) 13:06, 2 April 2019 (UTC)Reply[reply]

Pageview stats down

The pageview stats tool is down. It isn't showing the results for 1 April (example here). Does anyone know what's wrong with it. The C of E God Save the Queen! (talk) 05:39, 2 April 2019 (UTC)Reply[reply]

It's not down. That shows the data you're looking for has not been generated. Read this. – Ammarpad (talk) 08:50, 2 April 2019 (UTC)Reply[reply]
Any ideas when they will be generated @Ammarpad:? The Royal C (talk) 12:27, 2 April 2019 (UTC)Reply[reply]
The FAQ I linked above answers your question. It could be up to few hours or days.– Ammarpad (talk) 13:44, 2 April 2019 (UTC)Reply[reply]
Typically yes, you should wait at least 24-36 hours before concluding something is wrong, especially on the 1st of the month since there is a lot of other per-month data being generated. However this time it seems there was an outage. More at phab:T219842. The Analytics team is working to restore the missing data. MusikAnimal talk 13:55, 2 April 2019 (UTC)Reply[reply]

Content model help: CSS

Could someone mark Template:Wikipedia Signpost/Research quote/styles.css as a CSS page? I'm not really sure how to do that, or if it's even possible for mortals to do that. Headbomb {t · c · p · b} 19:02, 30 March 2019 (UTC)Reply[reply]

Until phab:T85847 is resolved only admins can do that. – Ammarpad (talk) 19:18, 30 March 2019 (UTC)Reply[reply]
Well, hopefully an admin is around. @Anomie: maybe? Headbomb {t · c · p · b} 19:55, 30 March 2019 (UTC)Reply[reply]
TemplateStyles gave a new option "Sanitized CSS". mw:Content handlers says "For sanitized CSS intended for use with TemplateStyles". I'm not sure of the difference from the normal CSS setting but it's a template page so I set it to Sanitized CSS. PrimeHunter (talk) 20:58, 30 March 2019 (UTC)Reply[reply]
The normal CSS type is for use with e.g. MediaWiki:Common.css or user common.css. It doesn't do any validation, just syntax highlighting. The "Sanitized CSS" type validates that the content is valid, known-safe CSS, which means it's safe to be edited by all editors and can be loaded via wikitext with <templatestyles />. Anomie 13:26, 31 March 2019 (UTC)Reply[reply]
There has also been some chatter about giving the permission to template editors, which resulted in a testwiki task at phab:T217499. --Izno (talk) 22:02, 30 March 2019 (UTC)Reply[reply]

mw:Help:TemplateStyles says that the sanitized CSS content model is the default for subpages in the Template namespace that end with .css. Is this not the case on English Wikipedia for some reason? isaacl (talk) 15:17, 2 April 2019 (UTC)Reply[reply]

@Isaacl: it is, for pages created in the Template: namespace. In the example above, this page was created in the Wikipedia: (Project:) namespace and then moved. — xaosflux Talk 15:19, 2 April 2019 (UTC)Reply[reply]


Is there a way to add a (thank) link to a user's block log, to thank the blocking Admin? Example here - FlightTime Phone (open channel) 18:04, 2 April 2019 (UTC)Reply[reply]

Take a read through the epic phab:T60485. Basically, not everyone was in agreement, nor appears to be now, about whether such a thing would be good or not. If the sysop left a blocking template (not done above) you can thank them for that edit; otherwise, a friendly talk page note would of course be welcome. ~ Amory (utc) 18:23, 2 April 2019 (UTC)Reply[reply]
Thanx. - FlightTime Phone (open channel) 18:25, 2 April 2019 (UTC)Reply[reply]

Chrome error

File:Screenshot of Chrome error page.png

Could you see the error when try to open Wikipedia through Chrome browser? Any solution. --A-wiki-guest-user (talk) 13:17, 2 April 2019 (UTC)Reply[reply]

@A-wiki-guest-user: this can be caused by a few less-nefarious issues - 1st check the date and time on your computer, if they are off they can cause SSL errors. 2nd, you could be using a network that intercepts SSL for various purposes (company network, unsecured wifi that you haven't accepted terms of service for yet) or it could be something nefarious like someone intercepting your traffic. In any case, unless you know what is going on you should not send passwords over that connection. — xaosflux Talk 13:21, 2 April 2019 (UTC)Reply[reply]
Date and time is fine. As per my knowledge, the network is fine and already used. Anyway, I will try again and report. --A-wiki-guest-user (talk) 13:23, 2 April 2019 (UTC)Reply[reply]
It works in firefox. --A-wiki-guest-user (talk) 13:24, 2 April 2019 (UTC)Reply[reply]
@A-wiki-guest-user: make sure you have a current version of chrome, and possibly restart your computer. If it persists we can help, but will need more information on the certificate error you are getting. This error says that the Certificate Authority on the chain is not valid for chrome, but it doesn't say more, can you provide us the entire SSL Chain you are seeing, especially the CA? — xaosflux Talk 15:02, 2 April 2019 (UTC)Reply[reply]
Also, check your network / connection settings in Chrome and make sure that it's set correctly, and that it's not set to use any proxy server for your connection. It should usually be set to "auto-detect connection settings". ~Oshwah~(talk) (contribs) 18:29, 2 April 2019 (UTC)Reply[reply]

Updating Template:Subject bar for mobile view

 – See template talk page for further info.

Greetings, The "Templates for discussion" here is now closed. Wondering when change can be done so that "Subject bar" will appear in Mobile view? I posted at talk page of "Template:Subject bar" with fewer than 30 watchers without responses.

If we just remove the navbox class from the module, we get / Which works on mobile devices. From User:Hawkeye7. I have zero knowledge of how to do this so if a more experienced admin could make the change please. Regards, JoeHebda (talk) 14:33, 2 April 2019 (UTC)Reply[reply]

To clarify, this would consist of simply removing the line :addClass('navbox') from Module:Subject bar. I posted an example of what Template:Subject bar the module without the navbox class would look like, at Template talk:Subject bar#Update for mobile view per the TFD. --Pipetricker (talk) 18:51, 2 April 2019 (UTC)Reply[reply]
Responded at the original discussion. – Jonesey95 (talk) 20:11, 2 April 2019 (UTC)Reply[reply]

Template:divbox bolds Template:reflist?

This doesn't seem to make much sense? Could some HTML guru take a look? Headbomb {t · c · p · b} 18:49, 2 April 2019 (UTC)Reply[reply]

Possibly this change by Izno. – Jonesey95 (talk) 20:14, 2 April 2019 (UTC)Reply[reply]
Jonesey95, yes that is the one.. I hope Izno remembers what heading exactly, because otherwise we will break those.. —TheDJ (talkcontribs) 20:31, 2 April 2019 (UTC)Reply[reply]
Dumb question: Why is there a references list in a divbox?
This can be fixed trivially--the div targeted is <div class="center">{{{2|}}}</div> in {{divbox}}. --Izno (talk) 20:52, 2 April 2019 (UTC)Reply[reply]
@Izno: this is what I was trying to do. It works now, so thanks. Headbomb {t · c · p · b} 20:55, 2 April 2019 (UTC)Reply[reply]

Article "0" has no display title in Vector

0 has no edits today, so someone could've edited some transcluded template and now there's no display title at all. (talk) 23:29, 1 April 2019 (UTC)Reply[reply]

  • Looks fine to me. April fools? Rmhermen (talk) 00:31, 2 April 2019 (UTC)Reply[reply]
    To clarify, it is fine on WP:MOBILE subdomain but invisible on desktop version (with Vector skin, logged out). Still an issue, after purging the page cache. (talk) 00:58, 2 April 2019 (UTC)Reply[reply]
    Also invisible with vector skin, logged in --DannyS712 (talk) 01:18, 2 April 2019 (UTC)Reply[reply]
    I see the problem in Vector, but Timeless, Minerva (and mobile domain), Modern, Cologne Blue, and Monobook are all unaffected. --Izno (talk) 03:21, 2 April 2019 (UTC)Reply[reply]

0 using Vector skin (title is not displayed) and 1 using Vector skin (title is displayed). The HTML title displays for 0 and 1 using Vector are:

<h1 id="firstHeading" class="firstHeading" lang=""></h1>
<h1 id="firstHeading" class="firstHeading" lang="en">1</h1>

Johnuniq (talk) 09:22, 2 April 2019 (UTC)Reply[reply]

It's the same with safemode=1 and at other wikis, e.g. nn:0. The title is "Editing 0" in preview, as normally. shows the title was displayed 12 February but not 23 March and 29 March. It must be a MediaWiki bug unrelated to 1 April. PrimeHunter (talk) 09:29, 2 April 2019 (UTC)Reply[reply]
It's happening in other languages as well: wuu, cy, th, sl. Probably time for a phab bug report. – Jonesey95 (talk) 10:24, 2 April 2019 (UTC)Reply[reply]
Looks like it could be related to this change here, which is tracked here: T217172. rchard2scout (talk) 10:39, 2 April 2019 (UTC)Reply[reply]
Rchard2scout, good guess ;) —TheDJ (talkcontribs) 20:32, 2 April 2019 (UTC)Reply[reply]
Also, I checked another Wiki to see what's happening there, and for example ArchWiki doesn't have this problem. They're on MediaWiki 1.32.0, while we're on 1.33.0-wmf.23, so it's probably recent. Also, the change I mentioned was first included in -wmf.22, which was deployed on 21 March, which matches with the dates PrimeHunter found on rchard2scout (talk) 10:48, 2 April 2019 (UTC)Reply[reply]
I checked for all languages with an article called "0" at Wikidata for our 0 or Year zero. ja:0 showed the title 10 March. There are no archived pages between this and 23 March where the title was gone in our article. mw:MediaWiki 1.33/Roadmap shows mw:MediaWiki 1.33/wmf.21 and mw:MediaWiki 1.33/wmf.22 were deployed in this interval. PrimeHunter (talk) 16:39, 2 April 2019 (UTC)Reply[reply]
(ec) Could also be caused by gerrit:499743. I opened a new task at phab:T219864. This is happening only in Vector skin. – Ammarpad (talk) 10:52, 2 April 2019 (UTC)Reply[reply]
Has there been a software change along the lines of if (title) then display title, in a language which regards the string value "0" as false (as Perl does)? Certes (talk) 11:39, 2 April 2019 (UTC)Reply[reply]
PHP is widely used in MediaWiki and has the same convention. If some fix replaced $title by $title || "" to guard against an unset variable, which works for almost all titles, that would have the unfortunate side-effect of changing "0" to "". I'm looking through relevant parts of the release notes for such a change but can't see one at the moment. Certes (talk) 16:53, 2 April 2019 (UTC)Reply[reply]
I have made the title italic as a (hopefully temporary) workaround. Certes (talk) 11:59, 2 April 2019 (UTC)Reply[reply]
A fix for phab:T219864 has now been released and the article 0 displays its title normally. The workaround has been removed. Certes (talk) 23:27, 2 April 2019 (UTC)Reply[reply]

LUA help needed at Wikipedia:Wikipedia Signpost/Templates/Article list maker

This is a template that invokes Module:Signpost.

You can make it do fun things, like

Extended content

without |break_date=2014-01-01

Extended content

with |break_date=2014-01-01

The issue is that as stories get added, the cutoff date doesn't change. So I'm looking at a way that you can, instead of specifying a cutoff date, you can specify the number of articles to keep in the sidebar. Headbomb {t · c · p · b} 01:37, 31 March 2019 (UTC)Reply[reply]

@Pppery: something you might be able to help with? Headbomb {t · c · p · b} 00:01, 3 April 2019 (UTC)Reply[reply]
@Headbomb: Indeed, you are correct. Wikipedia:Wikipedia Signpost/Templates/Article list maker now takes a |limit= parameter that limits the number of articles. {{3x|p}}ery (talk) 00:22, 3 April 2019 (UTC)Reply[reply]
@Pppery: The 'more articles' expanded table doesn't seem to work sadly, unless a break/start date is specified. See updated examples. Headbomb {t · c · p · b} 00:45, 3 April 2019 (UTC)Reply[reply]
@Headbomb: What, exactly, is supposed to happen in that case. I see that you've added a default limit of five articles; does that mean that all uses of the template for tags with >|limit= articles should include a breakpoint after the |limit=th article?. {{3x|p}}ery (talk) 01:31, 3 April 2019 (UTC)Reply[reply]
@Pppery: The way I'm imagining things, the template would collapse everything exceeding the limit under "more articles". So if you have |sortdir=ascending, show the first 5 articles in ascending order, and articles 6+ under "more articles". And if you have |sortdir=descebing (the default option), show the first 5 articles in descending order, and articles 6+ under "more articles". With the relevant modifications when |limit=3 or |limit=10 is set. Headbomb {t · c · p · b} 01:34, 3 April 2019 (UTC)Reply[reply]
@Headbomb: Would this change completely replace the |break_date= parameter? I seem to be having technical issues getting the templates to work right with both numerical and date limits. {{3x|p}}ery (talk) 02:00, 3 April 2019 (UTC)Reply[reply]
@Pppery: That would be the idea. I suppose it would be good to check with @Smallbones: to see if they agree with that, but the idea here would be to more or less throw to present (by default at least) the five most recent stories on a topic, even if you're browsing something from 2012. Otherwise you could go from an article from 2017, to an article in 2007, and then lose your way back to the other articles in the topic because you landed on a page with the old presentation that had only the 3 oldest stories from before 2007. Or land on a page which said to display articles from after a certain date, and now there are 104 of them, rather than the 3 that were present at the time of writing. Headbomb {t · c · p · b} 02:04, 3 April 2019 (UTC)Reply[reply]
@Headbomb: OK, after spending far too much of my tile struggling with this, it should finally work. (I completely removed support for the date-based parameters) {{3x|p}}ery (talk) 02:10, 3 April 2019 (UTC)Reply[reply]

@Pppery: Thanks a bunch. I mayyyyyyyyy have some more request later, but I'll let you get a day of rest at least :p. Unless you're in the mood for some more technically wizardry involving scripts this time. Headbomb {t · c · p · b} 02:13, 3 April 2019 (UTC)Reply[reply]

If you mean JavaScript, then, while I do know that programming language, I have little interest in doing that on Wikipedia. {{3x|p}}ery (talk) 02:15, 3 April 2019 (UTC)Reply[reply]
@Pppery:... actually... not quite done. Expand these boxes. In the first case, the 25 March 2015 article is present both in the uncollapsed and in the 'more article' section, rather than the other articles. And I'll find someone else to bother for scripts if it comes to that. Headbomb {t · c · p · b} 02:16, 3 April 2019 (UTC)Reply[reply]
And done! {{3x|p}}ery (talk) 02:18, 3 April 2019 (UTC)Reply[reply]

DYK QPQ check tool is down

The tool is not working at the moment: for example, see this example. I tried raising this at WT:DYK but without response. Can something be done about this here? Narutolovehinata5 tccsdnew 02:53, 3 April 2019 (UTC)Reply[reply]

@Narutolovehinata5: its based on an issue related to one of the database tables (mw:Manual:Database layout) - "Unknown column 'rev_comment' in 'field list'". This is likely because rev_comment has been deprecated in favor of the comment table. Instead, rev_comment_id should be retrieved, which matches with the new comment_id in the comment table. --DannyS712 (talk) 03:01, 3 April 2019 (UTC)Reply[reply]
@Narutolovehinata5: That tool maintainer (Δ) has been blocked here for a while but is still somewhat around, you could try leaving a note on their talk page. — xaosflux Talk 03:13, 3 April 2019 (UTC)Reply[reply]
DannyS712, Yep, anymore you have to "join comment on comment_id = rev_comment_id" and select comment_text in order to get the edit summary. SQLQuery me! 03:30, 3 April 2019 (UTC)Reply[reply]

Analytics "pagecounts-ez" not generating

Talking on the behalf of data master West.andrew.g: The article viewership data source hasn't been updated since the 25th. This is the data source that powers the WP:5000 and from which the WP:Top25Report is derived, and we're already behind one of the weekly reports. igordebraga 22:39, 1 April 2019 (UTC)Reply[reply]

I would guess this is a victim of the operating system change on Tools labs. MusikAnimal? --Izno (talk) 23:57, 1 April 2019 (UTC)Reply[reply]
I don't think (production) would be affected by the Debian Stretch upgrade on Toolforge. phab:T219718 comes to mind, which also happened around the 25th, but that is about and not So, I'm not sure :( I would contact the Analytics team. MusikAnimal talk 00:12, 2 April 2019 (UTC)Reply[reply]
@West.andrew.g and Igordebraga: Someone asked about this on the Analytics mailing list. The issue is being tracked at phab:T220012. MusikAnimal talk 16:38, 3 April 2019 (UTC)Reply[reply]

Adding a link at top of screen

I would like to add a link at the top of my screen to where when I click on it it would take me to The Pending changes log. I have already modified my User:A 10 fireplane/common.js page once and want to know if I change all the New User To Pending chances if it would work A 10 fireplane Imform me 17:26, 3 April 2019 (UTC)Reply[reply]

Yes. Specifically, replace Special:Log/newusers with Special:PendingChanges. You should also probably change pt-newusers to something unique like pt-pendingchanges. ~ Amory (utc) 20:38, 3 April 2019 (UTC)Reply[reply]
@Amorymeltzer: Awesome thank you A 10 fireplane Imform me 20:39, 3 April 2019 (UTC)Reply[reply]

V • T • E (Navbar) template links not working on a phone

You know those drop down templates found at the bottoms of articles, such as Template:Xiamen? Also know how there are three buttons at the top left on all of them that say "V", "T", and "E", for "view", "talk", and "edit"? I'm on Chrome on a Huawei phone, and none of the buttons work at all. Pressing them only brings up descriptions of the buttons, "edit this template", etc. I can still edit them of course, but it's kind of inconvenient. How do I fix this? Woshiyiweizhongguoren (🇨🇳) 11:17, 28 March 2019 (UTC) (Originally asked at the Teahouse but later moved here)Reply[reply]

@Woshiyiweizhongguoren: You cannot personally fix this. If anyone can, it will be at Template talk:Navbar. --Izno (talk) 13:02, 29 March 2019 (UTC)Reply[reply]
I've experienced this. Reference Tooltips is interfering. Nardog (talk) 17:32, 3 April 2019 (UTC)Reply[reply]
Woshiyiweizhongguoren, try turning off "Reference Tooltips" under "Browsing" on the Gadgets tab in your preferences and then reload the Template:Xiamen page. --Pipetricker (talk) 19:23, 3 April 2019 (UTC)Reply[reply]
@Pipetricker: That's not really a solution, though. (And a better workaround is to click on the gear icon on the tooltip and uncheck "Show tooltips over text with a dotted underline in Reference Tooltips style".) The problem comes from the gadget's interaction with <abbr>...</abbr>. Perhaps something to be dealt with at MediaWiki talk:Gadget-ReferenceTooltips.js. Nardog (talk) 09:21, 4 April 2019 (UTC)Reply[reply]
You're right that clicking on the cogwheel icon on the reference tooltip and unchecking "Show tooltips over text with a dotted underline ..." is a better workaround, if that enables the navbar links. My suggestion to Woshiyiweizhongguoren was just intended to verify that Reference Tooltips is part of the problem. --Pipetricker (talk) 11:06, 4 April 2019 (UTC)Reply[reply]

A parenthesis within the "ref" template

Within the "ref" template at the end of the first paragraph of Collins–Valentine line, this appears:

{{citebook|author=Francis M. Carroll|title=A Good and Wise Measure: The Search for the Canadian–American Boundary, 1783–1842|pages=74–79, 85, 163|publisher=University of Toronto Press|year=2001}}

Thus what is seen in the "References" section looks like this:

Francis M. Carroll (2001). A Good and Wise Measure: The Search for the Canadian–American Boundary, 1783–1842. University of Toronto Press. pp. 74–79, 85, 163.

I would like to add a parenthetical remark so that it will look like this:

Francis M. Carroll (2001). A Good and Wise Measure: The Search for the Canadian–American Boundary, 1783–1842. University of Toronto Press. pp. 74–79 (see in particular the map on p. 76), 85, 163.

Can that be done within the "ref" template? Michael Hardy (talk) 20:50, 2 April 2019 (UTC)Reply[reply]

  • {{cite book |author=Francis M. Carroll |title=A Good and Wise Measure: The Search for the Canadian–American Boundary, 1783–1842 |pages=74–79 (see in particular the map on p. 76), 85, 163 |publisher=University of Toronto Press |year=2001}}
  • Francis M. Carroll (2001). A Good and Wise Measure: The Search for the Canadian–American Boundary, 1783–1842. University of Toronto Press. pp. 74–79 (see in particular the map on p. 76), 85, 163.

Works just fine. Headbomb {t · c · p · b} 21:02, 2 April 2019 (UTC)Reply[reply]

  • Which produces this under the hood: '"`UNIQ--templatestyles-0000006A-QINU`"'<cite id="CITEREFFrancis_M._Carroll2001" class="citation book cs1">Francis M. Carroll (2001). ''A Good and Wise Measure: The Search for the Canadian–American Boundary, 1783–1842''. University of Toronto Press. pp.&nbsp;74–79 (see in particular the map on p. 76), 85, 163.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=A+Good+and+Wise+Measure%3A+The+Search+for+the+Canadian%E2%80%93American+Boundary%2C+1783%E2%80%931842&rft.pages=74-79+%28see+in+particular+the+map+on+p.+76%29%2C+85%2C+163&" class="Z3988"></span>
  • Which looks sub-optimal to me from a metadata perspective. --Izno (talk) 21:13, 2 April 2019 (UTC)Reply[reply]
    For those who haven't worked it out, Izno is concerned about pollution of the rft.pages parameter in the title attribute of that last <span>...</span> element. You could use the |postscript= parameter for the parenthesis:
    • Francis M. Carroll (2001). A Good and Wise Measure: The Search for the Canadian–American Boundary, 1783–1842. University of Toronto Press. pp. 74–79, 85, 163 (see in particular the map on p. 76).{{cite book}}: CS1 maint: postscript (link)
    --Redrose64 🌹 (talk) 22:13, 2 April 2019 (UTC)Reply