Template talk:WikiProject Redirect

{{WPRedirect}}

FYI Template:WPRedirect (edit | talk | history | links | watch | logs) has been nominated for deletion -- 65.94.171.126 (talk) 07:14, 7 June 2014 (UTC)

Suggestion from talk page of the project page

The following is borrowed from the approval discussion so that the "class=" parameter can be improved:

To keep it being used as intended, modify the accepted values for the class parameter from the defaults for WikiProject Banners. Redirect project obviously has no need to use regular article classes (stub, C, FA, etc), and these should be disabled. |class=project, |class=template and |class=category are the relevant classes for pages where the banner would be used, and I'm not sure any other classes should really be supported. |class=redirect is incredibly dangerous; this class could be disabled, but if a invalid class parameter is used anyway, presumably the pages would show up in an "unknown class" category. I'd suggest instead that using |class=redirect would display a prominent error/warning message on the banner, and would place pages in an administrative category that is marked as being supposed to have no pages. If there's a need to categorize templates that are redirects themselves (like {{R from typo}}), make a new |class=templateredirect (or |class=TR) for these. If, for some reason there really is a need to put the banner on a normal article space redirect, that could be achieved with another class parameter (perhaps |class=redirecttalk if the contents of the redirect's talk page are what makes it worth bannering). Bottom line, to prevent misuse of the banner, |class=redirect needs to be handled differently from other WikiProject banners.

— Plantdrew (talk) 15:23, 5 June 2014 (UTC)

I'll get to work on this soon. – Paine Ellsworth ^CLIMAX! 07:14, 17 June 2014 (UTC)

The challenge I keep knocking up against is that this BannerMeta template calls everything an "article". The project NAME, "Redirect", is used, so everything is (something) Redirect article. "Mid-importance Redirect article" – "NA-class Redirect article" – and so on. I've studied the masking in the Meta template, but everything still comes up "[...] Redirect article". All I can do at present is to subdue the QUALITY_SCALE altogether, so no matter what someone enters as a "class" or "importance" level, it will not appear in the banner. This way either myself or someone else can continue to test different ways to improve this particular parameter set. Also should note that, in addition to sorting the talk pages of mainspace articles and redirects to an admin category, there will be a notification box asking that the template be deleted from the talk page immediately:

That way editors may catch their blunder and, if not, those who monitor the admin cat will catch it and make the repair. Joys! – Paine Ellsworth ^CLIMAX! 08:18, 22 June 2014 (UTC)

Perhaps I can help with this? A simple namespace detection is probably sufficient for this template to determine the class. For example see Template:WikiProject Articles for creation (admin) which does something similar. You probably need NA-class as well, just to catch anything else. If you tell me exactly which classes you need, I will fix your template. — Martin (MSGJ · talk) 09:29, 13 January 2016 (UTC)

Ping User:Paine Ellsworth ... — Martin (MSGJ · talk) 12:32, 14 January 2016 (UTC)

To editors Martin and Plantdrew: by all means, Martin, any help you give is greatly appreciated. The approved classes would be those that are suggested above and on the project talk page as follows:

• class=project
• class=template
• class=category

The above are already added automatically, for example, as shown at WT:Double redirects (plural), Template talk:R unprintworthy and Category talk:All redirect templates. Also, as shown at WT:Double redirect (singular), the Redirect class can be overridden with the "class=(something else)" parameter, in this case, "class=project". If that overriding class is left out, then this WikiProject template would automatically apply the Redirect class to that talk page and its redirect.

• class=templateredirect

There are some instances, such as Template talk:R to related, when the Redirect class does apply. It's been suggested that instead, this WikiProject template should apply "class=templateredirect". Then the "redirect class" can be either subdued or used to introduce an error message, which has already been accomplished for mainspace redirect pages. Perhaps Plantdrew can explain why this "class=templateredirect" should be added and the "class=redirect" should be eliminated?

Thank you both for any help you can give! Happy New Year! Paine  12:14, 16 January 2016 (UTC)

Well, I'm not especially committed to a templateredirect class; I was just throwing out ideas at that point. There was significant concern that creating a project banner from WikiProject Redirect would lead to large numbers of article space redirects getting tagged for WikiProject Redirect. That hasn't happened, and to me doesn't seem likely to happen; the warning message the banner displays when used on article-space redirects seems to be sufficient. 21:20, 16 January 2016 (UTC)

Yes, and in addition to the fact that those mainspace talk pages to which this banner is Save page'd will populate CAT:WRONG, which I monitor almost daily.  Paine  22:46, 16 January 2016 (UTC)

I think the code at Template:WikiProject Redirect/class should suit your needs and there is no need to specify a class parameter as everything should be detected automatically. You did not mention MediaWiki-class above so I have not implemented that. It could be adjusted as necessary. Regards — Martin (MSGJ · talk) 09:33, 18 January 2016 (UTC)

Thank you, Martin, and I agree that there is usually no need to specify a class param due to its automated application, and in those few instances when editors might need to override the automated class with a different class, that appears to work well, also. I implemented the MediaWiki class in order to apply it on this page, while figuring that it might become more useful in the future, and to avoid creating an unnecessary Category:NA-Class Redirect articles. That brings me to the possible automation of a "class=module" parameter, or should these be classed alongside templates? (class=template) And "pages" would work better than "articles", but that would mean the need to rename the categories.  Paine  06:56, 20 January 2016 (UTC)

I've classified modules as Template-class, and everything else (including Mediawiki) is now lumped into Project. If you want to adjust this, just change Template:WikiProject Redirect/class. — Martin (MSGJ · talk) 12:43, 20 January 2016 (UTC)

Renamed talk page

It should be noted that when this page is moved into template space, then this associated talk page will also be moved to "Template talk:WikiProject Redirect". – Paine Ellsworth ^CLIMAX! 08:30, 22 June 2014 (UTC)

Assessment categories

Currently your assessment categories are of the form XX-class Redirect articles which doesn't seem quite right. Would you like to use "pages" instead of articles? And the "Redirect" should probably not be capitalised for consistency with other projects. — Martin (MSGJ · talk) 09:35, 18 January 2016 (UTC)

Unless there is some comment on this in the next 24 hours, I will rename the assessment categories to XX-class redirect pages. — Martin (MSGJ · talk) 11:09, 19 January 2016 (UTC)

To editor Martin: As I said above, "pages" would be better than "articles", and I was concerned that the categories would have to be renamed. If you want to do that, you will hear no objections from me.  Paine  07:00, 20 January 2016 (UTC)

All done. These are the 4 subcategories of Category:WikiProject Redirect pages. Pages will take a few days to find their way to the new category names. — Martin (MSGJ · talk) 12:43, 20 January 2016 (UTC)

Thank you very much, Martin! And module → template as well as MediaWiki → project works for me.  Paine  20:02, 22 January 2016 (UTC)

Class= parameter

To editor Martin: noticed that you converted this to Lua last month. Don't know if that has something to do with it, but the |class= parameter now shows an error in preview: Preview warning: Page using Template:WikiProject Redirect with unexpected parameter "class". Does this mean that all class parameters should be removed from all the templates? P.I. Ellsworth , ed. ^{put'er there} 17:32, 18 October 2023 (UTC)

Hi Paine, I need to explore what has happened here because all the assessments have been turned off — Martin (MSGJ · talk) 17:48, 18 October 2023 (UTC)

Okay, good fortune to you. The talk page on which I noticed this in preview was Template talk:R from adjective. Thank you very much for your help! P.I. Ellsworth , ed. ^{put'er there} 17:53, 18 October 2023 (UTC)

So |class= is definitely not needed, because the class is decided by the namespace only. But I can put it back in if the error messages are bothering you. — Martin (MSGJ · talk) 17:54, 18 October 2023 (UTC)

I'll go with anything you say, Martin. I can always remove the class parameter when I come across it. I'm okay with anything you decide. P.I. Ellsworth , ed. ^{put'er there} 17:59, 18 October 2023 (UTC)

I've added the class parameter back, even though it's not required — Martin (MSGJ · talk) 07:31, 19 October 2023 (UTC)

Yes, I noticed that the error message disappeared, thank you very much, Martin! P.I. Ellsworth , ed. ^{put'er there} 16:33, 19 October 2023 (UTC)

"Unassessed redirect pages"

There's been more than one instance of this template's incorrect use on mainspace talk pages autogenerating a nonexistent Category:Unassessed redirect pages that had to be cleaned up as a redlinked category at Special:WantedCategories — and I know that since the template isn't supposed to be used on mainspace talk pages, it can be resolved just by removing the template, but since templates aren't supposed to be able to generate redlinked categories, it shouldn't even exist as a problem for the redlinked category crew to even have to deal with.

If you want it as a tracking category for erroneous use of the template on mainspace talk pages, then feel free to create it as a maintenance tracking category — but if you don't want it, then could somebody please edit this template to prevent it from even being generated in the first place? Thanks. Bearcat (talk) 13:37, 4 November 2024 (UTC)