Template talk:Temporary

Nice

Great work Poke, definitely something useful. --Landon144 (talk) 12:43, 30 July 2013 (UTC)

Thanks, please note the ongoing discussion on the topic though. poke | talk 13:41, 30 July 2013 (UTC)

There's a problem with this template, or at least its usage. It is being used to mark events as no longer in use. Unfortunately, the {{area events}} will continue to list in an area's events as there is no |historical = y parameter to stop it being included. --Claret (talk) 20:42, 23 February 2014 (UTC)

All it needs is to be put into a unique category, then for area events template to exclude said category. Historical isn't always going to be proper, since some of the things listed with temporary may return. Konig 01:26, 24 February 2014 (UTC)

Edit: Another problem though - the banner icons used until now are not longer being made for The Origins of Madness and on. Konig 01:27, 24 February 2014 (UTC)

As a pure notice template, this is not meant to provide any categorization. As such, a historical parameter does not make any sense either (plus would seem rather redundant, no?). Categorization, especially for events, is done by the infobox, so if an event is historical, that should be noted there by adding historical = y to the infobox.

As for the banner icons, yes, this is indeed a problem. And I don’t really have any idea how to solve this yet; I was originally hoping that ANet would still continue to make those for the navigation but that is not the case. This is also an issue (imo) on release (which looks so boring now without those images); maybe we will have to come up with our own graphics. poke | talk 09:34, 24 February 2014 (UTC)

So, we need a category of temporary which is excluded by {{area events}} and similar. Not using the historical parameter with infoboxes that are actually historical or probably recurrent, leaves the area lists with incorrect information at present. --Claret (talk) 09:54, 24 February 2014 (UTC)

As for the release nav images, see the discussion here. —Dr Ishmael 13:18, 24 February 2014 (UTC)

name

move to {{release}} since this is a tag for release content instead of anything considered temporary.--Relyk ~ talk < 22:53, 11 March 2014 (UTC)

Except that this is never used on articles for things that were permanent. Or at least, wasn't until recently if it is. Konig 23:17, 11 March 2014 (UTC)

It will never be used on permanent articles anyways, maybe {{release notice}}.--Relyk ~ talk < 23:30, 11 March 2014 (UTC)

I would agree that {{release notice}} would be a better name. However would anything temporary as apposed to historical not be part of a release. It would also be nice if we could automatically add this like we do historical.Anzenketh (talk) 13:52, 15 May 2014 (UTC)

After thinking about it for a bit. Release name would not be a good name. Mainly due to this template flags it as temporary content. There may be releases that contain events that are not temporary. Items that were not designed to be temporary but removed or were designed to be temporary but not part of a actual release should use the {{historical}} flag. A example of such a item would be the Mystic Chest.Anzenketh (talk) 15:10, 15 May 2014 (UTC)

Historical temporary content

I do like this template however it has one issue. It does not flag something as historical there is some discussion in this talk page on that it was not designed to flag it that the historical flag should be used. Flagging items as historical is important as we may want to use GW2W:SMW to query for items/events/NPC/etc.. but may want to exclude things no longer in game. We could just flag things as historical but if we do that it looks like this. I think of a few possible solutions.

1. Not use the template at all. Have people read the summary.
2. Change the infobox so we can suppress the {{historical content}} template but still have SMW flag it as historical and still have it added to the historical category. Then we can add the {{temporary}} template to the top manually. I see multiple other reasons why this may be useful.
3. Change the infoboxes even more as I suggested here (a lot of work and a horrible if tree would result. See the code in this userbox template to understand what I mean). However this has a big advantage as it makes it easier for us to keep up with changes.
4. Add another SMW parameter temporary that is basicly the same as historical. (redundant)
5. The easiest route of all. Do nothing and have both the {{historical content}} and {{temporary}} template show on the article.

What say ye?

The above comment was made by me on 2 June 2014‎‎ Anzenketh (talk) 17:09, 4 June 2014 (UTC)

its a nice template, why wouldn't we use it on content that is expected to return such as Halloween, Wintersday etc? -Chieftain Alex 14:47, 6 June 2014‎ (UTC)

I think that would be a good use for the template if the community has decided that historical content that is related to the living world should only be flagged with historical and show only the {{historical content}} template. My viewpoint on the matter with the changes to {{historical content}} it is fine if we do it either way however we should not display both. The question is though if we do only use it for special events then what happens as soon as content does not return. Do we mark it as historical and remove the {{temporary}} template? Anzenketh (talk) 14:54, 6 June 2014 (UTC)

well if its not returning, then its historical, so yes we'd apply {{historical content}}. There shouldn't ever really be two notices on a page. -Chieftain Alex 15:19, 6 June 2014 (UTC)

