Help talk:Template/2008

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search

Complete rewrite

I think few would dispute that the current version of the Help:Template page is horrifically cluttered, poorly laid out and structured, repetitive, out-of-date and overly technical, among many other faults. I have completed a first draft of a complete rewrite which can be found at User:Happy-melon/Template. I am interested to hear what other editors think of the version and whether it would make a suitable replacement for the existing page. Please feel free to contribute to the discussion on the talk page. Happymelon 19:48, 25 January 2008 (UTC)

I don't think so. Meta-wiki provides documentations which can be used by any wikimedian or, in general, anybody who uses the mediawiki engine. This page is the most up-to-date of its kind. Its cook-book and reference manual style together with the examples illustrating the technical details are very useful and important for practioners; There are introductory pages such as Help:A_quick_guide_to_templates which may help a new editor learn. Hillgentleman 18:22, 29 January 2008 (UTC)
I agree fully with Happy melon. I have attempted to dumb down this page, liberally using <ref> tags to move unnecessary techno babble to the foot notes. Odessaukrain 16:56, 4 April 2008 (UTC)
Trying to learn about templates, I find that there are too many template-help pages that are poorly structured. I have read quite a few pages until I found this one. Searching for template usually brings up material on template messages; perhaps someone can review the whole set of related pages, I would be grateful. Vigilius 16:42, 15 April 2008 (UTC)
One specific point: Trying to understand how parameters are used, the explanation is strange. I understand triple braces, but I frequently find {{{1|}}} and so far fail to understand this. The example under "Parameter mechanism": "A parameter tag such as {{{3|stu}}} can both be referenced explicitly with e.g. 3=pqr, or implicitly by putting pqr in the third position among the unnamed parameter definitions. If the name is not a "small" positive integer it can only be referenced explicitly." is very strange. Using pipe is suddenly introduced without explanation, and the relation between stu and pqr - neither of which is mentioned before on the page - is not explained. Please help and rewrite this! (Postscript: I just found Help:Parameter_default - which helps some, but is not linked from the current article page. Vigilius 16:42, 15 April 2008 (UTC)
It was already linked, but I added another link and some clarification.--Patrick (talk) 01:14, 17 April 2008 (UTC)


To say that Help:Template is written badly would be giving Help:Template too much credit. That is why I added the merge tags at Help:Template and User:Happy-melon/Templates. For years I have wondered and searched for how to add formal tags. Several times I have attempted to read Help:Template and have always gone away confused because of the technobabble.

I started to painfully rewrite this page today, putting the worst technobabble in footnotes. Then I started to read the much better written User:Happy-melon/Templates and I will completely abandon this page. Odessaukrain 17:10, 4 April 2008 (UTC)

I looked up w:Technobabble, which confirmed that the term is not applicable at all.--Patrick (talk) 22:50, 6 April 2008 (UTC)
If you want introductions you can find help:a quick guide to templates or you may ask somebody. The page is a reference manual for all (not just for beginners); As we know, reference manuals often appear to be terse to beginners and yet they are necessarily so in order to provide information on most forseeable situations. Hillgentleman 01:14, 17 April 2008 (UTC)
  • You are welcome to write supplementary help pages on aspects of the template mechanism, and put links to them from the main page.
  • If you really want to restructure it, I would suggest refactor the pages in the w:wikipedia:Summary Style, moving the finer points to subpages and keeping an accessible overall structure. However, it may make it more difficult for users from other wikis to copy-and-paste from this meta page.Hillgentleman 01:23, 17 April 2008 (UTC)

Please merge these too pages, I immediatly understood most of the happy-melon version while i didnt understand the other one, sorry, and i'm not even a beginner, I use a wiki for the charity I support and I also use wikis an awful lot at work grts,Pinq 18:04, 24 April 2008 (UTC)

Again, It would be a good thing to restructure the content. We may move more content to help:advanced templates or even add a new page such as help:advanced 1/2 templates. However, simply merging the two pages may actually lead to confusion. Hillgentleman 20:07, 24 April 2008 (UTC)

That sounds reasonable Hillgentleman, I think that would be a good solution. grts,Pinq 17:46, 25 April 2008 (UTC)

In that case we should outline what material should be included in each of the pages. It is reasonable to expect that the page named help:template would be the first port of call of anybody. So it should at least serve to: 1. explain clearly what templates are so that everybody can understand; 2. provide direction to more details. We can be flexible in naming the subpages and in the style of presentations. Hillgentleman 00:06, 29 April 2008 (UTC)
  • I am going to start a new section at the bottom of this talk page: #Refactor? Hillgentleman 00:08, 29 April 2008 (UTC)

Counting templates

Is there a way to count the number of times that a particular template is used within a single article? I have a template that is used multiple times within an article. The very first time I would like it to render a special help icon/link. All future times I would like it to not render it. I suppose I would need to store a count in the article page itself and increment the state within the template. However, I am unsure how to store article state. Any ideas? Two separate templates could be used as a workaround, but I would prefer to avoid this. Thanks. 05:30, 7 February 2008 (UTC)

You would need something like mw:Extension:VariablesExtension. Without that, you still don't need two separate templates, but you would need to mark the first template call yourself by a parameter.--Patrick (talk) 15:54, 7 February 2008 (UTC)

Monitoring Parameter Usage

Did something change? I was doing this up until recently, and today I clicked on the same link, but it doesn't show any usage. This it the page that has all of the links to monitor the usage. I already checked the templates, and none have changed in any way that should have affected the usage monitoring. The only thing I can think of is the new preprocessor, but the example page still works. Could someone help figure this out? Thanks, MrKIA11 (talk) 21:35, 10 February 2008 (UTC)

Yes, it is probably the new preprocessor. It is not yet activated on Meta.--Patrick (talk) 09:25, 11 February 2008 (UTC)
You can use w:Template:Voidd instead.--Patrick (talk) 09:49, 11 February 2008 (UTC)
Thanks, MrKIA11 (talk) 12:05, 11 February 2008 (UTC)

Expansion at load time?

The page states that templates are expanded at page load time. Is that really true? I mean, wouldn’t it be far better to flag all templates which are not time-dependent and for all articles save a version of the wikitext with all those templates expanded until the next revision? Otherwise, is there a way to have the wikitext saved without substing? --Quilbert 03:57, 21 February 2008 (UTC)

Actually, caching is done, I added a note. I don't know the details, such as whether the expanded wikitext is cached, or the html. May be there are caching mechanisms on various levels.--Patrick (talk) 10:51, 21 February 2008 (UTC)


Nearly every other link at is red. Is some effort being made to correct this problem? 16:16, 24 February 2008 (UTC)

Finding existing templates

How can one list what templates exist? Should they be listed under "Specialpages"? It seems that one could create a category specifically for the purpose and then make sure to define in each template that it then belongs to the category, but this relies on each template creator knowing that this needs to happen and that they remember to do it. If one doesn't know that a template exists, there's every chance that multiple editors will create different templates to produce the same result. 17:08, 11 March 2008 (UTC)

You can go to Special:Prefixindex. Type nothing in the "Display pages with prefix" box, select Template in the Namespace box, and click Go. The entries in italics are redirects. Libcub 19:37, 11 March 2008 (UTC)

Template Categories

I have lots of templates in my wiki, some boilerplate, some parameterized, and I have placed these templates into categories for the sole purpose of being able to easily find all templates in a particular category. The problem is, the category page lists not only the templates, but also every page that uses those templates, which can be pretty much all of them. The clutter renders this approach unusable.

Is there a way I can use categories to show only templates? or must I manually keep a wiki page up to date with links to the actual templates? 06:31, 28 March 2008 (UTC)

Instead of [[Category:Something]] apply <noinclude>[[Category:Something]]</noinclude> (don't put an enter before it becuse it would appear in the article where template is used). Bináris 10:23, 28 March 2008 (UTC)

Internal Wiki-Link in a template

I am attempting to make a template of a standard design. In this design i have various parameters and each is good enough on its own. But some of the parameters i am currently having to type out the linke code i.e. |location=[[something:elswhere]] where as i would like to just type |location=elsewhere.

Below is what i would like to happen but cant.
A Template example:
page name = Template:something


Page input:


Basic results of the template filled in from input:


Thanx for your time,
John Wood
02:35, 1 April 2008 (UTC)

You cannot use the "pipe trick", but you can simply write out the piped link: [[something:{{{location}}}|{{{location}}}]].--Patrick (talk) 06:51, 1 April 2008 (UTC)

Example moved to talk page

I move the example on this page here:

A page with:
{{t1demo|{{ta}}|{{tb}}|{{tc}}={{td}}|1={{te}}|2={{tf}}}}, with {{tim|t1demo}}
only using parameter {{{1}}}, and giving start-start-pqr-end-end,
displays templates tc and te only.

This example needs to be better written, I replaced it with a very simple example. I know the above example has many more tricks, but it is almost impossible to decipher, and many of the pages it links to "ta" "tb" have been redirected. Odessaukrain 16:58, 4 April 2008 (UTC)


We have seen some opinions expressed that this page is hard to read. It is true that this page is a little long. I don't think we should dilute or remove any of its content, but refactoring the page in w:wikipedia:summary style may help everybody in either learning template functionalities or in looking up particular details. In particular, we may move some of the contents to more specific subpage. What do people think? Hillgentleman 00:15, 29 April 2008 (UTC)

  • Endorse Hillgentleman: It is reasonable to expect that the page named help:template would be the first port of call of anybody. This is a key point. Whatever goes here cannot be impenetrable nor should it be a dead end.
  • Approve with reservations User:Happy-melon/Templates. It is a big step in the right direction. This page (2008 Aug 08) is highly technical and nearly impenetrable. However, both are far too long for a gateway page. Both advanced and novice readers wander too much before discovering their needs may not be met here.
  • Support a major refactor, going well beyond this page.

Templates were first perceived as just another simple feature, or so it seems. I conjecture that the very first transclusions had no parameters at all. Then parameters were added, then more and more features; eventually, parser functions strapped a rocket engine onto the whole mess. The syntax reflects this piecemeal development and the help files reflect both.

All considered, template syntax isn't terrible; another couple releases and it may be Turing complete. It's not half as bad as w:brainfuck, although when the consecutive right brace count passes about 8, my eyes start to water. Anyway, there's little hope of a complete rewrite since backward compatibility must be maintained. The important point is that with parser functions and magic words, template syntax has taken on all the documentation requirements of a real programming or scripting language.

What's wanted at this page is the bare minimum of content required to meet the needs of beginners, because they are the only ones whose needs can be met in a short space; coupled with plentiful links to more examples and more technical details -- these wisely explained and not simply stuffed in (as See More Jargon). I don't like bare lists of outgoing links (like See also). A few are briefly annotated but what's wanted, for each link, is an indication of what is to be found there -- not in terse words that assume the reader already has a working knowledge of the subject but in plain English, flagged by difficulty level and organized so that prerequisites to understanding are exposed.

I very strongly support the cookbook approach of much of Happy-melon's draft. Explaining anything using the metalanguage approach:

The foo bar is a bar of framistats with frobnitz Foo. just as meaningless to the newcomer as it reads to you now. The sentence cannot be comprehended properly until all its terms are understood and by that time, well, the reader knows pretty well what a foo is. Worse, since words with common meanings outside of MediaWiki are used, the impulsive reader is likely to think he understands one or more, and if his understanding is slightly in error, a mushrooming ball of confusion will blow through his developing concept of whatever is the topic of the explanation. (By the way, the above example was taken from the subject of our talk.)

To an extent, this shock cannot be avoided; the novice to any field must absorb a number of things all at once and understanding proceeds slowly until the meaning of a basic set emerges. Key is to limit, just as far as possible, the number of items introduced at one time, including metalanguage terms, keywords, syntax patterns, and potential variations. "Throw the baby in the deep end" is not a great way to teach swimming, although it has a deplorable popularity in the software community.

So, I like the cookbook format. To start it requires only two metalanguage terms, being some synonyms for Do This and Get This; and one metaconstruct, the table. Templates are a step up and require at least two pages of source to make any sense so there must be three columns altogether:

You type You see
Template:TEx1 Help:Sandbox:TTest Help:Sandbox:TTest
Hello world! [[:Help:Sandbox:TTest]] Help:Sandbox:TTest

It's simple, straightforward, and puts the concept across with the least demand on prerequisites. Those who follow the links will see exactly what's going on, without wordy metalanguage explanations. We might want to protect the pages containing helpful examples but I suggest a set of sandbox pages in the same format will complement the examples nicely. Add a Purge link....

Just don't get carried away on this page. After every few examples, link to where more information in that same direction can be found. Some of those pages can be more cookbook; some can be detailed reference manual pages oozing with metalanguage.

Put any absolutely required laundry lists in a floatright navbox and keep the rest of the page clean. I know there's a temptation to stuff a whole bunch of explanatory text at the bottom but I say, if anybody gets all the way down to the bottom and is confused or unsatisfied, this gateway page has not done its job.

Xiongtalk* 08:01, 18 August 2008 (UTC)

Ambiguity of Magic Words?

I have a template A that contains {{B}} and a template B that contains {{REVISIONTIMESTAMP}}. I want a page that includes A to display the time B was edited. Instead it displays when A was edited. Is there a way to make this work?

Revisiontimestamp provides information for the page you are viewing. For your purpose, you may try {{last edit}}.Hillgentleman 02:59, 9 June 2008 (UTC)

Need to restructure pages related to template writing

I understand the need for both a reference manual and various types of user guide pages, as mentionine din the discussion of a proposed merge (above). But the current structure is hopeless: Help:Template is the first page editors are offered if they use the standard Wikipedia Help facility, but is as user-friendly as the proverbial cornered rat.(2) Most "programmers" learning a new "language" start with a tutorial or guide, then cheat sheets, and only look at reference manuals when they have enough experience to handle the allusiveness (often circular) and terseness of the typical reference manual.(1) I therefore suggest that:

  • Help:Template should be moved to a new page, e.g. Template/Reference Manual.
  • Help:Template should become a portal page that gives access to: the reference manual; a guide / tutorial; a set of cheat sheets. I expect that the user guide and cheat sheets will need to be spit over multiple pages. I also suspect that the reference manual should also be split, so that clarity does not need to be sacrificed in order to keep the page length within reasonable limits.

(1) I'm a retired computer consultant; I've taught myself several languages, taught a few, and written more documentation than I care to remember.
(2) A common expression among Information technology professionals. Philcha 13:20, 24 June 2008 (UTC)

Restructuring is good. Hillgentleman 07:55, 30 June 2008 (UTC)

single level categorisation

I have a template that I use (eg. Template:Monster). The template (amongst other things) contains <includeonly>[[Category: {{{variable}}}]]</includeonly>, where {{{variable}}} is based upon parameters passed to it. I then use Template:Monster in my Goblin article, and Goblin is then nicely categorised. All good so far.

The problem is with my Monsters article which includes (amongst many others) the Goblin article. The Monsters article is therefore placed into every category that any of my monster articles (that use Template:Monster) are in.

How can I avoid this? Is there a way to tell an article not to be in a category? Ideally, I would be able to include <noinclude>[[Category: {{{variable}}}]]</noinclude> in Template:Monster so that while Goblin was categorised, it wouldn't get passed down the line to Monsters.

Help please? 05:18, 30 June 2008 (UTC)

We may try to noinclude around the template on goblin or use {{#if...|[[category:...]]|}} on template:monster. It depends on what you are doing. Hillgentleman 08:06, 30 June 2008 (UTC)
Essentially, the whole article of Goblin is generated by Template:Monster, so I can't use <noinclude>{{Monster|...}}</noinclude> in Goblin, because then it wouldn't appear in the Monsters article. The template could provide many categories, and is partly it's purpose, so moving that functionality out of the template and into each article, such as Goblin, doesn't work for me either. 23:23, 30 June 2008 (UTC)
Can you provide some links to the pages you are talking about? Hillgentleman 23:48, 30 June 2008 (UTC)
The wiki is private, so no can do there, but following are 3 sample pages to indicate the exact type of thing I've got going on to better illustrate. There's much more, of course, to each of these pages in my wiki, but this should be enough.
{{#foreach:Cat$n$|[[Category:{{ucfirst:{{{Cat$n$}}}}} Monster Category]]}}
{{Monster|Name=Goblin|Description=yada yada|Cat1=Humanoid|Cat2=Intelligent}}
Hopefully, that gives you a better idea of my structure. The problem is that the Monsters article is also getting categorised into Category:Humanoid Monster Category, Category:Intelligent Monster Category, etc. whereas only Goblin, Kobold, etc. are supposed to be. And of course, every monster will have varying categories. 05:38, 1 July 2008 (UTC)
I haven't played with loop functions. But from what I can see, in Template:Monster, could you replace [[Category:{{ucfirst:{{{Cat$n$}}}}} Monster Category]] with something like {{#ifeq:{{PAGENAME}}|{{{Name|}}}|[[Category:{{ucfirst:{{{Cat$n$}}}}} Monster Category]]|}} ? Hillgentleman 17:01, 1 July 2008 (UTC)
That's worked well. I had to add case insensitivity by using {{#ifeq:{{uc:{{PAGENAME}}}}|{{uc:{{{Name|}}}}}|.... Awesome. Thanks for your help. 23:23, 1 July 2008 (UTC)

Handling this help page

I've just rediscovered my work at User:Happy-melon/Templates, and it's prompted me to want to sort this page and Help:Advanced templates out once and for all. I think what we should be looking to do is, first of all, write a completely comprehensive but non-repetitive replacement for Help:Template, probably working on User:Happy-melon/Templates. Then that should probably be transwikied over mw:Help:Templates leaving m:Help:Template either as a soft redirect or a clone. The technobabble involving configuration, parser-order, etc, should probably then be split out of that to mw:Manual:Templates, but that's another job.

So to get things moving, I'd like to deal with the criticism that has been raised about User:Happy-melon/Templates leaving out information that is currently buried somewhere in this current help page. I would very much appreciate any specific examples. I know, for instance, that the fact that the parser strips hashes from template names is not documented; is there anything else? Happymelon 21:25, 30 June 2008 (UTC)

It strikes me that the majority of useless junk on this help page is not, per se, completely useless. It just consists of 'tips and tricks' to use with templates. That's not what this page should be about. So what I think I want to do is move this page to something like Help:Template tricks, and make Help:Templates just be the raw functionality of template code (ie, User:Happy-melon/Templates). Comments? Happymelon 16:42, 1 July 2008 (UTC)
I think perhaps you need 3: Help:Templates, Help:Templates reference, and Help:Template tricks. I am sure that some of the initially confusing and unreadable stuff on this page is indeed essential for advanced users and should be kept somewhere and linked from here, but an accessible introduction it is not. The important thing, though, is think your excellent revision urgently needs to be available somewhere. If resistance from proponents of this page is delaying that, then perhaps make it a new page - Help:Templates introduction, and add a link here? Mcewan 11:28, 16 September 2008 (UTC)

super template

i don't know if i'm posting in the correct article, but well, go on. I'm searching a template or a mediawiki syntax which alllow me to hide a dynamic string of an article (in my exemple the string to extract is [[image:XXXXXXXXXXXXXXXXXX]] with various argument). For example if i do {{supermodel|{{:name of an article}}}}it'll allow me to see the article without any picture on it. And of course i need the reverse model which show me only the image. I don't know if it's clear or not, but well, I'm not finding anything on it. 23:38, 2 August 2008 (UTC)

I am not sure if that would help, but you may be interested in mw:Extension:RegexParserFunctions. Hillgentleman 15:46, 16 September 2008 (UTC)

Doesn't work

I'm experiencing a problems with template feature in MediaWiki 1.13rc. I'm putting {{Languages}} box or {{Warning ...}} box and it just transforming to {{Template:Languages}} box or {{Template:Warning ...}}

Do anybody know what's happened?

Also i cant' find a place where i can adjust toolbar of post editor and footer with samples to make it similar as in


How to fix references to redirected templates

I have the following situation:

This requires fixing all pages that use w:Template:hs to use the new name. How do I do that?

I see that you found w:Wikipedia:Bot requests already.--Patrick (talk) 13:03, 4 September 2008 (UTC)

Recursion error?

We recently moved a project to a MediaWiki 1.12.0 install... and have been getting Template loop detected: [pagename] errors when a template includes itself even a single level. (Which they often do for documentation.) This didn't used to throw errors, and I notice that Wikipedia exhibits the same problem.

When did this behavior change, and is there any way to get the old behavior (no error for a single layer of inclusion,) back? -Deriksmith 01:23, 24 September 2008 (UTC)

nesting of noinclude in includeonly might be not pointless

Help:Template/2008#Noinclude, includeonly, and onlyinclude says

Nesting an includeonly block within a noinclude block (or vice-versa) is legal but pointless.

But there is a reasonable way to potentially use such a nesting! But the current software doesn't interpret it that way.

Consider a template (say, T1) for building another template (T2), which is used on pages, for example, on P. You might want to place T1 into a category C1, and automatically place all built templates such as T2 into another category C2, and to automatically place P into some category C3, but not into C2.

To implement this "but not place P into C2", one might write in T1:


but this doesn't currently work the way one might want it: it doesn't place T2 into C2 now.


  1. can the required behavior be somehow implemented on the current software?
  2. could the software be improved to implement the described behavior of the described construction?

--Imz 20:05, 1 October 2008 (UTC)

Well, I've done it just by a comparison like this:
since in my case P was a very specific page.--Imz 21:18, 1 October 2008 (UTC)

template call

Can someone give me a non-technical definition of "template call" which I can add to the article? thank you.Odessaukrain 13:03, 16 October 2008 (UTC)

Using an external link in a parameter?

Can I create an external link in a parameter?

For example the template would be something vaguely like this:

The best market for houses is [{{{1}}} {{{2}}}]

And the use of the parameters would be:

{{template:house||my link}}

Which I would like it to give:

The best market for houses is my link

How could I do this?

Thank you, Odessaukrain 15:26, 16 October 2008 (UTC)

I got it to work:
The best market for houses is [{{{1}}} {{{2}}}]
I notice that if the web adress has an equal sign in it, then the parameters won't work properly.
Will not work because of the equal "=" signs.
So I used to make this long site name short, with no equal signs:
Odessaukrain 19:09, 16 October 2008 (UTC)

Calling templates within template calls


I'd like to do something like this:

|value1=text for template1 {{template2|value2=sometext for template 2}}more text for template 1}}

Which is calling template2 having variable value2 from within the content of the variable of value1 which is a variable of the template1

this doesn't work in a normal context because it gets:

|value1=text for template1 {{template2
|value2=sometext for template 2


text for template1 

for value1 in template1


sometext for template 2

for the value2 in template1 (which template1 probably doesn't use)


more text for template 1}}

as free text not passed to any template.

template2 doesn't get called and the whole page becomes horrible looking

How can I solve this?

thank you, --Dongiulio 18:19, 26 November 2008 (UTC)

That should work fine; if it doesn't, you probably have an error in your code (maybe unmatched square or curly brackets). For example:
  |value1=text {{User:Pathoschild/Sandbox3
  }} text
Pathoschild 19:33:19, 26 November 2008 (UTC)

I Need Help Making A Very Complex Template

Ok... what I am trying to do is make a very complex template for a wiki on Wikia. It works PERFECTLY on all but two pages. On two specific pages, which will be mentioned in my template, I only want the custom text that I specify to be included in the page. The names of the two pages on the wiki I am making this template for were called: "MediaWiki:Createplate-achievement" and "Wiki Name:Achievement Pages/Preloader". So I tried using the following code. I was expecting it to ignore the only include tags if it didn't meet the conditions of the if statement, but what actually happened is the text of both only include tags was the only thing being included on all pages, not just the ones specified. Now that I explained what I was trying to do, here is the code I used:

{{#ifeq:{{lc:{{{PAGENAME|}}}}}|Createplate-Achievement|<onlyinclude>This page is a "createplate" used with [[Special:CreatePage]] in order to make the creation of achievement pages easier.</onlyinclude>}}
{{#ifeq:{{lc:{{{PAGENAME|}}}}}|Achievement Articles/Preloader|<onlyinclude>This page is a "preformatted page model" which makes it easier to manually create achievement pages. If you don't want to manually create an achievement page, then you can use [[Special:CreatePage]].</onlyinclude>}}

I really have no idea how to get this to work. Is there any other code that has a similar effect? (Actual Wiki Name was removed because I didn't want to spam advertising}

"onlyinclude" is applied before any other expansion, such as the evaluation of conditions. Why do you need it anyway?
By the way, if you apply "lc" the result is never equal to a text including capitals. And if you mean the variable PAGENAME, use {{PAGENAME}}.
Patrick (talk) 08:42, 29 November 2008 (UTC)

Parameter help needed...

Well this is hard to explain, but basically, I want to insert a template into an article with parameters, but I also want the parameters to be, well accessible to a template included in the template that's included in the article. But when I try that, the second template doesn't have access to the parameters specified for the first template. What could should I use to have all of the parameters for the first template automatically the parameters for the second template? 04:53, 10 December 2008 (UTC)

See Help:Template#A_parameter_value_depending_on_parameters.--Patrick (talk) 08:54, 4 January 2009 (UTC)