@Jdlrobson
One remark made on frWP is that the identifier of the fields should be more descriptive and stable, so that CSS styling can be safely applied on some fields. Currently, it seems that the fields identifiers are auto-numbered so they can change with new versions or even for different usages of the page (depending on what other fields are added or not). Would it be possible to have meaningful identifiers for the fields, instead of things like ooui-php-18 currently in ProtectionForm for the checkbox for the cascade protection?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Thu, Feb 18
Wed, Feb 17
I just saw your message on frWP sysop board: feel free to close again, but I still believe there's something going on with Protect-cascade
According to the comment on Group-sysop.css, it says that "it hides MediaWiki:Protect-cascade, which shouldn't be used". And indeed, when I check again https://fr.wikipedia.org/w/index.php?title=Gilbert_Moses&action=protect&safemode=1, the box title says "Protection en cascade - A NE PAS UTILISER" (Protect cascade - DO NOT USE). So what has changed about the usage of "Protect-cascade" ?
@Jdlrobson
Here's the current status :
Tue, Feb 16
In T274934#6835129, @Jdlrobson wrote:Just to confirm I understand the issue, per @Aklapper I am also seeing the following - is this what is supposedly missing?:
If so, I'll explore what could be happening here..@NicoV could you also confirm you do not see it on the following URL:
https://fr.wikipedia.org/w/index.php?title=VTV_1&action=protect&safemode=1
?
Mon, Feb 15
I thought it was happening again today, I even took screenshots, but I noticed one line with several hundreds modifications from Wikidata for a single user page...
It was probably something similar last time, I think we can close this task.
Thanks for the notification @GoingBatty . I completely refactored this part for performance, and it seems I introduced a few bugs on the way... I will try to fix it today.
Sat, Feb 13
Fri, Feb 12
Mon, Feb 8
Fri, Feb 5
I've modified WPCleaner to allow working on a subset of regular expressions when running in bot mode. This is based on optionally defining a group name for each regular expression, and configuring the bot to run only on a selected list of groups (by default, no groups are selected).
Wed, Feb 3
Sorry for the delay, but I just pushed a new version that should keep the bot flag when creating a new subpage (as it was missing, it's probably not watched), but the bot flag will still be there when updating the subpage (in case someone added it to its watchlist). Does this seem ok to you? (and does it work as expected on cswiki ?)
Jan 22 2021
@Etonkovidova
Thanks for the answer. The problem lasted for almost a day, and I wasn't the only one having the problem (I asked here). I hope it was a temporarily glitch
Jan 20 2021
Dec 22 2020
In T269225#6707499, @ArielGlenn wrote:In T269225#6706807, @NicoV wrote:At least for frWP, it seems the step "Recombine articles, templates, media/file descriptions, and primary meta-pages." doesn't start even if the step "Articles, templates, media/file descriptions, and primary meta-pages" is done for more than 20 hours. See https://dumps.wikimedia.org/frwiki/20201220/
They seem done to me.
2020-12-21 01:41:19 done Recombine articles, templates, media/file descriptions, and primary meta-pages. frwiki-20201220-pages-articles.xml.bz2 4.6 GBNote that the servers running everything else but enwiki have the old version of the utils so they wil work just as they always have.
Dec 21 2020
At least for frWP, it seems the step "Recombine articles, templates, media/file descriptions, and primary meta-pages." doesn't start even if the step "Articles, templates, media/file descriptions, and primary meta-pages" is done for more than 20 hours. See https://dumps.wikimedia.org/frwiki/20201220/
Dec 17 2020
Dec 16 2020
Yes, I understand that typo list pages can only be changed once a new AWB release has been rolled out (and probably after some time to be sure users have upgraded). That's why I'm pushing to include this patch, so that it won't be too long before modifications can be made in the typo list pages. At least, once I know this patch will be included, I can also start modifying WPCleaner to take advantage of this, even before we can add the new attributes to the typo list.
Dec 14 2020
I just pushed a new version that should remove the bot flag for the edits on the main talk page. I can't test it properly on frWP, can you tell me if it works on csWP ?
Dec 13 2020
Ok, thanks for the example, I will see to remove the bot flag for the edit on the main talk page.
I modified WPCleaner a few months ago to remove the bot flag when adding warnings on talk pages (or subpages), to have a better chance of article authors noticing the warning. What better way do you think of?
Dec 8 2020
Dec 7 2020
Hello @Rjwilmsi (or other AWB developer?): what is the process to submit patches?
Dec 5 2020
Dec 4 2020
Dec 3 2020
Thanks @ArielGlenn , I could download the dump analysis for frWP
Dec 2 2020
Nov 30 2020
In T56947#6657213, @Tgr wrote:In T56947#6654187, @Esanders wrote:The volume in the above mentioned edit filter (T56947#2098243) would be a good metric for success. It might be useful to have it on more high volume wikis.
Note that the filter only catches changes to dates (which is a good way to avoid false positives, but it avoids the vast majority of true positives too). So it's a good way of measuring whether problematic edits become less frequent, but not a good way of measuring how frequent they are, in an absolute sense.
Nov 29 2020
Done.
Nov 21 2020
Nov 19 2020
Nov 16 2020
Nov 15 2020
Nov 14 2020
Dump analysis done, and automatic fixing tested.
Nov 12 2020
Nov 11 2020
The switch to Java 8 is done, other improvements (using Optional<>, using Nullable and Nonnnull annotations, streams, lambda...) will be done in other tasks.
First version done. I will run a dump analysis and see what can be fixed automatically.
Nov 10 2020
Nov 9 2020
Nov 8 2020
Nov 7 2020
Done. Each error can be in its own package: for example, for error #501, package will be api.check.algorithm.5xx.50x.501.
Done.
Nov 5 2020
Nov 4 2020
Done.
Nov 3 2020
Nov 1 2020
Oct 21 2020
Oct 19 2020
If needed, a few more recent edits:
https://en.wikipedia.org/w/index.php?title=Miss_Universe_Cambodia_2019&diff=983133739&oldid=982344028
https://en.wikipedia.org/w/index.php?title=Miss_Cambodia&diff=983135015&oldid=983132050
https://en.wikipedia.org/w/index.php?title=Ministry_of_Mining_and_Energy_(Serbia)&diff=982383906&oldid=953995112
https://en.wikipedia.org/w/index.php?title=Ministry_of_Health_(Serbia)&diff=982383040&oldid=964534644
https://en.wikipedia.org/w/index.php?title=Ministry_of_Education,_Science_and_Technological_Development_(Serbia)&diff=982381908&oldid=953989723
https://en.wikipedia.org/w/index.php?title=Ministry_of_Agriculture,_Forestry_and_Water_Economy_(Serbia)&diff=982380534&oldid=961787908
https://en.wikipedia.org/w/index.php?title=Minister_without_portfolio_(Serbia)&diff=982652098&oldid=949141558
...
Oct 18 2020
Done.
Oct 17 2020
Oct 4 2020
Second step, block by default, but allow specifying a command line parameter to allow Java 7.
@ppelberg and @matmarex
Is the Parsoid fix supposed to handle also this kind of edits? Because it was done on Septembre 30th, 2 weeks after Parsoid fix has been deployed, and there are still many "link=" added by VE (but to new images). My bot fixed it for the pass on the October 1st dump.
Code modified to avoid automatic replacements when some tags are involved.
Oct 2 2020
@ppelberg Seems ok to me
Sep 26 2020
I already ran my bot twice this month, but one thing that can also partly explain the difference is that in August, I ran it very late (like 30th of August instead of 22nd or 23rd), so it fixed some that would usually be fixed in the beginning of the next month.