Jump to content

Wikipedia:Village pump (technical): Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Line 482: Line 482:


'''<nowiki><ref>{{cite web ... |date=Jun 1, 2022}}</ref></nowiki>''' ....[[User:0mtwb9gd5wx|0mtwb9gd5wx]] ([[User talk:0mtwb9gd5wx|talk]]) 06:38, 28 August 2022 (UTC)
'''<nowiki><ref>{{cite web ... |date=Jun 1, 2022}}</ref></nowiki>''' ....[[User:0mtwb9gd5wx|0mtwb9gd5wx]] ([[User talk:0mtwb9gd5wx|talk]]) 06:38, 28 August 2022 (UTC)

==Search CRASH !==
result was: '''upstream connect error or disconnect/reset before headers. reset reason: overflow''' .... [[User:0mtwb9gd5wx|0mtwb9gd5wx]] ([[User talk:0mtwb9gd5wx|talk]]) 06:54, 28 August 2022 (UTC)

Revision as of 06:55, 28 August 2022

 Policy Technical Proposals Idea lab WMF Miscellaneous 
Shortcuts
The technical section of the village pump is used to discuss technical issues about Wikipedia. Bug reports and feature requests should be made in Phabricator (see how to report a bug). Bugs with security implications should be reported differently (see how to report security bugs).

If you want to report a JavaScript error, please follow this guideline. Questions about MediaWiki in general should be posted at the MediaWiki support desk. Discussions are automatically archived after remaining inactive for five days.


mbox is now TemplateStyled only

Please report any issues you see at MediaWiki talk:Common.css#mbox is now TemplateStyled only. Thanks! Izno (talk) 17:50, 17 August 2022 (UTC)[reply]

Congrats! 🥳 Jon (WMF) (talk) 21:23, 18 August 2022 (UTC)[reply]
Congratulations indeed! What's next on the list, .hlist? —⁠andrybak (talk) 13:16, 23 August 2022 (UTC)[reply]
You can help (decide). ;) Izno (talk) 17:52, 23 August 2022 (UTC)[reply]

Deactivating certain global scripts per local project

Hello!

Is there a way to have some globally activated user scripts (Meta - global.js) not affect certain local projects (exclude them)? - Klein Muçi (talk) 09:04, 18 August 2022 (UTC)[reply] 

if (mw.config.get('wgDBname') !== 'enwiki') {
    mw.loader.load('Script1');
    mw.loader.load('Script2');
    And any other usual js stuff
    // + Any message you wish to keep
}
Change enwiki to the wiki you want to disable scripts. You can see a working example at my global.js (from line 55 until end) but it's a mess tbh. —CX Zoom[he/him] (let's talk • {C•X}) 09:15, 18 August 2022 (UTC)[reply]
@CX Zoom, thanks a lot! Exactly what I wanted. And thank you for the detailed example! :) - Klein Muçi (talk) 10:17, 18 August 2022 (UTC)[reply]
@CX Zoom, what would I need to do if I wanted to disable them on more than 1 wikiproject?
(mw.config.get('wgDBname') !== 'enwiki', 'sqwiki') doesn't work. — Klein Muçi (talk) 01:30, 24 August 2022 (UTC)[reply]
(mw.config.get('wgDBname') !== 'enwiki' && mw.config.get('wgDBname') !== 'sqwiki') Izno (talk) 02:04, 24 August 2022 (UTC)[reply]
Izno, thank you! :) — Klein Muçi (talk) 02:19, 24 August 2022 (UTC)[reply]

Template font size

Resolved

