Template talk:Next period
This template does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||
|
Template:Next period is permanently protected from editing because it is a heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use {{edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's documentation to add usage notes or categories.
Any contributor may edit the template's sandbox. This template does not have a testcases subpage. You can create the testcases subpage here. |
Cambrian
editThis edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Missing some relationships between stages in upper Cambrian:
|guzhangian=upper cambrian<!-- fix! --> |paibian=tremadocian |tremadocian=floian
It must say:
|guzhangian=paibian |late middle cambrian|paibian=jiangshanian |jiangshanian=stage 10 |cambrian stage 10|stage 10=tremadocian |tremadocian=floian
I can't edit the template. --PePeEfe (talk) 22:47, 17 April 2013 (UTC)
- Done — Martin (MSGJ · talk) 13:12, 28 August 2013 (UTC)
fortunean
editfortunean is miss spill must be (fortunian) Waso99 (talk) 08:57, 24 March 2019 (UTC)
Template-protected edit request on 18 March 2020
editThis edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
as of July 2018, three new ages have been ratified by the ICS (the meghalayan, the northgrippian, and the greenlandian). in addition, some other periods need to be added here, mainly the calabrian, the chibanian, and the upper/lat pleistocene. I request that these three are added to the bottom of this template, in this manner (the first line of the following example is found near the bottom of the template):
|gelasian=calabrian |calabrian=chibanian|ionian |chibanian|ionian=upper pleistocene|late pleistocene|tarantian |upper pleistocene|late pleistocene|tarantian=greenlandian |greenlandian=northgrippian |northgrippian=meghalayan |tertiary=quaternary |neogene=quaternary |meghalayan|holocene|quaternary|cenozoic|phanerozoic|now|recent|present=now |{{{1|{{PAGENAME}} }}} }}<noinclude>{{template doc}}</noinclude>
I believe this should work, and would allow functions like period span and period end to function correctly for these ages. thanks for processing my request! Benniboi01 (talk) 20:12, 18 March 2020 (UTC)
Template-protected edit request on 10 April 2020
editThis edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Sorry I forgot to mention this last time. I didn't realize this mistake until the last edit was already done. I would like the 'cambrian series 3' have the alternate name 'Miaolingian' because the name of that geological period was officially changed in 2018. I also want the wuliuan added as an alternate name for the cambrian stage 5. I also request that certain alternate names be added for the greenlandian, northgrippian, and meghalayan are all alternately referred to on the I have inserted this change into the sandbox, so feel free to copy-paste it. I have provided labelled sections of the code showing where I made changes. if you copy-paste from the sandbox, please be sure to take out the comments I made next to the places I edited (i don't want to clutter up the code).
<!-- this part can be found closer to the top-middle of the code--> |fortunian|earliest cambrian=stage 2 |cambrian stage 2|stage 2=stage 3 |cambrian stage 3|stage 3=stage 4 |cambrian stage 4|stage 4|late early cambrian=wuliuan<!--new code starts on this line--> |wuliuan|cambrian stage 5|stage 5|early middle cambrian=drumian ... <!--this part is a little below the middle of the code--> |maastrichtian=early paleocene |early paleocene|lower paleocene=middle paleocene |middle paleocene|mid paleocene=late paleocene |late paleocene|upper paleocene=early eocene |early eocene|lower eocene=middle eocene |middle eocene|mid eocene=late eocene |late eocene|upper eocene=early oligocene |early oligocene|lower oligocene=late oligocene |late oligocene|upper oligocene=early miocene |early miocene|lower miocene=middle miocene |middle miocene|mid miocene=late miocene |late miocene|upper miocene=early pliocene |early pliocene|lower pliocene=late pliocene |late pliocene|upper pliocene=early pleistocene |early pleistocene|lower pleistocene=middle pleistocene |middle pleistocene|mid pleistocene=late pleistocene |late pleistocene=early holocene<!--new code starts on this line--> |early holocene|lower holocene=middle holocene |middle holocene=late holocene ... <!--this last part is at the very end of the code--> |tertiary=quaternary |neogene=quaternary |late holocene|upper holocene|meghalayan|holocene|quaternary|cenozoic|phanerozoic|now|recent|present=now <!--here's where the new code is--> |{{{1|{{PAGENAME}} }}} }}<noinclude>{{template doc}}</noinclude>
Thank you! Benniboi01 (talk) 18:13, 10 April 2020 (UTC) Benniboi01 (talk) 18:13, 10 April 2020 (UTC)
Template-protected edit request on 30 June 2023
editThis edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
The switch keys are all duplicated:
|
---|
|
- the first in the file takes precedence - these duplicates should be removed Desb42 (talk) 14:35, 30 June 2023 (UTC)
- Not done: please make your requested changes to the [template's sandbox] first; see WP:TESTCASES. Tried to do this in the sandbox, but it became very confusing. Seems some of the duplications are necessary? In any case, this should be done in the sandbox by an editor more savvy about these periods than I am. P.I. Ellsworth , ed. put'er there 17:44, 30 June 2023 (UTC)
- I have modified the sandbox to reflect the changes I have mentioned. #switch uses the first matching key, regardless of any subsequent key that has the same value. So duplicates should be removed - the only real issue is whether the first matching key is the right one (In this case I believe I have made the right choices) Desb42 (talk) 12:22, 5 July 2023 (UTC)
- Thank you, editor Desb42, and completed. Time will tell. P.I. Ellsworth , ed. put'er there 16:04, 5 July 2023 (UTC)
- I have modified the sandbox to reflect the changes I have mentioned. #switch uses the first matching key, regardless of any subsequent key that has the same value. So duplicates should be removed - the only real issue is whether the first matching key is the right one (In this case I believe I have made the right choices) Desb42 (talk) 12:22, 5 July 2023 (UTC)