This template was considered for merging with Template:Archive banner and six other templates on 2015 August 24. The result of the discussion was "Keep". |
Is there any way to truncate this template on the last archive, so a redlink to a nonexistant archive doesn't appear? / Blaxthos 21:12, 7 October 2006 (UTC)
I've never coded for wiki* or anything, so maybe this is a silly suggestion, but how about just adding a boolean 3rd arg, when set to 1 (or present at all) it supresses the redlink'd archive page (Archive+1). / Blaxthos 21:23, 7 October 2006 (UTC)
I'm a bit tired at the moment, and can't understand the code I wrote, but I did the above in {{ Log}}. It might or might not work here if somebody wants to try it! -- kingboyk 00:23, 6 March 2007 (UTC)
I recently created User_talk:Carcharoth/Archive_7, which displays the archive pages at the top fine, but the previous page, User_talk:Carcharoth/Archive_6, doesn't have the link to Archive 7. What is going on? Carcharoth 02:18, 11 December 2006 (UTC)
I made the change to enable a dynamic list of up to 20 pages, instead of the older static display of three fixed pages. Any problem? → Aza Toth 23:22, 2 January 2007 (UTC)
Have I done something wrong, or is this broken on category talk pages? Please see:
-- kingboyk 19:57, 6 April 2007 (UTC)
As some old archives were named incorrectly (e.g. "archive2" instead of "Archive 2"), I have added the possibility to use custom pagenames with optional "prev" and "next" fields. I suppose no bugs should result from this. Súrendil 18:26, 7 September 2007 (UTC)
{{
editprotected}}
Hmmm... one of my previous archives appears to have changed during this new process. It doesn't seem that inconvenient but I'm requesting a change to the archive template anyway, if anybody has the time to do it. :| TelCo NaSp Ve :| 13:57, 13 July 2010 (UTC)
{{ editprotected}}
Can an admin move the documentation information to a seperate /doc page by adding {{ documentation}}? Thanks! Math Cool 10 Sign here! 02:29, 14 April 2009 (UTC)
Not sure what has happened here, but this template has not formatted correctly on my first archive page, it is fine on all the rest. Link User_talk:Mollsmolyneux/Archive_1. What have I done wrong? Thanks for any help -- Mollsmolyneux ( talk) 19:13, 11 July 2010 (UTC)
We had a consensus to merge this template with {{ Archive nav}} back in October, but no consensus on how to implement it. I think the best path forward is to do like SMcCandlish said: "integrate the best functionality of both [template]". I will list the features of both templates and hope we can come to some sort of consensus.
Features of {{ Archive navigation}}:
Features of {{ Archive nav}}:
In my opinion having many links is significantly more versatile, imagine for example you're looking for a November 2019 discussion at WT:MILHIST. You guess that could be something like archive 150, but realize that's too early. With the current {{ archive navigation}} you would either have to go back to the archive box on the main talkpage, write in the URL field or painfully slowly work your way forward in time. With {{ archive nav}} you can with one click try archive 155 see that you overshot and with just one more click end up at archive 153 which you were looking for.
I can see if you think {{ Archive nav}} have a bit excessive amount of links, but a few more would definitely be beneficial.
Hiding of links I've realized is a surprisingly contentious topic, but I think there at least should be an option which way it should be only affecting the next archive which is the only link I've seen people argue is beneficial. I would suggest to use |noredlink=
like is done in {{
Aan}}.
I think both changing the default path and manually specifying links should be supported. Both have usecases and are beneficial. With multiple links I guess prev (with alias prev1) would be the archive immediately before, prev2 the one before that and so on. Prev2 and next2 would probably only be used very rarely, but it would probably be occasionally useful.
What do you think? Feedback appreciated! Pinging participants in the TfD: @ Pigsonthewing, Izno, Gonnym, Tom (LT), Sdkb, and SMcCandlish:. -- Trialpears ( talk) 15:12, 26 March 2021 (UTC)
Regarding how, I like the way {{ Archive nav}} uses the word "archive" only on the current one; it's not needed for more than that. I also like how it displays more than just the very next or very previous archive. For pages with dozens of archives, we probably don't want to list all, but for ones with only 10 or so, sure, let's have all. I prefer {{ Archive navigation}}'s vertical separators rather than Archive nav's horizontal ones.I realize that doesn't address all the current outstanding questions; I'll trust others to handle those. {{u| Sdkb}} talk 17:15, 26 March 2021 (UTC)
|
separators, which is inconsistent with navboxes and inline lists in other navigational elements and in {{
hlist}}
and {{
flatlist}}
. I think Sdkb's underlying probable objection to –
separators is their width, and I would agree that it's unnecessary. We should just use mid-dot bullets like everything else does. (I have no objection to a |separator=
parameter, though; we could even add that to {{hlist}}
and {{flatlist}}
). I would propose a merged template that does the following:
|noredlink=
(from {{
aan}}
) for this purpose, if not already a supported parameter name.
{{
hlist}}
or {{
flatlist}}
to do the layout, or at least use bullets consistent with them as the default separator.{{
Historical}}
, or a time-limited thing like annual ArbCom elections) and we thus don't expect there to ever be another archive page in the series. Obviously, the former case – of more discussion over time being likely and thus eventually needing archival – is more common by orders of magnitude, so it makes sense as the default behavior. Having more rather than less navigation is more helpful, so that should also be the default, as long as there is actually stuff to navigate.PS: We should also see about merging in other features of {{
aan}}
({{
Automatic archive navigator}}
) so that template, too, can be merged away. It's confusing to have so many extremely similar templates for the same thing, which which all do inconsistent things with inconsistent parameter names. Just make all parameters for the same stuff be aliases of each other across every template of this sort, which makes eventual merger easy. Even if we keep some old template names as wrappers that pre-specify certain parameters, we should have a single codebase for this stuff.
—
SMcCandlish
☏
¢ 😼
01:01, 27 March 2021 (UTC)
I've made a version at Template:Archive navigation/sandbox ( testcases). It's based on {{ Archive nav}} with the following changes:
|next=
and |prev=
for backwards compatibility with {{
Archive navigation}} and weird quirks with names. |next2=
, |prev3=
and so on are not supported.|noredlink=
or |noredlinks=
. |showmissing=
from {{
Archive navigation}} is not supported since it is only used on
26 pages and it will be confusing to have inverse parameters.I've checked other templates for aliases that should be added and only found |root=
as an alias for |base=
which haven't been mentioned before.
Are there more things we want here or is this version satisfactory and we are ready to implement it? --
Trialpears (
talk)
21:10, 31 March 2021 (UTC)
I've now implemented the merger with the version I suggested above. I will of course help implement improvements or changes in the future as well if there are any concerns. -- Trialpears ( talk) 22:04, 18 April 2021 (UTC)
I am not sure how the template should intend to look like since the documentation has not been updated, but the transclusion on Wikipedia talk:Requested templates/Archive 1 looks wrong to me:
Is this intended or not? ~ Aseleste ( t, e | c, l) 14:09, 24 April 2021 (UTC)
I noticed that many pages transcluding this template (listed at
Special:WhatLinksHere/Archive 2) incorrectly show a redlink to the mainspace page
Archive 2 instead of the actual Archive 2 subpage. This happens whenever the markup {{archive-nav|1|next=Archive 2}}
appears on the page. The template needs to be fixed so that the pages using that markup correctly link to the Archive 2 subpage instead of showing a redlink to
Archive 2.
GeoffreyT2000 (
talk)
00:18, 30 August 2021 (UTC)
There are now only 41 pages left with both {{ archive}} and {{ archive navigation}}. [1] I have not converted them because they're protected, but the conversion will be straightforward on all of them. The {{ archive navigation}} template has an additional 750 transclusions. [2]
I don't think that {{ archive navigation}} should be deleted. Once the remaining 41 pages are converted from {{ archive}}+{{ archive navigation}} to {{ aan}}, then {{ archive}} can be merged without issues.
The 750 other transclusions include a lot of archives, especially in userspace, that have atypical names or formats. There's no benefit to removing {{ archive navigation}} from these pages, and I don't think there is much benefit in trying to move or reformat the types of situations below:
Feedback welcome, Rjjiii ( talk) 22:13, 6 July 2024 (UTC)
This template was considered for merging with Template:Archive banner and six other templates on 2015 August 24. The result of the discussion was "Keep". |
Is there any way to truncate this template on the last archive, so a redlink to a nonexistant archive doesn't appear? / Blaxthos 21:12, 7 October 2006 (UTC)
I've never coded for wiki* or anything, so maybe this is a silly suggestion, but how about just adding a boolean 3rd arg, when set to 1 (or present at all) it supresses the redlink'd archive page (Archive+1). / Blaxthos 21:23, 7 October 2006 (UTC)
I'm a bit tired at the moment, and can't understand the code I wrote, but I did the above in {{ Log}}. It might or might not work here if somebody wants to try it! -- kingboyk 00:23, 6 March 2007 (UTC)
I recently created User_talk:Carcharoth/Archive_7, which displays the archive pages at the top fine, but the previous page, User_talk:Carcharoth/Archive_6, doesn't have the link to Archive 7. What is going on? Carcharoth 02:18, 11 December 2006 (UTC)
I made the change to enable a dynamic list of up to 20 pages, instead of the older static display of three fixed pages. Any problem? → Aza Toth 23:22, 2 January 2007 (UTC)
Have I done something wrong, or is this broken on category talk pages? Please see:
-- kingboyk 19:57, 6 April 2007 (UTC)
As some old archives were named incorrectly (e.g. "archive2" instead of "Archive 2"), I have added the possibility to use custom pagenames with optional "prev" and "next" fields. I suppose no bugs should result from this. Súrendil 18:26, 7 September 2007 (UTC)
{{
editprotected}}
Hmmm... one of my previous archives appears to have changed during this new process. It doesn't seem that inconvenient but I'm requesting a change to the archive template anyway, if anybody has the time to do it. :| TelCo NaSp Ve :| 13:57, 13 July 2010 (UTC)
{{ editprotected}}
Can an admin move the documentation information to a seperate /doc page by adding {{ documentation}}? Thanks! Math Cool 10 Sign here! 02:29, 14 April 2009 (UTC)
Not sure what has happened here, but this template has not formatted correctly on my first archive page, it is fine on all the rest. Link User_talk:Mollsmolyneux/Archive_1. What have I done wrong? Thanks for any help -- Mollsmolyneux ( talk) 19:13, 11 July 2010 (UTC)
We had a consensus to merge this template with {{ Archive nav}} back in October, but no consensus on how to implement it. I think the best path forward is to do like SMcCandlish said: "integrate the best functionality of both [template]". I will list the features of both templates and hope we can come to some sort of consensus.
Features of {{ Archive navigation}}:
Features of {{ Archive nav}}:
In my opinion having many links is significantly more versatile, imagine for example you're looking for a November 2019 discussion at WT:MILHIST. You guess that could be something like archive 150, but realize that's too early. With the current {{ archive navigation}} you would either have to go back to the archive box on the main talkpage, write in the URL field or painfully slowly work your way forward in time. With {{ archive nav}} you can with one click try archive 155 see that you overshot and with just one more click end up at archive 153 which you were looking for.
I can see if you think {{ Archive nav}} have a bit excessive amount of links, but a few more would definitely be beneficial.
Hiding of links I've realized is a surprisingly contentious topic, but I think there at least should be an option which way it should be only affecting the next archive which is the only link I've seen people argue is beneficial. I would suggest to use |noredlink=
like is done in {{
Aan}}.
I think both changing the default path and manually specifying links should be supported. Both have usecases and are beneficial. With multiple links I guess prev (with alias prev1) would be the archive immediately before, prev2 the one before that and so on. Prev2 and next2 would probably only be used very rarely, but it would probably be occasionally useful.
What do you think? Feedback appreciated! Pinging participants in the TfD: @ Pigsonthewing, Izno, Gonnym, Tom (LT), Sdkb, and SMcCandlish:. -- Trialpears ( talk) 15:12, 26 March 2021 (UTC)
Regarding how, I like the way {{ Archive nav}} uses the word "archive" only on the current one; it's not needed for more than that. I also like how it displays more than just the very next or very previous archive. For pages with dozens of archives, we probably don't want to list all, but for ones with only 10 or so, sure, let's have all. I prefer {{ Archive navigation}}'s vertical separators rather than Archive nav's horizontal ones.I realize that doesn't address all the current outstanding questions; I'll trust others to handle those. {{u| Sdkb}} talk 17:15, 26 March 2021 (UTC)
|
separators, which is inconsistent with navboxes and inline lists in other navigational elements and in {{
hlist}}
and {{
flatlist}}
. I think Sdkb's underlying probable objection to –
separators is their width, and I would agree that it's unnecessary. We should just use mid-dot bullets like everything else does. (I have no objection to a |separator=
parameter, though; we could even add that to {{hlist}}
and {{flatlist}}
). I would propose a merged template that does the following:
|noredlink=
(from {{
aan}}
) for this purpose, if not already a supported parameter name.
{{
hlist}}
or {{
flatlist}}
to do the layout, or at least use bullets consistent with them as the default separator.{{
Historical}}
, or a time-limited thing like annual ArbCom elections) and we thus don't expect there to ever be another archive page in the series. Obviously, the former case – of more discussion over time being likely and thus eventually needing archival – is more common by orders of magnitude, so it makes sense as the default behavior. Having more rather than less navigation is more helpful, so that should also be the default, as long as there is actually stuff to navigate.PS: We should also see about merging in other features of {{
aan}}
({{
Automatic archive navigator}}
) so that template, too, can be merged away. It's confusing to have so many extremely similar templates for the same thing, which which all do inconsistent things with inconsistent parameter names. Just make all parameters for the same stuff be aliases of each other across every template of this sort, which makes eventual merger easy. Even if we keep some old template names as wrappers that pre-specify certain parameters, we should have a single codebase for this stuff.
—
SMcCandlish
☏
¢ 😼
01:01, 27 March 2021 (UTC)
I've made a version at Template:Archive navigation/sandbox ( testcases). It's based on {{ Archive nav}} with the following changes:
|next=
and |prev=
for backwards compatibility with {{
Archive navigation}} and weird quirks with names. |next2=
, |prev3=
and so on are not supported.|noredlink=
or |noredlinks=
. |showmissing=
from {{
Archive navigation}} is not supported since it is only used on
26 pages and it will be confusing to have inverse parameters.I've checked other templates for aliases that should be added and only found |root=
as an alias for |base=
which haven't been mentioned before.
Are there more things we want here or is this version satisfactory and we are ready to implement it? --
Trialpears (
talk)
21:10, 31 March 2021 (UTC)
I've now implemented the merger with the version I suggested above. I will of course help implement improvements or changes in the future as well if there are any concerns. -- Trialpears ( talk) 22:04, 18 April 2021 (UTC)
I am not sure how the template should intend to look like since the documentation has not been updated, but the transclusion on Wikipedia talk:Requested templates/Archive 1 looks wrong to me:
Is this intended or not? ~ Aseleste ( t, e | c, l) 14:09, 24 April 2021 (UTC)
I noticed that many pages transcluding this template (listed at
Special:WhatLinksHere/Archive 2) incorrectly show a redlink to the mainspace page
Archive 2 instead of the actual Archive 2 subpage. This happens whenever the markup {{archive-nav|1|next=Archive 2}}
appears on the page. The template needs to be fixed so that the pages using that markup correctly link to the Archive 2 subpage instead of showing a redlink to
Archive 2.
GeoffreyT2000 (
talk)
00:18, 30 August 2021 (UTC)
There are now only 41 pages left with both {{ archive}} and {{ archive navigation}}. [1] I have not converted them because they're protected, but the conversion will be straightforward on all of them. The {{ archive navigation}} template has an additional 750 transclusions. [2]
I don't think that {{ archive navigation}} should be deleted. Once the remaining 41 pages are converted from {{ archive}}+{{ archive navigation}} to {{ aan}}, then {{ archive}} can be merged without issues.
The 750 other transclusions include a lot of archives, especially in userspace, that have atypical names or formats. There's no benefit to removing {{ archive navigation}} from these pages, and I don't think there is much benefit in trying to move or reformat the types of situations below:
Feedback welcome, Rjjiii ( talk) 22:13, 6 July 2024 (UTC)