Operator: BrownHairedGirl ( talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 19:49, Saturday, October 26, 2019 ( UTC)
Function overview: When a portal has been deleted at MFD, remove or replace links to it which are generated by one of 4 templates: {{ Portal}}, {{ Portal bar}}, {{ Portal-inline}}, {{ Subject bar}}
Use the next-most specific portal if available, otherwise remove the link(s). In most cases I have flagged this at the MFD.
Automatic, Supervised, or Manual: Automatic, but monitored.
Programming language(s): AWB
Source code available: See AWB settings files linked below
Links to relevant discussions (where appropriate): User talk:BrownHairedGirl#Your_AWB_edits, where I was encouraged by User:TheSandDoctor to use a bot for this task
Edit period(s): Whenever a portal is deleted. There may be one or two per day, or none for a week, or five on one day.
Estimated number of pages affected: Anywhere between 1 and 15,000 per deleted portal
Namespace(s): Article, Category, Draft
Exclusion compliant (Yes/No): Can't see how to do it in AWB, but will do if possible
Function details:
I use a separate AWB settings file for each portal. For each run I copy the most recent settings file of that type (single replace/double replace/remove), save it under a new name. I then modify the edit summary and the regexes in the "Find and replace: advanced settings" to use the relevant portal names, and test it on a few sample pages.
Core tasks:
Tidyup tasks, all flagged as minor so that they are not implemented unless a portal link is replaced:
Genfixes:
</br>
, < br>
, or </ br>
– to <br />
as you encounter them, though preferably as a part of a more substantive edit."Note that replacing one portal link with two links breaks {{
Portal-inline}}, which accepts only one portal as parameter. It would be simple to replace {{
Portal-inline|Foobar}}
with {{
Portal-inline|Foo}}
{{
Portal-inline|FoobarBar}}
… but the template is used in a variety of different contents with preceding markups, so my experiments with regex replacement got v complex and still didn't cover all cases. So my current strategy is to let AWB leave them with the multiple parameters, and the manually clean them up. I modified
[1]
Module:Portal-inline to track such cases in
Category:Portal-inline template with more than one portal parameter, so they are easily and reliably detected. There are usually very few such cases, even after a long run, and they are easily fixed.
I have already used this setup successfully on over 100,000 pages. -- BrownHairedGirl (talk) • ( contribs) 19:49, 26 October 2019 (UTC) reply
Approved for trial. Please provide a link to the relevant contributions and/or diffs when the trial is complete. a full run for 1 deleted portal. Pick one that isn't spammed on 13 billion articles (aim for <100 pages if possible). Headbomb { t · c · p · b} 22:05, 26 October 2019 (UTC) reply
<br>
to <br />
, as in
here. Or useless <br/>
to <br />
ones like
[2]. That seems unnecessary, and isn't part of default genfixes for a reason.
Headbomb {
t ·
c ·
p ·
b}
17:45, 1 November 2019 (UTC)
reply
better avoided. I guess if I read the whole thing more closely maybe the "recommended fix" of the previous para doesn't apply to those valid forms. As above, it still strikes me as an easily-done change which muchly helps those who use syntax highlighters, and I don't see a downside. But again, if you want me to turn it off, I will do, though sadly. -- BrownHairedGirl (talk) • ( contribs) 22:58, 1 November 2019 (UTC) reply
Approved. without the <br>→<br/> thing. If there's a wider discussion in favour of those fixes, file another BRFA for those and I'll speedily approve. Headbomb { t · c · p · b} 23:45, 1 November 2019 (UTC) reply
Revoked. See Special:Diff/937425282. Primefac ( talk) 23:26, 24 January 2020 (UTC) reply
Operator: BrownHairedGirl ( talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 19:49, Saturday, October 26, 2019 ( UTC)
Function overview: When a portal has been deleted at MFD, remove or replace links to it which are generated by one of 4 templates: {{ Portal}}, {{ Portal bar}}, {{ Portal-inline}}, {{ Subject bar}}
Use the next-most specific portal if available, otherwise remove the link(s). In most cases I have flagged this at the MFD.
Automatic, Supervised, or Manual: Automatic, but monitored.
Programming language(s): AWB
Source code available: See AWB settings files linked below
Links to relevant discussions (where appropriate): User talk:BrownHairedGirl#Your_AWB_edits, where I was encouraged by User:TheSandDoctor to use a bot for this task
Edit period(s): Whenever a portal is deleted. There may be one or two per day, or none for a week, or five on one day.
Estimated number of pages affected: Anywhere between 1 and 15,000 per deleted portal
Namespace(s): Article, Category, Draft
Exclusion compliant (Yes/No): Can't see how to do it in AWB, but will do if possible
Function details:
I use a separate AWB settings file for each portal. For each run I copy the most recent settings file of that type (single replace/double replace/remove), save it under a new name. I then modify the edit summary and the regexes in the "Find and replace: advanced settings" to use the relevant portal names, and test it on a few sample pages.
Core tasks:
Tidyup tasks, all flagged as minor so that they are not implemented unless a portal link is replaced:
Genfixes:
</br>
, < br>
, or </ br>
– to <br />
as you encounter them, though preferably as a part of a more substantive edit."Note that replacing one portal link with two links breaks {{
Portal-inline}}, which accepts only one portal as parameter. It would be simple to replace {{
Portal-inline|Foobar}}
with {{
Portal-inline|Foo}}
{{
Portal-inline|FoobarBar}}
… but the template is used in a variety of different contents with preceding markups, so my experiments with regex replacement got v complex and still didn't cover all cases. So my current strategy is to let AWB leave them with the multiple parameters, and the manually clean them up. I modified
[1]
Module:Portal-inline to track such cases in
Category:Portal-inline template with more than one portal parameter, so they are easily and reliably detected. There are usually very few such cases, even after a long run, and they are easily fixed.
I have already used this setup successfully on over 100,000 pages. -- BrownHairedGirl (talk) • ( contribs) 19:49, 26 October 2019 (UTC) reply
Approved for trial. Please provide a link to the relevant contributions and/or diffs when the trial is complete. a full run for 1 deleted portal. Pick one that isn't spammed on 13 billion articles (aim for <100 pages if possible). Headbomb { t · c · p · b} 22:05, 26 October 2019 (UTC) reply
<br>
to <br />
, as in
here. Or useless <br/>
to <br />
ones like
[2]. That seems unnecessary, and isn't part of default genfixes for a reason.
Headbomb {
t ·
c ·
p ·
b}
17:45, 1 November 2019 (UTC)
reply
better avoided. I guess if I read the whole thing more closely maybe the "recommended fix" of the previous para doesn't apply to those valid forms. As above, it still strikes me as an easily-done change which muchly helps those who use syntax highlighters, and I don't see a downside. But again, if you want me to turn it off, I will do, though sadly. -- BrownHairedGirl (talk) • ( contribs) 22:58, 1 November 2019 (UTC) reply
Approved. without the <br>→<br/> thing. If there's a wider discussion in favour of those fixes, file another BRFA for those and I'll speedily approve. Headbomb { t · c · p · b} 23:45, 1 November 2019 (UTC) reply
Revoked. See Special:Diff/937425282. Primefac ( talk) 23:26, 24 January 2020 (UTC) reply