Category talk:CS1 errors: URL
Excluded namespaces
[edit]The note states "Pages in the User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories." Should other namespaces be excluded, such as Talk, Help talk, Module talk, Template talk? Thanks! GoingBatty (talk) 01:20, 3 May 2013 (UTC)
- You might want to take this question to Module talk:Citation/CS1/Archive 7#Error categories and user pages.
Request to expand
[edit]Could this category please be expanded to also capture URLs starting with "hhttp" (e.g. New Jersey Devils reference #77) and "hhttps" (e.g. Hiyasmin Neri reference #2)? If so, I would expand BattyBot's task to fix them. Thanks! GoingBatty (talk) 03:51, 21 February 2015 (UTC)
- An
insource:hhttp
search turns up 58 instances. Is that really enough of a problem for us to change Module:citation/CS1?
- —Trappist the monk (talk) 12:15, 21 February 2015 (UTC)
- @Trappist the monk: Having them included in the category would make them easier to find and fix quickly. I will go fix these manually now. I trust you have a better sense of the impact of making this change when you are implementing other changes to the module. Thanks! GoingBatty (talk) 19:12, 21 February 2015 (UTC)
- Right now, the tests are: (1) does the value assigned to
|url=
look like it might be a relative protocol uri? (2) are there zero or more characters that are not a forward slash preceding a colon? (^[^/]*:
). There are at least 80 permanent uri schemes plus some number more that are provisional, historic, or other. To properly identify uri schemes that aren't correct, Module:Citation/CS1 must know which are correct. This of course, is doable. The question is: should we. This backwater is probably not the place to discuss that possibility.
- Right now, the tests are: (1) does the value assigned to
Update, PRURL is now treated as error
[edit]Per the first two cites in this rev, it appears that protocol-relative URL now produces a CS1 error and places the article in this cat. Therefore it appears the comments on the Category page are incorrect, but I'm not confident enough to do a bold edit. Suggest changing:
The URL field is checked to ensure that it does not contain spaces. The URL may be protocol relative (begins with //). If there are no spaces and the URL is not protocol relative, then the scheme must comply with RFC 3986. Further validation is not performed.
To:
The URL field is checked to ensure that it does not contain spaces, and that the scheme complies with RFC 3986. Further validation is not performed.
@Trappist the monk: Pinging you since you appear to be the principal player here. ―Mandruss ☎ 23:48, 5 December 2015 (UTC)
And there's another mention of protocol-relative in the preceding paragraph that would need to change too. ―Mandruss ☎ 00:07, 6 December 2015 (UTC)
- Getting the url checking code right has proved to be more difficult that I thought it should be. There are other problems besides this one. I'll address this and the other problems at WT:CS1 in the coming days.
Why an error?
[edit]All articles with [1] are now tagged as having a URL error. Why? Clicking on the link brings up the study. --Lineagegeek (talk) 21:07, 2 January 2016 (UTC)
- The current live version of the url checking code doesn't like fully qualified domain names. That has been fixed in the sandbox. You can probably remove the dot after
http://www.afhra.af.mil
and get a correctly working link.
.cash error
[edit]See here Zcash. I have two errors even though these are correctly working links. [2] — TheJJJunk (say hello) 04:15, 8 November 2016 (UTC)
Common errors
[edit]After running my bot through this category, there are still over 4,000 articles with URL errors. Is there a way to generate a report with the most common errors, so we can see if we can fix them via bot and/or expanding AWB's general fixes? Thanks! GoingBatty (talk) 17:29, 10 January 2021 (UTC)
- And now there are zero articles -
magic???GoingBatty (talk) 03:34, 11 January 2021 (UTC)- Nope - apparently moved to Category:CS1 errors: URL. GoingBatty (talk) 03:36, 11 January 2021 (UTC)