That sounds good to me as long as we move the information in the {{temporary}} template to the actual article and specify what update it was removed on I think that is good practice for all historical content anyways. I think there is more consensus/approval from the community before we made a wide spread change on this however. Anzenketh (talk) 15:31, 6 June 2014 (UTC)

I'd implement this (minor) change at the same time as I reconfigure the historical logic on infoboxes + smw queries that reference "is historical". -Chieftain Alex 16:25, 6 June 2014 (UTC)

Ok now that you implemented your change. Where does this template come into play. Does it even come into play any longer? Do we not use this template any longer? If we do what is the criteria for using this template. Anzenketh (talk) 16:49, 11 June 2014 (UTC)

The temporary template has no bearing on the availability status of the NPC or content... so the changes are unrelated. -Chieftain Alex 17:20, 11 June 2014 (UTC)

So we are giving two notices. One that states when the content was available another that states if it is historical or discontinued? Anzenketh (talk) 17:29, 11 June 2014 (UTC)

One notice. Its either temporary (current) or historical. -Chieftain Alex 09:16, 12 June 2014 (UTC)

So then this is only used for content that temporary content that is currently active or on seasonal/special events correct? Anzenketh (talk) 13:06, 12 June 2014 (UTC)

Name revisited

I'm gonna open this up again, but slightly different. Time has passed and it seems whenever I see this tag is used now it's notating two things: a past release of things that are now historical or a yearly festival. I was pondering if perhaps this template could be moved and called {{festival}} and move things that became historical to the historical template. If not, at least move the things that did become historical to Template:Historical content, since if things were added and stayed in the game, that usually winds up in the notes on the page, and not on a tag at the top of the page, so leaving it here really isn't needed I think, and would remove there being double tags at the top(historical and temporary). - Do_odleplex 19:36, 20 October 2016 (UTC)

The reason I made {{infobox status}} was to solve this issue. Pages can only be under one type of status. We only need to be convert them over.--Relyk ~ talk < 20:20, 20 October 2016 (UTC)

Ah that seems simple enough, so all that needs to be done is just move the historical ones from here to there then, correct? - Do_odleplex 20:26, 20 October 2016 (UTC)

The template uses these templates for the notice tags. We'd replace any temporary or historical content templates with infobox status. That prevents pages being double-tagged in the future.--Relyk ~ talk < 21:16, 20 October 2016 (UTC)

Link Change

As unfortunately my attempts didn't work, can somebody change it so that if something is tagged as being from "A Very Merry Wintersday" or "Shadow of the Mad King" it goes to the original release pages and not the current release pages? The pages using this are (or should be anyway, if not they need to be corrected)from the original release and the following years were usually specified as exactly when, ie "Halloween 2015", "Wintersday 2015", etc. so there shouldn't be any issues. - Do_odleplex 21:52, 26 April 2017 (UTC)

While it is possible to do that I think it would be more practical to change the pages instead of the template. By changing the template to direct “Shadow of the Mad King” to “Shadow of the Mad King 2012” it can come off as misleading. J.Tesla (talk) 22:50, 26 April 2017 (UTC)

I don't think so, since the image for the nav has the date in it, I would think it would be fairly obvious the link would take them to the original release page. - Do_odleplex 23:22, 26 April 2017 (UTC)

Banner image dates

The images used in the banner have a date on them, which doesn't accurately depict release dates of temporary content that was added in a release of the same name in a later year (e.g. Prepare for a race around Divinity's Reach was released this year, not 2013 like the image would indicate (the first year of A Very Merry Wintersday). Is there any fix for this? --Gimmethegepgun (talk) 16:48, 13 December 2017 (UTC)

Add "Wintersday 2017", not the full release name, as that's meant for the original release. I haven't uploaded the image for this year yet(family stuff today cause holidays), but that should correct the dates when I have. - Do_odleplex 17:00, 13 December 2017 (UTC)

Special events

I think this template could use an update to support special events. --BuffsEverywhere (talk) 20:29, 16 July 2019 (UTC)

Multiple festivals

We now have at least one NPC (Holomancer) that appears at two festivals, but the template only seems to accept one 'seasonal' parameter at a time. -- kazerniel (talk | contribs) 23:58, 25 June 2021 (UTC)

There are more NPCs appearing during multiple festivals. We usually use either multiple templates, or when the list is veeery long (like for Drooburt or Gourdon), we use only categories at the bottom. ~Sime 00:14, 26 June 2021 (UTC)

Haha true, don't know how I forgot about Drooburt 🥴 Thanks for the info :) -- kazerniel (talk | contribs) 00:46, 26 June 2021 (UTC)

Commas

Seems this template generates , after the notice on Sparking Stone. —Kvothe (talk) 00:42, 7 October 2021 (UTC)

Thanks, fixed. --BuffsEverywhere (talk) 01:21, 7 October 2021 (UTC)