This is the talk page for discussing improvements to the Twinkle page.

Put new text under old text. Click here to start a new topic. New to Wikipedia? Welcome! Learn to edit; get help. Assume good faith Be polite and avoid personal attacks Be welcoming to newcomers Seek dispute resolution if needed

Archives: Index, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48Auto-archiving period: 30 days

Tips for writing good bug reports and feature requests: Include the affected article name and a diff. Include a screenshot. For bugs, include the exact steps to reproduce the bug. Bugs need to be reproducible. We will use this information to create a ticket on GitHub, which is our todo list for volunteer developers. For most tickets, expect them to take a long time (months). They will need to attract the interest of a volunteer developer, then go through code review, then get merged to master, then get deployed.

Twinkle has detailed documentation located at WP:TW/DOC.

Archives

Index 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 11, 12, 13, 14, 15, 16, 17, 18, 19, 20 21, 22, 23, 24, 25, 26, 27, 28, 29, 30 31, 32, 33, 34, 35, 36, 37, 38, 39, 40 41, 42, 43, 44, 45, 46, 47, 48

Other archives Friendly talk archives: 1, 2, 3, 4, 5 Old Bugs page; archive 1, 2, 3, 4, 5 Old RFA page; archive 1, 2

This page has archives. Sections older than 30 days may be automatically archived by Lowercase sigmabot III when more than 10 sections are present.

Documentation for ((COI)) says (formatting per original):

Like the other neutrality-related tags, if you place this tag, you should promptly start a discussion on the article's talk page to explain what is non-neutral about the article. If you do not start a discussion, any editor will be justified in removing the tag without warning.

[...]

Do not apply this tag simply because you suspect COI editing, or because there is or was a COI editor.

Can Twinkle be made to notify users of these terms, or at least to nudge them to comment on the talk page immediately after applying the template? There may be other templates with similar conditions, so a generic fix might be best. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:41, 15 March 2024 (UTC)[reply]

@Pigsonthewing. Looks like Twinkle already does this. Screenshot. –Novem Linguae (talk) 02:08, 29 March 2024 (UTC)[reply]

Yes, if "this" is part of my latter, fallback, suggestion. More would be better. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:01, 29 March 2024 (UTC)[reply]

 Courtesy link: Template:Dual fluency request

Non-breaking changes have been made to ((Dual fluency request)) to parallel similar changes to ((Translation request)) as discussed above at § Template:Translation request. I understand "non-breaking" as meaning that nothing will go wrong if you make no changes at the Twinkle end; however, the new version is more powerful, as it retrieves the foreign-language article automatically via Wikidata linkage. Parameter |orig= was formerly required in order to provide a link to the foreign article, but now it is no longer required and its use is discouraged. The |orig= parameter is still available (not deprecated) and if used, will override the Wikidata page link with whatever the user provides as the param value, so it exists solely as an override and to maintain backwards compatibility. If automatic processes generate the transclusion, then probably all you have to do is drop the use of parameter |orig=; everything else can remain the same; however nothing will break if you leave everything as is. If you do make the change, the result will be improved output at WP:PNT. Mathglot (talk) 01:45, 23 March 2024 (UTC)[reply]

@Mathglot. Thanks for your work on this. According to the program code, Twinkle posts in the format ((subst:duflu|pg=' + Morebits.pageNameNorm + '|Language=' + (lang || 'uncertain') + '|Comments=' + reason.trim() + ')) ~~~~. So I think it only uses the pg, language, and comments parameters of the template, and doesn't ever use orig. So probably no changes needed on Twinkle's end. –Novem Linguae (talk) 02:15, 29 March 2024 (UTC)[reply]

That sounds right to me. We should watch as the next few Duflu's from Twinkle come through to WP:PNT. I think the last one was this one, which says, "The initial language of this article was de.". I noticed another one just above it which also uses a lang code instead of a language name; could this be something in the Twinkle doc, or does Twinkle just point to the template doc and users are misreading/not reading it? Another upgrade to Duflu could eliminate this problem by emulating another change at Needtrans, which interprets lang codes if the user uses one by mistake instead of fully spelling out the language. Mathglot (talk) 02:38, 29 March 2024 (UTC)[reply]