{{Who's Who}} generates reduced size font. There are over 2,000 transclusions and the majority seem to be uses within the references section, where the font is already 90%, so the further reduction violates MOS:SMALL (e.g Maggie O'Farrell ref #8). What's the best way to resolve this? There could be a template parameter to specify font reduction when the template is used in normal-size text (if there are any, someone would have to find those and edit them). Is there a better way? MB 17:45, 18 August 2022 (UTC)[reply]

MB, a similar issue is present in template {{Cite OED}}, used for example in ref #10 in Alchemy#References. The problem comes from Template:Link note, which has hardcoded CSS font-size:0.95em; font-size:90%;. I think the best solution is just to remove this bit of the CSS – output of {{Link note}} is already A) wrapped in parentheses and B) also has CSS color:#555 (which some people don't like either). —⁠andrybak (talk) 17:57, 18 August 2022 (UTC)[reply]
It looks like there are 34k more from {{subscription required}} that would also be fixed. MB 18:05, 18 August 2022 (UTC)[reply]
95% (Link note) times 90% (references) is sufficiently sized for MOS:SMALL (>85%). There is a way that this could depend on where the text appears (TemplateStyles).
That said, our MOS:SMALL probably needs to be adjusted to point out the absolute minimum in pixels/pts, as text sizes on Wikipedia have generally increased with each new skin. There is also CSS min() which is newer but could be used later in the future (or double declared even today e.g. font-size: 95%; font-size: clamp(14px, 85%, 1em); or some such). Izno (talk) 18:35, 18 August 2022 (UTC)[reply]
I think using a percentage as guidance is still preferable, under the assumption that readers will use their browser zoom capability to set the base font size to a comfortable size for them. (I know this is not universally true, but it's a reasonable default assumption, as teaching someone how to use their browser zoom feature will enable them to set their desired font size on Wikipedia and other sites.) isaacl (talk) 21:44, 18 August 2022 (UTC)[reply]
Pixels being an example of "the minimum font size is actually X size, and we should not let anything go lower than that, percentages or otherwise". Our 85% rule is based on computing what the minimum font size was in Monobook, but Vector, new Vector, and Timeless all have larger font sizes, so it stands to reason that we can use smaller fonts and that really, it should be defined by the absolute minimum. Pixel-based sizes still respond to zoom anyway. Izno (talk) 22:06, 18 August 2022 (UTC)[reply]
Yes, precisely because pixel-based sizes zoom, I think a percentage is still preferable. A user will use the zoom function to adjust the base font to a comfortable size, no matter what pixel size the skin has set. Thus specifying a reasonable minimum size as a percentage of the base font size will automatically scale to the user's preference. isaacl (talk) 22:14, 18 August 2022 (UTC)[reply]
Then I don't see what issue you have with font-size: clamp(14px, 85%, 1em);. And anyway, that was illustrative. Izno (talk) 22:45, 18 August 2022 (UTC)[reply]
I apologize for not being clear. I wasn't referring to your code sample, but your statement our MOS:SMALL probably needs to be adjusted to point out the absolute minimum in pixels/pts. isaacl (talk) 23:01, 18 August 2022 (UTC)[reply]
MB, I have increased the font size at {{link note}} to 95%, which fixes this MOS:SMALLFONT problem. Thanks for reporting it. – Jonesey95 (talk) 14:41, 23 August 2022 (UTC)[reply]

dashes script malfunction

Of late, the dashes script and various mirrors have stopped performing, and the – button that calls the script in the dropdown menu (More tab) has been replaced by auto ed. At the same time, the script functionality has also disappeared. However, none of the core AutoEd modules seems to have changed. What could be causing this issue?  Ohc revolution of our times 09:47, 19 August 2022 (UTC)[reply]

The importScript call at line 150 is (I know not why) no longer returning a truthy value, so various things are not being set. I created a version of the script without that condition at User:William Avery/dashes.js, and it seems to work on my sandbox. William Avery (talk) 12:40, 19 August 2022 (UTC)[reply]
It would seem importScript is no longer synchonous since this change. William Avery (talk) 11:57, 20 August 2022 (UTC)[reply]
I completely removed it from my common.js a couple of days ago. I was concerned because of the what is mentioned above, but also the warning on GregU's dashes script, "Code that you insert on this page could contain malicious content capable of compromising your account." I really loved the convenience of using it, but not unless someone can come up with a safe and reliable code for us. — Maile (talk) 23:18, 22 August 2022 (UTC)[reply]
The warning is a standard warning and is something you should be concerned with for all the scripts you use. This particular issue is not pertinent to why that warning is there. Izno (talk) 23:30, 22 August 2022 (UTC)[reply]
The fix for this issue is to replace User:GregU/dashes.js with User:Ohconfucius/dashes.js on your common.js
file/page. Dawnseeker2000 16:22, 23 August 2022 (UTC)[reply]
importScript is not, and never used to be, synchronous. However, you're right that it no longer returns a truthy value, which is causing GregU's version to not work. Putting the importScript call in an if condition to check whether AutoEd has loaded, will no longer work – it should instead check if a global created by AutoEd is defined. – SD0001 (talk) 18:29, 23 August 2022 (UTC)[reply]

Is there an update to Vector-2022 today/yesterday?

Tracked in Phabricator
Task T315639

Not sure if there is an update to Vector-2022 on 18 August 2022 and/or 19 August 2022, as Xtools and Shortdesc helper are suddenly no longer functional despite both already enabled in gadgets. Both gadgets were working fine on 17 August 2022 and before. — Paper9oll (🔔 • 📝) 12:40, 19 August 2022 (UTC)[reply]

Paper9oll, I fixed XTools Article Info gadget on bnwiki in my own way. —Yahya (talk • contribs.) 14:50, 19 August 2022 (UTC)[reply]
@Yahya Haven't tried your script, but this isn't really a permanent solution. But any idea, if it's due to an update to Vector-2022 that rolled out probably in past 2 days, that causes both tools to suddenly stopped functioning in Vector-2022? Not sure, if the update removed or renamed some css classes that causes both tools to no longer function/display. — Paper9oll (🔔 • 📝) 16:35, 19 August 2022 (UTC)[reply]
The XTools gadget has now been fixed, both here on enwiki as well as the global script. Ironically, I was asked how the gadget worked so that the team would not break it, but it looks like that inquiry was for a different project (DiscussionTools), and unrelated to the change in Vector 2022. — MusikAnimal talk 19:41, 19 August 2022 (UTC)[reply]
@MusikAnimal: Please could you give some detail of how you fixed your gadget – there are other scripts that currently hunt for the contentSub id. @Galobtter: Shortdesc-helper attaches to #contentSub and I have a user script that does the same thing. — GhostInTheMachine talk to me 17:20, 20 August 2022 (UTC)[reply]
@GhostInTheMachine I did the same as Yahya did on bnwiki and am now inserting the content before #bodyContent, but only for Vector-2022. Hope this helps. — MusikAnimal talk 22:08, 22 August 2022 (UTC)[reply]
Thanks @MusikAnimal:. Would it be more "tidy" to insert the new content into the top of #bodyContent? i.e. $("#bodyContent").prepend( $("<div>New info</div>") ). This would keep the bodyContent div as the outermost container for all of the displayed content. It would also mean that the code does not need to test for a specific skin by name. Hopefully, navigating via only the bodyContent id might also be safer against any further skin changes that are outside of our control. — GhostInTheMachine talk to me 08:04, 24 August 2022 (UTC)[reply]
As well as Shortdesc Helper, d:User:Yair rand/WikidataInfo.js has stopped working for me on Vector 2022 around this time. Ham II (talk) 08:39, 21 August 2022 (UTC)[reply]
The Wikidata script is working for me now on Vector 2022, but Shortdesc Helper still isn't. Ham II (talk) 07:15, 24 August 2022 (UTC)[reply]
Fixed in shortdesc helper. Galobtter (pingó mió) 04:02, 25 August 2022 (UTC)[reply]
@Galobtter: Thank you! Ham II (talk) 17:35, 25 August 2022 (UTC)[reply]

Vector 2022 now leaving a lot of blank space on the left and right of my screen.

A waste of space and I'm sure not what was intended. Doug Weller talk 16:19, 21 August 2022 (UTC)[reply]

The blank space is intended, see mw:Reading/Web/Desktop Improvements/Features/Limiting content width § Goals and motivation and mw:Reading/Web/Desktop Improvements/Frequently asked questions § Why is the width of the content limited? Why is there so much white space?. Rummskartoffel 16:55, 21 August 2022 (UTC)[reply]
@Rummskartoffel and this change was done in the last day? It doesn’t show on my iPad just my Wondows pc. Doug Weller talk 19:03, 21 August 2022 (UTC)[reply]
None that I know about; there's (supposed to have) been a lot of blank space in Vector-2022 on larger screens for a while now. A difference between an iPad and a (presumably larger) PC screen would be expected. Rummskartoffel 19:52, 21 August 2022 (UTC)[reply]
@Doug Weller, if you don't want to keep this extra whitespace, then I found a gadget today that I've enabled that reduces the whitespace that's added. It's called wide-vector-2022 and is near the bottom of the gadgets list. Dreamy Jazz talk to me | my contributions 22:50, 21 August 2022 (UTC)[reply]
The gadget is only listed at Special:Preferences#mw-prefsection-gadgets if your skin is Vector 2022. Here is a comparison of Wikipedia in Vector 2022 without the gadget (assuming you haven't enabled the gadget) and with the gadget. PrimeHunter (talk) 23:56, 21 August 2022 (UTC)[reply]
Seems ok now. Doug Weller talk 20:14, 23 August 2022 (UTC)[reply]

Section edit deletes rest of page

This is an issue that occasionally appears. With this section edit I accidentally replaced the rest of the page with just the edited section. This happens if when an edit section preview is saved in the browser cache. This happend when I started the edit one day and previewed it, closed the browser without saving the edit, then finished the edit the next day in a new browser session. Everything looks normal as you preview the section, but when you save it the rest of the page is gone. While the simple solution is not to use cached edits, it's not a behaviour that should be expected. —  Jts1882 | talk  09:34, 22 August 2022 (UTC)[reply]

When I start a section edit at Talk:Fish#Why are conodonts excluded?, the url is https://en.wikipedia.org/w/index.php?title=Talk:Fish&action=edit&section=8. After a preview it becomes https://en.wikipedia.org/w/index.php?title=Talk:Fish&action=submit, the same as if I edited the whole page. Is it the same url's for you? The information that you edited a section is no longer in the url. When you closed the browser, this information was apparently lost. After reopening the browser, it remembered the last url and what you had in the text area but did not communicate with MediaWiki that it was a section edit. MediaWiki apparently assumed it was a whole page edit. I don't know whether this is a known issue or has a fix other than not doing that. What is the browser? PrimeHunter (talk) 14:32, 22 August 2022 (UTC)[reply]
Ah, the lack of the section in the preview url explains it. The the browser (Firefox) must cached the contents of the edit window but not the information needed to handle the section. I suppose I'll just have to be careful. —  Jts1882 | talk  13:44, 23 August 2022 (UTC)[reply]

refill ng

input:

  • <ref>https://www.worldcat.org/title/elementary-my-dear-groucho/oclc/829706209</ref>
  • <ref>https://www.worldcat.org/title/groucho-marx-and-the-broadway-murders/oclc/47893483</ref>
  • <ref>https://www.worldcat.org/title/groucho-marx-king-of-the-jungle/oclc/159708833</ref>
  • <ref>https://www.worldcat.org/title/groucho-marx-master-detective/oclc/1310412187</ref>
  • <ref>https://www.worldcat.org/title/groucho-marx-private-eye/oclc/914301746</ref>
  • <ref>https://www.worldcat.org/title/groucho-marx-secret-agent/oclc/982635033</ref>

output:

  • <ref>{{Cite web|url=https://www.overdrive.com/search?q=7D68B9AE-CCCC-4F14-983A-38CDC71C2315|title=Elementary, my dear Groucho|first=Ron|last=Goulart|date=August 22, 2011|publisher=Thomas Dunne Books/St. Martin's Minotaur|via=Open WorldCat}}</ref>
  • <ref>{{Cite web|url=https://www.worldcat.org/title/groucho-marx-and-the-broadway-murders/oclc/47893483|title=Groucho Marx and the Broadway murders|first=Ron|last=Goulart|date=August 22, 2002|publisher=Chivers Press ; Thorndike Press|via=Open WorldCat}}</ref>
  • <ref>{{Cite web|url=https://www.worldcat.org/title/groucho-marx-king-of-the-jungle/oclc/159708833|title=Groucho Marx, king of the jungle|first=Ron|last=Goulart|date=August 22, 2007|publisher=Camden|via=Open WorldCat}}</ref>
  • <ref>{{Cite web|url=https://www.vlebooks.com/vleweb/product/openreader?id=none&isbn=9781250090874|title=Groucho Marx, Master Detective|first=Ron|last=Goulart|date=August 22, 2015|publisher=St. Martin's Press|via=Open WorldCat}}</ref>
  • <ref>{{Cite web|url=http://rbdigital.oneclickdigital.com/|title=Groucho Marx, private eye|first=Ron|last=Goulart|date=August 22, 2015|via=Open WorldCat}}</ref>
  • <ref>{{Cite web|url=https://www.worldcat.org/title/groucho-marx-secret-agent/oclc/982635033|title=Groucho Marx, secret agent|first=Ron|last=Goulart|date=August 22, 2003|via=Open WorldCat}}</ref>
  • 0mtwb9gd5wx (talk) 02:42, 23 August 2022 (UTC)[reply]
    @0mtwb9gd5wx this is an external tool, you may report issues using the information here Wikipedia:ReFill#Reporting_problems. — xaosflux Talk 10:39, 23 August 2022 (UTC)[reply]

Duplicate tabs for user scripts (editProtectedHelper, csdhelper)

Resolved

I went away last week, and this week I am seeing duplicates for some of my user scripts (User:Jackmcbarn/editProtectedHelper and User:Ale_jrb/Scripts/csdhelper.js specifically). With EPHelper I get two rows of the same buttons (i.e. two "Respond", two "Remove request", etc), and with CSDhelper I get two "Speedy" tabs at the top of the page next to the Talk tab. I'm sure this is a THURSDAY issue, but I can't find anything obvious in the release notes to see what it was, and I'm not seeing a phab task indicating that anyone else has noticed (though I've never been good at finding tasks on there). Primefac (talk) 09:42, 23 August 2022 (UTC)[reply]

@Primefac: Assuming you are using the Vector skin, you are importing the scripts twice: common.js line 2 and vector.js line 16 for editProtectedHelper and common.js line 3 and vector.js line 18 for csdhelper. Apparently (see help desk question about the same issue), importScript() used to deduplicate imports, but no longer does so. Removing the duplicate imports should fix it. Rummskartoffel 10:03, 23 August 2022 (UTC)[reply]
Many thanks. Primefac (talk) 10:10, 23 August 2022 (UTC)[reply]

User:Kephir/gadgets/unclutter

Something has been changed on MediaWiki 1.39/wmf.25, causing the Signature minimisation to no longer work. The developer has not edited in two years, so just wondering if someone else could troubleshoot instead. 1989 (talk) 19:37, 23 August 2022 (UTC)[reply]

It's because of this change in mediawiki. This script internally uses importStyleSheet and expects it to return a style tag object. But this is no longer the case. Depending on what exactly the script does this for, there may or may not be a straightforward fix for this. One option is to propose a mediawiki change to keep the legacy return value. – SD0001 (talk) 20:35, 23 August 2022 (UTC)[reply]
@Krinkle: Any chance this could be amended? There could be more scripts no longer working because of this change. 1989 (talk) 21:06, 23 August 2022 (UTC)[reply]
I have filed a patch: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/825906. – SD0001 (talk) 21:07, 23 August 2022 (UTC)[reply]

Scripts now loading on mobile?

Have changes been made to the mobile code? I'm noticing the diff id is appearing in plain text when I load from watchlist and some of my userscripts are now loading in mobile mode (en.m). If so, any place I can see what changes were made? No real issue, just trying to see what else I can now do without switching to desktop mode. Slywriter (talk) 20:27, 23 August 2022 (UTC)[reply]

Yes. Scripts you import using importScript will now load on mobile. The change is this one, there's no phab ticket I think. – SD0001 (talk) 20:37, 23 August 2022 (UTC)[reply]
It was probably caused by the recent chatter in phab:T27845. Izno (talk) 21:01, 23 August 2022 (UTC)[reply]

What's causing the pink highlighting in this Afd comment?

What's causing the pink highlighting on the comment of 22:50, 22 August 2022 (diff; perma) in this Afd? The highlighting includes the four indented replies, and stops at the next bullet item flush left, and is visible on multiple browsers on Win 10 and iOS 15. Here's a bit of rendered html which might help.

Html of comment of 22:50, 22 Aug (text shortened for brevity) with slight context before and after
(Last bit of preceding, unhighlighted comment shown for context:)
...It's anti-creationist. <a href="/wiki/User:RedactedUserA" title="User:RedactedUserA">RedactedUserA</a> (<a href="/wiki/User_talk:RedactedUserA" title="User talk:RedactedUserA">talk</a>) 02:48, 24 August 2022 (UTC)<span class="ext-discussiontools-init-replylink-buttons" data-mw-comment="{"type":"comment","level":3,"id":"c-RedactedUserA-20220824024800-RedactedUserB-20220822224500","replies":[],"timestamp":"20220824024800","author":"RedactedUserA"}"><!--__DTREPLYBUTTONSCONTENT__--></span><span data-mw-comment-end="c-RedactedUserA-20220824024800-RedactedUserB-20220822224500"></span></dd></dl></li></ul>
(Start of comment by User1 with pink highlighting)
<ul><li><b><span data-mw-comment-start="" id="c-RedactedUser1-20220822225000-RedactedUser2-20220822032200"></span>Delete</b>. Per all of the above. Nothing else to say, except that
(Some content redacted here) 
depending on the result of the discussion on the WikiProject Talk page, naturally). <a href="/wiki/User:RedactedUser1" title="User:RedactedUser1">RedactedUser1</a> (<a href="/wiki/User_talk:RedactedUser1" title="User talk:RedactedUser1">talk</a>) 22:50, 22 August 2022 (UTC)<span class="ext-discussiontools-init-replylink-buttons" data-mw-comment="{"type":"comment","level":2,"id":"c-RedactedUser1-20220822225000-RedactedUser2-20220822032200","replies":["c-RedactedUser3-20220823005600-RedactedUser1-20220822225000"],"timestamp":"20220822225000","author":"RedactedUser1"}"><!--__DTREPLYBUTTONSCONTENT__--></span><span data-mw-comment-end="c-RedactedUser1-20220822225000-RedactedUser2-20220822032200"></span>
(End of first comment with hightlighting; all replies also highlighted; here's the first bit of the first reply, for context:)
<dl><dd><span data-mw-comment-start="" id="c-RedactedUser3-20220823005600-RedactedUser1-20220822225000"></span>DO NOT DELETE -- There is clearly a ...

I just don't see what is causing this. (please Reply to icon mention me on reply; thanks!) Mathglot (talk) 06:53, 24 August 2022 (UTC)[reply]

Note: I have script User:Headbomb/unreliable.js installed that pink-highlights refs that link to unreliable sources, and this comment set includes a twitter link (see the diff or permalink) but I thought that only highlights the source, not an entire comment set. Pinging User:Headbomb just in case. Mathglot (talk) 07:37, 24 August 2022 (UTC)[reply]
@Mathglot: See User:Headbomb/unreliable#Comments. 0xDeadbeef 07:40, 24 August 2022 (UTC)[reply]
D'oh! Thanks, User:0xDeadbeef. (Note to self: RTFM.)  Done. Mathglot (talk) 07:50, 24 August 2022 (UTC)[reply]
You can put the twitter link in brackets to only highlight the link, e.g. [1] Headbomb {t · c · p · b} 08:43, 24 August 2022 (UTC)[reply]
Thanks much for the additional tip. Mathglot (talk) 08:18, 25 August 2022 (UTC)[reply]
@Mathglot and anyone else who only wants to keep track of one or two sections on a page like this: Look in Special:Preferences#mw-prefsection-editing-discussion for an item called "Enable topic subscription". It'll be turned on everywhere before long. You can try it out just on this page by clicking here: https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)?dtenable=1 Whatamidoing (WMF) (talk) 03:10, 26 August 2022 (UTC)[reply]
Thanks, Whatamidoing (WMF), I see that already; or at least, I have a [subscribe] link on every section on this page, including this one. I assume that means I must have opted in to a beta feature already, though I haven't tried it, iirc. It should definitely ease my notifications for discussions on highly active pages like noticeboards; that will make a big difference. Mathglot (talk) 03:19, 26 August 2022 (UTC)[reply]

Bug in movable lunar calendar calculations.

I found a bug in lunar calendar date calculations. Current years are correct, the bug shows up as a 10 day discrepancy in 2024. I reported this on the talk page of the template where I found the bug (the above link), where editor @GreenC: verified the problem. However the buggy code is not in that template, but buried further down. Somebody at the Teahouse suggested this is the right place to report the bug. -- M.boli (talk) 12:31, 24 August 2022 (UTC)[reply]

The problem appears to be {{ctime:x}}. For example {{ctime:x|2024|1|1}} == 2024-02-10, but should be 2024-02-10. -- GreenC 14:10, 24 August 2022 (UTC)[reply]

Text jumbled up extending outside normal edit forms

Hello! Many times while browsing Wikipedia in mobile, if I open a page for editing, the source code may extend far beyond the editing form, jumbling up with other text sections at the bottom of the page. I happened to see that same effect on a page while on laptop now. I've never understood what exactly causes that effect and I became curious. Can someone explain to me why that happens and what may be some remedies for it if I ever encounter it (mobile/desktop)? - Klein Muçi (talk) 21:48, 24 August 2022 (UTC)[reply]

Please specify the mw:Editor with which you experience this. Nardog (talk) 21:59, 24 August 2022 (UTC)[reply]
Nardog, I've always dreaded talking about editors and notifications because I can never specify correctly which is which BUT I'll try to describe it as good as I can.
In mobile I've usually encountered that effect while trying to reply back in discussions, while being the in the mobile site. The only remedy I know of is to switch to the desktop site (from m.wikipedia.org to wikipedia.org.). In my laptop now, I encountered it while editing templatedata in a template. The numbered lines were extending beyond the text form. Funny enough, I switched to the mobile site and I was able to make the edit I wanted to make. — Klein Muçi (talk) 22:21, 24 August 2022 (UTC)[reply]
@Klein Muçi, can you make some screenshots and post them to Phab:? Whatamidoing (WMF) (talk) 03:13, 26 August 2022 (UTC)[reply]
Whatamidoing, I will if I encounter it again. If you can't already tell by the way I made my question, I thought it was a common/known thing. That's why I've never thought doing anything about it. — Klein Muçi (talk) 11:07, 26 August 2022 (UTC)[reply]

"Undo" greyed out (but CTRL+Z works)

This isn't a new problem, but rather something I've noticed since switching from Firefox to Chrome around 2010. If you make a mistake on most websites, Gmail for example, you can right click+"undo" to fix the mistake. On Wikipedia, I can only get the right-click method to work some of the time. It works when I use the reply tool, but almost never when using the source editor. Usually when I use the source editor, "undo" is greyed out (or in Edge, "undo" does not even appear). It's not a huge problem (I've recently overcome my laziness and learned to use AltCTRL+Z), but maybe some other editors don't know about the shortcut. I use Google Chrome and Microsoft Edge in Windows 11. Schierbecker (talk) 23:04, 24 August 2022 (UTC)[reply]

It's control+z. Alt+z or alt+shift+z, etc. is the access key for the Main Page. Graham87 06:49, 25 August 2022 (UTC)[reply]
Oops. I meant CTRL+Z, User:Graham87. Schierbecker (talk) 07:25, 25 August 2022 (UTC)[reply]
@Schierbecker, it looks like you're using the 2010 WikiEditor. It's possible that the 2017WTE ("New wikitext mode" in Special:Preferences#mw-prefsection-betafeatures) would work the way you want. Whatamidoing (WMF) (talk) 03:16, 26 August 2022 (UTC)[reply]

Wayback Machine not working -- anyone know why or for how long?

I can't get Wayback Machine (https://archive.org/web/) on any browser (I'm on Windows). I use Wayback regularly so it was probably working at least 48 hours ago. Anyone know why it's down, and for how long? Softlavender (talk) 00:56, 25 August 2022 (UTC)[reply]

It's been down for over an hour. Schierbecker (talk) 00:58, 25 August 2022 (UTC)[reply]
@Schierbecker:@Softlavender: https://archive.is/ .... 0mtwb9gd5wx (talk) 01:54, 25 August 2022 (UTC)[reply]
If someone notices it's back up again, can you please ping me? Softlavender (talk) 03:02, 25 August 2022 (UTC)[reply]
Twitter update. Known and being worked on. -- GreenC 05:30, 25 August 2022 (UTC)[reply]
removed tracking 0mtwb9gd5wx (talk) 08:00, 25 August 2022 (UTC)[reply]
@Softlavender: Wayback is up again. —Bruce1eetalk 14:03, 25 August 2022 (UTC)[reply]

ISBN Converter

https://www.loc.gov/publish/pcn/isbncnvt_pcn.html .... 0mtwb9gd5wx (talk) 01:54, 25 August 2022 (UTC)[reply]

@0mtwb9gd5wx: what is the technical issues, About Wikipedia that you are trying to discuss here? — xaosflux Talk 13:20, 25 August 2022 (UTC)[reply]

This note at the end is interesting:

Note: The United States ISBN Agency will soon begin assigning ISBNs starting with the prefix element 979 (in addition to the ISBNs with prefix element 978 currently assigned). Prior to 2007, the ISBN was 10 digits in length. In January 2007, the 13-digit ISBN launched to increase the capacity of the ISBN system. To date, 13-digit ISBNs assigned by the U.S. ISBN Agency include the 978 prefix, which allowed systems to contain both 10- and 13-digit ISBNs for all books. However, a 13-digit ISBN starting with 979 does not have an equivalent 10-digit ISBN. Once this change takes place, only 13-digit ISBNs starting with 978 or 979 should be used to identify a book.

10 and 13 are interchangeable meaning can translate between the two with a translator (I use a CLI tool). However the above is saying, I think, they are running out of the 13-digit ISBNs so they are creating a new 13-digit block that begins with 979 - they used to all start with 978 - and the 979's have no 10-digit equivalent. And they are deprecating the 10-digit entirely ("only 13-digits should be used") which I guess is true for new books issued but for Wikipedia citations it creates some confusion for verification since many old books were only known by the 10-digit, and that's how they are listed in many library catalogs. -- GreenC 15:48, 25 August 2022 (UTC)[reply]

I recommend that people interested in ISBN conversion try the ISBN tool I wrote, which should support ISBNs beginning with 979 so long as their range data is available in the official RangeMessage.xml file provided by the International ISBN Agency. Last I checked, the range data is fairly thin for the 979 prefix, largely because most of the possible values within the prefix remain unassigned. {{Nihiltres |talk |edits}} 16:52, 26 August 2022 (UTC)[reply]

Discussion Tools / Reply Tool - find user is not working

Tracked in Phabricator
Task T316219
Resolved
Thanks for the info. Gråbergs Gråa Sång (talk) 15:11, 25 August 2022 (UTC)[reply]

Sidebar customisation by namespace

XPosted from MW.org's support desk. Since this received no replies the first time, I'll try my luck here and see what actions/suggestions can be respectively taken/received.

On my creative-venture wiki, I've had a bit of trouble getting a particular sidebar section to work on the namespaces it's supposed to be visible on. Despite following the advice at mw:Manual:Interface/Sidebar#Parser functions in sidebar, the target section is not showing up and the affected HTML segment is no better for it.

From my site's own Sidebar message: 

* {{#switch:{{NAMESPACE}}{{!}}Voablivrile{{!}}Grammar{{!}}Corpus {{!}}Entry{{!}}Morpheme{{!}}Rhymes=Tovasala}}
** {{#switch:{{NAMESPACE}}{{!}}Voablivrile{{!}}Grammar{{!}}Corpus {{!}}Entry{{!}}Morpheme{{!}}Rhymes=Portal:Tovasala Dictionary{{!}}Home page}}
** {{#switch:{{NAMESPACE}}{{!}}Voablivrile{{!}}Grammar{{!}}Corpus {{!}}Entry{{!}}Morpheme{{!}}Rhymes=Voablivrile:Grammar{{!}}Grammar}}
** {{#switch:{{NAMESPACE}}|Voablivrile|Grammar|Corpus|Entry|Morpheme|Rhymes=Special:Random/Entry{{!}}Random headword}}
** {{#switch:{{NAMESPACE}}|Voablivrile|Grammar|Corpus|Entry|Morpheme|Rhymes=Special:Random/Morpheme{{!}}Random morpheme}}
** {{#switch:{{NAMESPACE}}|Voablivrile|Grammar|Corpus|Entry|Morpheme|Rhymes=Special:RandomInCategory/Snippets{{!}}Random snippet}}
** {{#switch:{{NAMESPACE}}|Voablivrile|Grammar|Corpus|Entry|Morpheme|Rhymes=Special:Random/Rhymes{{!}}Random rhyme list}}

HTML source: 

<nav id="p-{{#switch:{{NAMESPACE}}{{!}}Voablivrile{{!}}Grammar{{!}}Corpus_{{!}}Entry{{!}}Morpheme{{!}}Rhymes=Tovasala}}" class="mw-portlet mw-portlet-_switch_NAMESPACE_Voablivrile_Grammar_Corpus_Entry_Morpheme_Rhymes_Tovasala emptyPortlet vector-menu vector-menu-portal portal" aria-labelledby="p-{{#switch:{{NAMESPACE}}{{!}}Voablivrile{{!}}Grammar{{!}}Corpus_{{!}}Entry{{!}}Morpheme{{!}}Rhymes=Tovasala}}-label" role="navigation" 
	 >
	<h3 id="p-{{#switch:{{NAMESPACE}}{{!}}Voablivrile{{!}}Grammar{{!}}Corpus_{{!}}Entry{{!}}Morpheme{{!}}Rhymes=Tovasala}}-label" class="vector-menu-heading"> <span>{{#switch:{{NAMESPACE}}{{!}}Voablivrile{{!}}Grammar{{!}}Corpus {{!}}Entry{{!}}Morpheme{{!}}Rhymes=Tovasala}}</span>

Either I'll have to wait on a native fix from @Bawolff: or otherwise, or I'll provide a CSS-based solution of my own if it works later. --Slgrandson (How's my egg-throwing coleslaw?) 14:15, 25 August 2022 (UTC)[reply]

@Slgrandson: The only {{!}} should be in the output of the parser functions, i.e. before the link text. Try normal pipes in all other places. I don't have a place to test it myself. PrimeHunter (talk) 14:51, 25 August 2022 (UTC)[reply]
@PrimeHunter: Though I followed your advice, nothing--not even the MW.org {{#ifeq:}} approach--seems to work (at least on my site). When previewed through the Refreshed and Truglass skins, the sidebar setup at this writing:
* Tovasala
** {{#ifeq:{{NAMESPACE}}|Category|Portal:Tovasala Dictionary{{!}}Home page}}
only displays the "Tovasala" header with nothing below it. Either I'll get the Miraheze Phabricator team to look into it, or I'll have to go the CSS route myself...
P.S. Is this no longer actually supported in MW 1.38+? --Slgrandson (How's my egg-throwing coleslaw?) 11:25, 26 August 2022 (UTC)[reply]
Now tracked at MH T9699 in case anyone's paying further attention. --Slgrandson (How's my egg-throwing coleslaw?) 20:08, 26 August 2022 (UTC)[reply]
We aren't a support forum for non-WMF wikis. Please move along. Izno (talk) 20:18, 26 August 2022 (UTC)[reply]

Missing TOC without any magic word in use

I see that WP:Village pump (technical)/Archive 198 does not have TOC in Vector legacy skin. All revisions before Special:Diff/1097874722 had the TOC. All revisions since this revision doesn't. I don't see any obvious magic words added via this edit. So what went wrong? —CX Zoom[he/him] (let's talk • {C•X}) 15:32, 25 August 2022 (UTC)[reply]

The __NOTOC__ is in {{int:protectedpagetext|editprotected|create}} per Special:ExpandTemplates. Izno (talk) 15:41, 25 August 2022 (UTC)[reply]
(edit conflict) @CX Zoom: it is coming in via this line: {{int:protectedpagetext|editprotected|create}}. — xaosflux Talk 15:45, 25 August 2022 (UTC)[reply]
Fixed by adding __TOC__.[2] PrimeHunter (talk) 15:52, 25 August 2022 (UTC)[reply]
Thank you everyone. —CX Zoom[he/him] (let's talk • {C•X}) 16:39, 25 August 2022 (UTC)[reply]

Duplicated header tabs on Timeless

Screenshot of the issue

Must be THURSDAY... is anyone else having duplicated header tabs on Timeless? I know it's not a script, I've been able to reproduce this issue with safemode. ~ Matthewrb Talk to me · Changes I've made 15:59, 25 August 2022 (UTC)[reply]

After some additional searching, it appears to have been reported to Phab: T316196 ~ Matthewrb Talk to me · Changes I've made 16:02, 25 August 2022 (UTC)[reply]

Desktop version on mobile being too wide occasionally

Example screenshot

At Wikipedia:Village pump (technical)/Archive 198#Global projects being too wide since yesterday, I reported how on some projects are being so wide that text there is illegible, that hadn't yet affected enwiki. Today, it finally did. But it is very picky on when it works. Whenever, I click "open in a new tab" *any* (diff|hist) link found at Watchlist, the resultant page is too wide with a 70-30 probability, but that goes away on refreshing. On the other hand, if I click "open in a new tab" from normal content pages, width remains normal the same thing happens. This issue is a new one. —CX Zoom[he/him] (let's talk • {C•X}) 16:55, 25 August 2022 (UTC)[reply]

What kind of mobile device is this ? Screen dimensions, browser ? Also is your zoom set to 100% ? —TheDJ (talk • contribs) 18:21, 25 August 2022 (UTC)[reply]
Android 11 smartphone using MS Edge. All zoom/accessibility settings at system default. —CX Zoom[he/him] (let's talk • {C•X}) 19:40, 25 August 2022 (UTC)[reply]
To be clear, the issues are happening globally on all projects. On Vector legacy, things are extremely stretched (see screenshot above) and minimised. On vector-2022, there are long empty spaces on either side of the screen and the actual content is minimised. —CX Zoom[he/him] (let's talk • {C•X}) 11:05, 27 August 2022 (UTC)[reply]
On Safari on an iPad, every time a page loads it’s zoomed by approx 20% so too wide for the screen. Resetting the zoom to 100% (cmd-0) fixes it until you refresh or visit another page. I assume this is the same issue.—Northernhenge (talk) 20:50, 27 August 2022 (UTC)[reply]

Redlinks are a different red

It's Thursday, and the red links seem to have a different red color. What may be causing this? Weeklyd3 (talk) 22:45, 25 August 2022 (UTC)[reply]

It's deliberate. See #Tech News: 2022-34 and phab:T213778. PrimeHunter (talk) 23:08, 25 August 2022 (UTC)[reply]
Thanks for pointing that out. I don't like this new color so I'm changing it back in my CSS file. Weeklyd3 (talk) 23:11, 25 August 2022 (UTC)[reply]
I'm going to give it a week or two before I make any decisions about it. This sort of change always feels weird initially. Whatamidoing (WMF) (talk) 03:23, 26 August 2022 (UTC)[reply]
I don't like the new visited link colour, especially in my watchlist. Dreamy Jazz talk to me | my contributions 14:43, 26 August 2022 (UTC)[reply]
I'm glad they made the change, but I don't really want the new colors right now and I can't figure out how the CSS works to customize it. —Danre98(talk^contribs) 13:48, 27 August 2022 (UTC)[reply]
What the Tech News item doesn't say is that only the Vector skin is affected. —Kusma (talk) 12:17, 27 August 2022 (UTC)[reply]

Editing news 2022 #2

Read this in another language • Subscription list for this multilingual newsletter

Graph showing 90-minute response time without the new tool and 39-minute response time with the tool
The [subscribe] button shortens response times.

The new [subscribe] button notifies people when someone replies to their comments. It helps newcomers get answers to their questions. People reply sooner. You can read the report. The Editing team is turning this tool on for everyone. You will be able to turn it off in your preferences.

–Whatamidoing (WMF) (talk) 00:35, 26 August 2022 (UTC)[reply]

I don't have a specific deployment date for this wiki, but I want to say that I really like this and use it regularly. I'm curious how it will change our communication patterns in the long term. (Will we ping less, since everyone subscribes/follows the threads they're interested in? Will we learn to deliberately slow down our response times in heated conversations?) Whatamidoing (WMF) (talk) 03:25, 26 August 2022 (UTC)[reply]
It would be fantastic if someone could produce a gadget to move these pings out of the notification bar and into the watchlist where every other reply appears. I don't know whether that's technically possible. Then we could, for example, watch one RfD without triggering a watchlist entry every time someone comments on a different redirect listed on the same day. Certes (talk) 10:05, 26 August 2022 (UTC)[reply]
I've been using the [ subscribe ] button for months. It's a huge efficiency. My main use case is watching a section of a busy noticeboard, without watchlisting the entire 100-edit-a-day noticeboard. I really hope they implement this Phab ticket, which would let you subscribe to headings lower than the first level. This would open up a whole new world of useful subsections to subscribe to on pages such as AE, TFD, CFD, RFD, FFD, RPFF/I, DRV, and ITN. –Novem Linguae (talk) 10:13, 26 August 2022 (UTC)[reply]
A gadget is not technically possible. Izno (talk) 17:12, 26 August 2022 (UTC)[reply]
@Certes, you could try Bawl which can do both (notifications and watchlist). — Qwerfjkltalk 21:03, 26 August 2022 (UTC)[reply]

Can't make image larger

Okay, last time I asked about this I was terribly misunderstood and the issue was not resolved. I am currently working on the Josquin des Prez article and am unable to increase the size of the lead image of a woodcut of Josquin. I have tried using both "px number" or "upright=1.whatever" as I normally do to change images, but for some reason this is not working. Does anyone know what the issue is? I am just trying to make it a little larger so it fits the width of the Renaissance music sidebar below. Aza24 (talk) 04:37, 26 August 2022 (UTC)[reply]

It's just a really tiny image (as uploaded) - only 20kb. When they say "No higher resolution available" on the file you can't make it any larger on-wiki, afaik anyway. You could find a larger file & upload that, or no doubt expand it with photo-editing software off-wiki, then upload that. Johnbod (talk) 04:55, 26 August 2022 (UTC)[reply]
Thanks John! New image now uploaded. Aza24 (talk) 05:49, 26 August 2022 (UTC)[reply]

"More" dropdown in Vector Legacy tab bar is broken

Tracked in Phabricator
Task T315418

As of today, when I roll over the "More" tab in the tab bar on Vector Legacy, the menu doesn't show up. I have to click it to make it show up, where previously I could just roll over it. I tried it with my alt account and I had the same problem so it's not caused by a gadget or script. Is there a Phabricator ticket for this? —pythoncoder (talk | contribs) 05:34, 26 August 2022 (UTC)[reply]

Known bug. There's a patch for this one currently in code review. phab:T315418. Should hopefully be fixed in a week or two. –Novem Linguae (talk) 10:22, 26 August 2022 (UTC)[reply]

Global login

Has something changed in the way global login works? I logged out yesterday and I logged back in here and I found out that I wasn't logged in anywhere else anymore. I waited a bit, tried different projects, refreshed the page and cleared caches but nothing worked. I tried logging in "locally" and yes, it worked fine but still it looks like I have to do that on every project now. I thought that maybe something has changed and now I need to login to Meta to make it global so I went there and there was the only place where I got the mw.notify message saying that I should reload to load my user settings (without needing to log in first). I thought it got fixed and I would be logged in globally after that but I went to Commons immediately after and, no, I still wasn't. What is going on? - Klein Muçi (talk) 11:17, 26 August 2022 (UTC)[reply]

Unable to reproduce. When I do the logout and login thing, it will either keep me logged in on other projects, or it will re-log me in when I load a second page on that project. Perhaps a recent bug in mw:ExtensionCentralAuth? Does anyone else have OP's problem? –Novem Linguae (talk) 11:44, 26 August 2022 (UTC)[reply]
Novem Linguae, it's very inconsistent. I followed your MW link now and it gave me the message to reload for applying user settings on Mediawiki. Tried going to WikiQuote and I don't get it. Maybe it's a temporary server/database problem. :/ — Klein Muçi (talk) 11:47, 26 August 2022 (UTC)[reply]
Just to be clear, some projects don't log you back in at all, right? –Novem Linguae (talk) 11:51, 26 August 2022 (UTC)[reply]
Novem Linguae, they don't log me back automatically. I can log in normally to them if I put my credentials and they stay logged in. — Klein Muçi (talk) 11:54, 26 August 2022 (UTC)[reply]
What browser are you using? It may be blocking certain cookies needed for central login. Rummskartoffel 14:45, 26 August 2022 (UTC)[reply]
Google Chrome. Klein Muçi (talk) 15:52, 26 August 2022 (UTC)[reply]
Hmm, then it's less likely cookies being blocked is the problem, Chrome doesn't really do that as much, AFAIK. Still, try going to chrome://settings/cookies and making sure that "Block third-party cookies" or "Block all cookies (not recommended)" are not selected, but instead either "Allow all cookies" or "Block third-party cookies in Incognito". Rummskartoffel 16:23, 26 August 2022 (UTC)[reply]
Rummskartoffel, I switched to "Allow all cookies" momentarily and that fixed it! Thank you! There I saw the option: Sites that can always use cookies
Do you know what exactly would I need to put into it to allow all Wikimedia's sites to use cookies? - Klein Muçi (talk) 20:37, 26 August 2022 (UTC)[reply]
Enter [*.]wikipedia.org into the "Site" field, and tick Work done! "Including third-party cookies on this site". Do the same for all Wikimedia domains, i.e. [*.]wiktionary.org, [*.]wikimedia.org etc. Rummskartoffel 21:29, 26 August 2022 (UTC)[reply]
Rummskartoffel, ah! Is there no way to do it for all domains at once? That's what I was hoping for. :P - Klein Muçi (talk) 22:33, 26 August 2022 (UTC)[reply]
I don't think there is, no. Rummskartoffel 10:39, 27 August 2022 (UTC)[reply]
Rummskartoffel :( Thank you anyway! - Klein Muçi (talk) 15:31, 27 August 2022 (UTC)[reply]
CentralAuth doesn't play nice with how browsers function these days. Probably nothing happened yesterday, it's just the first time you've bumped into the issue. Izno (talk) 17:14, 26 August 2022 (UTC)[reply]
Izno, most likely. I don't log out pretty often so... Glad I could solve it though. - Klein Muçi (talk) 20:37, 26 August 2022 (UTC)[reply]

Problem with G13 eligible soon category

Hi, folks,

We have a category that some editors working in the AFC area check, Category:AfC G13 eligible soon submissions. It contains drafts and user pages that will become eligible for CSD G13 status in the next 30 days. Sometimes editors check the category to tag drafts for deletion when they become eligible, other times they "rescue" promising drafts that would otherwise be deleted. Typically, the total number of pages is around 3,000-5,000 drafts and user pages. The number can sometimes go down to 2,000 but the category always refills itself. We use to have a problem with the category becoming empty about a year or year and a half ago but I worked with ProcrastinatingReader and he had some way of making sure that the category periodically refilled.

Any way, there haven't been any problems with this category for a long time but I periodically check it and the category is down to 1,426 pages! We typically have 200-225 drafts expire each day so that isn't even a week's worth of pages. I went to ProcrastinatingReader's talk page but he has been away since May 2022. I'm not sure what he did to refill the category but I'm guessing it had something to do with bots categorizing drafts and I'm hoping someone here will know something or at least have a good guess.

We do have a back-up system, SDZeroBot's lists, but some editors prefer to use the category because it has had the most up-to-date listing. Any ideas or fixes you can think of? Thanks in advance for any help you can offer. Liz Read! Talk! 05:38, 18 August 2022 (UTC)[reply]

I posted this message at the Bot Noticeboard 9 days ago and didn't get any helpful advice there except a report of a sighting of PR on a phab ticket. I've since emailed PR but no response. The category is now down to 550 pages and will be completely empty in a few days. Any advice from anyone on what can be done here? Thanks! Liz Read! Talk! 18:08, 26 August 2022 (UTC)[reply]
Is this one of the problems that can be fixed by performing a null edit on all pages linked from User:SDZeroBot/G13 soon sorting? —Kusma (talk) 19:57, 26 August 2022 (UTC)[reply]
Hello, Kusma,
I don't know about that but there are 5942 drafts on that page! I'm not skilled in the editing tools that would make this possible other than manually doing this over the weekend and I'm not that ambitious. But thanks for the suggestion. Liz Read! Talk! 22:05, 26 August 2022 (UTC)[reply]
Probably yes. * Pppery * it has begun... 22:18, 26 August 2022 (UTC)[reply]
The proposed algorithm (null editing all wikilinks on the page User:SDZeroBot/G13_soon_sorting) would be super easy to code a bot for, and I am willing to do so. As a test of the proposed algorithm, I tried purging and null editing Draft:Grayson Souter, which is on the User:SDZeroBot/G13_soon_sorting list but not the Category:AfC G13 eligible soon submissions list, and it did not add itself to the category. Am I doing something wrong, or is the algorithm incorrect? Let's get the algorithm verified with a test case before moving forward. That is, let's find a page that should be in the category but isn't, null edit it, then make sure it appears in the category after the null edit. –Novem Linguae (talk) 22:29, 26 August 2022 (UTC)[reply]
I think I found some documentation for ProcBot. At User:ProcBot/PurgeList: The bot can purge all members of a category, including their links and categories. Use page User:ProcBot/PurgeList2. So it appears to be a purge, not a null edit. On the PurgeList2 page, we have the following data:
{{/purge-cat|Category:Declined AfC submissions|7|day}}
::::{{/purge-cat|Category:Rejected AfC submissions|7|day}}
::::{{/purge-cat|Category:Pending AfC submissions|6|day}}
Most of that seems straightforward, except the "including their links and categories" part. Does that mean it does some sort of recursion? Hmm. I wish PR had released their source code. Re-inventing the wheel is kind of meh. Ping @ProcrastinatingReader on the off chance they log in. –Novem Linguae (talk) 22:52, 26 August 2022 (UTC)[reply]
I think it just means passing forcelinkupdate to the purge API (see Special:ApiHelp/purge). And Draft:Grayson Souter did not get added to the category because it's not an AfC submission (the category is added by {{AfC submission}}) * Pppery * it has begun... 23:01, 26 August 2022 (UTC)[reply]
BRFA filed –Novem Linguae (talk) 23:18, 26 August 2022 (UTC)[reply]

Two list manipulation questions

Hi, not sure where to ask this, I'm hoping someone knowledgeable can point me in the right direction:

  1. I want to compare two large lists of page links (lists of ~10k articles against the list of ~50k Vital Articles). When I make the lists on AWB (either in the regular list maker, or in the list comparer tool), it cuts off the list (at 5k, 10k, or 25k, depending on the tool and how I make the list). Is there a tool that will help me do this for large lists (~50k), or some existing method?
  2. I have lists of >10k bluelinks, and I'd like to separate links to redirects from links to disambiguation pages and links to articles. Is there a tool/method to do this?

Thanks for your help! Levivich 19:39, 26 August 2022 (UTC)[reply]

Have you tried page pile? IDK if it will help. Izno (talk) 20:08, 26 August 2022 (UTC)[reply]
Re first item: depending on what you want to do, Version control-oriented plain text diff tools might work for your task. For example, install Notepad++ and its "Compare" plugin from app's plugin manager or KDiff3. —⁠andrybak (talk) 20:11, 26 August 2022 (UTC)[reply]
Thank you Izno and Andrybak, that got me where I needed to go! I didn't know about PagePile, and that also reminded me about PetScan. PetScan will create the very large lists, and will follow redirects (or not) and there's a flag for tagging disambiguation pages, and it'll output it to either PagePile or some other format, and then I can use PP or Notepad++ to do the list comparisons, even with large lists. That's what I was looking for: thanks again!! Levivich 20:34, 26 August 2022 (UTC)[reply]
(edit conflict) Re second item: you could paste your list into Wikipedia:PetScan (field "Manual list" in the "Other sources" tab) and try to intersect it with Category:All article disambiguation pages and Category:Main namespace redirects (PETSCAN might not like going deep into this category) correspondingly.
On Wikipedia itself, wikilinks to redirects produce <a> tags with class="mw-redirect", wikilinks to disambigs have class="mw-disambig". Wikilinks to articles don't have any special CSS classes added to them. JS or even CSS tricks could be used to selectively filter/display the portion of the list that you want:
/* hide links to redirects */
.mw-parser-output a.mw-redirect {
  display: none;
}
/* hide links to disambigs */
.mw-parser-output a.mw-disambig {
  display: none;
}
/* hide links to regular articles */
.mw-parser-output a:not([class]) {
  display: none;
}
—⁠andrybak (talk) 20:38, 26 August 2022 (UTC)[reply]
Unix CLI tools.[3] Awk is easiest. -- GreenC 04:26, 28 August 2022 (UTC)[reply]

External tools not working

External tools on talk pages not working.....wmcloud.org. down?

Find addition/removalFind edits by user (Alternate)Page statisticsPageviewsFix dead links

Moxy- 14:53, 27 August 2022 (UTC)[reply]

 Works for me @Moxy are you still having this problem? What is happening when you try? — xaosflux Talk 14:59, 27 August 2022 (UTC)[reply]
Still down this page stats.Moxy- 15:03, 27 August 2022 (UTC)[reply]
Your link worked for me. What is exact error message you're getting when you visit that link? –Novem Linguae (talk) 15:04, 27 August 2022 (UTC)[reply]

Article count going down?

I periodically track various Wikipedia statistics. I've just seen the following:

  • 2022-08-09: 6,562,221 articles
  • 2022-08-27: 6,544,978 articles

This is remarkable; article count typically goes relentlessly upward, with the occassional deletions being a drop in the ocean compared to article creations. So: is the article counter broken, or have ~18,000 articles been deleted recently, or is this something else? Does anyone know what's actually going on? — The Anome (talk) 19:08, 27 August 2022 (UTC)[reply]

See Wikipedia:Village pump (miscellaneous)#30,000 articles gone missing? * Pppery * it has begun... 19:17, 27 August 2022 (UTC)[reply]

Three of five Great Lakes missing on map

There is a route map at Interstate 80 that does not show Lake Huron, Lake Erie or Lake Ontario. Instead, it shows a gigantic non-existent land border between the U.S. and Canada. This problem has been reported since 2019. What can be done to fix it? Cullen328 (talk) 19:13, 27 August 2022 (UTC)[reply]

Yes, that's really weird; the higher-resolution map that opens when you click the map does not have that problem, so it looks like the current software and data work fine. Perhaps all that is needed is to re-render the map thumbnail? — The Anome (talk) 19:28, 27 August 2022 (UTC)[reply]
I have no idea how to even try that, The Anome. Cullen328 (talk) 19:31, 27 August 2022 (UTC)[reply]
I've tried purging the article, which typically re-renders everything on the page, and it does not change anything; the map is still missing lakes. More perplexingly, when I experiment with hacking the URL of the embedded image in the page to generate novel image sizes, for example, like this: https://maps.wikimedia.org/img/osm-intl,a,a,a,365x483@2x.png?lang=en&domain=en.wikipedia.org&title=Interstate+80&groups=_282cfae208f7f8f41a530a00b3795d6c65bc261f, thus forcing it to render new images, the maps you get are still missing the three lakes. Yet the map generated by https://en.wikipedia.org/wiki/Interstate_80#/map/0 renders all five lakes correctly. If huge features like Great Lakes are omitted, who knows what other map features are being missed out?

This is clearly a technical problem, and one for WMF engineering to investigate. — The Anome (talk) 19:39, 27 August 2022 (UTC)[reply]

zoom=5 zoom=4 zoom=2 (no line)

Map

Map

Map

Seems an issue for |zoom= less than 5. Changing the window size, coordinates of the map centre or included oblects doesn't seem to matter. —  Jts1882 | talk  19:48, 27 August 2022 (UTC)[reply]
See Wikipedia:Village_pump_(technical)/Archive_194#Missing_Great_Lakes from last December. The associated Phab ticket says the problem was fixed. I have no idea if the fix really didn't work or this is a new/different problem. MB 21:26, 27 August 2022 (UTC)[reply]
It does seem to have been fixed, but has since unfixed itself. It looks likely that the underlying problem is phab:T218097. Can someone please inform the relevant people on the engineering team? — The Anome (talk) 21:42, 27 August 2022 (UTC)[reply]
Posting in relevant phab tickets with a link to and summary of this discussion will likely generate emails to the relevant software engineers. Might be worth a try :) –Novem Linguae (talk) 22:09, 27 August 2022 (UTC)[reply]
  • Don't fix this. I like this map better. Lol. Schierbecker (talk) 21:46, 27 August 2022 (UTC)[reply]
    Is the simplified version 50% superior? Certes (talk) 00:48, 28 August 2022 (UTC)[reply]
    The missing lake is eerie. -- GreenC 04:28, 28 August 2022 (UTC)[reply]
    some goof drew the borders of canada wrong. The good side of niagara falls is on the canadian side. pls fix right away. Schierbecker (talk) 05:43, 28 August 2022 (UTC)[reply]

There also appears to be a problem with rendering the lakes Vänern and Vättern in Sweden, and Lake Ladoga in Russia. Schierbecker (talk) 05:15, 28 August 2022 (UTC)[reply]

  • I'm not sure if this is a related problem, but there is some shenanigans going on with the 1994 treaty line between Israel/Palestine and Jordan. When you zoom in, parts of the border pop into and out of existence. Also many of the oases around the Dead Sea (like Ein Gedi) do the same thing. Schierbecker (talk) 05:54, 28 August 2022 (UTC)[reply]

Two "Speedy" drop-downs with CSDHelper

Hi all,

When I look at a page that's tagged for speedy deletion, I see

| Article | Talk | Speedy | Speedy |

This is with the User:Chairboy/csdhelper.greasemonkey.js script.

Both drop-down menus are functional. Super-low priority, just odd.

(And as for the "kangaroo" emoji, uh, it looks like a snail poking its head out of a hole to me, but not much we can do about that here.)

User:Shirt58 (talk) 🦘 02:28, 28 August 2022 (UTC)[reply]

A recent software change (Krinkle, this is report #4 of brokenness) has made it so if you are importing the same script multiple times, instead of cleaning up for you, it will run the script as many times as you import it. Depending on which skin you are using, you have a copy of this script in both your common.js and your vector.js/monobook.js. Remove the skin versions to correct it. Izno (talk) 05:11, 28 August 2022 (UTC)[reply]

www.youtube.com/watch: dateText

https://www.youtube.com/watch?v=QpiRWKRn1tE has ,"dateText":{"simpleText":"Jun 1, 2022"}}},

using source code editor citation template please parse for :

<ref>{{cite web ... |date=Jun 1, 2022}}</ref> ....0mtwb9gd5wx (talk) 06:38, 28 August 2022 (UTC)[reply]

Search CRASH !

result was: upstream connect error or disconnect/reset before headers. reset reason: overflow .... 0mtwb9gd5wx (talk) 06:54, 28 August 2022 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(technical)&oldid=1107114762"