This template does not require a rating on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||
|
Template:R from domain name is permanently
protected from editing because it is a
heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by
consensus, editors may use {{
edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's
documentation to add usage notes or
categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases. |
Note: Any changes made to this template's content needs to be checked as workable in the tables on the references which include it directly: |
I have proposed this merger because, although this template is somewhat newer than Template:R from dotcom, this one is used a lot more extensively and its name is bigger-encompassing, more clearly indicating that it can be applied to titles with .edu and .org suffixes. Thoughts? If there's no disagreement, I'll go ahead and perform the merger. Lenoxus " * " 21:33, 16 April 2008 (UTC)
I just saw the subcategories in
Category:Redirects_from_domain_names today. These categories are manually added to the redirects and not with a R from templates. I suggest that this template (R from domain name) just check the ending of the redirect title and then add a second category i.e.
Category:Redirects from .com domain names.
Christian75 (
talk)
14:31, 5 February 2019 (UTC)
It could be made with something like, {{#ifeq:{{#invoke:String|match|{{PAGENAME}}|%.com$|nomatch=nomatch}}|.com|[[Category:Redirects from .com domain names]]}}.
Christian75 (
talk)
14:59, 9 February 2019 (UTC)
I think it is probably easier to do this simply with a new parameter. This would also help with edge cases, such as where a redirect title doesn't actually contain the domain name (such as
steamcommunity or
target com). I added an optional |domain=
parameter to the
sandbox; if no one opposes I think it should be fine to just add it. ―
Jochem van Hees (
talk)
15:00, 16 June 2021 (UTC)
And then of course it should be recommended to use the new parameter in the documentation. Maybe there could even be a tracking category for transclusions that don't include the parameter or something, because in almost all cases the parameter should be used. ― Jochem van Hees ( talk) 16:24, 16 June 2021 (UTC)
I changed the text:
This is a redirect ... to an article about a website (or the entity to which the official website belongs) that is more often referred to by its short name or company name rather than its domain name
to:
This is a redirect ... to an article about an associated entity or website, which is more often referred to by its official name than by its domain name.
This seemed more useful, since there are way more articles about people and organizations that have websites than about websites themselves. — Sangdeboeuf ( talk) 20:39, 4 September 2020 (UTC)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Implement
the changes to the sandbox that improve the |domain=
parameter. You no longer have to precede the domain name with a dot, and the domain name will be displayed on the template. Otherwise the template will instruct you to add the domain parameter. I have
tested these changes and they appear to work. ―
Jochem van Hees (
talk)
11:56, 13 September 2021 (UTC)
|domain=.com
then it will categorise it under both
Category:Redirects from .com domain names and
Category:Redirects from domain names. Or should it only be the subcat? ―
Jochem van Hees (
talk)
14:34, 14 September 2021 (UTC)
I see Christian75, Glades12, and Jochem van Hees were discussing automatically filling the .com subcategory above. I agree and think we can probably go further. This template should be extracting the top-level domain from the title, checking to see if it matches a subcategory, and sorting it automatically if so. There will still be some edge cases that'll need doing manually, like the Target example above, but the vast majority can be automated, and that'll save us a lot of busywork. {{u| Sdkb}} talk 03:41, 18 November 2021 (UTC)
|domain=
parameter is preferred I think it could work. ―
Jochem van Hees (
talk)
10:29, 18 November 2021 (UTC)
|domain=
will always override any automatic detection. The only situation we need to be worried about is a page title that ends in one domain with a category but actually belongs in a different one, since those would be miscategorized until overridden. I can't think of any circumstance in which what could happen—can you? {{u|
Sdkb}}
talk
16:07, 18 November 2021 (UTC)
You are invited to join the discussion at Wikipedia:Bot requests § Redirects from organization/newspaper domain names. {{u| Sdkb}} talk 08:28, 12 October 2023 (UTC)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Add {{ lowercase title}}. Website domain names are always written in all lowercase. InfiniteNexus ( talk) 06:58, 5 May 2024 (UTC)