You're the first to ask for support of 2FA : I will have a look, but I don't know when (very little time to devote to WPCleaner).
I never tried bot password, but it may work as is (you create a bot password in Wikipedia and use it instead of your own password in WPCleaner)

Hi @Liu1126 , sorry for not answering sooner, I wasn't notified.

I don't know how I can fix that, this a problem at Java level with Telugu => closing

No answer, closing

Hi @2NumForIce , can you check https://en.wikipedia.org/wiki/Wikipedia:WPCleaner/FAQ ?

Hi @DavidMulder , thanks for the report.

Hello @Mastrocom, sorry for the long delay in answering.

I've configured a bit WPCleaner so that it should suggest other replacements for CW#81 on itwiki:

• I've created template groups so that the configuration for the main template will also work for its redirects
• I've configured some of templates/parameters you mentionned so that WPCleaner will use the parameter value to suggest a name for the ref

If you want to complete the configuration, do not hesitate. Do you see the new suggestions in WPCleaner for itwiki? Is it helpful?

So, do you know a few templates on itwiki where we can use some of their parameters to name the ref tag? On frwiki, I mainly used the citation templates with their title parameter. What should I use on itwiki?

I've added a parameter error_081_name_max_length_itwiki in the code that can be used to set a hint for the maximum length of the reference name.

For the parameter, it's already possible to have a priority between parameters : cite web|surname|publisher|title will first take surname parameter then publisher then title. But it's not as powerful as you wish, it just takes the parameter and applies it. For frwiki, I used this and automatically fixed all pages, and I got no negative feedback.
It can still be useful for itwiki, if you don't set error_081_automatic_title_itwiki to true, it will only be suggestions, not automatically applied. I can think of adding a max length for the parameter value.

Recently, I've done a complete refactoring of the code that handles CW#81, to fix a few issues and be able to automatically handle more situations. In the process, I've removed the Fix automatically feature that was asking a lot of questions...

Thanks @Verdy_p , it's supposed to be a verb, so I have changed it to Name the reference from template parameter

• Detect the templates : https://github.com/WPCleaner/wpcleaner/commit/81ebeeae89ccf8297ab880aa5eac146796d57395
• Fix automatically : https://github.com/WPCleaner/wpcleaner/commit/367377b84e1966b3d7bf86f2e6314c6e7109cde8

This is due to regular expressions in AutoWikiBrowser/Typos that are not optimized (typically, regular expressions beginning with look-behind) : only way to improve performance, is either to optimize the problematic regular expressions, or to disable them. But nothing to do on WPCleaner's side

It really seems to be a Java rendering problem, not really related to WPCleaner. I don't see what I can do on my side. The only thing I can suggest for the moment is that you try another font than Gautami to render Telugu text, maybe Noto Sans Telugu ? You need to download the family, extract the .ttf files from the zip and install them before being able to select them in WPCleaner (and restart)

@Chaduvari , so it seems to be a rendering problem.

@Chaduvari, at least, it's a good first step having the Gautami font used everywhere for you.

Hi @Chaduvari , I've just tried my last option, but I don't manage to make it work on my end. You can try yourself if you see any difference, but I doubt it will work...

I tried to make a new version that changes all the fonts with the other font specified in the options. Any change ?

Hi @rudrudu, I understood that you :

• Started WPCleaner
• Logged in tewiki
• Clicked on Project Check Wikipedia
• Selected some error numbers from checkwiki (given the log, it seems 3, 4, 5, 7, 8, 10, 14, 15, 19, 23, 24, 25, 28, 32, 34, 36, 37, 39, 43, 49)
• Clicked on Load errors: it takes some time to retrieve the lists from check wiki, it's normal
• Clicked on Load pages: it takes also some time because some regular expressions defined in AutoWikiBrowser/Typos take a long time to be processed on the article

I tried something, can you see if it changes anything ?

With the configuration page, you can use WPCleaner on gom wiki, but it will be limited in features as it won't find checkwiki errors : you can edit pages, be warned about links to disambiguation pages... but not checkwiki errors.

I've added gom wiki to WPCleaner.

For me the only thing that didn't work last time I checked is the font. If I find the time to work on this problem, it will probably be on WPCleaner Next Generation, so not really soon. Please open a new issue for each of the problems that are still present for you.

WPCleaner should now be able to work on mniwiki. I haven't checked what it will look like in WPCleaner, but I'm not sure it will be easily usable, because Java may have some troubles with some alphabets. If you have a font installed on your computer that works with your language, you can try configure WPCleaner to use it.