Another upgrade to Duflu could eliminate this problem by emulating another change at Needtrans, which interprets lang codes if the user uses one by mistake instead of fully spelling out the language. This sounds like the way to go if it isn't too time consuming. In an ideal world, there's no reason these two similar templates should have divergent behavior for the same collected parameters. –Novem Linguae (talk) 04:12, 29 March 2024 (UTC)[reply]

@Steel1943. Hey there. Re this ping. Twinkle's current algorithm is to place entries directly below <!-- Add new entries directly below this line. -->. In the situation on that RFD page, a new user placed their entry above that comment, ignoring the instructions. My recommended fix is to move all entries below that comment. I am disinclined to change Twinkle's algorithm since it's simple and it usually works fine. Hope that makes sense. –Novem Linguae (talk) 02:01, 29 March 2024 (UTC)[reply]

@Novem Linguae: Of course (it makes sense). I was, more or less, suggesting that whatever XFDcloser does to determine the top of the page when relisting, somehow incorporate that into Twinkle with posting new RFDs since whatever XFDcloser does is not reliant on that hidden text whereas Twinkle is. Steel1943 (talk) 04:56, 29 March 2024 (UTC)[reply]

Can Twinkle be made to work with ((alert)) and its various permutations? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:04, 29 March 2024 (UTC)[reply]

I created a ticket for this in June of last year. Would be a lot of work though. Would probably need to create a new module. There's already a user script that does this at User:TheresNoTime/Scripts/CT-Helper.js if you want to try that out. –Novem Linguae (talk) 03:40, 30 March 2024 (UTC)[reply]

Often IP user's will add information that appears good faith, but could be problematic or suspected of lacking a neutral point of view. I would like to welcome these IP user rather than scare them off with a warning template. Could ((Template:Welcome-anon-unsourced)) added to the Twinkle selection list? It is a more friendly and instructive way of welcoming users rather than ((Template:Welcome-anon-unconstructive)). Apologies if this has been settled before. Classicwiki (talk) If you reply here, please ping me. 19:12, 29 March 2024 (UTC)[reply]

Sure. Ticket created. I think you can just add this as a custom welcome template in your Twinkle preferences though. Wikipedia:Twinkle/Preferences#welcome, "Custom welcome templates to display". Might be quicker than waiting for a patch. –Novem Linguae (talk) 03:51, 30 March 2024 (UTC)[reply]

I noticed that the Twinkle automated system for non-English welcomes does not support some languages for which we have a template, such as Italian and Hindi. Can this be fixed? Kind regards 14 novembre (talk) 🇮🇹 11:19, 3 April 2024 (UTC)[reply]

What are the exact template names please? –Novem Linguae (talk) 11:47, 3 April 2024 (UTC)[reply]

@Novem Linguae ((welcomeen-it)) and ((welcomeen-hi)) 14 novembre (talk) 🇮🇹 13:15, 3 April 2024 (UTC)[reply]

Sounds good. I created a ticket. Same advice as in the section above though. You can just add these to Twinkle via your Twinkle preferences. –Novem Linguae (talk) 14:40, 3 April 2024 (UTC)[reply]

@Novem Linguae Perfect. Thank you so much and kind regards 14 novembre (talk) 🇮🇹 15:58, 3 April 2024 (UTC)[reply]

