Difference between revisions of "Template:Ansreq"
m (fix groupId) |
|||
| (101 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | < | + | <noinclude> |
| − | < | + | This template is used to create the header and the answerbox of a requirement. The answerbox needs to be closed by using the [[Template:CloseReq|CloseReq]]-Template.<br> |
| − | < | + | For example like that:<br> |
| − | < | + | <div class="toccolours"> |
| − | + | :<nowiki>{{Ansreq|num=1|page={{PAGENAME}}}}<nowiki /></nowiki><br> | |
| − | | | + | :<nowiki>Here you can write your answer. Any MediaWiki-Content is possible.</nowiki><br> |
| − | | | + | :<nowiki>{{CloseReq}}</nowiki> |
| − | + | </div> | |
| − | </ | + | The <nowiki><nowiki /></nowiki> tag is needed so there is no unnecessary line break at the begining of the answer. |
| − | </ | + | For the Example the <nowiki>{{PAGENAME}}</nowiki> was replaced with a fixed name, but at an honor page the template will get the needed information out of the pagename. |
| − | < | + | |
| − | < | + | If the page argument contains the word "Requirement" then the requirements are fetched directly from that page. If it doesn't, then we construct the requirements page by extracting the first two elements of the page (assumed to be "AY Honors/''honor''") and appending "/Requirements" to it. We need this to support variant requirements, as it allows us to specify |
| − | < | + | <pre>page=AY Honors/''honor''/Requirements_2</pre> |
| − | </ | + | in the honor landing template. |
| − | </ | + | |
| + | {{Ansreq|num=1|page=AY Honors/Aboriginal Lore}}<nowiki /> | ||
| + | This is the example answer. Any MediaWiki-Content is possible (Tables, Templates, ...). | ||
| + | {{CloseReq}} | ||
| − | <noinclude> | + | {{Ansreq|level1_ID=1|page=AY Honors/Taste}}<nowiki /> |
| + | This is the example answer. Any MediaWiki-Content is possible (Tables, Templates, ...). | ||
| + | {{CloseReq}} | ||
| + | </noinclude><includeonly><div class="req-container"><div class="req-head"><p class="req-num">{{#vardefine:landingID|{{GetHonorLandingPageID|honorname={{{honorname|{{#titleparts:{{{page|{{PAGENAME}}}}}|1|2}}}}}}}}}{{#vardefine:req|{{#cargo_query: | ||
| + | tables=Honors_Requirements | ||
| + | |where=landingID='{{#var:landingID}}' | ||
| + | AND reqVariantNo='{{{reqVariantNo|0}}}' | ||
| + | {{#if:{{{sectionID|}}}|AND sectionID='{{{sectionID}}}'|}} | ||
| + | {{#if:{{{groupID|}}}|AND groupID='{{{groupID}}}'|}} | ||
| + | {{#if:{{{level1_ID|{{{num|}}}}}}|AND level1_ID ='{{{level1_ID|{{{num|}}}}}}'|}} | ||
| + | {{#if:{{{level2_ID|}}}|AND level2_ID ='{{{level2_ID}}}'|}} | ||
| + | {{#if:{{{level3_ID|}}}|AND level3_ID ='{{{level3_ID}}}'|}} | ||
| + | {{#if:{{{level4_ID|}}}|AND level4_ID ='{{{level4_ID}}}'|}} | ||
| + | {{#if:{{{level5_ID |}}}|AND level5_ID ='{{{level5_ID}}}'|}} | ||
| + | {{#if:{{{level6_ID|}}}|AND level6_ID ='{{{level6_ID}}}'|}} | ||
| + | AND language='{{{language|{{PAGELANGUAGE}}}}}' | ||
| + | |fields=text | ||
| + | |template=CargoOutput-NoFormatting | ||
| + | |default=}}}}{{#if:{{#pos:{{{page|}}} | ||
| + | |Requirements}} | ||
| + | |{{#vardefine:reqpage|{{{page}}}}} | ||
| + | |{{#vardefine:reqpage|{{#titleparts:{{{page}}}|2|1}}/Requirements}} | ||
| + | }}{{{dispreq|{{{level6_ID|{{{level5_ID|{{{level4_ID|{{#if:{{{level3_ID|}}}|{{#invoke:Converters|FNumToRoman|{{{level3_ID}}} }}|{{#if:{{{level2_ID|}}}|{{#invoke:Converters|FNumToAlphabet|{{{level2_ID}}} }}|{{{level1_ID|{{{num}}}}}}}}}}}}}}}}}}}}}}</p><div class="req-text">{{#if:{{#var:req}}|{{#var:req}}|{{#lst:{{#var:reqpage}}{{GetLangSuffix}}|req{{{num}}} }}}}</div></div></div><div class="req-answer"></includeonly> | ||
| + | <noinclude>[[Category:Requirements Template]]</noinclude> | ||
Latest revision as of 16:37, 29 December 2022
This template is used to create the header and the answerbox of a requirement. The answerbox needs to be closed by using the CloseReq-Template.
For example like that:
- {{Ansreq|num=1|page={{PAGENAME}}}}<nowiki />
- Here you can write your answer. Any MediaWiki-Content is possible.
- {{CloseReq}}
The <nowiki /> tag is needed so there is no unnecessary line break at the begining of the answer. For the Example the {{PAGENAME}} was replaced with a fixed name, but at an honor page the template will get the needed information out of the pagename.
If the page argument contains the word "Requirement" then the requirements are fetched directly from that page. If it doesn't, then we construct the requirements page by extracting the first two elements of the page (assumed to be "AY Honors/honor") and appending "/Requirements" to it. We need this to support variant requirements, as it allows us to specify
page=AY Honors/''honor''/Requirements_2
in the honor landing template.
1
This is the example answer. Any MediaWiki-Content is possible (Tables, Templates, ...).
1
This is the example answer. Any MediaWiki-Content is possible (Tables, Templates, ...).
