Template talk:Deprecated template

Why is this template in Category:Redirect templates? It's not for use on a redirect page, is it? –RHolton≡– 02:50, 3 September 2006 (UTC)[reply]

Probably because it's a "soft" redirect. _→AzaToth 18:20, 21 September 2006 (UTC)[reply]

I see. I suppose that makes sense. Thanks. –RHolton≡– 18:43, 23 September 2006 (UTC)[reply]

What is the advantage of categorizing deprecated templates by month? We'll just be left with a lot of monthly categories, possibly many only holding one or two templates.

How does one use the new format for templates that are replaced with non-template solutions? For example, {{qif}}. The old version allowed free text to describe replacements. Pagrashtak 17:48, 14 October 2006 (UTC)[reply]

Any objections to linking the word

I've linked it to the category page (where I'll add a description in a moment), which should make it clear to inexperienced users what the term means, while also providing an explanation of the whole process – Gurch 15:47, 12 April 2007 (UTC)[reply]

I found this idiom somewhere that can be used when there are multiple candidates for replacing an old template:

<div style="border:1px solid #CCC; padding:1px;">{{tdeprecated|old|new=one of the templates below|category=}}
:: {{[[Template:new1|new1]]}}, for when the arg is argled
:: {{[[Template:new2|new2]]}}, for when the bar is bargled
</div>

— Ksero 21:38, 27 May 2007 (UTC)[reply]

Modified above to show code and remove cat. Rich Farmbrough, 11:55, 1 October 2009 (UTC).[reply]

Why is it necessary to have to type in the name of the template for the old parameter? I think that adding {{PAGENAME}} should be fine because the template will not be used anywhere but the template's page itself. –Dream out loud (talk) 00:09, 2 July 2007 (UTC)[reply]

