![]() | Template:Official website 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. |
This is the talk page for discussing improvements to the Official website template. |
|
Archives: 1, 2, 3, 4Auto-archiving period: 3 months ![]() |
![]() | This template was considered for deletion on 13 August 2009. The result of the discussion was "speedy keep". |
|
||||
This page has archives. Sections older than 92 days may be automatically archived by Lowercase sigmabot III when more than 4 sections are present. |
What's the correct way to mark a {{official website}} as a dead link? -- Mikeblas (talk) 16:35, 9 March 2021 (UTC)
{{webarchive}}
using the |title=
arg to give the same wording eg. {{webarchive |url=https://web.archive.org/web/20210309010101/https://example.com|date=2021-03-09|title=Official website}}
which produces:
|archive-url=
support. ~Kvng (talk) 14:04, 7 June 2022 (UTC)
|archive-url=
is a CS1|2 argument name. I don't think we should use that key name, unless it is a CS1|2 template, to avoid confusion about which arguments the template supports. -- GreenC 19:54, 28 March 2023 (UTC)
Is there any guidance that it is not appropriate to have this template in an infobox?Naraht (talk) 22:12, 8 February 2024 (UTC)
|website=
parameter should be for an official website only (e.g., {{Infobox person}}).http/https
portion). The documentation and examples often suggest the use of {{URL}}. {{Official URL}} can be a useful alternative. Note that in some cases, the infobox documentation specifically advises not to include the www.
portion of the url unless the website requires it (presumably to save space in space-constrained infoboxes). However, {{Official URL}} displays the full website name including the www.
portion if that is what is stored in wikidata or passed in as the first parameter.[https://about.me/ About Me]
used, especially when the official website url is very long. Others also use, incorrectly, the deprecated second parameter of {{URL}} to display alternative text instead of the url itself."Module:Official website," when used to create "Category:Official website different in Wikidata and Wikipedia," appears to assume that there is one and only one official website listed in Wikidata. However, this is not necessarily the case. For example, see FIFA Men's World Ranking which lists an official website, https://www.fifa.com/fifa-world-ranking/men, and the corresponding Wikidata page (FIFA World Rankings (Q180825)), which has 3 official pages listed, https://www.fifa.com/fifa-world-ranking/, https://www.fifa.com/fifa-world-ranking/women, and https://www.fifa.com/fifa-world-ranking/men. So, despite the Wikipedia page and the Wikidata page both listing an overlapping identical official page, the Wikipedia page is still flagged by the module to be a member of "Category:Official website different in Wikidata and Wikipedia," because the Wikidata page also lists two other official pages. This seems like an incorrect outcome. Is it possible for the module to be modified to check any official website included in the Wikidata listing? So long as Wikidata allows the inclusion of multiple official websites, this seems like a worthwhile change. Coining (talk) 02:08, 2 April 2024 (UTC)
laggard, Wikidata maintains a stable identity for its items. If you want to distinguish the Men’s world rankings from the general concept, you should create a new item for it; if you are shifting the subject of a Wikipedia article, you may want to link it to another item. (See also d:Talk:Q180825.) Lucas Werkmeister (talk) 18:07, 5 April 2024 (UTC)
We still don't seem to have proper handling of websites with multiple languages when getting data from Wikidata. Both:
are needed.
Previous discussions:
Is there any progress? or a workaround? Boud (talk) 16:04, 21 December 2024 (UTC)
There does appear to be a piece of code in Module:Official website to select the English language if available:
-- Finds whether a Wikidata property is qualified as being in English. local function isEnglish(prop) local ret = quickPcall(function () for i, lang in ipairs(prop.qualifiers.P407) do if lang.datavalue.value['numeric-id'] == 1860 then return true end end return false end) return ret == true end
but it doesn't seem to have an effect. This looks like a bug. Boud (talk) 16:09, 21 December 2024 (UTC)
I want someone to create an 'official blog' template using similar code as this. Wikidata has a property for it under official blog URL (P1581) and bare link versions are sometimes used, such as in the article Anna's Archive. Juwan (talk) 02:29, 11 April 2025 (UTC)