Wikipedia talk:Twinkle

"WT:TW" redirects here. For other uses, see WikiProject Taiwan talk page.

Adding Redirect Cat Causes Double Redirect

Where do I report an error in trying to add a redirect category to an existing redirect using the Tag button?

I tried to add the {{R with possibilities}} tag to a redirect, and it created a second empty redirect shell. The original redirect had been Special:Permalink/1210632744. When I tried to add the additional category, using the Tag button, it applied this diff: Special:Diff/1237443069. As can be seen, it moved the existing redirects into a new shell, leaving an empty shell. Robert McClenon (talk) 00:30, 30 July 2024 (UTC)

When you say "double redirect", are you referring to the issue described at WP:2R? I haven't heard the phrase used in any other sense before. jlwoodwa (talk) 22:03, 1 August 2024 (UTC)

Those links don't work. Nardog (talk) 01:49, 8 August 2024 (UTC)

Dark mode compatibilty

Tracked in github.com
Issue #1979

I used the AFD functionality of Twinkle today, and with dark mode enabled I was barely able to use the form because of some light-grey-on-white text. There are some official recommendations for fixes at mw:Recommendations for night mode compatibility on Wikimedia wikis. Usually I find either picking mode-sensitive colors from the official palette or using class="skin-invert" does the job. -- Beland (talk) 06:29, 9 August 2024 (UTC)

I converted the warn module a week or two ago. Myself or someone else needs to convert all the other modules now. –Novem Linguae (talk) 07:27, 9 August 2024 (UTC)

A potential tweak if within our rules

Tracked in github.com
Issue #1988

When an editor is indeffed and can take no action, Twinkle still notifies them of AfD, CSD, etc. That seems a difficult thing to receive, and is probably pointless. If it is within our rules, please can Twinkle at least have an option not to post the user advisory message when the editor it would notify is indeffed? 🇺🇦 Fiddle^Timtrent Faddle^Talk to me 🇺🇦 07:51, 9 August 2024 (UTC)

This has come up a couple times this year, with me and Primefac often opposing, and others supporting, but too low participation to get a good consensus. Might be time to RFC it to get more participation. Taking away an editor's right to be notified of their articles getting deleted feels like a big deal to me so I am hesitant to change the status quo without a consensus. –Novem Linguae (talk) 08:11, 9 August 2024 (UTC)

At the very least it seems it should be rate limited. It feels not great to see a blocked user suddenly get 20 notifications of article deletions, it looks very much like rubbing salt in a wound. CMD (talk) 09:44, 9 August 2024 (UTC)

Just noting that one can turn off the "notify page creator" box when nominating a page (though if the page is PRODded a bot will notify them anyway). Primefac (talk) 10:36, 9 August 2024 (UTC)

@Primefac And I never noticed it previously. Thank you.

A tweak that would be unlikely to need consensus might be a message "The editor who will be notified is blocked indefinitely and can take no action, are you sure you wish to notify them? If not please choose This option ->>>>" to highlight the option. I doubt I am alone in failing to spot it. 🇺🇦 Fiddle^Timtrent Faddle^Talk to me 🇺🇦 11:30, 9 August 2024 (UTC)

"User is blocked" would fit better in the space given. Primefac (talk) 12:13, 9 August 2024 (UTC)

I'm not wedded to any particular words 🇺🇦 Fiddle^Timtrent Faddle^Talk to me 🇺🇦 14:26, 9 August 2024 (UTC)

@Novem Linguae I agree that such a change would require consensus were it to change the default state. 🇺🇦 Fiddle^Timtrent Faddle^Talk to me 🇺🇦 11:27, 9 August 2024 (UTC)

For what it's worth, I also oppose this. Indeffed users get unblocked sometimes and there's no harm in the user getting talk page notifications about it. Hey man im josh (talk) 12:54, 9 August 2024 (UTC)

I somewhat agree to this, for example, some LTAs in proxies that I have been dealing with don't really need those long warnings as they will never read them. However, it does concern me that some users will not use this function appropriately.

I did notice the Speedy template says ": Please consider placing the template: XXXX on the talk page of the author.", in which Twinkle already does. Myrealnamm (💬pros · ✏️cons) 14:53, 12 August 2024 (UTC)

Maybe just letting the twinkle user know someone is blocked could be a good compromise. https://github.com/wikimedia-gadgets/twinkle/issues/1988 –Novem Linguae (talk) 15:46, 12 August 2024 (UTC)

