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.
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:
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:
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)[reply]
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 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)[reply]
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?
Because Lx has the option to hide certain links and PageLinks itself doesn't, a direct merge is impossible. The next best thing would be to convert the transclusions to invocations of Module:PageLinks. Doesn't look too impossible at first glance. Snowmanonahoe (talk·contribs·typos) 00:20, 14 January 2024 (UTC)[reply]
Problem: Lx's 20,000 transclusions are kinda fake, because almost all of them are transclusions of transclusions. Even if we restrict it to the template namespace, most of those are transclusions of transclusions of transclusions in the doc subpage. Snowmanonahoe (talk·contribs·typos) 00:38, 14 January 2024 (UTC)[reply]
The more I look at this, the more it appears technically infeasible. Lx has some really bizarre arguments like tag and label which can't be replicated by Module:PageLinks. When Lx was used to link to a normal page, namespace is usually Talk and label is usually talk, but when it's used to link to a talk page, either could be anything. Also, the recursive transclusion issue means the only way to get our pages would be an insource search, which means we'd also have to deal with pages like this.
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)[reply]
Hi now that {{Wikisourcelang}} is being merged, how do I use the merge target template to point to sister language Wikisources? All the links keep incorrectly pointing to the English version and the documentation of {{Wikisource}} has not been updated about this. Folly Mox (talk) 20:16, 11 August 2023 (UTC)[reply]
Folly Mox, the merge has not yet been completed, so you should use the appropriate currently-existing template to do whatever it is you are planning until the merge is complete. The existing uses will be converted appropriately at that time. Primefac (talk) 09:00, 14 August 2023 (UTC)[reply]
Oops, I forgot I had posted here. My assertion was incorrectly based on the first instance I had tested, which had been misusing parameters in such a way that it worked prior to the start of the merge process but not afterwards. The links to en.s/lang:page do properly redirect if the parameters are used correctly, but I didn't initially follow the links to check. It was quite an embarrassing hour or so of my contribution history. Folly Mox (talk) 13:00, 14 August 2023 (UTC)[reply]
I see I am not supposed to use {{Wikisourcehas}} on "additional pages" so I have had to move to using {{Sister project}} because {{Wikisource}} does not have the required functionality. I shall look out for further developments because some very clever coding will be needed. Thincat (talk) 13:13, 17 August 2023 (UTC)[reply]
For over a year now we have been instructed not to use {{Wikisource author}}, {{Wikisourcelang}} and {{Wikisourcehas}} and this is a nuisance because avoiding their use is not at all trivial. Can we have a report on progress with the merge, please, or permission to again use these templates? Thincat (talk) 16:55, 12 July 2024 (UTC)[reply]
See Primefac's note above. Just keep using the existing templates. They will be converted for you during the merge process, whenever it happens (these merges sometimes take a while, as you can see above). When the conversion is done, the merged template will support the features that you need. That's how it's supposed to work, anyway. – Jonesey95 (talk) 19:01, 12 July 2024 (UTC)[reply]
Thank you. That's helpful. Is there a change that could be usefully made to the display text in {{being deleted}}? Or maybe the assumption is that no one reads beyond the first line anyway. Thincat (talk) 20:41, 12 July 2024 (UTC)[reply]
I wasn't aware of that discussion, thanks. If it turns out that they shouldn't be ported, feel free to revert my edits. I'll look into the other params later.— mw (talk) (contribs) 22:14, 20 December 2023 (UTC)[reply]
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.
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).
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.
