Template talk:Stub/PTR
Category for previous patches
Does anyone think it would be worthwhile to have the template automatically add a category if the patch specified wasn't the latest? That way it was easy to distinguish which articles need updated. -Howbizr (talk) 20:02, 24 February 2009 (UTC)
- I have added T:Stub/Updated on the theory that
- a) updating a stub for data from a new patch is easier than filling it in from the ground up
- b) having a patch ID is a very useful feature for the stub
- c) ideally, updated stubs will be removed as they get updated, requiring cleanup of individually labeled "updated" categories (such as {{removedfromgame}} uses) as they get emptied.
- d) having all the updated stubs in one category avoids some of them being hidden from someone taking updating as their task.
- I am not attached to the category name, the template name, or the text involved. If you think different names/text would suit, please be BOLD. --Eirik Ratcatcher (talk) 20:23, 26 August 2009 (UTC)
- I think you missed the point by creating a new template. We would add a parameter inside the template, so that if anyone provided something other than the latest patch, the category would be added.
- His stub was so that the items that were added/changed in a upcoming PTR patch (in this case 3.2.0. I was changing the {{Stub/PTR|<patch 3.2.0>}} stubs to {{Stub/Achievement}}, {{Stub/Item}}, {{Stub/Mob}}, {{Stub/NPC}} and {{Stub/Other}} as per the stub PTR wording for when the build was released into the game. His stub puts them into a seperate category so they can be easily found and fixed and NOT lost into the OVER 7,000 stubed {{Stub/Item}} as it were. Granted this category will grow in number as well if they are never worked on as the other stubbed articles are. I guess someone has to start somewhere!?!? -- (M o r p h | C | T ) 20:35, 28 August 2009 (UTC)
Category problems
I cannot figure this out, with the <includeonly> and <onlyinclude>. I'm trying to show, only for transcluded pages, either the category Stubs/Upcoming Patch or the category Category:Patch update stubs. No matter what I try, it just isn't working. Howbizr(t·c) 9:56 PM, 4 Sep 2009 (EDT)
This template still appears in category:Patch update stubs. The documentation page (as it uses this template) also appears in that category, despite having used "doc=". I wouldn't call that fixed, necessarily. I don't know if it became UN-fixed since september. --Eirik Ratcatcher (talk) 21:27, November 16, 2009 (UTC)
Remove Stub/PTR
- Depreciate {{Stub/PTR}} and {{Stub/PTR-section}} by:
- Using other stub templates when applicable, such as {{Stub/Item}} or {{Stub-section}}.
- Using expansion templates when applicable, such as {{t|Shadowlands}} or {{sl-section}}.
- Modifying {{Patch}} to inform users about the presence of future content when the release date is unknown.
This proposal was declined by a winning No vote according to Warcraft Wiki Voting policy.
|
Votes
- Yes
- Yes DDC (talk) 16:11, 31 December 2021 (UTC) - (Nominated)
- No
- No PeterWind (talk) 11:45, 1 January 2022 (UTC) - (I use the PTR category frequently when working on PTR content.)
- Abstain
- Abstain — Surafbrov T / C 19:13, 1 January 2022 (UTC) - (In terms of the main stub template, I'm for. Against the idea of removing the PTR-section template as that is more useful for specific lore sections that are PTR-current.)
- Abstain WardsJames (talk) 22:30, 9 September 2023 (UTC) - (no comment)
Comments
@PeterWind, the PTR category would be incorporated into the {{Patch}} template (apply to patches whose dates are not set). During this time, we could use an intersection for specifics like Category:Item stubs and Category:Future patch stubs. Once the patch goes live, those stuff can still be found in their appropriate stub categories like the item stubs category. — Surafbrov T / C 19:13, 1 January 2022 (UTC)