Ok, I see your point. Myrealnamm (💬pros · ✏️cons) 15:49, 12 August 2024 (UTC)

I'd just like to comment that this doesn't always work. I've unchecked it before in cases involving SPAs and obvious public relations article creators, but resulted in a bot intervening and leaving an automated notification on the creator's talk. Courtesy ping to @Timtrent:. Graywalls (talk) 18:14, 12 August 2024 (UTC)

Template:Uw-blank1

My Twinkle doesn't have these template, I have not seen any Twinkle users using this template as well, so does Twinkle use this template or not? The notice starting with If you plan to make breaking changes to this template... exists on uw-blank1 and uw-blank2, should it be removed? Myrealnamm (💬pros · ✏️cons) 14:55, 12 August 2024 (UTC)

Wikipedia:List of policies should be in Twinkle welcome messages

This is a very useful summary of our policies. I've seen at least one case today where an editor could have avoided problems if whatever welcome they had linked to this. Doug Weller talk 10:53, 14 August 2024 (UTC)

I think this might be something to discuss on the welcome templates talk pages (or a central WikiProject if there is one); Twinkle just places the notifications, it doesn't control or maintain them. Primefac (talk) 10:58, 14 August 2024 (UTC)

I agree 100% (I come from here). JacktheBrown (talk) 11:43, 14 August 2024 (UTC)

CTOP notifications

Tracked in github.com
Issue #1806

Are these not available in Twinkle or are they buried somewhere? Kcmastrpc (talk) 17:54, 17 August 2024 (UTC)

It's not native to Twinkle. But User:TheresNoTime/Scripts/CT-Helper.js is a good workaround. –Novem Linguae (talk) 18:42, 17 August 2024 (UTC)

Uw-AI

Tracked in github.com
Issue #1901

Should you include the AI user warning templates? Ahri Boy (talk) 07:21, 20 August 2024 (UTC)

Sure. We've got a ticket and a patch for that, so it's in progress. In the meantime you can go into Twinkle's preferences and add those warning templates to your custom warning templates. –Novem Linguae (talk) 10:04, 20 August 2024 (UTC)

Thanks. Some warning templates haven't been added into the software. I might mention later. Ahri Boy (talk) 00:22, 21 August 2024 (UTC)

Fringe theories

Tracked in github.com
Issue #1996

Please can you add {{Fringe theories}} to the standard installation for maintenance tags

thanks,

Daisytheduck ^{quack quack} 01:18, 27 August 2024 (UTC)

"One source|Section" tag moved to multiple issues box at top

Tracked in github.com
Issue #1997

When adding a "globalize" tag, I had the "use multiple issues box" checked. To my surprise, some section tags were moved to the top[1]. This seems to be unwanted behaviour. Fram (talk) 12:24, 29 August 2024 (UTC)

CSD C4

Tracked in github.com
Issue #1994

Just noting that our language needs to be changed in the CSD reasons, the text for G8: Categories populated by a deleted or retargeted template needs to be updated to the new WP:C4 language (see e.g. Category:Singapore political party logo templates, which I deleted under the old G8 not remembering that it had been changed to C4). Primefac (talk) 10:16, 30 August 2024 (UTC)

Addition to CSD criteria list

Hello, Twinkle folks,

Could you add "C4. Unused maintenance categories" to your list of CSD criteria (see Wikipedia:Criteria for speedy deletion#C4. Unused maintenance categories)? I've been using "CSD G6 Housekeeping" as a deletion criteria for expired maintenance categories because I didn't see C4 on your list of options and I think this criteria would be more appropriate. Thank you. Liz ^{Read! Talk!} 20:31, 2 September 2024 (UTC)

Merged into previous section, same request. Primefac (talk) 00:16, 4 September 2024 (UTC)

Nomination for merger of Template:Advert

Template:Advert has been nominated for merging with Template:Promotional tone. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:05, 4 September 2024 (UTC)

Error when navigating away from page very quickly after page load

Tracked in github.com
Issue #1998

I've been noticing this issue for a while now but figured there was no way to fix it, until very recently when I managed to fix it in a script of mine. If you click a link to another page immediately after the page loads, there will often be an error message "Could not load your Twinkle preferences, resorting to default preferences". It seems like the browser (Firefox at least – haven't tested across browsers) makes all pending network requests fail as soon as navigation to a new page starts, but before JS execution stops, so the error handler still has a chance to run and display the message even though there was never actually an error.

