Template talk:ArticleVersion

Having one template that covers both old and new articles is, I think, a mistake. (I didn't know it was the same at first.) When it comes time to change the latest to "old", it will require that every one be checked - and there is no way to keep track of that.

Instead, having one "old info" template, and one "current info" template would allow users/Admin to go out and change all the "current info" articles to "old", and then proceed from there. The serve diff functions, they should not be the same.--Albedo 20:23, 17 March 2010 (UTC)

You're absolutely right, of course. I'm not quite certain why I didn't think of splitting this into separate templates, but it clearly should be. There's also the matter of Emi's recent changes assuming the presence of a "DF2010" pseudonamespace which, at this moment, does not exist. --Quietust 23:19, 17 March 2010 (UTC)

Albedo, I'm getting the feeling that you don't understand how this template works. When it comes time to change the latest to "old" one line will have to be changed in this template's code, and then every single one will have changed to read "out of date". The entire premise of having one template that uses parser functions to determine what appears, is so that no one will ever have to go through every article to check the templates. You'll notice that 40d:Milk shows up as out of date, but that DF2010:Milk shows up as current. This is because the template is looking for what namespace the page it appears on is in, and it appears differently depending on what namespace it is.

Also, to Quietust, the 'fixes' you made to the template were actually to intentional errors. I wanted to avoid doing things that would have to be reversed later as much as possible, but still wanted to test. So to avoid having to ask Briess to temporarily add DF2010 as a namespace, I left the namespace check for current blank. As for the non-existent DF2010: I just wanted something to test with, I never meant to imply that the DF2010 namespace was the one people had agreed upon.

If you need me to explain more, I'd be happy to. I'm also lurking around on IRC (newnet as Emi). Emi 00:17, 18 March 2010 (UTC)

Why is this template not working? I never see links to the old 40d articles that still actually have content. It is very annoying. --Altaree 13:14, 2 April 2010 (UTC)

It's working fine for me. What page are you seeing this on? Remember, it only links to the 40d article if the 40d article exists with the exact same name. --Briess 13:16, 2 April 2010 (UTC)

whoops, I'm wrong. A new DF2010 page must be created with an av template to allow me to see the link back to the 40d article on the redirect. ick. --Altaree 13:18, 2 April 2010 (UTC)

Some notes...

First off, for some reason, on the legacy and current versions of the template, there's an extra line at the top which screws up the layout of the page a bit. I can't find where it's getting that from.

Secondly, I really don't think this template should throw the pages into a category. If it's going to be on every page, and it looks like it will, the categories will just become huge and useless. Categories are going to be tricky to work with now with the split, but this is certainly not the way to do it.

Finally, if this is going to be on every page, it needs to be as discrete as possible. I suggest scaling down the text, and making the colors more subtle.

Thoughts? --Mikaka 04:58, 3 April 2010 (UTC)

Previous versions were even less discrete, this was a compromise between discreteness and people being able to notice it and easily find different version of the articles.

As for the layout problem, could you link me to a page where this problem is occurring?

As for the categories, I'm not sure what I think about them. Emi [T] 05:01, 3 April 2010 (UTC)

Your recent edit fixed the layout. The template table now rests snugly against the top of the articles in question. Thanks. Perhaps we can turn up the discreteness once people become used to having to the new system. For now it works. --Mikaka 05:12, 3 April 2010 (UTC)

Font Size

Could you please increase the font size of the alternate version links? Particularly 40d? They are very small at the moment and I think they could be quite easily missed by a lot of the congregation users. Garanis 15:12, 8 April 2010 (UTC)

Formatting

Shouldn't this be using style sheets for its links and such? People seem to be having a lot of individual issues with it, but if the template were using CSS, they could fix it themselves. That is, they could do it without being lynched by people who liked it the way it was before they made their edits. ~ Midna 23:00, 6 May 2010 (UTC)

Mybrowserbar address when clicking versions

What is this api.mybrowserbar that keeps popping up when I click on different versions of pages? If I go to the 2010 subterranean trees article and click on "v0.31.08" it tries to redirect me to the api.mybrowserbar page which my antivirus software catches and calls.--208.81.12.34 18:44, 24 June 2010 (UTC)

I can't figure out which page you're talking about. Clicking on the versioning template at Category:DF2010:Subterranean_trees just gets the standard redlink page, and checking the HTML for that doesn't seem to show anything. I'd guess that your computer is infected with a virus in its browser. Run a full scan with your antivirus, and probably one or two others if you can. --DeMatt 20:09, 24 June 2010 (UTC)

Current/Obsolete Categories

Is it really necessary for this template to categorize pages in Category:Current and Category:Obsolete? As I see it, it would be far more useful to simply place them in categories matching their namespace name (as is already done for categories) so that we don't end up with one category that contains every single article from 3 old but very much distinct versions of Dwarf Fortress. --Quietust 17:47, 5 November 2012 (UTC)

That probably makes sense. --Briess 20:09, 5 November 2012 (UTC)

NR link

The NR text should act as a link, and it does on Template:av. However, on this page, it doesn't. Adding {{PAGENAME}} to the top of the page does display the page name as it should. Could this be related to spaces, by any chance? The only page I've found without a redirect that doesn't have spaces is DF:Versions (the av template is in the middle, as an example, but it does have a NR link that functions correctly). I don't see why spaces would be causing a problem – they usually work without problems – but does anyone know of a way to fix this? --Lethosor (talk) 23:41, 25 February 2013 (UTC)

This bug was caused by the inter-namespace link rewriting code--generic links to "foo" are automatically rewritten to "{{NAMESPACE}}:foo" when in one of the "versioned" namespaces (DF2012, v0.31, etc.). I have modified the template to explicitly force the NR link to point to mainspace as intended. --Loci 02:21, 26 February 2013 (UTC)

Thanks. It looks like all of the "Missing Redirect" articles now point to the correct article in the main namespace. --Lethosor (talk) 02:36, 26 February 2013 (UTC)

Auto create redirect does NOT work

Just stumbled upon a page with pink text in its template(this one). So I clicked it, assuming thats what youre supposed to do when you see it(I never saw pink text before :P ). It sent me to a page with preset text, and when I clicked preview it showed me that the comment caused the page to not be recognized as a redirect.

I would fix this, but after a look at the source code I decided that I dont know enough about this template to figure out where the source of the preset page is located and remove the comment.

The comment is redunant anyway, as the info box that is preloaded when creating the redirect already tells you that you can press the save page button.

(I decided that I shouldnt create the redirect, actually, because the page is a subpage. Still, this bug should be fixed.) Latias1290 (talk)

• Actually, I used that to auto-create the Dipscript redirect, and it worked just fine. When you actually save the page, the comment gets subst'ed into nothing and leaves a working redirect. --Quietust (talk) 17:20, 31 March 2014 (UTC)

I went ahead and removed the redundant text in the edit field. I'm not really sure if the "NR" link is necessary on subpages–are there any cases where redirects to subpages are needed? If there aren't, I'll go ahead and disable the link on subpages. —Lethosor (talk) 19:02, 31 March 2014 (UTC)

Even with the comment removed, it still displays as "1. REDIRECT cv:Quickstart guide/Stockpiles" until saved, due to {{subst:PAGENAME}} occurring in the link. Once it's saved, however, Mediawiki treats it as a redirect and automatically redirects to the original (DF2012) page, most likely because it didn't realize it was a redirect before saving and didn't set the "redirect=no" parameter normally set when editing a redirect. —Lethosor (talk) 19:07, 31 March 2014 (UTC)

This link has been removed entirely, since the AutoRedirect extension makes mainspace redirects unnecessary (Main:Quickstart_guide/Stockpiles redirects to DF2012:Quickstart_guide/Stockpiles automatically). —Lethosor (talk) 15:08, 7 June 2014 (UTC)

"Note that some content may still need to be updated."

I suggest removing "Note that some content may still need to be updated." from this template. We already have Template:migrated article and Template:migrated section; if those templates aren't present the reader should assume the content is accurate for v50. NiftyManiac (talk) 21:31, 3 January 2023 (UTC)

I added this because someone pointed out seemingly-conflicting language between this template saying an article is "current" and {{migrated article}} saying that it's not. I could have sworn that discussion was somewhere on Dwarf_Fortress_Wiki_talk:Versions, but I can't find it anymore. Anyway, I agree this language should be the first to go out of the various warnings. —Lethosor (talk) 21:45, 4 January 2023 (UTC)

It'll probably be a while until all 2k remaining migrated pages lose {{migrated article}}. Since the migrated article template is always first, why not make the version text conditional on its presence? Tried a couple of options; the last purple one is my favorite, we could cut down on the amount of warnings by just putting the migration text completely in the version template. If we went this route I'd probably pick yellow for the color of current-but-migrated.

Right now the Engraving article text doesn't start until halfway down my screen, so this would help. OddballJoe (talk) 19:59, 5 January 2023 (UTC)

It's an interesting idea, but I don't think we can necessarily guarantee that {{migrated article}} will always be before {{av}}, or paired with {{av}}, so I am hesitant to make {{migrated article}} invisible. I'm open to reverting the {{av}} language at this point, I suppose, since {{migrated article}} is so obvious. —Lethosor (talk) 18:57, 10 January 2023 (UTC)

Good point. Oooorrr... {{migrated article}} and {{av}} both include Template:version info, which displays the av, migration, or combined messages, and only draws itself once per page. Wait nvm that doesn't work at all. OddballJoe (talk) 19:41, 10 January 2023 (UTC)

v50 articles only show one previous version

Lethosor, did you deliberately make this template show only v50 and v0.47 versions on v50 pages, while all other pages show all versions? Wanted to double check before I went ahead and fixed this. OddballJoe (talk) 20:05, 4 January 2023 (UTC)

Yes, that was deliberate, I (and Emi) wanted to just show the most commonly-used versions on the current pages. —Lethosor (talk) 21:36, 4 January 2023 (UTC)

Fix for ifexist wanted links

I don't know if it's of any interest, but someone figured out a way to check for the presence of a page via page properties to avoid the creation of a wanted link. See Template:Linkless_exists at Avatar Wiki. Like the page says, it's a little more expensive and the result is cached (which can be fixed/updated by API purging the template with the recursive arguments).--PlNG (talk) 16:35, 5 February 2023 (UTC)