We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Requested by A smart kitten at https://en.wikipedia.org/wiki/Wikipedia_talk:Twinkle#Removal_of_rcat_tagging_menu_for_category_redirects
disable tag module for category redirect pages
Pages such as https://en.wikipedia.org/wiki/Category:Angus_and_Julia_Stone show the tag module for some reason. We should not place redirect tags on category redirects.
The text was updated successfully, but these errors were encountered:
tag: disable tagging of category redirects (wikimedia-gadgets#1947)
415b859
tag: disable tagging of category redirects (#1947) (#2007)
3425932
Noting for the record that https://en.wikipedia.org/wiki/Wikipedia:Redirect#Category_redirects says that on enwiki, for categories, we should always use {{Category redirect}} and not #REDIRECT.
Noting for the record that while I didn't notice this when I made the ticket, sometimes rcats are indeed placed in {{Category redirect}}s. Example:
{{Category redirect | Years of the 19th century in Ceylon | {{R from category navigation}} {{R from template-generated category}} }}
We may need to come back later and add this capability if it is common/useful. I think it is very uncommon though.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Requested by A smart kitten at https://en.wikipedia.org/wiki/Wikipedia_talk:Twinkle#Removal_of_rcat_tagging_menu_for_category_redirects
disable tag module for category redirect pages
Pages such as https://en.wikipedia.org/wiki/Category:Angus_and_Julia_Stone show the tag module for some reason. We should not place redirect tags on category redirects.
The text was updated successfully, but these errors were encountered: