Wikipedia:Templates for discussion/Holding cell: Difference between revisions
→To orphan: rm {{Vandalism (band)}}, deleted |
→Meta: Rm {{Infobox name module}}, finally completed. Phew |
||
Line 116: | Line 116: | ||
====Meta==== |
====Meta==== |
||
* Merge with [[Template:Infobox Chinese]] |
|||
** {{tfdl|Infobox name module|2017 April 7|section=Template:Infobox name module}} |
|||
*:1.5 years later I've taken another look. The merger itself doesn't look toooo bad but I'm really not a fan of adding "Infobox Chinese" to tons of articles not related to China in the slightest. The [[Template_talk:Infobox_Chinese#Requested_move_23_September_2019|2019 RM]] didn't go too well though and it's perhaps best to try to at least partially take a look at the (imo not so relevant) things cited as issues in the RM. These are adding support for some other major languages which is currently partially or completely missing (Arabic, Hebrew, Urdu if I'm not mistaken, Greek and probably a few more). The ordering support is also somewhat lacking which would be a pain to fix if it wasn't a module. I'm not particularly trilled about taking it on but I'm not a fan of having this ancient merger around indefinitely either. {{u|Trappist the monk}} you seem like the obvious person to ask since you both developed the module and is the language guru, but it's completely understandable to not want to touch this. --[[User:Trialpears|Trialpears]] ([[User talk:Trialpears|talk]]) 23:18, 27 March 2021 (UTC) |
|||
*::If I remember correctly, I wrote [[Module:Infobox multi-lingual name]] to consolidate multiple various templates (with all of their unique peculiarities) into a single source. Then I wrote a long long document describing the things that should be done to make the whole mess more sensible. Alas, I lost that document as the result of a catastrophic computer failure which was perhaps serendipitous because of the drama the would inevitably arise – you know how wikipedians hate hate hate change because oh my god the sky is falling. In retrospect, I came to realize that the better solution is to restart as a fresh design beginning with a whole new specification. If the fresh design is any good it can organically take over from existing infoboxen without drama. I have done nothing to advance that because, as you can see, it appears that wikipedians are more-or-less happy with the crap template that I wrote. And, it appears, that wikipedians couldn't give two hoots about merging the two infoboxen because nigh on four years since the tfds and here the merge lingers... Better to declare the merger dead and get on with life? |
|||
*::—[[User:Trappist the monk|Trappist the monk]] ([[User talk:Trappist the monk|talk]]) 00:20, 28 March 2021 (UTC) |
|||
*:::Regarding the name - keep in mind we can create any number of useful redirects if adding "...Chinese" to something that isn't is a problem. That being said, if it gets built into a location-neutral module, it would make ''so much sense'' to rename the main template (wink wink). [[User:Primefac|Primefac]] ([[User talk:Primefac|talk]]) 13:14, 28 March 2021 (UTC) |
|||
*:::It's a mess right now but I think the problem isn't that people don't care but that there are very few people who feel confident enough with both the lua and the languages to take it on and the few who do either don't want to get involved in the drama side or are simply busy elsewhere. I think I may deal with it after I've finished the mergers I've started but then there won't be any huge improvements to the module but rather just what's required for the merger. No matter what a second RM is coming. --[[User:Trialpears|Trialpears]] ([[User talk:Trialpears|talk]]) 14:17, 28 March 2021 (UTC) |
|||
*::::The primary purpose of this board is to implement the merger. If there are improvements made along the way that's great, but they're not a requirement and (not that this is the case for this merge) shouldn't hold up a merge. [[User:Primefac|Primefac]] ([[User talk:Primefac|talk]]) 15:11, 28 March 2021 (UTC) |
|||
*::::: That the merge hasn't completed in 4 years surely means that it's reasonable to consider whether or not the original merge is still relevant. If we do continue with a merger, it seems perfectly reasonable to change the target to be called something like [[Template:Infobox multi-lingual name]], using [[Module:Infobox multi-lingual name]], rather than using the name of a language that isn't pertinent to many (most?) transclusions — the first page of [[Special:WhatLinksHere/Template:Infobox_name_module]] shows me some Chinese but also a bunch of Japanese, French, Spanish and Italian films. — <span class="vcard"><span class="fn">[[User:OwenBlacker|OwenBlacker]]</span> <small>(he/him; [[User talk:OwenBlacker|Talk]]; please {{[[Template:ping|ping]]}} me in replies)</small></span> 20:30, 13 May 2021 (UTC) |
|||
*::::::{{ping|OwenBlacker}} I tried renaming at [[Template_talk:Infobox_Chinese#Requested_move_23_September_2019]]. More likely than not I will get to this during the summer so at least it shouldn't get to five years. I don't really see much that would have changed people opinions on this template. Not much has actually happened on this front. --[[User:Trialpears|Trialpears]] ([[User talk:Trialpears|talk]]) 21:03, 13 May 2021 (UTC) |
|||
*:::::::@[[User:Trialpears|Trialpears]] I hope that this gets done soon. ;) [[User:Techie3|Techie3]] ([[User talk:Techie3|talk]]) 00:06, 12 April 2022 (UTC) |
|||
*::::::::{{u|Techie3}} There's actually been some significant progress since my comment above, most significantly that {{tl|Infobox East Asian name}} actually got done and a lot of the template work needed for a proper merge was done including some upgrades to {{tl|Infobox Chinese}}. It still remains some features that need fixing before a full merge is possible though and I'm not excited about doing that work. I can probably get a list of things that need doing if someone is interested in some annoying module work though and can deal with the template replacements afterwards. --[[User:Trialpears|Trialpears]] ([[User talk:Trialpears|talk]]) 12:59, 12 April 2022 (UTC) |
|||
*:::::::::This merger is hard, it's boring and have been a huge time sink for several people for almost 6 years now. I never plan on touching this again and wouldn't oppose this just being removed as not done like was suggested in 2021. --[[User:Trialpears|Trialpears]] ([[User talk:Trialpears|talk]]) 20:29, 10 January 2023 (UTC) |
|||
*::::::::::The non-Chinese East Asian language usages in Infoboxes can replaced with templates redirects to subtemplates of {{tl|Infobox Chinese}}. I'll work on this. [[User:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ|ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ]] ([[User talk:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ|talk]]) 06:14, 11 January 2023 (UTC) |
|||
*:::::::::::Having taken a deeper look at this, there are [https://en.wikipedia.org/w/index.php?search=insource%3A%2F%5C%7C+%2Anative_name+%2A%5C%3D+%2A%5C%7B%5C%7B%28Film+name%7CInfobox+name+module%29%5C%7C%5Ba-z%5D%5Ba-z%5D%5C%7C%5B%5E%3D%7D%5D%2B%5C%7D%5C%7D%2Fi&title=Special:Search&profile=advanced&fulltext=1&ns0=1 4.4k] of form <code><nowiki>{{Infobox name module|lang_code|text}}</nowiki></code>. Most of these are European, Middle eastern and Indian languages which are inappropriate to merge with {{tl|Infobox Chinese}}. Apparently at the time of TFM in 2017 most usage of this template was for Chinese writing systems, obviously it has changed now. In light of this, I think we should just replace Chinese, Japanese and other languages that have multiple writing systems for which we already have subtemplates in {{tl|Infobox Chinese}}. We can add a tracking param, replace usages in articles with subtemplates or redirects, remove the params after they are replaced and retain {{tl|Infobox name module}} for iso language codes. [[User:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ|ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ]] ([[User talk:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ|talk]]) 11:26, 11 January 2023 (UTC) |
|||
*::::::::::::Tracking cat setup at [[Template:Infobox name module/sandbox]]. Will make this live in a few days if there are no objections to my solution proposed above. [[User:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ|ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ]] ([[User talk:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ|talk]]) 12:11, 11 January 2023 (UTC) |
|||
:{{od}}Tracking cat added. I had already cleared most Japanese params, will work on others in the coming weeks. [[User:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ|ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ]] ([[User talk:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ|talk]]) 17:10, 14 January 2023 (UTC) |
|||
::@[[User:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ|ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ]] As mentioned on your talk page, the changes you made to various South Korea-related articles that utilized <code>Infobox name module</code> causes issues to the Infobox presentation due to the subheader (Korean name) that was included automatically by <code>Infobox Korean</code> causing parameters (genre, based_on, developed_by, etc) that are part of <code>Infobox television</code> to be misleadingly displayed as if it's part of the Korean name grouping. Please resolve this before continuing with your extremely speedy replacement. '''<span style="color:#f535aa">—</span> [[User:Paper9oll|<span style="background:#f535aa;color:#fff;padding:2px;border-radius:5px">Paper9oll</span>]] <span style="color:#f535aa">([[User talk:Paper9oll|🔔]] • [[Special:Contributions/Paper9oll|📝]])</span>''' 17:41, 20 January 2023 (UTC) |
|||
:::Trialpears said above that this merger has {{tq|been a huge time sink for several people for almost 6 years now}}. Well you can add a few hours of my time to the list. <s>Unless anyone enjoy drama and getting complaints from those you dislike any change, I too would suggest removing this as not done/stale.</s> [[User:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ|ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ]] ([[User talk:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ|talk]]) 18:59, 20 January 2023 (UTC) |
|||
::::Actually strike that, there are some options to replace it with minimal change to page rendering. Having two templates with similar functions is unhelpful for editors too and all the progress on this over the years shouldn't go waste. I'll see this through, compromising with the best options available. [[User:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ|ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ]] ([[User talk:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ|talk]]) 15:22, 23 January 2023 (UTC) |
|||
:::::I have emptied [[:Category:Infobox name module using deprecated parameters|the tracking cat]], which had ~6,000 articles. There is nothing more that can be broken off from this template that is handled by other templates. This is now ready for removal of Chinese, Japanese, Korean, Vietnamese and Sinhala params. Have updated doc page pointing to their replacements. I intend to sync [[Special:PermanentLink/1137787299]] from sandbox in a few days, along with removing the {{tl|being deleted}} template. [[User:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ|ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ]] ([[User talk:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ|talk]]) 12:44, 6 February 2023 (UTC) |
|||
*{{tfdl|Old_move|2020 November 28|section=Template:Old move}} |
*{{tfdl|Old_move|2020 November 28|section=Template:Old move}} |
||
*{{tfdl|Old_moves|2020 November 28|section=Template:Old move}} |
*{{tfdl|Old_moves|2020 November 28|section=Template:Old move}} |
Revision as of 17:40, 12 February 2023
Deletion discussions |
---|
|
Articles |
Templates and modules |
Files |
Categories |
Redirects |
Miscellany |
Speedy deletion |
Proposed deletion |
This page has a backlog that requires the attention of willing editors. Please remove this notice when the backlog is cleared. |
If process guidelines are met, move templates to the appropriate subsection here to prepare to delete. Before deleting a template, ensure that it is not in use on any pages (other than talk pages where eliminating the link would change the meaning of a prior discussion), by checking Special:Whatlinkshere for '(transclusion)'. Consider placing {{Being deleted}} on the template page.
Tools
There are several tools that can help when implementing TfDs. Some of these are listed below.
- Template linking and transclusion check – Toolforge tool to see which pages are transcluded but not linked from or to a template
- WhatLinksHereSnippets.js – user script that allows for template use to be viewed from the Special:WhatLinksHere page
- AutoWikiBrowser – semi-automatic editor that can replace or modify templates using regular expressions
- Bots – robots editing automatically. All tasks have to be approved before operating. There are currently five bots with general approval to assist with implementing TfD outcomes:
- AnomieBOT – substituting templates via User:AnomieBOT/TFDTemplateSubster
- SporkBot – general TfD implementation run by Plastikspork
- PrimeBOT – general TfD implementation run by Primefac
- BsherrAWBBOT – general TfD implementation run by Bsherr
- PearBOT II – general TfD implementation run by Trialpears
Closing discussions
The closing procedures are outlined at Wikipedia:Templates for discussion/Closing instructions.
To review
Templates for which each transclusion requires individual attention and analysis before the template is deleted.
- None currently
To merge
Templates to be merged into another template.
Infoboxes
- Merge into the singular {{infobox ship}} (currently a redirect):
- 2022 April 30 – Infobox_ship_begin ( links | transclusions | talk | doc | sandbox | testcases )
- 2022 April 30 – Infobox_ship_career ( links | transclusions | talk | doc | sandbox | testcases )
- 2022 April 30 – Infobox_ship_characteristics ( links | transclusions | talk | doc | sandbox | testcases )
- 2022 April 30 – Infobox_ship_class_overview ( links | transclusions | talk | doc | sandbox | testcases )
- 2022 April 30 – Infobox_ship_image ( links | transclusions | talk | doc | sandbox | testcases )
- 2022 April 30 – Infobox_service_record ( links | transclusions | talk | doc | sandbox | testcases )
- I have hacked Module:Infobox ship which implements ship infoboxen without the external wikitable that the above templates require. Uses Module:Infobox;
{{infobox ship begin}}
is no longer required; parameter names are changed from sentence- to snake-case; section header height for career, characteristics, service record sections is normalized; custom fields are supported. I chose to retain the individual section templates as subtemplates:{{Infobox ship/image}}
{{Infobox ship/career}}
{{Infobox ship/characteristic}}
{{Infobox ship/class}}
{{Infobox ship/service record}}
– Module:Infobox ship implements only the 'ship' portion of{{Infobox service record}}
- In the main infobox these subtemplates are called with the
|section<n>=
parameters (aliases of|data<n>=
). - Comparisons between wikitable infoboxen and Module:Infobox ship infoboxen can bee seen at my sandbox (permalink).
- —Trappist the monk (talk) 14:57, 21 May 2022 (UTC)
- Since the intent is to use Module:Infobox directly, why is Module:Infobox ship being used to generate the infobox? I can understand if there is need for a backend module to validate a value or something, but is there really a reason to have this unique code? Gonnym (talk) 17:50, 21 May 2022 (UTC)
- The original complaint was that the ship infoboxen templates are
table templates masquerading as infobox templates
. None of those templates use Module:Infobox. Module:Infobox ship answers that complaint. Yeah, we still have subtemplates, but, in my opinion, that is a good thing because the appropriate parameters and their data are contained in each particular subtemplate. The container subtemplates make it relatively easy for an editor reading an article's wikitext to understand. The current ship infobox system allows sections in any order (except for the position of{{infobox ship begin}}
– not needed with Module:Infobox ship); whatever the final outcome of this mess, that facility must not be lost. - Module:Infobox ship does do some error checking (synonymous parameters
|ship_armor=
/|ship_armour=
,|ship_draft=
/|ship_draught=
,|ship_honors=
/|ship_honours=
, and|ship_stricken=
/|ship_struck=
). Whether{{infobox ship}}
directly calls Module:Infobox or whether{{infobox ship}}
calls Module:Infobox ship which then calls Module:Infobox is really immaterial so long as the final rendered result is a correctly formatted infobox. - —Trappist the monk (talk) 19:06, 22 May 2022 (UTC)
- @Trappist the monk are you still interested in working on this Module? If not, I'd like to try to get it finished myself. The massive deviation I had in mind was to make one invocation of the module do everything. Each page will require individual attention to complete the merge into a proper infobox anyway, so I reason to go the extra mile to make it nicer in general. Repeatable parameters will have the normal n number appended to the end of the parameter. An alternative would be to have subboxes for repeating sections, which would be easier in general to replace and implement. SWinxy (talk) 20:26, 20 August 2022 (UTC)
- Sure, but I don't think that this page is the proper place to discuss. Choose some place more proper and let me know where that is?
- —Trappist the monk (talk) 22:58, 20 August 2022 (UTC)
- @Trappist the monk are you still interested in working on this Module? If not, I'd like to try to get it finished myself. The massive deviation I had in mind was to make one invocation of the module do everything. Each page will require individual attention to complete the merge into a proper infobox anyway, so I reason to go the extra mile to make it nicer in general. Repeatable parameters will have the normal n number appended to the end of the parameter. An alternative would be to have subboxes for repeating sections, which would be easier in general to replace and implement. SWinxy (talk) 20:26, 20 August 2022 (UTC)
- The original complaint was that the ship infoboxen templates are
- Since the intent is to use Module:Infobox directly, why is Module:Infobox ship being used to generate the infobox? I can understand if there is need for a backend module to validate a value or something, but is there really a reason to have this unique code? Gonnym (talk) 17:50, 21 May 2022 (UTC)
- I have hacked Module:Infobox ship which implements ship infoboxen without the external wikitable that the above templates require. Uses Module:Infobox;
- 2023 January 23 – Infobox_Oklahoma_legislation ( links | transclusions | talk | doc | sandbox | testcases ) → {{Infobox U.S. State legislation}}
- 2023 January 23 – Infobox_CA_legislation ( links | transclusions | talk | doc | sandbox | testcases ) → {{Infobox U.S. State legislation}}
- 2023 January 24 – Infobox_U.S._state_symbols ( links | transclusions | talk | doc | sandbox | testcases ) → {{Infobox region symbols}}
- None currently
Link templates
- 2021 May 6 – IOC profile ( links | transclusions | talk | doc | sandbox | testcases )
- 2021 May 6 – Olympic Channel ( links | transclusions | talk | doc | sandbox | testcases )
- 2022 October 6 – Bibleverse ( links | transclusions | talk | doc | sandbox | testcases )
- 2022 October 6 – Bibleverse-lb ( links | transclusions | talk | doc | sandbox | testcases )
- 2022 October 6 – Bibleverse-nb ( links | transclusions | talk | doc | sandbox | testcases )
- 2022 October 6 – Biblesource ( links | transclusions | talk | doc | sandbox | testcases )
- 2022 October 6 – Bibleref2 ( links | transclusions | talk | doc | sandbox | testcases )
- 2022 October 6 – Bibleref2-nb ( links | transclusions | talk | doc | sandbox | testcases )
- 2022 October 6 – Bibleref2c ( links | transclusions | talk | doc | sandbox | testcases )
- 2022 October 6 – Bibleref2c-nb ( links | transclusions | talk | doc | sandbox | testcases )
- I feel a very major question was left unanswered here: What should be done when different templates uses different websites for the same verse and bible version? Bibleverse uses a bunch of different websites, Biblesource uses exclusively Wikisource and Bibleref uses only BibleGateway. Ineffablebookkeeper do you have thoughts on this as an editor who is actually editing Christianity related articles? --Trialpears (talk) 04:50, 11 January 2023 (UTC)
- Bibleverse is being left untouched, for the most part, other than merging in bits from the other templates as a result of the merge. Thus, any extant uses of biblesource will still use wikisource when it's converted, same for bibleref. I'm working on this at the moment and have about half of them worked out, with two done completely; I'm planning on doing one big bot run when they're all completed as some pages use multiple templates. Primefac (talk) 09:18, 11 January 2023 (UTC)
- @Primefac: thank you for your hard work! @Trialpears: iirc biblegateway doesn't have every translation that can be used in these templates at present, or at least some of them appear to have more translation options than others. I'd assume that for translations not found on biblegateway, it'd look through other sources such as wikisource instead? A full list of available translations on the template's documentation, alongside which website the template will link to for this, would be much appreciated.—Ineffablebookkeeper (talk) ({{ping}} me!) 15:06, 11 January 2023 (UTC)
- Bibleverse is being left untouched, for the most part, other than merging in bits from the other templates as a result of the merge. Thus, any extant uses of biblesource will still use wikisource when it's converted, same for bibleref. I'm working on this at the moment and have about half of them worked out, with two done completely; I'm planning on doing one big bot run when they're all completed as some pages use multiple templates. Primefac (talk) 09:18, 11 January 2023 (UTC)
- I feel a very major question was left unanswered here: What should be done when different templates uses different websites for the same verse and bible version? Bibleverse uses a bunch of different websites, Biblesource uses exclusively Wikisource and Bibleref uses only BibleGateway. Ineffablebookkeeper do you have thoughts on this as an editor who is actually editing Christianity related articles? --Trialpears (talk) 04:50, 11 January 2023 (UTC)
- 2022 October 17 – IPvandal ( links | transclusions | talk | doc | sandbox | testcases )
- 2022 October 17 – Vandal ( links | transclusions | talk | doc | sandbox | testcases )
- 2022 December 19 – Bcdb ( links | transclusions | talk | doc | sandbox | testcases )
- 2022 December 19 – BCDB_title ( links | transclusions | talk | doc | sandbox | testcases )
Other
- 2020 February 1 – Football_squad_player2 ( links | transclusions | talk | doc | sandbox | testcases ) and 2020 February 1 – Football_squad_player ( links | transclusions | talk | doc | sandbox | testcases )
- Note Pending Redesign RfC robertsky (talk) 18:51, 11 April 2020 (UTC)
- I've closed the RfC. Mdaniels5757 (talk) 15:15, 3 May 2020 (UTC)
- At this point this is ready for large scale replacement. I said a while ago that I could do it but due to me being quite busy IRL this seems unlikely to get done in a timely manner. If you feel like doing a large scale replacement job feel free to take this one. --Trialpears (talk) 17:34, 2 February 2021 (UTC)
- Trialpears, what large-scale replacement? I (foolishly?) jumped into this rabbit hole, and have been in it for over a day now. This is a very complex merge; I've got the documentation diff to show fewer differences, but there's still more to be done. – wbm1058 (talk) 15:04, 14 February 2021 (UTC)
- Note Pending Redesign RfC robertsky (talk) 18:51, 11 April 2020 (UTC)
- 2021 June 18 – Clickable_button ( links | transclusions | talk | doc | sandbox | testcases ) and 2021 June 18 – Clickable_button_2 ( links | transclusions | talk | doc | sandbox | testcases )
- I made a few changes to Module:Clickable button 2/sandbox that would combine the functionalities of the two different templates. Someone may want to review that. –MJL ‐Talk‐☖ 23:21, 23 September 2021 (UTC)
- MJL, as our resident expert on this module, what in-line changes need to be made to {{clickable button}} calls in order to get them working properly with the module? The /doc examples don't give a clear enough indication of the differences, and to me it looks like they run on the same syntax. (please do not ping on reply) Primefac (talk) 11:55, 24 January 2022 (UTC)
- @Primefac: So, my current computer is bricked a la an upgrade to Windows 11. I'll have to get back to you on this until it gets fixed, sorry. –MJL ‐Talk‐☖ 02:51, 25 January 2022 (UTC)
- Friendly nudge. Primefac (talk) 13:08, 25 March 2022 (UTC)
- Thanks for the extra ping:
- The current main 2 blockers are #brackets and pipe in label and #URL placed as label. I am not sure how common the second thing is, but I know the first is a real thing that would break things like User:TheJJJunk/Backlog. –MJL ‐Talk‐☖ 02:58, 27 March 2022 (UTC)
- @MJL I've made a change to the sandbox which should fix the brackets and the pipe (tested it with only a limited amount of testcases). Take a look and hopefully that helps. Gonnym (talk) 10:27, 27 March 2022 (UTC)
- @Gonnym: It broke a lot of other things (#No link, #1st set nil; 2nd unset, and #Brackets around 1st) sadly. Though, it's definitely a good start! –MJL ‐Talk‐☖ 16:22, 27 March 2022 (UTC)
- Okay, with the most recent changes, we're almost all set for a merge. {{Clickable button 2}} generates the button within the link while {{Clickable button}} never generated a link by itself, so I just got a run AWB or something to migrate current uses of {{Clickable button}} correctly. Give me a few days to get that done. –MJL ‐Talk‐☖ 18:52, 27 March 2022 (UTC)
- @MJL I've made a change to the sandbox which should fix the brackets and the pipe (tested it with only a limited amount of testcases). Take a look and hopefully that helps. Gonnym (talk) 10:27, 27 March 2022 (UTC)
- Friendly nudge. Primefac (talk) 13:08, 25 March 2022 (UTC)
- @Primefac: So, my current computer is bricked a la an upgrade to Windows 11. I'll have to get back to you on this until it gets fixed, sorry. –MJL ‐Talk‐☖ 02:51, 25 January 2022 (UTC)
- MJL, as our resident expert on this module, what in-line changes need to be made to {{clickable button}} calls in order to get them working properly with the module? The /doc examples don't give a clear enough indication of the differences, and to me it looks like they run on the same syntax. (please do not ping on reply) Primefac (talk) 11:55, 24 January 2022 (UTC)
- I made a few changes to Module:Clickable button 2/sandbox that would combine the functionalities of the two different templates. Someone may want to review that. –MJL ‐Talk‐☖ 23:21, 23 September 2021 (UTC)
- Merge the Wikipedia:WikiProject Geographical coordinates/dim: guidance to 2022 March 3 – Coord-doc-dim ( links | transclusions | talk | doc | sandbox | testcases )
- 2022 July 4 – Import-blanktable ( links | transclusions | talk | doc | sandbox | testcases ) and 2022 July 4 – Row_hover_highlight ( links | transclusions | talk | doc | sandbox | testcases )
Meta
- 2020 November 28 – Old_move ( links | transclusions | talk | doc | sandbox | testcases )
- 2020 November 28 – Old_moves ( links | transclusions | talk | doc | sandbox | testcases )
- Module version created. More information at Template talk:Old move#Module and merger. --Trialpears (talk) 19:37, 12 December 2020 (UTC)
- 2022 October 6 – Over-coverage ( links | transclusions | talk | doc | sandbox | testcases )
- 2022 October 6 – Globalize ( links | transclusions | talk | doc | sandbox | testcases )
To convert
Templates for which the consensus is that they ought to be converted to some other format are put here until the conversion is completed.
- 2022 January 6 – Malaysian_party_colour ( links | transclusions | talk | doc | sandbox | testcases )
- Both of the above need to have their entries added to the module. Hopefully this can be semi-automated by the same process that was used with the /meta templates. --Gonnym (talk) 10:21, 15 January 2022 (UTC)
- Probably not, as these uses (see for example 2005_Pengkalan_Pasir_by-election#Election_results) call an acronym which then triggers the colour to be returned. Each acronym will need to be paired up with the related party, added to the module, and then swapped in the related articles to use (hopefully something other than) {{Malaysian election result}} with the newer values. I haven't looked into it enough to know how much can be automated, but "not much" is my initial read of it. Primefac (talk) 18:33, 15 January 2022 (UTC)
- Template:Malaysian party colour/name/default and Template:Malaysian party colour/colour/default/sandbox updated and ready. The only party names I left as is were the ones I couldn't find an en.wiki article to confirm spelling, etc. But if others feel differently feel free to add them. The party color should be synced when everything is ready for a bot to help as the calling templates have a "#" in them and Module:Political party also sends them with it. Gonnym (talk) 21:09, 15 January 2022 (UTC)
- Probably not, as these uses (see for example 2005_Pengkalan_Pasir_by-election#Election_results) call an acronym which then triggers the colour to be returned. Each acronym will need to be paired up with the related party, added to the module, and then swapped in the related articles to use (hopefully something other than) {{Malaysian election result}} with the newer values. I haven't looked into it enough to know how much can be automated, but "not much" is my initial read of it. Primefac (talk) 18:33, 15 January 2022 (UTC)
- Both of the above need to have their entries added to the module. Hopefully this can be semi-automated by the same process that was used with the /meta templates. --Gonnym (talk) 10:21, 15 January 2022 (UTC)
To substitute
Templates for which the consensus is that all instances should be substituted (e.g. the template should be merged with the article or is a wrapper for a preferred template) are put here until the substitutions are completed. After this is done, the template is deleted from template space.
- None currently
To orphan
These templates are to be deleted, but may still be in use on some pages. Somebody (it doesn't need to be an administrator, anyone can do it) should fix and/or remove significant usages from pages so that the templates can be deleted. Note that simple references to them from Talk: pages should not be removed. Add on bottom and remove from top of list (oldest is on top).
- None currently
Ready for deletion
Templates for which consensus to delete has been reached, and for which orphaning has been completed, can be listed here for an administrator to delete. Remove from this list when an item has been deleted.
- None currently