This section is pinned and will not be automatically archived. |
This script is a tweaked copy of User:Ucucha/HarvErrors.js ( compare the two).
Differences:
CITEREF
anchor IDs, does not emit warning messagesCITEREF
anchor IDs:
==Further reading==
==External links==
@ Trappist the monk: Having the red errors messages is usually fine on talk pages (although of limited value), but the brown warnings are rather pointless there. No idea if the red errors should be disabled on (all) talk pages, but the brown warnings definitely should. Headbomb { t · c · p · b} 14:24, 7 July 2020 (UTC)
@ Trappist the monk: False positive with {{ Cite DCB}} e.g. Alexander_Mackenzie_(politician)#cite_note-FOOTNOTEForster1990-2 – Finnusertop ( talk ⋅ contribs) 21:41, 15 July 2020 (UTC)
@
Trappist the monk, @
Headbomb: Per
mw:ResourceLoader/Migration guide (users)#importScript, importScript
is deprecated since MediaWiki 1.29 and does not work on mobile view. The install instruction should be changed such that it uses mw.loader.load
instead.
ネイ (
talk) 13:49, 2 October 2021 (UTC)
Not sure anything should be done about this, but have a look at the at note 1 at
Transgender#Notes. The individual bullets are not cited in the body, because they are part of the
WP:CITEBUNDLE listed in the <ref group="note">
in section
§ Transgender. As part of the bundle, they're unaddressable as individual citations and thus no need to flag them. On the other hand, if it would require a lot of squirrelly parsing and/or explode the test cases, then it may be better just to ignore the false positives in this case, if there's a risk of making the script more fragile in other cases. Thanks for this script, I just added it, and it looks really useful.
Mathglot (
talk) 22:37, 28 June 2023 (UTC)
|ref=none
in the cs1|2 templates.As part of the bundle, they're unaddressable as individual citationsWhat does that mean? Certainly they are 'addressable':
[[Transgender#CITEREFOliven1974]]
→
Transgender#CITEREFOliven1974|ref=none
will make them unaddressable
{{
sfn}}
or {{
harvnb}}
but that doesn't mean that they can't be. Also, for those references, linking to archived snapshots of the google books landing page seems to me to be sort of pointless...I'd like to propose that one of the error messages be downgraded to "warning", because failing to fix it does not violate any Wikipedia policy or hurt Verifiability or the article in any way, or at least, no more seriously than a layout violation. Currently, "Harv error: linked from 'X' " is listed as an error, but really, imho it should only be a warning. Here's why:
Of all the four messages generated, only #1 ("link from 'X' doesn't point to any citation") and #2 ("'X' has multiple targets") if left unrepaired, impact the verifiability of the article. WP:Verifiability is policy, and if left unchanged, other editors would be justified by policy in removing article content preceding those error messages based on lack of sourcing. WP:BURDEN says, "Any material lacking an inline citation to a reliable source that directly supports[ 2 the material may be removed and should not be restored without an inline citation to a reliable source."
However, this is not the case for the other two messages. The message "Harv error: linked from 'X'" represents a citation with an incoming link from some sfn being located under the wrong section header, perhaps under "Further reading" where it should be under "Bibliography". This isn't a serious error, the article bearing this message still supports verifiability, violates no other policy, and would not justify any content removal by another editor, even if it is never fixed. At worst, this is similar to a guideline violation of MOS:LAYOUT where stuff is not located in the right place, such as an external link being placed in the "See also" section. It's kind of the half-sister of the unused citation warning, which is really just another case of something being in the wrong place, only this time, it's the other way round: there's a full citation which isn't the target of a short footnote which was placed in section "Bibliography", whereas it should have been in "Further reading". Here once again, even if this is never fixed, it's at worst a LAYOUT violation, but Verifiability is not impacted. Both "wrong section" messages should be warnings, not just the one that is now. Mathglot ( talk) 00:26, 20 August 2023 (UTC)
Courtesy link: Wikipedia:User scripts/Requests § external css for a user script?
As far as I can tell, the defined color style of the error and warning messages in the script cannot be overridden because of the way it's coded in the script with the color-setting span "style" attribute coming last. In particular, the "ttm_harv_err" elements will always have the DarkOrange color, regardless of what the user might do in their common.css. Example (line 27; sample citeref substituted in for clarity):
<span class="ttm_harv_err" style="color:DarkOrange">Harv error: link from "CITEREFSmith2023" doesn't point to any citation.</span>
You can override other attributes, for example, adding this to common.css will shade the message with background color:
.ttm_harv_err {color:black; background-color:cornsilk}
but the font remains dark orange (not black) because of the order of priority of css style, with the inline css in the "style" attribute highest priority. I'm unaware of any method of overriding inline style defined right in the <span> tag. But I think you can still get the default dark orange font that you want, and have overridable color via a user's common.css by using two classes, one of which you define, and the other which you don't, and put after the predefined one, something like this:
<span class="ttm_harv_err_default ttm_harv_err">Harv error: link from "CITEREFSmith2023" doesn't point to any citation.</span>
and include a <style> block on the page where you'd define your defaults:
<style>.ttm_harv_err_default { color:DarkOrange }</style>
# you can include the other defaults in here at the same timeThe problem is, I'm better at css than I am at javascript, and I don't know if it's actually possible to implement this proposal using scripting. And secondly, in the template world, there's something called TemplateStyles.css, which fits somewhere into priority sequence, and maybe there's something analogous like ScriptingStyles.js, but if there is, I don't know about it. But I know who would: Izno; if you don't mind, could you look over my analysis to see if it makes sense, and if the proposed solution is viable, or if there's perhaps a better way to do it? Thanks, Mathglot ( talk) 20:48, 20 August 2023 (UTC)
!important
(without having to deal with too many of the reasons why you shouldn't generally). In this case, .ttm_harv_err {color:black !important; background-color:cornsilk}
would suffice to make the color black.
Izno (
talk) 21:24, 20 August 2023 (UTC)
!important
trick seems really useful, and I'll study up a bit to see what any concomitant "dont-use-it" issues might be. Thanks again,
Mathglot (
talk) 21:32, 20 August 2023 (UTC)Trappist, does this make sense, as far as removing the "style" attributes inline, and default the color via the class at the outset, if possible? That seems more straightforward for users, so that we don't force them to override via !important
.
Mathglot (
talk) 22:16, 20 August 2023 (UTC)
</head>
tag, and place the default class definition for .ttm_harv_err_default
(and the other ones) inside that block, and not on some other page.
Mathglot (
talk) 23:48, 20 August 2023 (UTC)If I understand correctly from the discussion at Wikipedia:User scripts/Requests#external css for a user script?, this issue has now been resolved, which is great news, and makes it possible to fill out section § Style customization and provide guidance to users who wish to customize the colors and other style attributes of the error and warning messages, so I've updated that section. It's been a real education here, and at that discussion, and I wanted to thank you for your contributions in both, your efforts to resolve this, and indeed for your maintenance and improvement of this highly useful script that I feel is getting justifiably adopted more and more. Thanks again. Mathglot ( talk) 05:20, 22 August 2023 (UTC)
The ==Publications== section appears to be used for listing works by authors, such as in these articles:
I think replacing line 49 as follows should do it:
− | var sections = [further_reading, | + | var publications =
content.find('#Publications').parent().nextUntil('h2').find('.citation').get(); // get all cites inside a Publications section
var sections = [further_reading, external_links, publications]; // make an array of links in these sections |
Thanks, Mathglot ( talk) 03:36, 5 October 2023 (UTC)
{{
harvnb|Knuth|1997}}
above
Donald Knuth § Publications. When I preview the article, I see Harv error: linked from CITEREFKnuth1997 and Harv error: duplicate target for CITEREFKnuth1997 messages for the first two templates under The Art of Computer Programming. These are, I think, the results to be expected.I am getting ttm_harv_err ("no link pointing to...") when wrapping a section of a page containing a cite_book and two citec's with template Reflib, even with {{ sfn whitelist}} in effect. To reproduce, place the following code on Special:ExpandTemplates or other test page:
{{reflib|lib=Asea|Catsambis-2011}}
{{sfn whitelist|CITEREFCarlson2011|CITEREFDelgado2011}}
This wraps a section containing a {{ cite book}} template, and two {{ citec}} templates linked to it. Even with the follow-up sfn whitelist, two ttm_harv_err's are emitted anyway.
Reflib is working to spec, but if you suspect something fishy with it, or just want to eliminate one extra possible source of error, you can generate the identical output without Reflib, using selective transclusion, this way:
{{#section-h:Template:Reflib/Ancient seafaring|Catsambis-2011}}
{{sfn whitelist|CITEREFCarlson2011|CITEREFDelgado2011}}
I poked around a bit in the code, but not sure what's going on. One thing I noticed: if you look at the ExpandTemplates output, whereas the main, cite_book template generates a <cite id="CITEREFCatsambisFordHamilton2011"...>
, the two citec templates do not—they generate a <span id=...>
instead, so I wonder if that's a clue.
ExpandTemplates output
|
---|
Generates the following result html in ExpandTemplates (extra line breaks added, to make code-reading easier): *<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles> <cite id="CITEREFCatsambisFordHamilton2011" class="citation book cs1">Catsambis, Alexis; Ford, Ben; Hamilton, Donny L., eds. (2011). ''The Oxford Handbook of Maritime Archaeology''. OUP. [[ISBN (identifier)|ISBN]] [[Special:BookSources/978-0-19-537517-6|<bdi>978-0-19-537517-6</bdi>]]. [[OCLC (identifier)|OCLC]] [https://www.worldcat.org/oclc/639940479 639940479].</cite> <span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=The+Oxford+Handbook+of+Maritime+Archaeology&rft.pub=OUP&rft.date=2011&rft_id=info%3Aoclcnum%2F639940479&rft.isbn=978-0-19-537517-6&rfr_id=info%3Asid%2Fen.wikipedia.org%3AShips+of+ancient+Rome" class="Z3988"></span> * <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles><span id="CITEREFCarlson2011" class="citation">Carlson, Deborah N. "[https://books.google.com/books?id=GOESDAAAQBAJ&pg=PA379 17. The Seafarers and Shipwrecks of Ancient Greece and Rome]". In [[#CITEREFCatsambisFordHamilton2011|Catsambis, Ford & Hamilton (2011)]], pp. 379–405.</span> * <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles><span id="CITEREFDelgado2011" class="citation">Delgado, James P. "Ships on Land". In [[#CITEREFCatsambisFordHamilton2011|Catsambis, Ford & Hamilton (2011)]], pp. 182–191.</span><br /> |
If you want to see the real-world occurrence that sparked this stripped down example, see Ships of ancient Rome#Works cited. Thanks, Mathglot ( talk) 06:52, 23 October 2023 (UTC)
{{
sfn whitelist}}
is for
Module:Footnotes-generated errors; it has no meaning to HarvErrors.js. HarvErrors.js will never recognize {{sfn whitelist}}
because that template does not create output that is visible in the article's html (where HarvErrors.js operates).{{
harvc}}
templates should be near the cs1|2 template (
Template:Harvc § Basic example illustrates my preferred style). Not used, hide or remove.I'm seeing unexpected "no-links" warnings at Collaborationism in France during the Second World War in section "#Reviews", which isn't one of the sections I thought it emitted warnings for. Mathglot ( talk) 11:39, 22 November 2023 (UTC)
I often use Template:Multiref2 to bundle sources. I have noticed that some of the bundled citations incorrectly display Harv warnings. I was able to narrow it down.
If the page uses Sfn (or harv) citations anywhere on the page, then a multiref-bundled cite-web citation with a name parameter (|author= or |last=) will incorrectly display the error. The harv warning is NOT displayed for bundled citations that do NOT use names. The warning doesn't display if I unbundle the citations (ref them separately instead of putting them in a multiref container). And the harv warning is NOT displayed if Sfn or Harv are never once used on the page.
I made a sample page to show the behavior: User:Grorp/sandbox4
It is written like a bug report, with instructions for an interaction. You can edit the page and remove the one instance using Sfn and you'll see the anomaly disappear.
It doesn't make sense that the same citation which doesn't generate a warning, does show a warning if bundled into multiref or multiref2. ▶ I am Grorp ◀ 01:04, 23 January 2024 (UTC)
CITEREF
id attributes for each citation's enclosing <cite>...</cite>
tag only when there is an author, contributor, or editor name.{{
sfn}}
or {{harv}}
-family templates in a page, HarvErrors does not check for errors and so does not emit error and warning messages.{{sfn}}
or {{harv}}
-family templates, HarvErrors emits the no-link-pointing-to-this-citation warning message when a cs1|2 citation has a CITEREF
id and when the citation is not inside its own <ref>...</ref>
tags or is not in §Further reading, §External links, or §Publications sections.{{
multiref2}}
have author names (CITEREF
ids) but are not wrapped inside their own <ref>...</ref>
tags (and are outside of any §Further reading, §External links, and §Publications sections).|ref=none
to the two cs1|2 templates with author names.This section is pinned and will not be automatically archived. |
This script is a tweaked copy of User:Ucucha/HarvErrors.js ( compare the two).
Differences:
CITEREF
anchor IDs, does not emit warning messagesCITEREF
anchor IDs:
==Further reading==
==External links==
@ Trappist the monk: Having the red errors messages is usually fine on talk pages (although of limited value), but the brown warnings are rather pointless there. No idea if the red errors should be disabled on (all) talk pages, but the brown warnings definitely should. Headbomb { t · c · p · b} 14:24, 7 July 2020 (UTC)
@ Trappist the monk: False positive with {{ Cite DCB}} e.g. Alexander_Mackenzie_(politician)#cite_note-FOOTNOTEForster1990-2 – Finnusertop ( talk ⋅ contribs) 21:41, 15 July 2020 (UTC)
@
Trappist the monk, @
Headbomb: Per
mw:ResourceLoader/Migration guide (users)#importScript, importScript
is deprecated since MediaWiki 1.29 and does not work on mobile view. The install instruction should be changed such that it uses mw.loader.load
instead.
ネイ (
talk) 13:49, 2 October 2021 (UTC)
Not sure anything should be done about this, but have a look at the at note 1 at
Transgender#Notes. The individual bullets are not cited in the body, because they are part of the
WP:CITEBUNDLE listed in the <ref group="note">
in section
§ Transgender. As part of the bundle, they're unaddressable as individual citations and thus no need to flag them. On the other hand, if it would require a lot of squirrelly parsing and/or explode the test cases, then it may be better just to ignore the false positives in this case, if there's a risk of making the script more fragile in other cases. Thanks for this script, I just added it, and it looks really useful.
Mathglot (
talk) 22:37, 28 June 2023 (UTC)
|ref=none
in the cs1|2 templates.As part of the bundle, they're unaddressable as individual citationsWhat does that mean? Certainly they are 'addressable':
[[Transgender#CITEREFOliven1974]]
→
Transgender#CITEREFOliven1974|ref=none
will make them unaddressable
{{
sfn}}
or {{
harvnb}}
but that doesn't mean that they can't be. Also, for those references, linking to archived snapshots of the google books landing page seems to me to be sort of pointless...I'd like to propose that one of the error messages be downgraded to "warning", because failing to fix it does not violate any Wikipedia policy or hurt Verifiability or the article in any way, or at least, no more seriously than a layout violation. Currently, "Harv error: linked from 'X' " is listed as an error, but really, imho it should only be a warning. Here's why:
Of all the four messages generated, only #1 ("link from 'X' doesn't point to any citation") and #2 ("'X' has multiple targets") if left unrepaired, impact the verifiability of the article. WP:Verifiability is policy, and if left unchanged, other editors would be justified by policy in removing article content preceding those error messages based on lack of sourcing. WP:BURDEN says, "Any material lacking an inline citation to a reliable source that directly supports[ 2 the material may be removed and should not be restored without an inline citation to a reliable source."
However, this is not the case for the other two messages. The message "Harv error: linked from 'X'" represents a citation with an incoming link from some sfn being located under the wrong section header, perhaps under "Further reading" where it should be under "Bibliography". This isn't a serious error, the article bearing this message still supports verifiability, violates no other policy, and would not justify any content removal by another editor, even if it is never fixed. At worst, this is similar to a guideline violation of MOS:LAYOUT where stuff is not located in the right place, such as an external link being placed in the "See also" section. It's kind of the half-sister of the unused citation warning, which is really just another case of something being in the wrong place, only this time, it's the other way round: there's a full citation which isn't the target of a short footnote which was placed in section "Bibliography", whereas it should have been in "Further reading". Here once again, even if this is never fixed, it's at worst a LAYOUT violation, but Verifiability is not impacted. Both "wrong section" messages should be warnings, not just the one that is now. Mathglot ( talk) 00:26, 20 August 2023 (UTC)
Courtesy link: Wikipedia:User scripts/Requests § external css for a user script?
As far as I can tell, the defined color style of the error and warning messages in the script cannot be overridden because of the way it's coded in the script with the color-setting span "style" attribute coming last. In particular, the "ttm_harv_err" elements will always have the DarkOrange color, regardless of what the user might do in their common.css. Example (line 27; sample citeref substituted in for clarity):
<span class="ttm_harv_err" style="color:DarkOrange">Harv error: link from "CITEREFSmith2023" doesn't point to any citation.</span>
You can override other attributes, for example, adding this to common.css will shade the message with background color:
.ttm_harv_err {color:black; background-color:cornsilk}
but the font remains dark orange (not black) because of the order of priority of css style, with the inline css in the "style" attribute highest priority. I'm unaware of any method of overriding inline style defined right in the <span> tag. But I think you can still get the default dark orange font that you want, and have overridable color via a user's common.css by using two classes, one of which you define, and the other which you don't, and put after the predefined one, something like this:
<span class="ttm_harv_err_default ttm_harv_err">Harv error: link from "CITEREFSmith2023" doesn't point to any citation.</span>
and include a <style> block on the page where you'd define your defaults:
<style>.ttm_harv_err_default { color:DarkOrange }</style>
# you can include the other defaults in here at the same timeThe problem is, I'm better at css than I am at javascript, and I don't know if it's actually possible to implement this proposal using scripting. And secondly, in the template world, there's something called TemplateStyles.css, which fits somewhere into priority sequence, and maybe there's something analogous like ScriptingStyles.js, but if there is, I don't know about it. But I know who would: Izno; if you don't mind, could you look over my analysis to see if it makes sense, and if the proposed solution is viable, or if there's perhaps a better way to do it? Thanks, Mathglot ( talk) 20:48, 20 August 2023 (UTC)
!important
(without having to deal with too many of the reasons why you shouldn't generally). In this case, .ttm_harv_err {color:black !important; background-color:cornsilk}
would suffice to make the color black.
Izno (
talk) 21:24, 20 August 2023 (UTC)
!important
trick seems really useful, and I'll study up a bit to see what any concomitant "dont-use-it" issues might be. Thanks again,
Mathglot (
talk) 21:32, 20 August 2023 (UTC)Trappist, does this make sense, as far as removing the "style" attributes inline, and default the color via the class at the outset, if possible? That seems more straightforward for users, so that we don't force them to override via !important
.
Mathglot (
talk) 22:16, 20 August 2023 (UTC)
</head>
tag, and place the default class definition for .ttm_harv_err_default
(and the other ones) inside that block, and not on some other page.
Mathglot (
talk) 23:48, 20 August 2023 (UTC)If I understand correctly from the discussion at Wikipedia:User scripts/Requests#external css for a user script?, this issue has now been resolved, which is great news, and makes it possible to fill out section § Style customization and provide guidance to users who wish to customize the colors and other style attributes of the error and warning messages, so I've updated that section. It's been a real education here, and at that discussion, and I wanted to thank you for your contributions in both, your efforts to resolve this, and indeed for your maintenance and improvement of this highly useful script that I feel is getting justifiably adopted more and more. Thanks again. Mathglot ( talk) 05:20, 22 August 2023 (UTC)
The ==Publications== section appears to be used for listing works by authors, such as in these articles:
I think replacing line 49 as follows should do it:
− | var sections = [further_reading, | + | var publications =
content.find('#Publications').parent().nextUntil('h2').find('.citation').get(); // get all cites inside a Publications section
var sections = [further_reading, external_links, publications]; // make an array of links in these sections |
Thanks, Mathglot ( talk) 03:36, 5 October 2023 (UTC)
{{
harvnb|Knuth|1997}}
above
Donald Knuth § Publications. When I preview the article, I see Harv error: linked from CITEREFKnuth1997 and Harv error: duplicate target for CITEREFKnuth1997 messages for the first two templates under The Art of Computer Programming. These are, I think, the results to be expected.I am getting ttm_harv_err ("no link pointing to...") when wrapping a section of a page containing a cite_book and two citec's with template Reflib, even with {{ sfn whitelist}} in effect. To reproduce, place the following code on Special:ExpandTemplates or other test page:
{{reflib|lib=Asea|Catsambis-2011}}
{{sfn whitelist|CITEREFCarlson2011|CITEREFDelgado2011}}
This wraps a section containing a {{ cite book}} template, and two {{ citec}} templates linked to it. Even with the follow-up sfn whitelist, two ttm_harv_err's are emitted anyway.
Reflib is working to spec, but if you suspect something fishy with it, or just want to eliminate one extra possible source of error, you can generate the identical output without Reflib, using selective transclusion, this way:
{{#section-h:Template:Reflib/Ancient seafaring|Catsambis-2011}}
{{sfn whitelist|CITEREFCarlson2011|CITEREFDelgado2011}}
I poked around a bit in the code, but not sure what's going on. One thing I noticed: if you look at the ExpandTemplates output, whereas the main, cite_book template generates a <cite id="CITEREFCatsambisFordHamilton2011"...>
, the two citec templates do not—they generate a <span id=...>
instead, so I wonder if that's a clue.
ExpandTemplates output
|
---|
Generates the following result html in ExpandTemplates (extra line breaks added, to make code-reading easier): *<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles> <cite id="CITEREFCatsambisFordHamilton2011" class="citation book cs1">Catsambis, Alexis; Ford, Ben; Hamilton, Donny L., eds. (2011). ''The Oxford Handbook of Maritime Archaeology''. OUP. [[ISBN (identifier)|ISBN]] [[Special:BookSources/978-0-19-537517-6|<bdi>978-0-19-537517-6</bdi>]]. [[OCLC (identifier)|OCLC]] [https://www.worldcat.org/oclc/639940479 639940479].</cite> <span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=The+Oxford+Handbook+of+Maritime+Archaeology&rft.pub=OUP&rft.date=2011&rft_id=info%3Aoclcnum%2F639940479&rft.isbn=978-0-19-537517-6&rfr_id=info%3Asid%2Fen.wikipedia.org%3AShips+of+ancient+Rome" class="Z3988"></span> * <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles><span id="CITEREFCarlson2011" class="citation">Carlson, Deborah N. "[https://books.google.com/books?id=GOESDAAAQBAJ&pg=PA379 17. The Seafarers and Shipwrecks of Ancient Greece and Rome]". In [[#CITEREFCatsambisFordHamilton2011|Catsambis, Ford & Hamilton (2011)]], pp. 379–405.</span> * <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles><span id="CITEREFDelgado2011" class="citation">Delgado, James P. "Ships on Land". In [[#CITEREFCatsambisFordHamilton2011|Catsambis, Ford & Hamilton (2011)]], pp. 182–191.</span><br /> |
If you want to see the real-world occurrence that sparked this stripped down example, see Ships of ancient Rome#Works cited. Thanks, Mathglot ( talk) 06:52, 23 October 2023 (UTC)
{{
sfn whitelist}}
is for
Module:Footnotes-generated errors; it has no meaning to HarvErrors.js. HarvErrors.js will never recognize {{sfn whitelist}}
because that template does not create output that is visible in the article's html (where HarvErrors.js operates).{{
harvc}}
templates should be near the cs1|2 template (
Template:Harvc § Basic example illustrates my preferred style). Not used, hide or remove.I'm seeing unexpected "no-links" warnings at Collaborationism in France during the Second World War in section "#Reviews", which isn't one of the sections I thought it emitted warnings for. Mathglot ( talk) 11:39, 22 November 2023 (UTC)
I often use Template:Multiref2 to bundle sources. I have noticed that some of the bundled citations incorrectly display Harv warnings. I was able to narrow it down.
If the page uses Sfn (or harv) citations anywhere on the page, then a multiref-bundled cite-web citation with a name parameter (|author= or |last=) will incorrectly display the error. The harv warning is NOT displayed for bundled citations that do NOT use names. The warning doesn't display if I unbundle the citations (ref them separately instead of putting them in a multiref container). And the harv warning is NOT displayed if Sfn or Harv are never once used on the page.
I made a sample page to show the behavior: User:Grorp/sandbox4
It is written like a bug report, with instructions for an interaction. You can edit the page and remove the one instance using Sfn and you'll see the anomaly disappear.
It doesn't make sense that the same citation which doesn't generate a warning, does show a warning if bundled into multiref or multiref2. ▶ I am Grorp ◀ 01:04, 23 January 2024 (UTC)
CITEREF
id attributes for each citation's enclosing <cite>...</cite>
tag only when there is an author, contributor, or editor name.{{
sfn}}
or {{harv}}
-family templates in a page, HarvErrors does not check for errors and so does not emit error and warning messages.{{sfn}}
or {{harv}}
-family templates, HarvErrors emits the no-link-pointing-to-this-citation warning message when a cs1|2 citation has a CITEREF
id and when the citation is not inside its own <ref>...</ref>
tags or is not in §Further reading, §External links, or §Publications sections.{{
multiref2}}
have author names (CITEREF
ids) but are not wrapped inside their own <ref>...</ref>
tags (and are outside of any §Further reading, §External links, and §Publications sections).|ref=none
to the two cs1|2 templates with author names.