The way I (mostly) fixed this was to add a beforeunload listener which sets a flag, and test that flag before displaying the error message. There are a few scenarios where this won't work, because a couple browsers (iOS Safari appearing to be the biggest example) don't fire the event, and it is possible for other scripts to cancel the page unload in their own beforeunload listeners. I figured not firing the event was not an issue (the error will just still show up, which is not a change), and that the chance of both having another script installed listening for beforeunload, and having the user both navigate away and also cancel that navigation in the VERY short time between the request being sent and completed is so low as to be negligible, especially for something as relatively trivial as displaying an error message. Tollens (talk) 21:22, 4 September 2024 (UTC)

I've noticed this nuisance message too. Perhaps the best way to handle it would be to convert it to a console.log() instead. Even if this message is legit, for example a person's Twinkle preferences page became corrupted, it is hard to imagine that the user would want a mw.notify() about this displayed every time they visit a page. –Novem Linguae (talk) 22:45, 4 September 2024 (UTC)

I had figured it was a useful message if it was actually supposed to show up – not sure, though. Reading the code, I don't think someone's preferences being corrupted would cause this particular error to fire (the "Could not load" one), since it should only happen if the network request doesn't complete normally. It would be very surprising, though, for someone to be able to load the Wikipedia page they are viewing but not their Twinkle preferences page, thinking about it further. Maybe changing only the "Could not load" error to a console.log (or .error, probably) and leaving the "Could not parse" error as mw.notify would make sense? Personally I would want to be harassed by an error message if I had screwed up my config file, but I might be an exception. Tollens (talk) 23:04, 4 September 2024 (UTC)

Sure, that's fine. I've updated the ticket to just change the load message to console.log() and not the parse message. –Novem Linguae (talk) 00:15, 5 September 2024 (UTC)

Notability category: organizations

Tracked in github.com
Issue #1999

If you tag an article with {{notability}}, Twinkle lets you select a subcategory, like {{notability|companies}}, which puts the article in Category:Company articles with topics of unclear notability. However, the dropdown menu is missing {{notability|organizations}}, which would populate Category:Organization articles with topics of unclear notability. I didn't notice this for a while, since WP:NCORP and WP:NORG are the same notability guideline, but it means a bunch of non-company organizations have ended up in Category:Company articles with topics of unclear notability. jlwoodwa (talk) 22:37, 4 September 2024 (UTC)

The dropdown already has {{notability|Companies}} which displays the same template and has a description of "notability guideline for companies and organizations". However it wouldn't hurt to add it if it helps people find the correct entry. Ticket created. –Novem Linguae (talk) 22:57, 4 September 2024 (UTC)

It's not just to help people find the correct entry. The issue is that {{notability|companies}} and {{notability|organizations}} aren't just synonyms – they place the article in different categories. jlwoodwa (talk) 23:15, 4 September 2024 (UTC)

I guess the template that is visible to the user is the same because WP:NCORP combines the two. But anyway, sounds good. I've updated the ticket. –Novem Linguae (talk) 00:16, 5 September 2024 (UTC)

Creator notification with WP:BLPPROD

Just curious if anyone can direct to me to why the option to not notify a page creator is deactivated when applying a BLPPROD? I'm guessing it is because these are usually very new articles but I just ran across one where the creator is long-term inactive. Just Step Sideways ^{from this world ..... today} 22:44, 4 September 2024 (UTC)

I followed the history of the line containing "has to be notified" in GitHub, and it goes back 14 years to the "initial import from Wikipedia". So it has been this way for at least 14 years. So the "why" is probably lost to history.

Isn't BLPPROD intended to motivate the author to add sources within 1 week to avoid deletion? If I had to guess, that is probably the reason. Kind of hard to motivate the author of an article to act if they are not notified.

This is also related to the discussion of how much to notify blocked users, which has been discussed on this talk page a couple times this year. –Novem Linguae (talk) 23:21, 4 September 2024 (UTC)

db-commons should be dated

When deleting a file under WP:F8 using Twinkle's dated speedy deletion module, {{db-commons}} is placed on the description page. This is a redirect to {{Now Commons}}, which ideally should be given a date as parameter. (Note that {{Now Commons}} can also be placed directly on a file's description page using Twinkle's file maintenance tagging module, which does pass the date as a parameter.) jlwoodwa (talk) 01:04, 6 September 2024 (UTC)