This is an archive of past discussions about Wikipedia:Huggle. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
It seems the issue popped up today (Blocks yesterday worked just fine). I would add that i have been using the block button on the report page exclusively today, so that might be related. Excirial (Contact me,Contribs)21:02, 5 December 2013 (UTC)
Sorry for being lazy and not checking the archives, this should have been brought up before. Most other antivandalism tools link to contributions of IP/editor in the edit summary, like "Reverted edits by 50.196.130.97 identified as vandalism" HG 3 does not. This feature is very important (for me) as it greatly facilitates checking other contributions of a potential vandal. Materialscientist (talk) 02:24, 7 December 2013 (UTC)
Diff window incorrectly reports "0" as size change.
The Diff window contains the text "Size Change", followed by a number that indicated the number of added or removed characters. The "History" contains the same information: The amount of characters in revision A, and the amount of characters in revision B. At times it seems that the diff window reports a change of 0 characters while the diff and history window show that this is incorrect.
It always seems to occur on page blanking (The diff always reports 0 character changes, if the page is blanked).
It other occurs otherwise as well, though i haven't been able to determine any common denominator for this issue. A non exhaustive list of examples would be: ([1][2][3][4][5][6])
It occurs on additions and removal of characters, and seems unrelated to future edits - as in: article's show a 0 size diff even if no further revers or edits took place in the article. Hope the above is somehow useful, Excirial (Contact me,Contribs)21:07, 9 December 2013 (UTC)
Yes I know about this, it happens only for irc feed and clearly is related to irc parser which randomly fails to read the number for some reason... Petrb (talk) 09:41, 10 December 2013 (UTC)
Query failed: srlimit may not be over 50 (set to 500) for users
That is pretty cool given that there actually is NO huggle 3 mac installer :D so I am wondering where have you get it. Or did you compile it instead of installing? Petrb (talk) 08:41, 12 December 2013 (UTC)
Instead of using a simple internal rating system for "badness" of edits, wouldn't it be possible to take advantage of ClueBot NG's RC feed and prioritise according to its score? With a fallback for when CB NG is down, of course. CB NG is very good at spotting vandalism now, and I suspect that much of the vandalism that it doesn't revert falls just below its conservative threshold: this would provide much better prioritisation of the edits that warrant examination, and - most usefully - it would completely avoid that bane of all hugglers, being beaten by ClueBot :) —SMALLJIM14:02, 7 November 2013 (UTC)
Seems like a good idea! All though Huggle is very good at filtering edits which could be vandalism, many pages still has vandalism that wasn't detected by Huggle, so the use of ClueBot NG "algorithm" seems more productive and will make detection easier. ///EuroCarGT03:11, 9 November 2013 (UTC)
I would prefer both feeds being mixed. Regarding cluebot not conflict with other users, it just needs to connect to HAN and that's all, if it was there it can report directly what it reverts so that other huggle users are in sync. Right now if 2 huggle users are connected to HAN they can hardly beat each other because they share their actions Petrb (talk) 08:26, 15 November 2013 (UTC)
I created a relay, but unlike huggle, cluebot doesn't send a notification that it is going to revert edit before, but only after it is reverted. Because wikipedia is very slow when it comes to reverting, this creates a lag of several seconds and make cluebot's feed pretty useless. Until you are informed that cluebot reverted an edit, there is still a huge delay during which many users may attempt to revert the edit as well, which result in same EC as now. Petrb (talk) 12:56, 19 November 2013 (UTC)
I can see that would be a problem if both feeds are used at the same time. But I was thinking of using only the ClueBot feed (I mean the complete RC Feed on #cluebotng-spam as described in the second bullet, here) which adds the useful vandalism score to every edit it sees. We know the threshold score below which ClueBot will not revert, so by using that feed (which claims less than a second of lag) and only presenting to the huggler the edits that fall below the threshold we know we won't be beaten by ClueBot and we can take advantage of its rating system to prioritise the edits in the list (highest score at the top, ignore anything below, say 0.5). We completely ignore the lagged reverted edits. Would this not work? —SMALLJIM22:40, 19 November 2013 (UTC)
No, in fact mixing both feeds is simpler and possible and already implemented. Only reason why you don't see it in huggle now is that cluebot is down. Once it's back you will see its contributions to scoring of edits Petrb (talk) 19:39, 28 November 2013 (UTC)
I don't think you mean no it wouldn't work (at all), do you? Anyway I didn't realise you'd implemented a link with the CB NG feed, so it sounds like it's time for me to try v3 again - thanks! —SMALLJIM20:41, 29 November 2013 (UTC)
Yes it now uses the huggle feed, but to be honest I think that when huggle follows CB suggestions, it get far worse ordering than when it doesn't. So there needs to be option to disable suggestions at all, because huggle internal ordering system seems to be much more precise (when following CB's I get often vandalism to bottom of queue and often good edits on top) Petrb (talk) 08:12, 12 December 2013 (UTC)
Thanks Petrb - I've had a play with H3 (#763) today: it's very fast and looking good (though I do miss that graphic representation of edits in H2!). You're combining ClueBot's scores with Huggle's in some way, aren't you? In the Network panel I'm seeing messages like "ClueBot rescored edit <article> by <user><rev> by <a positive or negative integer>", whereas CB's scores range from 0 to 1. Almost all the high (>500) CB scores in that Network panel that I've managed to find in the Queue have been clear vandalism so far. Can't you fix the problem by changing how the CB scores are used - giving the higher ones an even higher weighting, for instance? Or even (innovative idea?) allow the user to adjust the relative Huggle-CB weighting, so he can tailor this own queues. Or failing that, an option to use either only Huggle's scoring system or only ClueBot's would be good – then we could have two sets of Hugglers working on independent feeds, each clearing vandalism not rated highly by the other. —SMALLJIM18:13, 12 December 2013 (UTC)
After re-reading a few pages (WP:Huggle/HAN and WP:Huggle/Privacy etc), I see that some of what I suggested above couldn't be implemented under the system as it stands (the core being at irc.tm-irc.org). Sorry about that. But what about adding into huggle.exe some randomness to the ordering of the queue? I'm sure this would benefit the users because it would help avoid everyone trying to revert the same edit at once - which is a problem I think all regular Hugglers are familiar with. If possible, the degree of randomness introduced should depend on how many Hugglers are online (increasing from none or a low figure, if there's only one). —SMALLJIM14:05, 13 December 2013 (UTC)
Missing feature -- ability to AGF revert/rollback with custom edit summary
I'm testing out HG3 build 793. Wow is the performance better! Unfortunately it's missing a critical feature I used all the time with HG2--in that build I was able to hit "Y" and rollback AGF, and specify my own edit summary. I used that all the time. I don't see any way in HG3 to specify my own edit summary. Am I missing something or can that be added? Thanks... Zad6816:25, 13 December 2013 (UTC)
The {0} is actually a localization issue, so that wouldn't cause any big troubles but it is a good idea not to test destructive tools on production :-) that's what we have test wiki for (you can get sysop there if u need), anyway that both things need to be fixed Petrb (talk) 20:58, 17 December 2013 (UTC)
Seems that blocking a user contains a rather bad issue. The block form defaults to a 31 hour block, with the check-box for account creation disabled set. However, as evident from my block log the blocks it actually issues are 31 hour blocks with "Talk page disabled" set instead of "account creation blocked". In other words: The user cannot challenge the block, but can create a new account instead. Excirial (Contact me,Contribs)21:04, 16 December 2013 (UTC)
Will this issue be fixed? Because, it's supposed to block IP addresses for 31 hours with the check-box for account creation disabled set but, it blocks IP addresses for 31 hours with Talk page disabled instead of blocking account creation. Thanks! Thewikiguru1 (talk) 21:15, 16 December 2013 (UTC)
Not fixed. (Huggle build 780). I've just tested this on Coreva-Bot, and from what i can observe it would seem that all the settings in the block window are ignored (Except for the duration of the block). The third block aimed at the account had every option enabled on the block window, while the fourth block had every option disabled. In both instances the result seems to be a block where talk page access and autoblock are disabled. Excirial (Contact me,Contribs)19:23, 20 December 2013 (UTC)
In the Hindi language localization of Huggle, The Hindi script fonts appear very small and have jagged edges throughout the interface (in menus, toolbars etc.).This makes text almost impossible to read. The English text seems fine. Can a option be added to increase the GUI fontsize (and preferably to change the typeface) in the next version? Can it be fixed? Shubhamkanodia (talk) 12:00, 4 January 2014 (UTC)
Now that i've ended up on the feedback page anyway, i figure now is as good as anytime to suggest a couple of features.
Would it be possible to re-add the "You got talk messages" notification Huggle 2 had? I keep running into situations where someone commented on my talkpage, only for me to continue patrolling another hour before noticing it. Actually that is a compliment for Huggle 3 as a whole - these days i barely need to return to my browser for any wiki related activity while using Huggle.
More challenging perhaps, but is there any chance that the report user dialog could be extended with the list of previous blocks? (Huggle 2 had something similar). That feature was always convenient for detecting repeat offenders / school IP's for longer term blocks.
Huggle 3, Build 796. Deletion summaries and default block settings.
Another two request / suggestions from me i guess - though i am starting to feel rather greedy seeing the amount of those i've been adding here as of late...
The block window for IP editors seems to default to "Disable account creation". Can "Only Block Anonymous Editors" be checked by default as well? (For IP editors those two settings will be used 99% of the time).
And one related to the page deletion summary three sections up. The deletion reasons for EnWiki are listed here: MediaWiki:Deletereason-dropdown.
There are a few complications for adding these though. For one, the deletion dropdown is dependent on the pages namespace. The "General", "Redirect" and "Other" reasons types are always visible, but the other deletion reasons are displayed based on the current pages namespace(View the dropdown's source for those). Eg: If we're deleting an article namespace page, the deletion reasons for article's are displayed as well. To make things even more interesting: The deletion dropdown only allows entries that start with "**" to be selected as actual reasons. The category headers that start with * cannot be selected in the dropdown. Even so they they are displayed in bold text and serve as (quite practical) dividers between the deletion types.
Any chance this is possible? I've made a start adding the general reasons here, but it seems it doesn't like the comma's used in the description of G1: The current list shows "G1: Patent nonsense", "meaningless" and "or incomprehensible" as the deletion reasons and nothing else after that. Nothing that i cannot work around, but i figured i might just as well mention the above first.
Hi all, I would like to note that since now we aren't using translations on wiki anymore (these that were wikipages), if you want to help us with huggle translation, you can directly modify the localization files on github. Basically old process did consist of 2 parts, first was that someone did edit the wiki page, second was that random developer noticed that and updated source codes accordingly. Because waste majority of huggle developers are lazy and not very reliable, this method wasn't found as most fortunate. Hopefully, using github we wouldn't forget about updates so much and the work of translators would be more coordinated, we also have these nice cute stats now: http://huggle.wmflabs.org/language.htm
Thanks to these you can see how much current localization suck :-). So if you want huggle interface to be in a different language, you can update these. But keep in mind that because huggle is under very active development, there might be new strings every day, so even if your language was 100% localized yesterday, today it may not be. Petrb (talk) 16:08, 9 January 2014 (UTC)
Huggle 3, build 796: some preferences are reset upon startup
I open Huggle 3 and change one of the preferences (System, Preferences, Performance, On change of page, revert etc, Retrieve your own edit), and exit the Huggle. Checking my huggle.css, I notice that the setting is saved ([7]). When I open the application again, the setting is lost. When it is closed again, huggle.css is reverted to its original version([8]).
O.t.o.h. when I change System, Preferences, Reverting, On revert of multiple edits by same user, Revert), the preference is retained across sessions ([9]).
Sidenote, the setting of that first (Retrieve your own edit) seems to have no effect. When I make a revert, I prefer to see the result of it, instead of the next edit in the list. - DVdm (talk) 13:59, 10 January 2014 (UTC)
Yes, this is known issue, as you can see on beta info page. It will take few weeks for this code to be finished, it's rather huge. Petrb (talk) 15:45, 15 January 2014 (UTC)
Bug with reporting users on HG3 beta 796
Resolved
I don't know if it's just something wrong on my end, or if it's not just me, it's already a known bug, but when I click the "Check if user is reported" button when reporting users in HG3 build 796, it crashes. Lugia2453 (talk) 19:17, 14 January 2014 (UTC)
To be fair: The title sounds more serious then the issue really is. Fluffernutter and myself had our eyes on the same vandal, and as a result we ended up in a "block conflict" (Lacking a better word). Fluffy actually placed the block, but even though Huggle reported that the user was already blocked, it seems it still left a block template.
Yes it is, I fixed it many times and it got borked again. I don't know which client is causing it, if huggle 3 or huggle 2, but I haven't managed to reproduce this issue on neither of them. I will cron some cleanup job for this. Petrb (talk) 15:58, 15 January 2014 (UTC)
It says something about the resilience of Huggle that it continues to work despite having such a corrupted file in its config. If you can't reproduce the problem, might that suggest one user with a hacked copy of Huggle? The cause could no doubt be found with some detective work (time permitting!) but a regular cleanup sounds like a good workaround. —SMALLJIM20:39, 15 January 2014 (UTC)
Whitelist is all written in PHP and it is actually possible to both log changes and track who did them, as well as block certain users from being able to change them, or disallow certain types of changes (like addition of nonsense chars). However this need some devs to implement it, and given the size of huggle dev team, it's likely going to take some time. Only thing I made so far to protect whitelist from being permanently damaged is, that I am making a revision (copy) of content, everytime it's changed. So if someone ever broke it entirely, it can be always recovered to previous snapshot. Petrb (talk) 09:21, 17 January 2014 (UTC)
If you have a window that is currently displaying (you should have the Queue window) > Right click on the most top part tile bar of the window > You'll see a dialog box with check marks, the one's that are currently open are checked, meanwhile the one's you've closed are unchecked. Reactivate the windows by enabling it. If this has confused you, please forgive me; here is a picture:
There actually was a menu in past in main toolbar, but when I figured out that QT automatically provides this in a right click, either on widget label, or anywhere on toolbar area, I thought there is no point in creating such a menu by hand as well. If it's really so confusing I might put it back to main menu. Petrb (talk) 09:18, 17 January 2014 (UTC)
You can also put these widgets in tabs, so if you don't want to have some widget on screen all time in front, but you also don't want to hide it permanently, you can drag it (click on its title and hold button) and move over any other widget. This will put these 2 widgets look as 1 with extra tabs which actually allows you to switch them. Petrb (talk) 09:26, 17 January 2014 (UTC)
IRC feeds down
Resolved
At the time of writing, there are performance issues with IRC recent changes feed (check http://status.wikimedia.org/). Huggle users may force the software to use the API with System > Options > uncheck "Use IRC feed for recent changes if possible". Cheers! — MusikAnimaltalk18:46, 17 January 2014 (UTC)
What should happen when two users warn same user in same moment?
Currently there is this critical bug open https://bugzilla.wikimedia.org/show_bug.cgi?id=59982 the question is, how should we fix it, and is it really necessary to fix it? Imagine you have 2 users who revert 2 different changes made by 1 user in same moment. Both users are successful in revert because they both revert 2 different edits, however huggle parsed only 1 template from user page (none of these 2 users did update the user talk page so far). Both clients logicaly attempt to send level 2 warning. Is this necessarily wrong? There are possible solutions:
Do nothing (leave 2 level 2 templates on talk page) - pros: basically, we wouldn't need to change anything. cons: some users wouldn't like the idea of user receiving 5 warnings instead of 4 before they get blocked
Ask user what they want to do - cons: this may be annoying to some users
Send level 3 warning instead (here we need to resolve what to do when last template was lvl 4 warning, probably user need to be prompted to report user, despite the edit was reviewed possibly long time ago and user couldn't expect this to happen) - cons: this will make huggle slower (users with slow connection will be impacted much more)
What do you think? I personally think that given how rare this situation is, having 2 lvl 2 warnings wouldn't matter that much. On other hand implementing other 2 solutions isn't that hard. Petrb (talk) 16:54, 15 January 2014 (UTC)
Did some testing on Huggle 3 beta (version 673). Seems to work well. A few remarks:
Too much white space between lines in auxilary windows.
Page and user histories should be in reverse chronological order (most recent on top).
After a revert, the result of the revert should be shown, not the next entry in the queue.
Severely missing the horizontal graphic page and user history navigating ribbons on the top right of the page. This was arguably the single most useful feature of Huggle2 - absolutely indispensible.
Using most recent up-to-date versions of XP sp3 and WIN8.1
Extra white spaces between entry lines on windows History, User info, and Processes. No extra white spaces in windows System logs, Network. Not sure about window History of your changes.
Page history is indeed most recent on top. User info lists most recent at bottom.
Ok (it's user configurable in H2, probably not yet in H3).
This is the most important—and probably the toughest—feature of them all, of course :-)
Yes in 796 it is, I always send the Fixed message when the patch is commited to master in our repository (since that moment anyone can download the source code and compile the patched version) Petrb (talk) 15:53, 6 January 2014 (UTC)
Ok, tested. Much better now!
Regarding my point 4, are there plans to implement those brilliant version 2 ribbon-like histories with live coloured tiles, indication of warning level, reported, blocked, reversion, etc...?
Not in this toolbar style (unless someone create such an extension) but I will try to add these icons and colors to current history widget Petrb (talk) 10:03, 7 January 2014 (UTC)
Yes, I hadn't noticed that, since after each test, I'm sort of forced to stop after one edit, so I actually never noticed the layout of that window. I feel so terribly uncomfortable using this tool, simply because I don't automatically get to see the result of my action, and—of course—because the horizontal active button history ribbons are still missing. Frankly and sadly, without these two essental features the tool is pretty useless for me—even for testing. - DVdm (talk) 15:27, 18 January 2014 (UTC)
DVdm: There is an "Review your own edit" option in Huggle 3 (On default it is set to "Load next edit after revert"). It is available under "System" -> "Preferences" -> "Performance" -> "On change of page, revert etc". Setting this setting to "Retrieve your own edit" will cause Huggle to load the result of your revert instead of heading to the next page. Note that this will slow patrol speed since you will have to wait for each revert to be processed before it will display the result.
As for the graphical interface, i don't exactly miss any data at the moment. The "User Info" tab displays a users past edits and their warning level (Disclaimer: I assume that last functionality might be broken as of current, or i might interpret the window incorrectly) . The "History" tab will display the revision details on the current page including the user name, size and commentary for each revert. The history ribbons might provide a somewhat more condensed overview, but i can't see any information missing as of current (Though it does require some more glances at the various tabs). Excirial (Contact me,Contribs)15:53, 18 January 2014 (UTC)
As for the the graphical interface, indeed it has all the information, but it is—at least for me—useless, just because it severely suffers from information overload. The specific graphics and buttons of the version 2 ribbons allow to immediately see what is going with the article and with the user. Hovering over the buttons with the mouse provides only the detailed information one really needs. That is—again, for me—the single most powerful and really indispensble feature of Huggle. - DVdm (talk) 16:34, 18 January 2014 (UTC)
I had a play with build 796 today, and I have to side with DVdm. There's information overload in the History and User info tabs, but there are several other problems with them. Some improvements would be to give them user-selectable and adjustable columns - in the History tab, the all-important date (actually timestamp) field often disappears off to the right when there's a long edit summary. The text in the History tab is in a larger font than the User info one which exacerbates this problem (I've got them side-by-side at the bottom of the window). I think it would be better if these two tabs had differently-coloured backgrounds too (they're both blue here), and the time column could be presented in a more friendly format.
But to my mind a more significant problem is the retrograde step of using "bad" word lists as a factor in the ordering of the queue. This has long been known not to be a valuable way to find vandalism: it will always miss so much due to the impossibility of listing all possible variants (anyone remember Hagger and all those regexes?). Using word lists means that the more subtle vandalism will get pushed lower down the queue and therefore be less likely to be seen. Apropos this, I wasted time looking up A Ass Pocket of Whiskey in this diff because it was thrust to the top of the list with +2000 points for "Ass". The "bad" word wasn't even added in that edit. This was another one, at the top of the queue because the diff contains the word "dick".
I intend no disrespect at all to Petrb and the others' amazing programming skills, and I know it's still only beta software, but it isn't really "Huggle" any longer. —SMALLJIM19:49, 18 January 2014 (UTC)
Huggle 3, Build 796. Large amount of data uploaded during "Updating whitelist" step on Huggle exit
Fixed
Another hour, another report! When Huggle is started one of its first actions is downloading the whitelist - a step that transfers about 260 Kb data downstream to Huggle. However, once you exit Huggle the "Updating Whitelist" step suddenly starts guzzling a huge amount of upsteam bandwidth. I ran a few applications to monitor the traffic, and it looks like a massive 10Mb of data is being uploaded to Wikipedia by Huggle during that specific step. My upsteam connection is decent, but that amount of data still drains its entire capacity for a minute (And i don't even want to imagine what happens to users who have a slow connection). Since the actual user list is only a quarter of an MB i have a feeling that a 40x larger file indicates something might be going wrong there.
Another thing i noticed that attracted my curiosity: During application exit most packages are exchanged with Wikipedia or related servers, but Huggle also sends some packages over to 109-123-220-094.tvujweb.net. Since this seems to be a virtual server provider in the Czech Republic my guess is that it is yours (Guessing based only on geolocation). I am kind of wondering why Huggle connects to this host? Excirial (Contact me,Contribs)00:07, 18 January 2014 (UTC)
I could confirm that. No longer updating the whitelist takes such a long time. I was using network software and found the server location to be both Czech Republic (109.123.220.094) and Wikimedia's servers (208.80.###.###). ///EuroCarGT00:33, 18 January 2014 (UTC)
As an FYI, killing Huggle (using Task Manager in Windows) avoids the whitelist update and (on HG2 at least) has no adverse effects, apart from losing any config changes made during the session, of course. —SMALLJIM00:58, 18 January 2014 (UTC)
That IP address you talk about is probably of hub.tm-irc.org which is irc server that huggle 3 uses for HAN, you can disable this in preferences if you don't want to use HAN. hub.tm-irc.org is hosted in central europe, irc-3t.tm-irc.org is hosted in united states. I will update the url to round robin as soon as irc module get patched so that it can pass standard irc checks for valid client, which got implemented in new version of ircd running on irc-3t (hub is still running older ircd which doesn't have this check). I also noticed that WL update takes a long time, but I thought it's related to my bad internet connectivity (my upload is very slow). If it really transfer so much data, it's probably a bug. Petrb (talk) 10:10, 20 January 2014 (UTC)
Ok so I inserted some more debugging and this is what I see:
Mon Jan 20 11:46:15 2014 DEBUG[1]: Sending whitelist data of size: 10975 kb
So, huggle indeed try to upload this big data, in fact the whole whitelist encoded seems to be this big. It's rather interesting, I will check what could be done with that. Petrb (talk) 10:47, 20 January 2014 (UTC)
After removing the borked users, whitelist has 73kb I hope it's going to be fixed then. The issue wasn't in huggle but in whitelist itself. Petrb (talk) 10:53, 20 January 2014 (UTC)
How to install Huggle 3 beta; How to install qt on Mac OS X Mavericks
Resolved
I hope this is the right place for this, but from the talk page i got redirected here. I tried installing qt with the --HEAD as it says here but it didn't work so i didn't use the --HEAD and qt could be installed. I do have another problem installing huggle but i wouldn't say that is caused by my different qt installation. Maybe you should change the text that on Mavericks it 'might' be necessary to append --HEAD. I'm not really into the topic; but maybe it helps. --Macuser10 (talk) 14:57, 20 January 2014 (UTC)
It seems that Huggle had some trouble at times issuing the correct warning level - on this page it placed a level 2 warning whereas the user had already received a level 3 warning. There is a fairly large time gap between the warnings, so i don't assume this is a situation such as described in the "What should happen when two users warn same user in same moment".
Now that i mention that section anyway: Is the increase in bandwidth substantial? And when does Huggle try to parse the users talk page (Eg: Is this done at the same time a diff is first loaded, or is this done at the time the user presses revert?). In the latter case the chance of a conflict is so small it might not be worth spending the time on to fix. Excirial (Contact me,Contribs)21:40, 17 January 2014 (UTC)
A 15 minute gap between parsing a page to determine the warning level and sending a new warning is kind of long (Most active vandals tend to be warned again within that margin). In this case i would support re-checking the users talk page to determine the warning level before adding another warning. Might it be an idea to check the last modification date of a user talk page before retrieving its entire contents in order to determine if the user has been warned in the meantime? (Eg: Querying only the revision timestamp)? If Huggle logs the date/time it fetched a revision it could simply check if someone edited the user talk page in the meantime. If no-one edited it there is no need to do a (heavy) download of the entire user page. Not sure if the extra overhead / roundabout time from this check is really that much faster though (If at all). Excirial (Contact me,Contribs)14:13, 20 January 2014 (UTC)
The current plan is to fetch the edit token first time, and if it's expired during write, it just reparse the talk page. However while this sounds simple, coding this will take me some time. Petrb (talk) 15:05, 20 January 2014 (UTC)
Take your time. Huggle 3 is already shaping up nicely and judging from the talk page / repository check-ins you are already spending a rather sizable chunk of time working on Huggle (Not even factoring the time spend on rebuilding it in C++). Seeing the size of the project and the fact that this is for most part a 1-man-show in the development department i am actually quite impressed at the current development and fix rate. Excirial (Contact me,Contribs)19:52, 21 January 2014 (UTC)
Huggle 3 Beta install from source code on OS X Mavericks
Resolved
Everything works until I do the step "make". There it gives an error message saying something about the "duplicate member 'LocalConfig_RevertPatterns" I put the Error Message here. Feel free to delete this note if it is not important enough or if i did something wrong in my installation process. But from my knowledge of C++ this seems to be a problem in the Code itself and not in my system.--Macuser10 (talk) 15:13, 20 January 2014 (UTC)
I just read trough some source code and my guess is that it is a problem that there are those two lines (387 and 393) in the file "configuration.hpp":
QStringList LocalConfig_RevertPatterns; QList<QRegExp> LocalConfig_RevertPatterns;
and that there is two times the LocalConfig_RevertPatterns which results in an error when using my compiler because the object could have more than one property with the same identifier. But that is all just a guess. --Macuser10 (talk) 16:38, 20 January 2014 (UTC)
Yes, the source code was broken few days and nobody told me! Anyway, if you checkout last version (git pull) it will work. Petrb (talk) 16:44, 20 January 2014 (UTC)
Okay; thanks a lot. I just fixed it myself by writing LocalConfig_RevertPatternsb in the second line and then where the compiler was complaining. So now I've got my own little version :D. --Macuser10 (talk) 16:50, 20 January 2014 (UTC)
If you really just renamed the second declaration, you basically removed it. The mistake which happened before was that two separate variables were renamed to same name, so that 2 separate object were "de-facto" merged into 1 address in memory and even of a different data type. I don't know how it could even compile, but I doubt your huggle is able to recognize what is revert and what is not, given that parser needs to store these data in 2 different memory locations in order to process them. One object is a list of strings as they are in config and the other one is a list of regular expressions that represent these strings. I think that reason why it compiled is, that both types are based on QList which are compatible. But it can hardly detect a revert now give that it looks for a simple string instead of regular expression (which these definitions are). Petrb (talk) 09:34, 22 January 2014 (UTC)
okay; of course i also renamed three locations where the second decleration appeared. If there are more than those three it won't work out pretty well, i know. Thanks for the further explanation. --Macuser10 (talk) 15:14, 22 January 2014 (UTC)
wrong IP address in edit summary
Resolved
The edit summary for this apparent Huggle edit by Petrb says "Reverted edits by 72.70.186.211 identified as vandalism (WP:HG)". However, there hadn't been any recent edits by 72.70.186.211; the previous edit, corresponding to the change that was undone, had been by 173.212.50.148. —rybec00:01, 24 January 2014 (UTC)
20 September 2013? That is pretty much an old edit... Let me know if this happens for any of recent edits made by latest huggle I am sure this bug was fixed meanwhile Petrb (talk) 10:38, 24 January 2014 (UTC)
Huggle error
On my PC Huggle , which has worked fine for months , now produces the following error report on start-up
ArgumentOutOfRangeException: Value of '-1' is not valid for 'Value'. 'Value' should be between 'minimum' and 'maximum'.
Parameter name: Value
at System.Windows.Forms.ScrollBar.set_Value(Int32 value)
at Huggle.Main.DrawQueues()
at Huggle.Main.QueueSelector2_SelectedIndexChanged()
at Huggle.Main._Lambda$__410(Object a0, EventArgs a1)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
at System.Windows.Forms.ComboBox.set_SelectedItem(Object value)
at Huggle.Main.SetQueueSelectors()
at Huggle.Main.Configure()
at Huggle.Main.Initialize()
at Huggle.LoginForm.Done()
at Huggle.Misc.CallbackInvoke(Object TargetObject)
FWIW, bear with me... I always work on a laptop (XP Sp3), sometimes with a secondary monitor, sometimes without. I think I have this whenever I (1) stopped Huggle on the secondary monitor and then (2) restart Huggle with that monitor powered off or disconnected. In that case the main Huggle window is "missing", but from the task bar I can (3) maximize it, and then it jumps in maximized mode onto my primary monitor. As I hate working with maximized windows, I then have to (4) stop Huggle and (5) restart it. When I then (6) undo the maximization, the main window is very small. Finally when I try to (7) enlarge that little window by dragging the right bottom corner, I get an error report that I have never actually looked at closely, but I can imagine it would say something similar to what you have listed here. Upon that report I just (8) choose "continue" and (9),(10),... try dragging that corner again a few times, until eventually I manage to have a decent window to work with. Not sure if this will help, but it might be worth a try, I guess. Note that I can't try this right now because my second monitor happens to be out of the house for the weekend, as someone has taken it to some LAN party.
You can try some of the steps here. Perhaps it works. Perhaps not. Or you can do a system restore, bringing back your registry to some recent restore point. - DVdm (talk) 23:43, 25 January 2014 (UTC)
Thanks for that. Ignoring the error message and maximising Huggle followed by a restart fixed the problem. In only works in maximised mode now but that's fine. Regards VelellaVelella Talk 12:24, 26 January 2014 (UTC)
Glad that helped. I suspect it's a little bug with a division by zero in one of the standard windows widget object methods. - DVdm (talk) 12:31, 26 January 2014 (UTC)
Huggle 3, Build 796: user preferences issue, queuing issues, and display feature request
I am not a software development type and I'm prone to PEBCAK issues, so I apologize in advance for what is likely to be a less-than-ideally-organized bug report; please let me know what information you need that I'm not giving and I'll try to fill in any blanks. I'm using a Windows 7 system. That said, I'm noticing a few interface issues with Huggle 3 so far.
First, I have set my "Performance" user preference to "On change of page, etc...Retrieve your own edit" and saved it that way. If I'm understanding correctly, this should replicate what I'm used to in Huggle 2, where when I revert a user I can see a diff of how my edit has changed the page. However, when I revert an edit in Huggle 3, despite the set preference, I get the next edit in the queue, not my edit.
Second, the queue seems to be occasionally serving me edits I've already reverted that have already been reverted. This morning, on Eldho Mor Baselios, I was served a diff with a good-faith problem edit in it. I loaded the page in my browser, edited out that series of problematic edits, and saved the page. A few diffs later in Huggle, I was served a diff that had been made before I edited that page and that I had already reverted in my in-browser edit. Edited to add: after saving this report, I was just served a diff someone else had already reverted (this diff, at 15:22, after this revert). So the issue would seem to be edits anyone has reverted, not just edits I've reverted.
This is either because huggle wasn't notified that edit was reverted (didn't parse the reverting edit from feed for whatever reason) or because the revert summary wasn't matched by any of regexes configured so it didn't know that the edit is a revert. Did you see the revert symbol in history bar? By default huggle is inserting all edits to queue and if later someone (trusted, non IP user) revert the edit, it's removed from queue. However reverts themselves are displayed in queue, unless you filter them out in queue settings. Keep in mind that IP users often revert good edits, in order to restore their vandalism, so skipping these is not a best idea. Petrb (talk) 08:26, 21 January 2014 (UTC)
Third, and I'm sorry that I'm probably going to describe this poorly, Huggle 3 doesn't seem to keep up with page edits. That is to say...Huggle 2 had a feature where if a new edit to a page was made while I was viewing a diff, the diff would update in Huggle. The effect was that I was more or less up to date on the current version of any page before I made a decision about whether to revert. In Huggle 3, I'm shown a single diff that doesn't seem to update; quite often when I try to revert a diff in Huggle 3 I'm told "there are newer edits to the page, do you want to revert?" but I'm not shown what the newer edits are, so I have to either revert blindly or decline to revert at all (and since the queue auto-advances then, I lose that page entirely).
This is going to be implemented, but it must be tweakable, because I don't like idea that huggle just close and load different diff "under your hands" while you are checking another one. Imagine you decide this is a vandalism, you want to hit the revert and warn button, and right before that happens, different diff by another user get loaded, resulting in warning wrong user (possibly vandal fighter?). This needs to be implemented in some sane way. I think maybe a notification that a change was done to a page would be better. Petrb (talk) 08:26, 21 January 2014 (UTC)
And finally, a feature request: in the "History" panel (far right of my screen), I'd like to be able to drag and rearrange the order of the columns so that I can see the edit date first. A fluffernutter is a sandwich! (talk) 15:19, 20 January 2014 (UTC)
Regarding your 3rd point, if you click on the relevant entry in the User info tab, the History tab will update, though you then have to click on the new line in the History tab to see the new diff. Agree that it would be good if diffs could update automatically, like they used to.
ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
at Huggle.Misc.ParseUrl(String Url)
at Huggle.Requests.BrowserRequest.Done()
at Huggle.Requests.Request.ThreadDone() Dan653 (talk) 21:48, 25 January 2014 (UTC)
I get that a lot too. It commonly appears when I try to get Huggle to load a page that has only one revision, such as a recently created page. Huggle should've just normally viewed the page, but instead it tries to do something else, fails, and throws up an error. I have to manually copy the page title and load it in my browser, and then use Twinkle or something else to deal with the page. Very annoying. K6ka (talk | contribs) 16:07, 29 January 2014 (UTC)
Not certain if this is an issue, or if i am simply misinterpreting what is being displayed in Huggle. In the user info tab Huggle displays a text string such as this one: "Flags: -R + Tb Score:0 Level: 0". I am not sure what the individual flags represent but i believe that the "Score: 0" is related to the user badness score, and the "Level: 0" is the current warning level of the user.
If the latter conclusion is correct it looks as if this value is (nearly) always 0, even if a user has been warned recently. If a diff is loaded the level always seems to be level 0, no matter if the user previously received a warning. Manually loading a page and subsequently selecting an edit from its history seems to produce the same result. The only time the value seems to increase is after i revert made by myself. If i revert an edit and subsequently press [ to navigate back to that diff the user info tab's Level will be upped to 1. If displaying the current warning level is not the intention of this field i would note that such a feature would be neat - after all, a (possibly) questionable edit from a level 4 warned user deserves more scrutiny than an edit by a longer term productive editor. Excirial (Contact me,Contribs)22:47, 17 January 2014 (UTC)
regarding the level, I don't know what is wrong, it indeed should display the current user level as huggle see it (that means the warning which is going to be issued is this + 1) Petrb (talk) 09:57, 20 January 2014 (UTC)
I think that Huggle currently has some trouble detecting warnings left by applications other than itself:
This user was warned twice a few hours ago, yet reverting another instance of vandalism a couple hours later resulted in a level 1 warning.
This IP was warned by me, and subsequently warned trice again by another editor. Another revert from me resulted in a level 2 warning.
I've not encountered another Huggle 3 patroller though, so i am not entirely certain if those reverts are detected correctly (Or if it just counts mine). (Edit: Having just looked trough a large share of my warnings, i am fairly certain i can conclude the warning level always starts at 1, irregardless of any previous warnings left by other users). Excirial (Contact me,Contribs)19:39, 21 January 2014 (UTC)
Petrb: Would you mind giving me a nudge in case the warning detection is fixed? Normally i prefer using a compiled version over using my own, but right now this issue is kind of making a mess of my warnings (Whenever there are other patrols around my warning levels are off). So if this happens to be fixed i'd very much like to compile my own release from the trunk right away. Excirial (Contact me,Contribs)22:14, 4 February 2014 (UTC)
Huggle 3 Warning Issues
Huggle 3 doesn't seem to recognize previous warnings left by Twinkle users, please see this. Someone had warned them with twinkle minutes earlier and then when I reverted their edit with Huggle 3 it left a second level 1 warning instead of increasing to level 2. --Seahorseruler(Talk Page)(Contribs) (Report a Vandal)22:23, 13 February 2014 (UTC)
@Seahorseruler: - Known one, see up here. The issue doesn't seem to be solemnly linked to Twinkle trough; it seems that only warnings left by the user himself are currently recognized as such. Warnings left by other patrols don't seem to be recognized, irregardless of the tool they use. Excirial (Contact me,Contribs)23:34, 13 February 2014 (UTC)
Huggle
Hi! I was use Huggle yesterday and today. But when I update the pages, any page appear in section of pages. There are any bugs? I use huggle 2 for windows. Thanks! VitorMazucoTalk!14:14, 7 February 2014 (UTC)
I endorse the request for the above user. Was having problems with Huggle, did not appear recent changes. Appreciate it if the problem was solved. I use Google Chrome. What is happening? Thanks! --Zoldyick (talk) 00:14, 8 February 2014 (UTC)
@Developers: I suspect it was the recently deployed gerrit:107389 and the cause is that the order of the properties in the xml-response changed from ... "rcid", "pageid", "revid", "old_revid" ... to ... "pageid", "revid", "old_revid", "rcid" ... thus failing on the RegExp and the matching groups.
I will provide a patch if I can. --se4598 (talk) 19:44, 8 February 2014 (UTC)
If you have huggle version 2.1.21 or below and you are notified of an update, the auto update will likely fail at downloading the newest version. In this case please just download the newest version from the download page. --se4598 (talk) 22:44, 10 February 2014 (UTC)
Revert summaries not remembered across sessions in Huggle 2
Now working with 2.1.22, but this is a very old problem. I add an edit summary in Options, Reverting and close Huggle. The summary is saved: [11]. I start Huggle. I can use the saved summary. I close Huggle. The summary is removed: [12]. Likewise, the options/reverting window says that "summaries entered manually are remembered across sessions", but they aren't. - DVdm (talk) 12:46, 15 February 2014 (UTC)
Huggle Reporting Users that have been insufficiently warned
Huggle sometimes reports users without warning them or when they do not have a level 4/4im warning, such as this.
Maybe, the reporting user, chose to report the user using the toolbar? I know it would warn if the user has been insignificantly warned, but who knows. ///EuroCarGT00:28, 15 February 2014 (UTC)
Or install huggle 3 which actually ask you before report, and provides a dialog in which you can see whether user really has sufficient warnings and the history of user. Huggle is a program, it can't easily decide what is sufficient, and what is not, it uses just a simply math (more than 4 level warnings, report them) ;) Petrb (talk) 20:07, 19 February 2014 (UTC)
Months are not Localized (Huggle 3)
I think the months in the configuration file need to be localized, because they are written over each new page that gets a warning template. thanks, --Macuser10 (talk) 22:45, 16 February 2014 (UTC)
I managed to get Huggle 3 working on qt4 on mavericks, but I'm having problems getting it to work with qt5 (installed from brew). The first problem is that the ./configure script can't automatically detect qmake. By setting --qt5 --qmake <path>, the ./configure script works fine, but when I compile Huggle 3, I get this error,
./ui_mainwindow.h:13:10: fatal error: 'QtGui/QAction' file not found
When i install qt5 using brew, I got this message:
We agreed to the Qt opensource license for you.
If this is unacceptable you should uninstall.
This formula is keg-only, so it was not symlinked into /usr/local.
Qt 5 conflicts Qt 4 (which is currently much more widely used).
Generally there are no consequences of this for you. If you build your
own software and it requires this formula, you'll need to add to your
build variables:
LDFLAGS: -L/usr/local/opt/qt5/lib
CPPFLAGS: -I/usr/local/opt/qt5/include
Running './configure --qt5 --qmake /usr/local/Cellar/qt5/5.2.1/bin/qmake' gives no errors, but when running make, I get this error:
In file included from mainwindow.cpp:12:
./ui_mainwindow.h:13:10: fatal error: 'QtGui/QAction' file not found
I just managed to compile it, I just deleted the entire huggle directory and recloned it from git. It might have to do with the ./configure process generating some files the first time but didn't clear them out. Automatic detection didn't work, I manually entered the --qt5 and --qmake parameters. But otherwise it works now. Techman224Talk08:01, 23 February 2014 (UTC)
Feature request: genre warrior templates
Please add a genre warrior template interface to Huggle: {{subst:uw-genre1}}, {{subst:uw-genre2}}, {{subst:uw-genre3}}, {{subst:uw-genre4}} There seem to be many genre warriors doing mass changes back and forth. Jim1138 (talk) 01:42, 25 February 2014 (UTC)
Huggle 2 bug report - Windows 8.1
UnauthorizedAccessException: Access to the path 'C:\Program Files (x86)\Huggle2\Config' is denied.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, DirectorySecurity dirSecurity)
at System.IO.Directory.CreateDirectory(String path, DirectorySecurity directorySecurity)
at Huggle.ConfigIO.SaveLocalConfig()
at Huggle.ClosingForm.ClosingForm_Load()
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Thought it was a permissions issue, so I set the folder and programs permissions manually to full control, read/write, etc. No effect. Throws the same error. Huggle let's me make corrections and issue warnings, but fails to create the config folder/files. GeoffWho, me?01:29, 6 March 2014 (UTC)
Update. Well, Huggle runs fine when installed in and run from a folder under Documents. Must be due to my unfamiliarity with Windows 8 that I can't get it to run from Programs. GeoffWho, me?13:50, 8 March 2014 (UTC)
Persistent error
I have received this error multiple times:
ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
at Huggle.Misc.ParseUrl(String Url)
at Huggle.Requests.BrowserRequest.Done()
at Huggle.Requests.Request.ThreadDone()
15:20:18 Level 1 by CBNG
15:20:50 Level 1 by HG3
15:22:56 Level 2 by HG2
15:24:16 Level 2 by HG3
15:24:50 Level 3 by HG3
(block by me)
This needs fixing! It all happened quite quickly, but as far as I can see no edits appeared out of order on the IRC feed. Do I recall that HG3 only pulls edits in batches when its queue is full – might it be related to that? —SMALLJIM16:16, 31 March 2014 (UTC)
There are these 2 things that prevent this from being fixed, this bug https://bugzilla.wikimedia.org/show_bug.cgi?id=62698 and the fact that some of the warnings may not be recognized by huggle, because for example, the user who issue them uses some exotic timestamp in their signature (huggle is ignoring warnings with no or unreadable timestamp) - this really need to get fixed now. I will try to debug this but I still believe that one of reasons is just the mediawiki lacking this feature. Workaround (if you got really fast internet) is to set TalkpageFreshness to really low number, that is number of seconds how old can the talkpage be (in huggle's cache) so that it's still considered fresh. In case it's older huggle will download it again. If you set this number too low, huggle will keep indefinitely downloading it... It's a nasty workaround but one of few only solutions. Petrb (talk) 22:00, 31 March 2014 (UTC)
HA so maybe if excirial wasn't using outdated huggle: version:3.0.0.0 build: 860 98c2237 which doesn't even have the freshness thing, it wouldn't happen. Slap him when you see him. Petrb (talk) 22:03, 31 March 2014 (UTC)
Latest released beta is 1076, his version is more than 300 commits behind it, no wonder it's full of bugs. Petrb (talk) 22:05, 31 March 2014 (UTC) ok he doesn't, I just forgot the version is not on the same page now, this indeed is a bug in huggle Petrb (talk) 22:08, 31 March 2014 (UTC)
Huggle 3 Beta - Build #860 - error of delete page
"週一 二月 3 13:46:24 2014 ERROR: Unable to revert the page 美國麻將 because no previous version could be retrieved"
週一 二月 3 14:00:44 2014 ERROR: no diff available for 2007年香港電影金紫荊獎 unable to rescore
週一 二月 3 13:59:47 2014 ERROR: no diff available for 何瑞洛·纳尔逊 unable to rescore
週一 二月 3 13:58:21 2014 ERROR: no diff available for Template:BS-map/testcases unable to rescore
週一 二月 3 13:55:57 2014 ERROR: no diff available for 奥斯特立兹战役 unable to rescore
週一 二月 3 13:55:16 2014 WARNING: unable to retrieve diff for edit User:9shi/test/45 fallback to web rendering
週一 二月 3 13:55:12 2014 ERROR: no diff available for User:9shi/test/45 unable to rescore
週一 二月 3 13:55:09 2014 ERROR: no diff available for User:Ching-Hsiao unable to rescore
This has nothing to do with delete feature. The reason why it doesn't work to you is that ctrl+s wasn't bound to this feature at the time when you tried it. Petrb (talk) 16:40, 28 February 2014 (UTC)
If there is no error then it probably is not an error? Why do you think you are receiving some error? As far as I know, the huggle version you are using doesn't even have ctrl+S binded to delete command, so it's normal that it doesn't do anything when you press that Petrb (talk) 11:14, 3 April 2014 (UTC)
We are pretty close to something that seems to be stable enough to be used as a replacement for old huggle 2x, and right now we have 2 lists of release blockers:
Because bugzilla contains 0 release blockers and docs just 1 blocker right now, I assume that we are pretty close to a first release. However, my own opinion is that there is still likely many items that might need to get fixed, it's just that nobody told us and we can't fix things that we don't know about, so if there is anything you think that must be there in huggle before we release it and isn't now, it's a right time to tell us. Best what you can do is create a bugzilla ticket and set 34892 as dependency, that will make it a blocker for us. Thanks for your feedback. Petrb (talk) 09:04, 7 April 2014 (UTC)
What are the possible other things for a Mac? Who wrote that?
Mac install steps, "Install Qt: brew install qt (and possibly some other things?)" What other things? Who wrote that? Who'd know more? Banaticus (talk) 08:55, 13 April 2014 (UTC)
I can't give you exact information because I have no Mac, but as far as I know there are 2 things you need to do:
Install Qt framework
Disable breakpad in huggle (after running configure, open definitions.hpp and uncomment DISABLE_BREAKPAD
It looks like Huggle 3 is posting block notifications with wording that indicates a temporary block to users who have been indefinitely blocked. For example, User talk:Banclark45 is indefinitely blocked from editing, but the block notice says, "If you wish to make useful contributions, you may do so when the block expires". This should be amended to something more helpful, like {{Uw-voablock}}. Mz7 (talk) 20:04, 25 April 2014 (UTC)
Hi. Just wanted to say that after using Huggle 3 for I while, I can feel that it is significantly faster than Huggle 2, and the overall experience is much smoother and friendly. Thanks for you good work!
There are, however, a couple of feature from HG2 that I miss, and feel that they helped create a better experience. First and foremost is the red font highlighting the differences between revisions. This really helps to pin down the exact changes made to the article, and I feel the current implementation of simply putting changes in bold text doesn't really create a easy-to-read experience.
Secondly, I really do miss the drag down menu next to the Revert and Warn (Q) button. Often it helps to be able to comment the revert with something more accurate than just 'vandalism'. This may be a design decision to cut down unnecessary elements in the interface, I don't know, but it's something I feel would be a nice addition.
On that note, is it possible to revert and warn with a custom revert summary now? If it is, then it's certainly very hard to find (^^;). Again, it's just because each edit is unique, and some of them really need their own summaries to fully explain the nature of the vandalism.
On the positive side though, the flag as good (G) and flag as suspicious (S) are really neat! I feel that revert assuming good faith (Y) could be more prominently displayed, but overall the interface is a lot cleaner, responses are faster, and the overall experience is great! Thanks. CommandConquerer Logs 08:35, 16 April 2014 (UTC)
There still is that revert menu, its just that Qt framework uses different buttons than .Net, the dropdown is not on a side of button, but is activated by holding the button for a while. I don't know how we could make it more clear, there are limited options for this in Qt. 90.183.23.27 (talk) 08:41, 16 April 2014 (UTC)
Indeed. I had raised that before. It's a QT feature, and one of the reasons why I will never start using H3—hoping of course that H2 will not be strangled. - DVdm (talk) 08:46, 16 April 2014 (UTC)
ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at Huggle.Misc.ParseUrl(String Url)
at Huggle.Requests.BrowserRequest.Done()
at Huggle.Requests.Request.ThreadDone()
at Huggle.Misc.CallbackInvoke(Object TargetObject) --Novusuna (talk • contribs) 23:06, 16 February 2014 (UTC)
ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
at Huggle.Misc.ParseUrl(String Url)
at Huggle.Requests.BrowserRequest.Done()
at Huggle.Requests.Request.ThreadDone()
Happens to me all the time. Usually occurs when trying to load a page with only one revision (ie a new page). I usually open the page in my web browser and use Twinkle to deal with it. --k6ka (talk | contribs) 23:56, 8 April 2014 (UTC)
Stuckkey reported the following bug on pt:Special:Diff/38843455: Two days ago Huggle started to have some problems. To receive the "Filtered edits" we must go on "options" and uncheck "use the recent changes IRC feed if possible" every time one logs in. Otherwise it doesn't show any recent changes. This happens both in the new version and the old one. Helder.wiki11:21, 7 May 2014 (UTC)
I initially thought that this was a problem everyone was getting, but looking at this page it seems like that's not the case. After I login, up pops a warning - "Failed to download the whitelist, continue?" with options Yes and No. This has been happening for more than two days now. No proxy; 2.1.22; Windows 8.1. Thanks, -download׀talk00:40, 3 May 2014 (UTC)
Same here. If I counted correctly, since four days, Huggle 2.1.22 fails to download the whitelist, both on XP3 and Win8.1. Huggle 3 has no problem. - DVdm (talk) 08:16, 3 May 2014 (UTC)
Yes and that fixed it even more :P now you can even write to whitelist (I fixed only reading issue before, now it's both) Petrb (talk) 18:58, 4 May 2014 (UTC)
We need your help trying to find all bugs and gliches to make the final stable version of Huggle done, so we can fix them as fast as possible. If no-one reports them, they won't be fixed! (Simple logic!)
Remember to use this tool at your own risk and if anything goes wrong, it is up to you to fix the articles again...but so far (a few months) nothing terrible has happened! Thanks. (t) Josve05a (c)22:26, 10 May 2014 (UTC)
Thanks logs being listed as edits
Hi. Just reporting that version 2.1.23 is listing thanks logs on filtered edits. Sorry if that was previously reported. Hope you can fix that. Thanks.—Teles «Talk to me˱M@CS˲» 23:09, 18 May 2014 (UTC)
Wording correction
This is a grammar mistake in one of Huggle's templates: "Hello, I'm XXXXX. I wanted to let you know that I undid one of your recent contributions, such as the one you made with this edit", possibly reword to "Hello, I'm XXXXX. I wanted to let you know that I undid the contribution that you made with this edit". Philg88 ♦talk16:52, 14 May 2014 (UTC)
Done using a slightly different wording, since part of the sentence depends on whether the diff parameter is passed to the template. Waldirtalk19:14, 3 October 2014 (UTC)
Welcome Personal template doesn't auto append signature
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Questions
Sometimes, I wish to mark the edit as just an edit with no stipulation. (IE: No AGF or any other qualifier). This would be the equivalent of just using Twinkle's middle 'rollback' button. However, on Huggle 3.0, you only have the choice of doing a good faith revert or a vandalism revert, or just a revert in general.
Example. I spot a test edit. I don't want to manually type out 'test edit' into the 'assume good faith' box. I want to be able to use a dropdown to select 'test edit' and then revert it. The old Huggle had this. Does 3.0 have it?
Additionally, is there anyway to template for other issues? Other than vandalism? Like, editing tests specifically. Thanks. Tutelary (talk) 22:01, 24 May 2014 (UTC)
When I held down the revert button, it only reverted the edit I was on. (and a few others last time I tried it) That appears to not bring up any dialogue box on Huggle 3.0 Tutelary (talk) 22:32, 24 May 2014 (UTC)
It doesn't, it just reverts. I don't want to mistakenly revert any one's edits again just to test this. Tutelary (talk) 22:41, 24 May 2014 (UTC)
@Tutelary: Are you both talking about the same revert button here? The revert button can be R on the keyboard, but it can also be the button in the menu strip. If you hold down the R key it will indeed revert the the edit without warning, and possible other edits afterwards. If you press the revert button in the menu and hold for a few seconds, it will display a dropdown with options for the revert. Excirial (Contact me,Contribs)10:42, 25 May 2014 (UTC)
Hmm, that solves that problem. But how come it doesn't automatically issue warnings for the content choice? For example, a test edit warning for a test edit. Tutelary (talk) 14:34, 25 May 2014 (UTC)
It should do that. Which button in the menu did you press? There are three pessible buttons you can press. The red "pen"-button, with an orange ! is the "revert-and-warn"-button, while the button which is only a "red pen", is only reverting the edit, and the orange "!"-button is only a warn-button. (t) Josve05a (c)14:37, 25 May 2014 (UTC)
DERP. DERP DERP. K, managed to figure it out. Instead of holding down the "Q" or the "R" key, I had to use the mouse button to left click and then set the option that applied. Thanks you guys. Just a derp moment for me. Tutelary (talk) 16:29, 25 May 2014 (UTC)
Huggle 3 scaling problems on high DPS screen
Just wanted to report that I am encountering some scaling issues with Huggle 3 on my high DPS 2560x1440 13.3 inch laptop screen.
Sorry if this is already a known issue. :) -download׀talk22:58, 7 May 2014 (UTC)
Is this happening on other forms? I think that login form is fixed in latest version, which should be released soon. Let me know if it was happening in some other forms too Petrb (talk) 09:15, 8 May 2014 (UTC)
Did you try making the windows larger? Just click on window corner and enlarge it, login form is now resizable Petrb (talk) 13:28, 21 May 2014 (UTC)
Sorry about the late response - yep, just updated and it looks great! Thanks :) The diffs are still slightly small so it would be great if a scale option were added. -download06:57, 30 May 2014 (UTC)
Huggle 3 additional warnings
In huggle 3, is there a way to add warning templates that are not included by default? For example, uw-advert. I know in huggle 2 there was a way in the options (some sort of template tab), but that doesn't exist in Huggle 3. I'm sure there is some way to implement this, somehow.
This is possible in huggle 3.0.1 which will be hopefully soon released, but you really should add these new warnings project wide instead of keeping them for yourself, unless they are really very custom Petrb (talk) 15:36, 3 June 2014 (UTC)
Huggle 3 runnable without administrator privileges?
I tried running Huggle 3 on my school-loaned laptop, and User Account Control popped up asking me for the administrator password, which I do not have. I can run Huggle 3 on my personal computers, but (admittedly) my school laptop performs better than my personal ones (even my desktop!). Is it possible to get Huggle 3 to run without local administrator status/password (just like Huggle 2)? --k6ka (talk | contribs) 11:43, 4 June 2014 (UTC)
Yes, unfortunately we don't provide these .zip packages, so you have to make it. Just install huggle using installer on any computer where you have admin rights, then just copy whole folder from Program Files. Huggle doesn't use windows registry for anything and all .dll files are bundled with it. Only reason why it requires admin rights, is that Program Files aren't writable by regular users. It can be anywhere on disk. Petrb (talk) 14:17, 4 June 2014 (UTC)
Regarding performance issues can you provide some details? I was testing huggle3 on 800mhz pc will less than 512mb ram and it was running fast as hell (compared to huggle2 that would hardly load on that box). Petrb (talk) 14:29, 4 June 2014 (UTC)
Ubuntu doesn't support Qt5 in any version. You need to use some unofficial repository for them Petrb (talk) 12:55, 9 June 2014 (UTC)
Bug
I got logged out and for some reason, it still allowed me to revert with the tool. I'd link it, but then I'd be exposing my IP to everyone...anyone who I should email the links to the contributions? Tutelary (talk) 02:18, 14 June 2014 (UTC)
Just downloaded and installed 3.0.2, running on QT 4.8.6, OSX 10.9.3. Occasionally, maybe every 20-30 edits, Huggle will spike in CPU to over 100%. The application then becomes unresponsive and can take about 15 seconds or so to return to normal. Any ideas on this? Apologies if this is a duplicate report. — MusikAnimaltalk16:55, 16 June 2014 (UTC)
No this is new to me, can you start huggle in a debug mode? (Run ./huggle -v or more -v for more verbosity) that will provide some extra information. I am most interested in QGC number which should be in status bar (it display number of items managed by GC). That is the only thing that comes to my mind which could cause this. Also you can see debug logs in terminal, maybe you will see some connection when it lags. Petrb (talk) 17:51, 16 June 2014 (UTC)
I have been testing it heavily, I can't reproduce it. I was doing things like holding the [ key just to roll over 20 edits, and still, not even a small lag. I was doing this on 1ghz cpu, with only less than 100mb of ram free. It ran just fine. Petrb (talk) 22:01, 16 June 2014 (UTC)
Yeah, I'm not sure... It was happening quite frequently earlier today but now seems to be running just fine. I'll continue to run Huggle in debug mode and will report back with results should issue arise again. Thanks for your help! — MusikAnimaltalk22:22, 16 June 2014 (UTC)
I left Huggle 3 running by accident for over half-an-hour yesterday. When I got back, the program hung repeatedly for about thirty seconds, and then resumed normal operation. Huggle 3 also hangs whenever it tries unsuccessfully to connect to the HAN, which happens whenever I use Huggle on a bad Internet connection (such as my school's WiFi). However, it's never a major issue, just a minor annoyance. --k6ka (talk | contribs) 13:53, 17 June 2014 (UTC)
Hmm not sure if that was the issue I had. Where I have been using Huggle I have super duper fast and reliable internet.
To update you @Petrb: I have not experienced the CPU spike again, however I have had the app crash on me, apparently due to a Segmentation fault: 11. No other relevant log output. This happened after 10-15 minutes of inactivity and crashed without the app in focus. This has happened a few times since I upgraded to 3.0.2, I don't recall this with older versions. I have the full "problem report" that Apple generated, which I have emailed to you. I'm not sure if you want to create a new ticket in Bugzilla just yet as I have a hunch the issue may be completely on Apple's side. Perhaps you will be able to tell that. Hope I've been of some help. — MusikAnimaltalk16:54, 17 June 2014 (UTC)
Huggle 3 refusing to revert
Occasionally I get this odd error with Huggle 3, in which I hit revert and it throws this message in the system logs:
Fri Jun 20 12:49:02 2014 ERROR: Did not revert {{PAGENAME}}: because it was edited meanwhile
Fri Jun 20 12:49:02 2014 WARNING: main-revert-manual
BTW you can run huggle with parameters -v (or more like -vvv) which will make it more verbose. The reason why it thinks that page was edited meanwhile is then displayed in debug logs. Petrb (talk) 17:02, 20 June 2014 (UTC)
Turning off requirement for rollback on english wp
Hi,
I would like to change the configuration for this requirement:
There is number of other tools similar to huggle which do not require it and may be just as dangerous as huggle.
Some people who are dealing with vandalism may not like the bureaucratic process of requesting permissions on en wiki, but are experienced enough and want to use huggle.
The proposed change would be: require rollback or 500 edits to wikipedia in order to be allowed to use huggle.
Think we could go with STiki's example - either have rollback or upon special request. Er, change the "special request" part to require a specific amount of edits. I think 500 edits is a bit too low. However, you mentioned that "there are tools similar to Huggle and it might just be as dangerous". Isn't that opening another door for potential wiki-destruction? --k6ka (talk | contribs) 17:23, 20 June 2014 (UTC)
I'm concerned about expanding mass undoing features to users who don't have rollback. I get that STiki has an alternative edit requirement, but Huggle has more power in terms of reverting multiple edits, more pages to choose from as opposed to being presented with them, and is generally faster-paced (in my personal experience) and easier to make mistakes with. Streamlining WP:RFPERM is a laudable goal, but I don't see how it's too bureaucratic - you post on the board and an admin says yea or nay. It's not like you are forced to enroll at WP:CVUA or anything. BethNaught (talk) 17:43, 20 June 2014 (UTC)
Huggle 3 cannot scan Discusions
Hallo, Huggle 3 cannot scan the Discusion Site. Or I found not the Option.
But scanning and editing Diskusions with Huggle is very important, as it also contains a lot of vandals wreak havoc.
Sorry for the bad English --Natsu83 (talk) 08:22, 15 June 2014 (UTC)
Does the queue filter is implemented? I've tried to use it but I got no success. Actually I'm using the Huggle3 QT-LX 3.0.3 build: 1697 3.0.3 in the pt.wikipedia.org community.
When I select one option in the queue filter, I don't get pages filtered, no matter what I select I see the same result. Guiwp (talk) 20:23, 24 June 2014 (UTC)
Yes it works, but differently from legacy huggle as "require" option is not yet implemented. So for example filters like "new pages" don't work. It's only possible to filter items now, eg. you can filter specific items out of feed, but you can't request to filter everything except specific items. Petrb (talk) 21:17, 24 June 2014 (UTC)
Particularly I would like to see only modified pages that I've in my watchlist. Is it possible? When I select "Páginas vigiadas" (pt-BR of watched pages) I see no change in the list. Guiwp (talk) 23:31, 24 June 2014 (UTC)
Could we change the revert assuming good faith edit summary to "Reverted good faith edits by ...", linking "good faith" to WP:AGF? People who happen to click the link will be then become exposed to one of our core fundamental guidelines. Just thought it'd be a good idea! Thanks — MusikAnimaltalk18:54, 9 July 2014 (UTC)
Hi all, I noticed Commons has a category of the Huggle 3 iconset, but I cannot seem to find the iconset of the previous generation. Can someone direct me to it if it is online? --Rsrikanth05 (talk) 10:44, 19 July 2014 (UTC)
Yes, basically all graphics including red ball (not including custom version with huggle text) were taken from elsewhere, mostly KDE project Petrb (talk) 18:43, 19 July 2014 (UTC)
Oh, okay. I guess, I can add an additional category for them on Commons as Huggle 2 icons. Since they are anyway under a competent licence. --Rsrikanth05 (talk) 19:40, 19 July 2014 (UTC)
In version 3.0.5, the user info pane is blank for me. It used to give a user's other recent edits, which was very useful. What happened? I am using Chrome on Windows 7. BollyJeff|talk02:21, 20 July 2014 (UTC)
make huggle remember your login credentials (single click logon)
In huggle 3 it is possible to create a shortcut which if clicked, huggle log you in without asking for a password. I didn't think many people would like to use this feature, but based on IRC feedback I decided to share this information here. Feel free to create a howto page somewhere (I guess /Tips could be created?):
Create a plain text file somewhere on your HDD and put in it (replace with your username and password):
user:passwd
Create a shortcut that will point to huggle.exe (or huggle binary on UNIX systems) and append these parameters:
How does this have anything to do with BEANS, I am not telling you not to do something. I am telling you that you can do this. I just didn't think that someone would want to do that. That doesn't mean I think you shouldn't. Storing password in huggle is just as insecure as storing it in your browser and lot of people already do that. Petrb (talk) 12:46, 21 June 2014 (UTC)
I'd like to add a suggestion to Huggle. Right now, I changed my internal Wikipedia settings to not watchlist articles I revert or edit unless I manually want to select that box. What I encounter is sometimes on pages where there is long term IP vandalism, I manually have to get out of Huggle and watchlist the article manually. What I would like to suggest is the possibility of a keyboard combination to watchlist/unwatchlist an article/talk page/template/etc. Thank you. Tutelary (talk) 23:47, 5 July 2014 (UTC)
I keep hearing about Huggle 3 supporting optional extensions, but I haven't seen much else otherwise. Does anyone have any information on this? --k6ka (talk | contribs) 17:23, 4 July 2014 (UTC)
Yes, there is not much description on how to create these extensions, so right now there are just 2 available, but I am going to create some documentation so that people can start easily creating new, possibly extending huggle to all their needs. For beginning you can read:
What operating system? I can't reproduce this on linux. What Qt version you have? Can you paste the about line? (Version: 3.0.5 build: 1826 3.0.4-30-g0e5dd04 without python support, compiled using QT 4.8.6 Running on QT 4.8.6) Petrb (talk) 20:07, 14 July 2014 (UTC)
Version: 3.0.5 build: 1826 3.0.4-30-g0e5dd04, with python support, compiled using QT 5.2.1 Running on QT 5.2.1 works Petrb (talk) 20:11, 14 July 2014 (UTC)
I encountered this edit during a patrol of recent changes using Huggle. I reverted the edit but no action was taken on the article. I tried again and the same thing, nothing. I opened the page in my browser and reverted the edit manually. I am guessing that the pending changes protection confused the matter, and if so, it should be corrected I believe. Can anyone confirm if this is a known bug?—John Cline (talk) 08:07, 17 July 2014 (UTC)
What version of huggle is that and can you provide some logs? It's nearly impossible to check what the reason was for it not being reverted without logs. Petrb (talk) 13:50, 17 July 2014 (UTC)
I am using version 3 at the moment; haven't upgraded yet, and am still learning some of the new functionality. I am not entirely certain how to gather the logs you are requesting, or if it is possible to gather them from a closed session. I thought perhaps a test could be replicated on a page under pending changes to evaluate if it is that protection which hampered the reversion I had initiated. I strongly believe there is a causal relationship. Otherwise I will gather as much information as I can to assist researching the matter further. Thank you.—John Cline (talk) 15:39, 17 July 2014 (UTC)
Ok I can do that. Regarding logs: you can start huggle with parameter --syslog so that it creates a file huggle.log which contains same information as you can see in main windows of huggle Petrb (talk) 16:44, 17 July 2014 (UTC)
After evaluating every drop-down menu on the Huggle interface, reviewing every link within this page's header, and double checking myself, I was unable to determine the correct manner of "starting Huggle with |syslog= in place". Please tell me, using slightly more detail, how I can effect the parameter changes so as to begin maintaining a log such as that which you described. Thank you.—John Cline (talk) 06:29, 18 July 2014 (UTC)
Every program can be started with some parameters, most simple way to accomplish that is to use either command line, or to create a shortcut which you later modify, see picture: How to start huggle with some parametersPetrb (talk) 12:31, 18 July 2014 (UTC)
In your case you use --syslog instead of -vv (or both: -vv --syslog) note that path of program needs to be in quotes as on screenshot "c:\program files\blabla.exe" --parameter1 --parameter2Petrb (talk) 12:33, 18 July 2014 (UTC)
New Logo
I woke up today to find Huggle giving me the finger! At first I thought it had been vandalized. The new logo is awful! Change it back! --Sue Rangell✍ ✉18:02, 12 June 2014 (UTC)
That old was not a logo of huggle actually, but a free picture that was stolen from KDE nuvola icon set so that we have at least some picture :P this one is at least a proper huggle logo. On other hand if you don't like it, you can draw a better one! Petrb (talk) 21:02, 12 June 2014 (UTC)
Haha! I always told myself it was a broom, but in the end I couldn't identify it as an object at all. By the way... if it is giving you the finger, turn your monitor around to face the vandals. That'll teach them!! --k6ka (talk | contribs) 16:40, 13 June 2014 (UTC)
Actually @Petrb:, I might just take you up on that, if at least to see if it can fit in better with the visual language and the move away from the Nuvola iconset. tutterMouse (talk) 12:18, 17 June 2014 (UTC)
Okay, no response for two days. Very well, I'll just link to them and see what others think but the basic thing is the current one isn't nice and doesn't look that much like a floorbrush or anything else so why not a broom? I have two other ideas in case the broom isn't clear enough (I feel it looks slightly like a butterchurn). Anyway, a link to the "Broom" idea & those two other brushes as maybes. Hope to hear what people think! tutterMouse (talk) 17:35, 20 June 2014 (UTC)
Of course there was no response because there was no logo :P now when you shared it... not bad. I like the broom on second picture, where are actually 2 of them. Can you split that to multiple files? We need that logo in 2 sizes + some .ico files (64x64 and 32x32) Petrb (talk) 21:16, 20 June 2014 (UTC)
Which one do you mean on the second one, the left or the right? I still would say that those two are the most uninteresting and bland options I could have made and would far prefer the standalone logo be the one we use. tutterMouse (talk) 06:50, 21 June 2014 (UTC)
Also, I expected a response because I asked you a question, once on your usertalk even which you also completely ignored. I don't know what my expectations are when it comes to interacting with you but I did wait two days for one response, one you failed to give and I had to figure out as well as told "I didn't give you a response because there was nothing to see", I couldn't show you anything because I was asking how you'd like me to do it! I'd prefer if you try to give level concern to things rather than responding to others in a timely manner and leave others with their hands in their pockets like they asked nothing in the first place though they're trying to help your project out. tutterMouse (talk) 14:03, 21 June 2014 (UTC)
Well, being team lead in the absence of Addshore would make it yours, wouldn't it? I felt it was yours, I know Gurch made it but it is in your hands these days! Still, I see which you want now of those two but if you could give me a list of sizes and formats you'd like me to make and possibly email them to me or leave them on my talkpage it'd be incredibly helpful. tutterMouse (talk) 15:33, 21 June 2014 (UTC)
Ideally speaking, we could have a mini design event, where people can submit their own logos and/or iconsets which will be on the Commons, one of which can be used by HG after a public poll. The remaining will be on the Commons and hence can be used elsewhere. --Rsrikanth05 (talk) 10:47, 19 July 2014 (UTC)
Huggle 3.0.4 crashing
I've seen several crashes. Collected info from the last one.
Problem signature:
Problem Event Name: APPCRASH
Application Name: huggle.exe
Application Version: 0.0.0.0
Application Timestamp: 53ad1d40
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18247
Fault Module Timestamp: 521ea91c
Exception Code: c0000005
Exception Offset: 00052d37
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Huggle version: 3.0.4 build: 1796 3.0.4 without python support, compiled using QT 5.1.1 Running on QT 5.1.1; running on Win7pro with SP1. Wtmitchell(talk) (earlier Boracay Bill) 05:32, 11 July 2014 (UTC)
Moved from Wtmitchell user talk page, he states: On that particular crash, I had huggle open in one window, was looking at another non-huggle window, and got a pop-up notification that huggle had crashed. The pop-up had a clickable option to view details, so I did that, cut&pasted those details, and posted them as feedback. I have seen occasional similar crashes before and after that one, sometimes as I was working in the huggle window and sometimes as I was working somewhere else with a huggle window open.///EuroCarGT01:04, 18 July 2014 (UTC)
Another instance
I had returned to the computer after a brief absence and saw the huggle window open but grayed out and unresponsive to up/down arrow input from the keyboard. As I was sitting hoping for the grayout condition to cleared, I got a popup notice that huggle had crashed. Following is the detail info:
Problem signature:
Problem Event Name: APPCRASH
Application Name: huggle.exe
Application Version: 0.0.0.0
Application Timestamp: 53ad1d40
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18247
Fault Module Timestamp: 521ea91c
Exception Code: c0000005
Exception Offset: 00052d37
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
If it is useful for me to report similar information as I see other crashes, let me know and I will do that; otherwise I won't. Wtmitchell(talk) (earlier Boracay Bill) 00:28, 19 July 2014 (UTC)
That crash was probably 3.04. I am now using 3.05 and just had it crash on me but did not collect crash details. If it is useful for me to do that, let me know and I will do so for future crashes. Wtmitchell(talk) (earlier Boracay Bill) 00:46, 20 July 2014 (UTC)
Some options not saved, and a question
Under the interface tab, there's an option for "Page title in every diff ...". It works if set, but comes up unset when Huggle is reloaded. I've noticed this for this particular option, and have not tested whether other options might behave similarly.
Earlier, I had a working setup with this Huggle version which had an editable field for page name, and also had a user history contributions pane below the page history pane. I accidentally undocked the history panes and couldn't figure out how to re-dock them so I exited and reloaded Huggle. On reloading, I found that I had no editable page name and no history panes. I've gotten the page history pane back by changing options, but haven't found how to get the user history contributions pane back. Help appreciated if you have time. Wtmitchell(talk) (earlier Boracay Bill) 06:02, 18 July 2014 (UTC)
Thanks. I got the user info pane opened and docked. I now have all options listed there enabled, except for Tools, which is grayed-out. I still do not have the editable field for page name (with a Load button beside it)which I had earlier. Wtmitchell(talk) (earlier Boracay Bill) 22:08, 18 July 2014 (UTC)
Simple workaround is to remove layout config from your configuration folder (huggle tell you that in system log) there is file called mainwindow_state and mainwindow_geometry, try removing first one and even second one if it wouldn't help. On other hand the tool bar is meant to be uncloseable :P how did you close it? Petrb (talk) 06:31, 19 July 2014 (UTC)
I'm now using Version: 3.0.5 build: 1849 3.0.5 without python support, compiled using QT 5.1.1 Running on QT 5.1.1
On the toolbar, the right-click menu on the toolbar contains a checkable box labeled "Toolbar". Unchecking that gets rid of the toolbar.
On the config files, Windows can't find any files with names including "mainwindow". There's a directory on my Win desktop named "Config" containing directories named "Queues" and "Whitelists" and a file named "config.txt". That looks like huggle stuff (and I opine that it is inviting trouble to presume for an application to presume ownership of a desktop directory named "Config"). I tried renaming the "config.txt" file "config.txt.sav" then exiting and restarting huggle, but that did not get me the editable article name and the "Load" button back.
Removing the mainwindow_state file did it. Thanks. One of the directories in the path to that file was hidden, and that's probably why asking Win7 to search for files with "mainwindow" in the name didn't find anything. Cheers. Wtmitchell(talk) (earlier Boracay Bill) 02:16, 20 July 2014 (UTC)
Not detecting my OS
Huggle updater is unable to determine my OS. I'm using Windows 7. Is there any reason why it is not detecting it? Or is it an issue with Huggle for Windows? --Rsrikanth05 (talk) 04:29, 22 July 2014 (UTC)
There's currently no other text implemented in the updater in the case a manual download is required (currently almost always). At least to mention the OS right in the text if it is detected was on my ToDo list for the next week. --se4598 (talk) 08:10, 22 July 2014 (UTC)
Aaah. Okay. Got it. Thanks. --Rsrikanth05 (talk) — Preceding undated comment added 05:08 23 July 2014 (UTC)
Changes in huggle3.css
Hi, I think I'm having a little bug with huggle here. Every time when I close the program, it changes my huggle3.css page with (I guess) unnecessary editions. It always takes a line and puts in another. There is any way to stop that?
It's normal, not a bug, every time you exit Huggle, the huggle3.css has to be updated, this is in case you change the program settings, the settings are outputted into the page so the program could read and input it. This page also has to be updated once a new release of Huggle comes out, since new features are implemented. ///EuroCarGT19:25, 24 July 2014 (UTC)
This has been there since the release of the first version. It i actually helpful as all your settings are stored online rather than locally. --Rsrikanth05 (talk) 19:50, 24 July 2014 (UTC)
I thought it was a bug because some time ago (last year) I was using the Huggle and I don't remember these changes, and now, every time it happens. Anyway, thanks! Editeur?20:07, 24 July 2014 (UTC)
Last year, you would have probably used Huggle 2; which AFAIK, updated the page only once when a new update was released. --Rsrikanth05 (talk) 20:19, 24 July 2014 (UTC)
I don't think I've reported a 3.0.6 crash yet. Here's the details of one I just saw. Huggle Version: 3.0.6 build: 1854 3.0.6 without python support, compiled using QT 5.1.1 Running on QT 5.1.1; being run on a 32 bit Win7pro system with SP1:
Problem signature:
Problem Event Name: APPCRASH
Application Name: huggle.exe
Application Version: 0.0.0.0
Application Timestamp: 53cc2fe2
Fault Module Name: huggle.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 53cc2fe2
Exception Code: c0000005
Exception Offset: 000a9c34
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
I had the huggle window open at the time of the crash, but I had just returned there from another window where I had been googling.
If it is useful for me to report details on additional crashes with this version let me know. If it's a waste of time to report these crashes, please let me know. Wtmitchell(talk) (earlier Boracay Bill) 05:57, 25 July 2014 (UTC)
yes it is useful but it would be more useful if I could have some more details like:
What is your OS
What is version of huggle you run
Huggle internal logs (from system logs window) I know you can't copy them when huggle crashes, but you can always start huggle with option --syslog which will create huggle.log file and put all these in there
Huggle 3 is able to rollback edits, but is unable to warn the user afterwards. The error I'm getting in the System logs is:
ERROR: Unable to deliver the message to <IP OR USER>: Unknown error: badtoken
I run with Huggle 2 open as well, so I typically just jump over to Huggle 2 and warn the user from there, or I open up the user's talk page and warn with Twinkle.
The new interface is taking some getting used to, but I've had no errors and a pretty smooth performance from Huggle 3.1.0 Beta. —Josh3580talk/hist06:11, 3 August 2014 (UTC)
Huggle 3.1 feedback
Hello,
Sorry about not trying out the new Huggle—I've been gone from Wikipedia for a long time. Anyway, here's my initial feedback:
The "This is not the latest revision" popup doesn't go away immediately when you navigate away from the page (by pressing space for example), which seems really confusing.
Build fails (Linux/Ubuntu 14.04) with the --python flag. Haven't been following development at all so not sure if that should be happening.
There doesn't appear to be a key-binding for "Clear queue". In the old huggle this used to be Ctrl+SPACE.
Is there any way to customize queues by namespace? I couldn't find one.
(edit) I also notice that in some cases when huggle auto-loads the newest revisions for a page, the user listed at the top becomes incorrect.
if it fails with --python you need to provide us some details, anyway, it's a problem of python, not so much of a huggle. Ctrl + space does clear a queue, but it doesn't work in latest ubuntu because it ships with bugged Qt (there is a number of reports for that). 90.183.23.27 (talk) 08:11, 1 August 2014 (UTC)
Regarding --python, firstly it looks like it uses Python3, not 2, which I didn't see in the documentation. If it is configured with libpython2, it will fail to build (with bizarre errors). If you try to configure it against libpython3, it will fail to configure, as CMake apparently has issues finding it. I had to provide -DPYTHON_INCLUDE_DIR and -DPYTHON_LIBRARY in configure manually. Then it built fine. lartoven (t·c) 19:57, 1 August 2014 (UTC)
Just like the previous message, Huggle 3 is unable to warn but reverts well. But no message came up, I tried restarting it, but the problem still occurred. I used the keyboard shortcut Q and it only reverted. I looked for another case and pressed the Warn and revert button and it worked. Is there a problem with the keyboard shortcut? Or is it just something I did wrong with my Huggle settings, thanks, ΤheQ Editor Talk?17:35, 18 August 2014 (UTC)
Q is the right shortcut. Do you have any diffs where you only reverted (so that we can check the user talk page connected with the edit)? (t) Josve05a (c)20:30, 18 August 2014 (UTC)
trying to install
I'm trying to install, but get message " Login failed on enwiki: You don't have enable:true in your personal config." What is this referring to? The install instructions don;t mention it. DGG ( talk ) 18:18, 27 August 2014 (UTC)
Reverting blatant vandalism using rollback is sensible, even if there were some good edits in the mix. But when you want to revert a good-faith edit, you may more often times only want to revert only the revision visible in the Huggle browser. Is there a way to do this with "revert assuming good faith", where I can supply a custom edit summary?
Also, is there were a way to show the diff of all the edits you are about to revert? E.g. in the MediaWiki page history interface you can use the radio buttons to compare any two revisions. The ability to see everything I'm about to revert may shed light in some scenarios, where you think the edit is unconstructive but in actuality it coincides with prior subsequent edits by that user, that collectively can be considered constructive. — MusikAnimaltalk22:26, 26 August 2014 (UTC)
I am still a new Huggle user (about 24 hours old), and I really love it. However, I am not sure if I am missing something; but I couldn't figure out any feature in the software to mark revisions as flagged, which is actually a bit disappointing. In Wikipedia versions that uses the flagged revisions system, you'll always have to do one of two thing when you are reviewing a new user's edit; you'll either have to revert it or to mark it as flagged. In Arabic Wikipedia, we have already thousands of articles with edits pending to be flagged, some edits have been pending for over a year. If this feature is available on Huggle, it would be truly very very helpful! --Abbad (talk) 11:18, 22 August 2014 (UTC).
Another (minor) issue. I warned a user without deletion for editing tests (yellow button). To my surprise, the message on his/her user page said: has been deleted - while in fact it has not been deleted. So the action is OK, but the message is wrong. Can you fix this? Or am I mistaken somehow? Super48paul (talk) 13:45, 7 September 2014 (UTC)
This isn't that simple, there are warning templates on wiki: Template:Huggle they say "Your edits to blabla were reverted". These would need to be reworded a bit for this to get "fixed". Petrb (talk) 08:04, 8 September 2014 (UTC)
Welcoming?!
Since using Huggle, I seem to be welcoming new users. Presumably whenever I accept an edit (and the editor is new), the software puts in a welcoming message. Is this happening indeed? intended? and laudable practice? or a bit superfluous?!Super48paul (talk) 14:08, 7 September 2014 (UTC)
If you rate the edit as a "good edit" and lower the user badness score, the user will be given a welcome message if they haven't received one already. Pretty sure that's how it works, though I personally prefer welcoming users with Twinkle. --k6ka (talk | contribs) 16:55, 7 September 2014 (UTC)
Huggle 3.1.1 does not open pages in external browser
I have reluctantly started using Huggle 3.1.1 (due to the inability of Huggle 2.x to warn users now) but I can't open pages in an external window. Whether I click the icon, use the menu option, or press O, nothing happens. Any ideas? (My default browser is Chrome and I'm using Windows 8.1.) ...discospinstertalk17:35, 7 September 2014 (UTC)
I use Huggle in pt.wiki and I realized that Huggle 3 is failing to filter results listed in the queue. This bug is already known? (Huggle 2.x does not present the same problem). --Diego Queiroz (talk) 22:23, 3 September 2014 (UTC)
I will try to check this, but you need to be more specific I need to know which version of huggle you have (open help -> about to see it) and also which queue do you mean? Petrb (talk) 09:24, 4 September 2014 (UTC)
I am using the last version available over Windows 7 (Version: 3.1.1 build: 1966 3.1.1 without python support, compiled using QT 5.1.1 Running on QT 5.1.1). Actually the problem is not with an specific queue. The queue selector has no function at all for me (which means all queues displays the same behavior). Regardless of the option I choose, my queue is populated with all types of edits (possibly the "default" queue). --Diego Queiroz (talk) 14:35, 4 September 2014 (UTC)
When you change the filter, it doesn't change what you currently have there, it will only filter in a different way. You can also check preferences in order to create some new queues. I can't really reproduce it because it works fine to me, can you tell me which queue for example doesn't work? Did you try queues like "All new pages" etc. Petrb (talk) 18:52, 6 September 2014 (UTC)
So I really think this problem is somewhat related with the pt.wiki, and for some reason it does not affect other languages. I know how the filter works (I am a programmer also), and even if I clear the queue it continues to be populated with all kinds of edits, it doesn't really matter what filter I select. As I stated before, the legacy version (2.1.23) does not present the same problem. If for testing purposes you need an example, here is it: for the pt.wiki there is a queue named "Propostas de eliminação rápida" (transl. "pages for speedy deletion"). In this filter, the queue should be populated only with pages using the Template {{ER|...}} but this does not happen. The correct behavior can easily be noted with the legacy version 2.1.23. --Diego Queiroz (talk) 01:16, 8 September 2014 (UTC)
This filter doesn't work because this isn't yet supported in huggle 3, it uses category scans. Huggle 3 can do only "simply" filtering like filtering out bots, reverts, new pages etc etc. See the preferences in order to see what all can be filtered and how the filters behave now Petrb (talk) 11:45, 11 September 2014 (UTC)
Great! Thank you so much for your explanation. Now things are starting to make sense for me. :) I saw the configuration, but I thought it was some kind of "special-hardcoded-filter" (my fault). And are there any plans to support categories in the future? Or the lack of this feature was decided by design? --Diego Queiroz (talk) 14:59, 11 September 2014 (UTC)
No, that was because I totally overlooked that feature :P it is quite complicated to implement this, so it may take some time, unless someone else would do that. If you want to make sure I won't forget you better make a ticket in bugzilla, my memory is not so good as it used to be :P Petrb (talk) 15:04, 11 September 2014 (UTC)
Huggle warns me to enlarge the Provider Cache (otherwise edits will be lost, presumably from the IRC feed). I looked here and there but to no avail. How can I achieve this?! Thanks.Super48paul (talk) 11:22, 7 September 2014 (UTC)
That is interesting can you provide logs? This cache can be only changed in configuration file, which is in HUGGLEHOME/Configuration/huggle3.xml (on linux for example in ~/.local/share/data/Wikimedia/Huggle/Configuration/huggle3.xml) there is key called ProviderCache which by default has size 200, which IMHO is huge. Petrb (talk) 12:06, 7 September 2014 (UTC)
About every half minute I am being warned by messages like this:
zo 7. sep 15:05:54 2014 WARNING: insufficient space in irc cache, increase ProviderCache size, otherwise you will be loosing edits
zo 7. sep 15:05:32 2014 WARNING: insufficient space in irc cache, increase ProviderCache size, otherwise you will be loosing edits
zo 7. sep 15:04:51 2014 WARNING: insufficient space in irc cache, increase ProviderCache size, otherwise you will be loosing edits
zo 7. sep 15:04:25 2014 WARNING: insufficient space in irc cache, increase ProviderCache size, otherwise you will be loosing edits
zo 7. sep 15:03:48 2014 WARNING: insufficient space in irc cache, increase ProviderCache size, otherwise you will be loosing edits
zo 7. sep 15:03:26 2014 WARNING: insufficient space in irc cache, increase ProviderCache size, otherwise you will be loosing edits
zo 7. sep 15:03:04 2014 WARNING: insufficient space in irc cache, increase ProviderCache size, otherwise you will be loosing edits
zo 7. sep 15:02:36 2014 WARNING: insufficient space in irc cache, increase ProviderCache size, otherwise you will be loosing edits
zo 7. sep 15:02:08 2014 WARNING: insufficient space in irc cache, increase ProviderCache size, otherwise you will be loosing edits
zo 7. sep 15:01:40 2014 WARNING: insufficient space in irc cache, increase ProviderCache size, otherwise you will be loosing edits
zo 7. sep 15:01:10 2014 WARNING: insufficient space in irc cache, increase ProviderCache size, otherwise you will be loosing edits
I've been getting this as well, and my edit count goes up to 384 before it actually starts losing edits, but it's annoying. Shouldn't it just cap off at 200? Tutelary (talk) 13:49, 7 September 2014 (UTC)
When there is something retrieved from IRC it's put into this cache, then huggle will periodically retrieve the edits from provider and that will take it out from this cache and give it to huggle for processing. I just can't understand how it would be possible to get more than 200 irc lines in there. Edits are fetched out every 200ms, that means you would receive more than 200 irc lines within 200ms which just doesn't seem right to me. Either it's caused by heavy lag or some bug somewhere else... Petrb (talk) 08:01, 8 September 2014 (UTC)
This could be possible if huggle would lock up for some time (the cache is filled up by another thread), so if main thread would lock up this could happen. Did it stuck before you saw this message? Petrb (talk) 08:02, 8 September 2014 (UTC)
Petrb: it did not lock up as far as I could observe. And mysteriously, this morning the messages about the cache are absent - mystery!! Super48paul (talk) 09:37, 8 September 2014 (UTC)
The issue still persists for me. I've increased the cache to 2000, it just takes longer before the same thing happens. The program does not lock up, it simply stops refreshing and pulling new edits into the queue. You can still work on everything that was in the queue before it ran out of space in the cache, but you are unable to pull new edits. It's crippling, as it requires me to restart Huggle every ~5 minutes once the cache fills. --Slazenger (Contact Me)15:38, 9 September 2014 (UTC)
Which OS do you have? I tried now in Windows 7 (huggle 3.1.2) for more than 1 hour and didn't get any of these (on english wiki). Petrb (talk) 07:56, 11 September 2014 (UTC)
Call me fussy, but would that wipe out the queue so all edits in there are lost? That could potentially mean vandalism slipping by as if it were on a bullet train! --k6ka (talk | contribs) 00:16, 12 September 2014 (UTC)
Yes, but it's faster than restarting huggle which has the same result. I don't say it's a final solution, just a workaround until it's fixed. It's interesting that it happens only to some people, I was trying on many platforms and couldn't reproduce this. Petrb (talk) 08:06, 12 September 2014 (UTC)
I'm getting the issue on every computer that I use Huggle 3 on. Two are Windows 7 computers, the other is Windows XP. The two Windows 7 ones are laptops, the XP one is a desktop. --k6ka (talk | contribs) 20:15, 12 September 2014 (UTC)
Ok, can you send me a full logs since you start huggle until you get these? You can start it with parameter --syslog and -vv to get it written to a file and with higher verbosity. Petrb (talk) 09:50, 14 September 2014 (UTC)
Hi all, I'm 98% sure that the answer to this question in obvious, but apparently its so obvious that I can't locate the answer. In Huggle v3, I accidentally closed the Queue window, which normally resides above the "History of your Changes" window on the left-hand side of the Huggle UI. Well, now I can't seem to get the window to appear again. I've checked all the preferences inside the GUI, and don't see an obvious parameter in my Huggle3.css which would bring the Queue window back. Also, I've tried the standard un-install and re-install of Huggle. My next step would be blanking my huggle3.css to start from scratch but I'd like to avoid that if at all possible. Any suggestions? Cheers Bped1985 (talk) 19:08, 15 September 2014 (UTC)
right click on any title bar (dark grey) of the other windows (like "History" or "User info"). Then you can check the Queue entry to let the window reappear. --se4598 (talk) 19:14, 15 September 2014 (UTC)
Wiping the huggle3.css is of no help, this is in configuration file on your hard drive, you can see where in logs of huggle Petrb (talk) 20:02, 15 September 2014 (UTC)
Fixed Petrb (talk) 09:21, 8 December 2013 (UTC)
Fixed Petrb (talk) 09:21, 8 December 2013 (UTC)
Done fix in http://git.io/4lrq9w Petrb (talk) 08:42, 12 December 2013 (UTC)
Not fixed. (Huggle build 780). I've just tested this on Coreva-Bot, and from what i can observe it would seem that all the settings in the block window are ignored (Except for the duration of the block). The third block aimed at the account had every option enabled on the block window, while the fourth block had every option disabled. In both instances the result seems to be a block where talk page access and autoblock are disabled. Excirial (Contact me,Contribs) 19:23, 20 December 2013 (UTC)
Resolved
Excirial (Contact me,Contribs) 19:02, 16 December 2013 (UTC)
Confirmed - Pressing the button triggers an error for me as well. Subsequently pressing "Recover" on the error dialog triggers a hard CTD. Excirial (Contact me,Contribs) 20:30, 14 January 2014 (UTC)
Resolved
Thanks. (t) Josve05a (c) 22:26, 10 May 2014 (UTC)