This template is used on the template page and (once orphaned) every page transcluding it. This shows users a message notifying them that the template is deprecated when they use it somewhere. If we only use {{

Pathoschild

03:16:52, 02 July 2007 (UTC)

The {{

However the div structure in the implementation is buggy and fails with {{

Please note that {{Ambox}} is for article message boxes, not for template message boxes :) —Ms2ger (talk) 20:46, 13 January 2008 (UTC)[reply]

could you please add the turkish link? --> [[tr:Şablon:Geçersizş]]--78.180.58.116 (talk) 10:22, 28 February 2008 (UTC)[reply]

Done. Chris Cunningham (not at work) - talk 11:21, 12 April 2008 (UTC)[reply]

Rather than using a hand-hacked table, use an ambox directly. New code:

{{ ambox
| type = warning
| image = [[Image:Symbol opinion vote.svg|40px]]
| text = 
{{#if:{{{new|{{{2|}}}}}}|<div style="display:none;">}}The template {{[[Template:{{PAGENAME}}|{{PAGENAME}}]]}} is [[:Category:Deprecated templates|deprecated]]. Please use {{{use|{{[[Template:{{{1}}}|{{{1}}}]]}}}}} instead.<br /><small>This usage is deprecated. Please replace it with {{tdeprecated|{{PAGENAME}}|{{{1}}}}}.{{#if:{{{new|{{{2|}}}}}}||<includeonly>{{{category|[[Category:Deprecated use of tdeprecated]]}}}</includeonly>}}
<!-- new usage (with or without date) -->
{{#if:{{{new|{{{2|}}}}}}|</div>|<div style="display:none;">}}'''The template {{[[Template:{{{1}}}|{{{1}}}]]}} is deprecated. Please use {{{new|{{[[Template:{{{2}}}|{{{2}}}]]{{#if:{{{3|}}}||}}{{{3|}}}}}}}} instead.{{#if:{{{new|{{{2|}}}}}}||</div>}}

}}<includeonly>{{{category|{{#ifeq:{{ARTICLESPACE}}|Template|{{#if:{{{date|}}}|[[Category:Templates deprecated since {{{date}}}|{{PAGENAME}}]]|[[Category:Deprecated templates|{{PAGENAME}}]]}}|[[Category:Pages using deprecated templates]]}}}}}</includeonly><noinclude>
{{documentation, template}}
</noinclude>

Just drop the lot in. Chris Cunningham (not at work) - talk 11:21, 12 April 2008 (UTC)[reply]

Ambox is supposed to be used in articles, not elsewhere. The current version is fine and shouldn't be amboxed. Nihiltres^{t.l} 15:23, 12 April 2008 (UTC)[reply]

Do'h. I meant messagebox. Still, removing request until there's been more input. Chris Cunningham (not at work) - talk 15:42, 12 April 2008 (UTC)[reply]

I just gave this template a major overhaul. I upgraded it to use the new {{mbox}} that automatically changes style depending on what kind of page it is shown on. And I fixed lots and lots of other things in the code. And I of course tested it in the /sandbox before I deployed it, since this was a tricky update.

--David Göthberg (talk) 17:10, 17 August 2008 (UTC)[reply]

I just spent about ten minutes trying to determine if this template is deprecated or not, and I'm still not sure. Could we add a <noinclude> bit at the very top of the page, saying Below is an example of this template; this page is not really deprecated or Yes, this deprecation template is itself deprecated? JamesLucas (" " / +) 16:39, 17 August 2008 (UTC)[reply]

Hehe. This template itself is not deprecated. But using it without the second parameter is deprecated. Thus at the top of the page it shows a warning about that, which is confusing. And you are right, we should clarify that at the top of its documentation. I'll fix that.

--David Göthberg (talk) 17:13, 17 August 2008 (UTC)[reply]

Awesome. Thanks David. JamesLucas (" " / +) 20:36, 17 August 2008 (UTC)[reply]

I changed the stylized exclamation point image to one that, IMHO, is more in keeping with current trends.  –droll [chat] 10:14, 7 July 2010 (UTC)[reply]

The documentation for this template says that the box style changes depending on which type of page the template appears. I'm flabbergasted. The casual reader doesn't need to see our dirty laundry. Washing dirty laundry in public reflect an imperfect strategic approach. IMHO, it would be better to place the article in a hidden category. Then the problem could be addressed in a more systematic way. Thanks of reading this. Seems I just spreading joy all over today.10:30, 7 July 2010 (UTC)

In Wikipedia, every reader is a potential editor. In addition, it helps drawing attention. Debresser (talk) 11:43, 7 July 2010 (UTC)[reply]

Could the documentation describe whether this template should or should not be put in the /doc-page? My first guess: if the template is still in used, it should be in the /doc (which is in the <noinclude>) -DePiep (talk) 11:26, 1 September 2010 (UTC)[reply]

In general, Tdeprecated should not be put on the documentation page, but right in front of the template it is used upon. If that template is still in use on more than a few pages, it is advisable to add noinclude tags. Debresser (talk) 12:45, 1 September 2010 (UTC)[reply]

Then please put this in this templates doc. -DePiep (talk) 19:35, 1 September 2010 (UTC)[reply]

Why am I getting the impression, from the beginning in fact, that you never had a good look at the documentation page for this template? Debresser (talk) 22:00, 1 September 2010 (UTC)[reply]

I don't know why you got that impression. Maybe something in your browser.

I do know that I have read & used this template, and that further on the process got mixed up with the TfD-process, unannounced. For example, if I apply this template, in which Categories will be the template? Why do I see dropable templates in other, similar-named Categories, but not my template? And if I have found out (after a subst: probably), why a diff with TfD-deletion? Why no reference to the TfD-merge, which is quite parallel to deprecation?

Then please re-read my initial question: why not put it in /doc?

Just don't suggest I'm stupid. It could be that the /doc is not clear enough. -DePiep (talk) 23:10, 1 September 2010 (UTC)[reply]

Which categories this template sorts in is specified in the documentation. What are "dropable" templates, and which is "your" template? Why no reference to Tfd-merge? Because merging is relevant with templates that are in use, while this template is to be used when a template is being deprecated. ~~

I used this template ([here]), but it is very confusing. I do not even know in which category the templates ends up. Why is the template not in

This template did not work correctly with the parameters |1=, |2=, |4=, and |5=, or alternatively parameters |old= and |new=. To my surprise. To make it work with them correctly, took some thinking and some trial and error, see these edits. Debresser (talk) 04:15, 9 December 2013 (UTC)[reply]

Parameters |4=, and |5= have been removed from the code. Use |old= and |new=. Documentation updated. Debresser (talk) 16:53, 28 December 2013 (UTC)[reply]

@Junior5a: Lojbanist ^{remove cattle from stage} 18:44, 29 September 2018 (UTC)[reply]

It would keep it to aware about icon if you would without it would be confusing. ~ Junior5a (Talk) Cont 18:49, 29 September 2018 (UTC)[reply]

The icon we had a week ago was fine, and the new one is fine also.

No problem here. Debresser (talk) 21:51, 30 June 2020 (UTC)[reply]

 Done --Trialpears (talk) 22:28, 8 July 2020 (UTC)[reply]

‎JsfasdF252 recently move this template from "Deprecated template" to just "Deprecated". While I don't have any real issues with this I really think it should be done properly or not at all. We should update redirect links in the documentation, {{Deprecated inline}}, all the categorize and probably some other links. I also don't think this template should be used on things other than templates (and modules) making the rename quite pointless. --Trialpears (talk) 23:36, 28 April 2021 (UTC)[reply]

@Trialpears: I think it should be moved back. for stuff in other namespaces we have Template:Historical, and in response the suggested other uses that they added to the documentation: We do not keep depreciated modules around as they are not called directly in articles so editors will not be running across them, and I have no idea what the suggested use on files is supposed to accomplish. The template is coded so that it only works properly on template pages (e.g. it automatically adds a "Template:" prefix onto any names inputted to it) so that would also need fixing, but the usage on other namespaces seems pointless at best. 192.76.8.91 (talk) 00:10, 29 April 2021 (UTC)[reply]

Given that the mover didn't come to discuss I have now reverted. --Trialpears (talk) 23:37, 1 May 2021 (UTC)[reply]