It is in the speedy deletion procedure. Summaries for administrators are always "speedy deletion of <pagename>" while for all others (including me) it is "speedy deletion nomination of <pagename>" Why are summaries different for admins and others? Toadette ^{(Let's talk together!)} 22:37, 3 April 2024 (UTC)[reply]

@ToadetteEdit: Admins have the option of directly deleting the page with Twinkle, rather than simply nominating it for deletion. When this happens, Twinkle will leave a different warning template on the user's talk page that's been rewritten to inform the user that the page had already been deleted. For example, see the difference between ((Db-vandalism-notice)) and ((Db-vandalism-deleted)). —k6ka 🍁 (Talk · Contributions) 12:32, 4 April 2024 (UTC)[reply]

Good day, this is a courteous message to inform Twinkle’s maintainers and users that:

1.  Implemented: Revision and improvement to the body text in the warning message for ((Uw-copyright-new)), a 'Single-issue warning' in Twinkle.
2. Not sure. This should only affect Twinkle, and its users, if the boldtext parameter is used. In such a case, string of text in |boldtext=string of text may no longer function as expected as the body text at ((Uw-copyright-new/body)) has changed. But it seems it would be used more by users who would add the template manually than via Twinkle.
3. Checked: Checked testcases and tried implementation with Twinkle in many ways as possible. Functioning as expected.

waddie96 ★ (talk) 19:35, 5 April 2024 (UTC)[reply]

I only see the word "boldface" in Twinkle's code somewhere else, not in connection with ((Uw-copyright-new)). I don't think any action is needed. Thank you for checking. –Novem Linguae (talk) 21:54, 5 April 2024 (UTC)[reply]

I have noticed that when users respond to a welcome message that I have left using twinkle, I don't seem to get notified. Is there a way for me to fix this? Gaismagorm (talk) 20:00, 7 April 2024 (UTC)[reply]

It's a good idea and has been requested before. More info in this ticket. –Novem Linguae (talk) 21:35, 7 April 2024 (UTC)[reply]

ah ok Gaismagorm (talk) 21:48, 7 April 2024 (UTC)[reply]

For file maintenance, I suggest adding both ((Nominated for deletion on Commons)) and ((Deleted on Commons)) among the Twinkle options, as useful notice tags that the Commons copies of local files were nominated for deletion or deleted.

This is helpful in conducting future undeletion of files, in which the Commons copy should be requested for undeletion instead of transferring the local copy to Commons, as the transfer action effectively overwrites the deleted Cpmmons copy of the same file name. JWilz12345 (Talk|Contrib's.) 03:04, 8 April 2024 (UTC)[reply]

Sounds good to me. Ticket created. In the meantime, you can add them in Wikipedia:Twinkle/Preferences#tag -> Custom file maintenance tags to display -> Edit items. –Novem Linguae (talk) 08:53, 9 April 2024 (UTC)[reply]

@Novem Linguae thanks for opening the suggestion at GitHub. By the way, I also suggest the tags will be automatically placed above the information fields, like this. If the template is found at the lower part of the description page, some future file movers may not notice it and still conduct transfer of the said file even if there is an identical copy on Commons that can be simply requested for undeletion. JWilz12345 (Talk|Contrib's.) 10:19, 9 April 2024 (UTC)[reply]

@JWilz12345. Do you know if this is the "normal" spot to put the template? Is there an MOS:FILEORDER somewhere? Do we need to get consensus for placing these tags in an odd spot? –Novem Linguae (talk) 21:11, 12 April 2024 (UTC)[reply]

Is it possible to customize topics' titles or heading when using Twinkle? —Saqib (talk | contribs) 18:08, 11 April 2024 (UTC)[reply]

@Saqib. Is this for placing warnings on user talk pages? Something else? Do you have a diff you could provide of what Twinkle currently does, along with what you'd suggest changing the text to? –Novem Linguae (talk) 21:13, 12 April 2024 (UTC)[reply]

@Novem Linguae: I meant is there a way to customize the title when posting a warning message on a user talk page, instead of using the default title based on the current month. --—Saqib (talk | contribs) 17:26, 13 April 2024 (UTC)[reply]

Hi. Redrose64 reverted my changes, so I'll need to discuss this with you. I made the change for Template:Db-notice-multiple, which added features that can help users clarify if it was a hoax or not, or an unsourced biography of a living person that is entirely negative in tone or not. What do you think about the change? Should we accept the change?
Link to change: https://en.wikipedia.org/w/index.php?title=Template:Db-notice-multiple&oldid=1218647146 71.208.39.196 (talk) 17:13, 13 April 2024 (UTC)[reply]