Can you follow the steps described here ? A configuration page needs to be initialized on mniwiki, and it's specific to mniwiki it must be done by someone familiar with this wiki. Once this is done, I can add mniwiki to WPCleaner.

Done : https://github.com/WPCleaner/wpcleaner/commit/64c6bc242cf637eab52e9773c27e07f070f92596

I don't understand. If you don't fix an error, it stays in the list, that's the expected behavior. I'm trying to rewrite WPCleaner, so I'm not taking into account new feature requests unless they're really useful.

No other report of similar problems, no news on this issue, so no way to investigate on this one.

Will be done in WPCleaner rewrite (Next Generation)

Will be done in WPCleaner rewrite (Next Generation)

Hi @Lindsey40186. I was unable to reproduce the problem you're reporting, and you didn't tell me if it was still happening. I'm closing the issue.

Done, DOI surrounded by double parenthesis shouldn't be reported by WPCleaner as invalid anymore

Hi @Micler and thanks for the report.

Hi @Etthen, as you guessed loading the account name and password from the credentials.txt file is done using java.utils.Properties.

Hi @AramBakir , it should be fixed now.

Due to the lack of answer from AWB developers, I finally implemented an other solution. It's now possible to specify a list of regular expressions to disable in WPCleaner.

@AramBakir No need for the log file if it works for you. I'm releasing a new version of WPCleaner

@AramBakir , thanks for the log, I finally understood what is going wrong on your end...

Normally, there's no sensitive information (passwords, tokens... are removed from the logs). The logs weren't enough to understand the problem, but at least I hope it's enough to pinpoint where I should catch an error and add a log with it. Can you try again ? Hopefully, you should see logs tagged with the task number but at level ERROR instead of WARN...

@AramBakir I've no clues on what is going wrong... I added some logs to WPCleaner, can you run WPCleaner again and try to start the Automatic Fixing window ? In the logs, you should see logs tagged with the phabricator task number (T288422). Can you post them here ?

@AramBakir , I don't think uninstall/reinstall will work but you can try removing the configuration.

Ah, sorry, I found what you were talking about. It's in the configuration for Check Wiki, I removed it from the documentation.

Hi @Jilucorg. Does this phabricator task has anything to do with WPCleaner? If not, can you set the correct tag to this task and remove the WPCleaner tag?

It should be fixed now.

Hi @AramBakir. No real progress with the logs: on my computer the automatic fixing window opens without any log and without any problem.

Hi @Lindsey40186 , is it still happening?

Thank you @AramBakir , I'm starting to analyze. Here's what I extracted from WPCleaner.log file :

Hi @AramBakir , then I really need detailed explanation of the steps you're doing (with screen shots if you can) and to know what is in the log file. Because, as it's working for me, I can't understand what's going wrong on your computer.

I also tried with ckb language, and it also seems to work

I tried running WPCleaner for ckb wiki with English language selected:

• I open Check Wiki window
• I selected only error #513 (ckb doesn't seem to be configured for Check Wiki project so you won't get pages for most of the errors) and clicked on Load errors
• A list of pages is displayed on the left
• I can select a few of them and click on the Automatic fixing button => a new window opens (see below)
• I can also click on Load pages and it display page contents (see below)

Hi @Jony , sorry for the long delay in answering.

I'm now running several bot tasks on Toolforge. Only the dump analysis is still run on my own computer because this task requires a lots of CPU and memory: I may try later to run them also on Toolforge.

I'm not sure I understand what it the problem you're facing, because I tried again on my computer and it seems to work. I can only see 2 things to make some progress on this :

• Tell me exactly, step by step, what you're doing (starting with launching WPCleaner) and what you see. Try to have a minimal set of steps.
• In the folder where WPCleaner is installed, do you see a file named WPCleaner.log ? This file contains logs from WPCleaner. I'm interested in its content, but to have a limited size, you can delete the file, then start WPCleaner and do the steps that ends up in the problem you're reporting.

Thank you for the bug report. As explained by @GoingBatty

Done

Fix : still reported but no more suggestions for a quot inside a tag

Done for ISBN

CW#73

CW#72

CW#71

CW#70

First step on CW#69

Hi @Rjwilmsi , any hope of integrating the change I suggested in AWB ? Modifying the code shouldn't break any typo list pages, but it will allow starting to modify them after the release to benefit from the new capability.

Done

Sorry for not answering sooner, I didn't get any notification it seems of the new issue.

CW#81 already handles extra space characters at the beginning or end of the reference: <ref>Ref 1</ref> and <ref> Ref 1 </ref> are considered as the same reference by CW#81