This is the
talk page for discussing improvements to the
Twinkle page. |
|
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:
|
Twinkle has detailed documentation located at WP:TW/DOC. |
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
|
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)
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)
{{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)
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)
@
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)
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)
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)
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)
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)
Good day, this is a courteous message to inform Twinkle’s maintainers and users that:
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.waddie96 ★ ( talk) 19:35, 5 April 2024 (UTC)
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)
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)
Is it possible to customize topics' titles or heading when using Twinkle? — Saqib ( talk | contribs) 18:08, 11 April 2024 (UTC)
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/?title=Template:Db-notice-multiple&oldid=1218647146
71.208.39.196 (
talk) 17:13, 13 April 2024 (UTC)
Hi, what's the process of getting the {{ Uw-ai1}} through 3 warning templates added? microbiologyMarcus petri dish· growths 16:29, 16 April 2024 (UTC)
Could we add {{ uw-talkinarticle1}}, {{ uw-talkinarticle2}}, and {{ uw-talkinarticle3}}? It is already found on WP:UV, would be good to have on Twinkle. (I have already added it to my custom preferences, but its not ideal). I would prefer if was standard UW option. Classicwiki ( talk) If you reply here, please ping me. 20:28, 17 April 2024 (UTC)
Developers might be interested in this: I created a patch tonight to change Twinkle from its custom eslint rules, to use the plugin eslint-config-wikimedia. Eslint-config-wikimedia is the standard wikimedia set of linter rules. I think there's some good advantages to switching to the standard wikimedia linter (discussed in more detail in the ticket). I've turned off controversial rules such as requiring spaces in parentheses, and turned off limiting line lengths to 100 characters. If there's any concerns or objections, please let me know here or in the ticket. I think getting more rules turned on via this plugin is going to be an important step in modernizing the codebase.
Note that this patch also applies all the auto fixes, which includes a conversion from var to let/const. Wikimedia grade A support appears to be firmly at ES6 now, so it should be safe to make ES6 upgrades. This new linter also includes strict rules (stricter than previously) that warn if we try to use features over ES6, which is a nice feature for making sure we align with grade A support.
Thanks. – Novem Linguae ( talk) 06:54, 22 April 2024 (UTC)