Hello, I am Petr Bena also known as Petrb (my SUL). I am a volunteer developer working on multiple projects, including Huggle, wm-bot and many others
Whitelist was missing as well, that can be currently fixed only through pgsql query on labs db server, I need to create some interface for this later
Project:Huggle/Message is missing
Sat, May 19
ok just let me know when you decide if this is intentional or a bug in MW that needs to be fixed. If it's supposed to work like this, I can change the huggle code to login one site by one
So I rolled out the new config file: https://www.wikidata.org/wiki/Wikidata:Huggle/Config.yaml
I implemented new option into 3.4.0 in project config which is a regular expression that can be used to find user on report page, this how you can use it:
however what I posted is true as well, I think Huggle wouldn't be able to add new reports properly as of now
oh now I see this is not about adding new reports but checking existing reports
I think you should change aiv-section:2 to aiv-section:0
You can try here and reopen if you still have troubles https://petr.insw.cz/tmp/huggle.dmg
JS engine was implemented and is working pretty well, but there is a need to add huge amount of API's to make it really usefull
Keep in mind they are numbered from 0, so 3th item is item 2.
Works to me in 3.4.0 built with Qt 5.11
Fri, May 18
after a restart of bot it magically started working
Sun, May 13
I didn't even look on config page, because I am really busy with other tasks now, but I guess the problem is with regular expression for checks of report page. To debug this, you can probably copy paste the report and config page to test.wikipedia.org and test it there. The regex probably needs to be updated, I suppose you have same regex from english wikipedia which is designed for their report page.
That shouldn't break anything if you use default-template: "warning" per https://www.mediawiki.org/wiki/Manual:Huggle/Deploying/DefaultConfig.yaml
Fri, May 11
Thu, May 10
openSUSE Leap 42.3 with KDE
Mon, Apr 23
Apr 12 2018
Apr 11 2018
Apr 8 2018
I will make this my priority this years hackathon, anyone is welcome to join me.
I recently implemented JS scripting to other application I made: https://github.com/grumpy-irc/grumpy
Mar 29 2018
in stdout I see
it just happened now, the problem with this issue is that it happens randomly like once in a year :( so it's not easy to reproduce
Mar 22 2018
@Ilanosortap I just fixed it:
Mar 20 2018
Not all channels removed, but lot of them freed
Mar 14 2018
it worked :/
Mar 12 2018
I don't think we need any limits extended at this point, there is still about 150 free slots and lot of channels that in theory can be safely parted. So we are nowhere near the need to ask for some exceptions. All we need to do is clean the mess :)
Also non-wiki channels (don't have wiki in channel name) have "last used" older than 4 weeks in /cs info can be probably also parted.
I think that every channel which bot is in alone and isn't registered (/cs info #channel_name) can be safely removed. I removed some today, will continue later.
Mar 11 2018
I would appreciate if instead of blind @part of each channel with user count 1, we actually tried to figure out if channel is still registered and being used :), in round 1, let's remove the bot from unregistered channels first and dead channels (0)...
For now let's exclude all wikipedia channels (like #wikipedia-cs-rc) these are probably OK, since they belong to really small wiki projects, they are probably empty often.
Mar 6 2018
yes it's deployed.
if you find any other command that you think should be available in PM let me know
I made it possible to use seen again.
I think that module for labs was deprecated, otherwise only some commands can be used using PM, such as @seen
Feb 28 2018
But it's there - just click the button, see screenshot: https://pasteboard.co/H9LEUti.png
Feb 16 2018
But it was already activated long time ago, did you hit "Reload" in login form?
Feb 14 2018
instance huggle-pg was shut down by someone, I booted it back up, this instance hosts the postgre DB for browser.
Feb 8 2018
now, before we close this we need to check which tasks were finished and these that were not, can be reopened
Feb 4 2018
Yes, I agree. Don't have time now though to implement this, maybe during hackathon?
Feb 3 2018
it's available in read only now
Same with Windows 10
Feb 2 2018
Feb 1 2018
We definitely need to use what API say but is there even any information like the actual username in response?
does it still happen?
I wasn't able to reproduce this for a very long time, unless there is more feedback from users I will consider this resolved
Huggle is not part of mediawiki core, it's a separate project
of course, anyone who can edit pages on mediawiki and upload pictures to commons can do this.
I am not sure why you ask about codebase (which is at https://github.com/huggle/huggle3-qt-lx). This is a documentation for users, not developers. This task is for update of obsolete screenshot in user documentation (or manual).