Jump to content

Wikipedia talk:Huggle/Feedback: Difference between revisions

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Content deleted Content added
Line 161: Line 161:
::::Oh yes, but this Huggle didn't work in [[unix-like]]. [[User:Vitor Mazuco|<font color="#FF2400">Vitor</font> <font color="#000080">Mazuco</font>]] <sup>[[User talk:Vitor Mazuco|Talk!]]</sup> 15:54, 14 February 2016 (UTC)
::::Oh yes, but this Huggle didn't work in [[unix-like]]. [[User:Vitor Mazuco|<font color="#FF2400">Vitor</font> <font color="#000080">Mazuco</font>]] <sup>[[User talk:Vitor Mazuco|Talk!]]</sup> 15:54, 14 February 2016 (UTC)
:::::Vitor, You need to download last version for it to work [[User:Petrb|Petrb]] ([[User talk:Petrb|talk]]) 16:41, 14 February 2016 (UTC)
:::::Vitor, You need to download last version for it to work [[User:Petrb|Petrb]] ([[User talk:Petrb|talk]]) 16:41, 14 February 2016 (UTC)
::::::Thanks [[User:Petrb|Petrb]]. [[User:Vitor Mazuco|<font color="#FF2400">Vitor</font> <font color="#000080">Mazuco</font>]] <sup>[[User talk:Vitor Mazuco|Talk!]]</sup> 21:10, 14 February 2016 (UTC)


== Bad news for Mac users ==
== Bad news for Mac users ==

Revision as of 21:10, 14 February 2016

Huggle not broken

A unified account seems to fix the problem. I went to Special:MergeAccount and after I could get in Huggle. --CanadianLinuxUser (talk) 18:21, 3 October 2008 (UTC)[reply]
A lot of other stuff is broken as well. For example, blocking. Calvin 1998 (t·c) 19:51, 3 October 2008 (UTC)[reply]

A stricter queue

Is there a way to create or modify a queue that is basically filtered edits but much more strict? As in a very high score threshold. If that makes sense. --allthefoxes (Talk) 03:39, 2 January 2016 (UTC)[reply]

That is a perfect idea I will try to implement this. Petrb (talk) 16:09, 30 January 2016 (UTC)[reply]

OS X - Clear Queue

Hi there, I put this in #huggle connect but no response was given. In the latest versions of Mac OS X, command + space is an OS shortcut to open search. As such, the command isn't passed through to Huggle for 'clear queue' functionality. Is there a way to change this on the OS X release to another binding? Perhaps ctrl + space? Matthew Thompson talk to me! 13:55, 20 January 2016 (UTC)[reply]

Hello, sorry for late response but I am pretty busy these days and unfortunately not many people watch this page, unfortunately in current version you can't do that. In next version you will be able to open preferences -> shortcuts to change it Petrb (talk) 16:08, 30 January 2016 (UTC)[reply]

Huggle 2 unable to login

Can login to Huggle 3 but not to Huggle 2 (version 2.1.16). Message in login box: "Unable to login." Any idea? - DVdm (talk) 07:23, 22 January 2016 (UTC)[reply]

Suppose you mean 2.1.26. Same problem here in es:, en: and de:. --Jkbw (talk) 16:58, 22 January 2016 (UTC)[reply]
Yes, 2.1.26, sorry. - DVdm (talk) 17:07, 22 January 2016 (UTC)[reply]

Possibly same issue as being discussed at Wikipedia:Bot_owners'_noticeboard#Breaking_change. — xaosflux Talk 17:10, 22 January 2016 (UTC)[reply]

WP:STiki is also currently broken. Flyer22 Reborn (talk) 19:20, 22 January 2016 (UTC)[reply]

Huggle 2 back in business! - DVdm (talk) 14:44, 23 January 2016 (UTC)[reply]

User Diffs / User info pin

Frequently, a vandal will vandalize multiple pages. When looking at a page that needs a revert, the "User info" box displays other pages edited by the same account / IP address. Clicking the pages in that user info box shows that user's edit to various pages. Often times, those are vandal edits. Unfortunately, the Diffs don't tell you if what you're looking at is current or not, so there is no way to know whether to revert - all you can do is attempt a revert, and wait for the popup box to tell you there is a newer version.

The pane in the middle that shows the diffs should always indicate whether the pane on the right is the current version of the page. This way, it's easy to go through a vandal account's history and revert several pages without having to head to a browser to do it the old fashion way.

Similarly, reverting automatically brings up the next article in the queue, which obviously changes the User Info box as well.

For the purposes of auditing edits of a vandal account, there should be some sort of "push pin" to freeze the user info box on the vandal account, even after doing a revert (preventing the next queue article from popping up).

Some of the fastest, best anti-vandal work is done in auditing vandal edit history, and if Huggle made it easier to go through those and revert one after another without the article cue popping in, it would be a great tool. - superβεεcat  09:21, 22 January 2016 (UTC)[reply]

That is exactly how it works, check the screenshot: http://snag.gy/LdWRx.jpg the bold items in User info widget are top revisions. You can instantly see that. In next huggle version the colors will be different but it's always bold if top revision. Petrb (talk) 15:59, 30 January 2016 (UTC)[reply]
Regarding "push pin" just do "Revert and stay on page" instead of revert. For example by default Q reverts and warn user. Shift + Q revert and stay on the page. Which is exactly what you need. Petrb (talk) 16:01, 30 January 2016 (UTC)[reply]

Huggle 2 diff window shows too much

Since recently (a week or two) the diff part of the window in Huggle 2 shows the page titles and navigation links and the left side bar, whereas it used to just show the diff of the viewed edit. That means that with each view we have to scroll to the right to be able to see the diff, which is pretty annoying. Have others seen this too or is it just me? - DVdm (talk) 15:03, 23 January 2016 (UTC)[reply]

Yes, it looks like a complete diff as seen by a browser. For every diff to be displayed there is an entry in the log field "Failed to retrieve 'title=pagename&diff=..... ' Unknown error". According to my recollection this problem arose for the first time when WP announced its 15th birthday on every page, but this might be an accidental coincidence. --Jkbw (talk) 00:51, 25 January 2016 (UTC)[reply]

A11 CSD

Any particular reason why the A11 CSD tag isn't in Huggle? Dat GuyTalkContribs

I will check that, does it require some paramters? These are usually harder to set up Petrb (talk) 16:09, 30 January 2016 (UTC)[reply]

Failed to load configuration pages - HTTP used when HTTPS was expected

Since somewhere yesterday when logging on to Huggle 2 I get:

Failed to load configuration pages!: HTTP used when HTTPS was expected.

Is it me only? - DVdm (talk) 14:46, 30 January 2016 (UTC)[reply]

It's just WMF loving to break stuff... Recent enforcement of SSL on wikimedia sites caused quite a nightmare for tool devs, including me. And probably also nightmare for people who can't use https (some countries on east actually block https as government there wants to sniff what people do on internet). So in fact, wikipedia is no longer encyclopedia that everyone can read, just some chosen people in western countries. Petrb (talk) 16:06, 30 January 2016 (UTC)[reply]
Fortunately I have full access to HTTPS. Perhaps it's something hardcoded in the exe? When I replace all the strings "http:" with "https:" in config.txt, and try again, I get the message

Failed to load configuration pages!: You must be logged-in to have a watchlist.

Strange... - DVdm (talk) 16:10, 30 January 2016 (UTC)[reply]
Problem with huggle 2 was that it wasn't using API for everything. Last version might use it for login, but some stuff was retrieved by screen-scraping the HTML code returned from normal web requests from wiki (eg. non-api). Huggle 2 is a successor of Huggle 0x (1) which was developed back then when API were in cradle and this stuff had to be done this way. Lot of stuff changed and as I said, people in WMF don't like to keep old stuff supported for very long. But I recall these problems with "You must be logged-in to have a watchlist" from past, they were generally related to some login issues. The source code of huggle 2 is available there: http://github.com/huggle/huggle and everyone is welcome to fix it and submit a pull request with patch. Petrb (talk) 16:18, 30 January 2016 (UTC)[reply]
I find the first part of the messages in the EN.TXT, but there's no trace of the second part, so I guess it is part of what the program receives from the system. Anyway, I don't have a VS installed anymore (or yet), so this is (or might be) for later. Thanks. Meanwhile let's wait (wishfully thinking) till this problem (and the previous one with the diffs) somehow gets fixed all by itself. - DVdm (talk) 20:02, 30 January 2016 (UTC)[reply]
@Petrb: I downloaded the ZIP with the project. I installed an old VS2008 on an old XP3. When loading the project I get a large number of missing (unregistered) stuff. Apart from the zip, is there anything I can download to be able to successfully load and compile it? - DVdm (talk) 17:37, 31 January 2016 (UTC)[reply]

Problem solved. But still, I'd like to know: can H2 be compiled with Visual Studio 2008 or do I need a more recent version? There's a massive number of syntax error and warnings as well. Obvioulsy not here, but where can I ask if/when I encounter problems? Thx already. - DVdm (talk) 17:23, 1 February 2016 (UTC)[reply]

Hi, my old Huggle 2.1.26 worked again without any modification starting 31 January. About one and a half hour ago the HTTP/HTTPS problem arose again, but it vanished after about 30 minutes. Obviously it is a lottery, hope to hit the jackpot some day. --Jkbw (talk) 02:19, 2 February 2016 (UTC)[reply]

Huggle 2 suffers from HTTPS problem again. Vandals can do their thing... - DVdm (talk) 10:30, 5 February 2016 (UTC)[reply]

I managed to compile and debug H2 with Visual Studio 2015. Unfortunately the error "Failed to load configuration pages!: HTTP used when HTTPS was expected" is not generated in the program, but is a result coming from the server. There seems to be nothing that can be changed to Huggle itself. Must be something on the server. Any idea where I can escalate this? Anyone? - DVdm (talk) 11:56, 9 February 2016 (UTC)[reply]

@DVdm: if it's a Wikimedia server issue, Phabricator is where you'll want to raise it. ~ Matthewrbowker Drop me a note 17:00, 9 February 2016 (UTC)[reply]
Thanks! Will keep you posted. - DVdm (talk) 18:03, 9 February 2016 (UTC)[reply]
Follow Phabricator task T126357. - DVdm (talk) 18:45, 9 February 2016 (UTC)[reply]

Filter option

Do you think there could be a way that we can filter edits by WikiProjects? For example, I spend most of my time editing in WikiProject Professional wrestling and WikiProject National Football League and I would like to be able to select an option that allows edits to articles and templates in those projects appear only. Except have it set up to were we can add any WikiProject we'd like. CrashUnderride 18:01, 30 January 2016 (UTC)[reply]

Any thoughts??? CrashUnderride 11:06, 10 February 2016 (UTC)[reply]
Sound interesting, but how do you actually figure out which wikiproject page belongs to? This is definitely enwp only feature. Petrb (talk) 11:47, 12 February 2016 (UTC)[reply]
On the article's talk page. The projects banners. I would suggest using the categories at the bottom of the page. CrashUnderride 13:05, 13 February 2016 (UTC)[reply]

Ongoing problems with H2 and H3

  • Problems with H2
  1. Stops at login with error: "HTTP used when HTTPS was expected"
  2. Diffs show page headers and left navigation frame. Scroll to right needed with every diff
  3. Crashes when reporting a user through User menu, Report
  4. Crashes when requesting page protection through Page menu, Request protection
  5. Massive amounts of errors: "Failed to retrieve 'title=....&diff=.....&oldid=.....&uselang=....": Unknown error
  • Problems with H3
  1. Always opens in full screen mode (not a big issue, just mildly annoying with a large 4K UHD monitor)
  2. Many updates of pages not seen (while I do see them appear in H2)
  3. User warning level blobs almost never update in Page editbar, never update in User editbar, sometimes update in Page history window.
Numbers 2 and 3 still make H3 essentially unusable for me (sob sob), so I only use it for user reporting and page protection requests.

Are there any plans for fixing some of these problems? Hope you don't mind my insisting.- DVdm (talk) 11:34, 2 February 2016 (UTC)[reply]

FWIW, meanwhile —with a few simple hacks in a private version— I managed to solve Huggle 2 problems 1, 2, 5. Problem 3 does not occur anymore. Problem 4 status unknown.
If this is off-topic, please let me know. - DVdm (talk) 14:49, 10 February 2016 (UTC)[reply]
If you did some hacks to make huggle 2 work you might want to share them with others through a pull request on GitHub so that other HG2 users can keep on using it. Some of them can't use HG2 right now. Petrb (talk) 11:48, 12 February 2016 (UTC)[reply]
Hi Petr, I'd be glad to share, but I have no idea how and where to make a pull request on GitHub. And is that a pull of the source, or of the compiled (and renamed) exe? See also Phabricator task T126357 where I asked a similar question, and which is also where I documented the hack that made it work again.
By the way, at this moment H3 and H2 don't work at all, so there is not much point in sharing, see [1]. - DVdm (talk) 12:00, 12 February 2016 (UTC)[reply]

H3.1.19 seems okay. In order to fix my hack of H2 (and share it), can I find some kind of diff between H3.1.18 and H3.1.19 somewhere? - DVdm (talk) 18:45, 12 February 2016 (UTC)[reply]

https://github.com/huggle/huggle3-qt-lx/commit/2da6e2383624c423b856d61d0be50dcd8a4750ce Petrb (talk) 18:52, 12 February 2016 (UTC)[reply]
Thanks. Do you think(wishful thinking aloud here) there will be something similar in the H2 source??? Too bad I only have a VS2015 at the office, but perhaps I can install one here as well. We'll see about that. - DVdm (talk) 19:27, 12 February 2016 (UTC)[reply]
@Petrb: I have a properly running multi-dirty-hacked version 2.1.27 here. Alle my mods are documented with the string DVdm. How do I go about handing this over to you for scrutinizing and publishing? - DVdm (talk) 09:43, 13 February 2016 (UTC)[reply]

WrongToken

I'm trying to connect with huggle, but I'm getting a error message. After the "Retrieving white list" step, I get the error:

ERROR: api.php responded with unknown result: WrongToken

I've already tried on en.wiki, pt.wiki and test.wiki, and the same. Anyone knows what is going on? - Editeur ? 02:41, 12 February 2016 (UTC)[reply]

Same problem. Donner60 (talk) 03:33, 12 February 2016 (UTC)[reply]
Anomie debugged this and found that Huggle3 was assuming that the token returned by the API was safe to include in a URL without applying URL encoding. The SessionManager changes to MediaWiki that are included in the 1.27.0-wfm.13 branch which was deployed to all wikis at 2016-02-11T20:01Z included a change to the session tokens that invalidated this assumption. There is a proposed patch on GitHub that appears to fix the problem. I'm sure that Petrb will get a new build out as soon as the fix can be properly tested and confirmed. --BDavis (WMF) (talk) 04:09, 12 February 2016 (UTC)[reply]
Thanks. Donner60 (talk) 04:21, 12 February 2016 (UTC)[reply]
Huggle2 too: "Unable to log in." Yesterday I have been working with it without any problem. After that change, when H3 stopped, H2 stopped too. - DVdm (talk) 07:19, 12 February 2016 (UTC)[reply]
New release of huggle 3 is on the way, please be patient. HG2 might take some more time, not sure what is broken there, I thought we always encoded the token in that one. 89.177.100.4 (talk) 11:45, 12 February 2016 (UTC)[reply]
Huggle 3 binaries for Windows 7 and newer are prepared, build for MacOS and older windows should be done today. Petrb (talk) 12:23, 12 February 2016 (UTC)[reply]
It looks like the newest release, 3.1.19, resolves the issue (it is working for me now) - Mac users will have to wait. ~Oshwah~(talk) (contribs) 18:04, 12 February 2016 (UTC)[reply]
Yes, the 3.1.19 release for macs is coming. - Editeur ? 21:49, 12 February 2016 (UTC)[reply]
The 3.1.19 OSX build is now available on GitHub. --BDavis (WMF) (talk) 22:04, 12 February 2016 (UTC)[reply]
For me didn't worked. If I tried to use old version? I use HUggle for Linux/Ubuntu. Vitor Mazuco Talk! 13:10, 13 February 2016 (UTC)[reply]

Didn't work for me either: I'm having the same problem. -- Rrburke (talk) 13:54, 13 February 2016 (UTC)[reply]

I also get the "Unable to log in" error with Huggle 2. -- Rrburke (talk) 14:16, 13 February 2016 (UTC)[reply]
I have a solution for that, but I have no idea how to upload it. See previous thread. - DVdm (talk) 14:25, 13 February 2016 (UTC)[reply]
@DVdm Uploaded what? Vitor Mazuco Talk! 21:56, 13 February 2016 (UTC)[reply]
Huggle 2.1.27, working better than it did before. I found and fixed a few bugs in the original 2.1.26. I have the source package and/or the compiled executable. - DVdm (talk) 22:00, 13 February 2016 (UTC)[reply]
Oh yes, but this Huggle didn't work in unix-like. Vitor Mazuco Talk! 15:54, 14 February 2016 (UTC)[reply]
Vitor, You need to download last version for it to work Petrb (talk) 16:41, 14 February 2016 (UTC)[reply]
Thanks Petrb. Vitor Mazuco Talk! 21:10, 14 February 2016 (UTC)[reply]

Bad news for Mac users

Hi,

It's sad but my poor mac mini I got for huggle builds broke :( which means I can't build a Mac version. Because it wasn't cheap I can't get any other any time soon. So if there is someone with Mac and development skills who is willing to install whole X-Code and qt (about 2gb) on their OSX, please let me know so that we can prepare the .dmg for last version. Petrb (talk) 18:21, 12 February 2016 (UTC)[reply]

I have no experience with macs, but can't you run a virtual OSX under WMWare? - DVdm (talk) 18:43, 12 February 2016 (UTC)[reply]
I tried once, it wasn't even legal as you need a license for OSX and it didn't work. Answer from virtualbox was "running OSX on non-apple hardware is not supported". Petrb (talk) 18:47, 12 February 2016 (UTC)[reply]
+ you need to download stuff from apple store to which you don't have access on pirated OSX versions. Petrb (talk) 18:48, 12 February 2016 (UTC)[reply]
@Petrb: Give me a poke when you have the time, I have a MacBook and I'd be glad to build if you need it for a little while. Just can't do nightly ones, because my MacBook is also my personal machine. ~ Matthewrbowker Drop me a note 21:38, 12 February 2016 (UTC)[reply]

3.1.19 Installation problem

I tried to do a clean install of 3.1.19 but when I try to run Huggle after the installer is finished I get the following error:

"This application failed to start because it could not find or load the Qt platform plugin "windows". Reinstalling the application may fix this problem"

Reinstalling did not fix the problem. -- Rrburke (talk) 15:57, 13 February 2016 (UTC)[reply]

And no Huggle directory or files were created during the install. -- Rrburke (talk) 16:00, 13 February 2016 (UTC)[reply]
Which one is that? 32/64/mingw? 89.177.100.4 (talk) 18:18, 13 February 2016 (UTC)[reply]
I tried installing both 64 and 32; both generated the same error on exiting the installer. -- Rrburke (talk) 20:38, 13 February 2016 (UTC)[reply]
I can't replicate this can you check if there is folder Huggle in your Program Files directory? If yes, can you send me complete listing of all files in that folder? 89.177.100.4 (talk) 13:12, 14 February 2016 (UTC)[reply]
Hi and thanks for your help. No, there is no Huggle folder. -- Rrburke (talk) 13:48, 14 February 2016 (UTC)[reply]
Ok can you restart the installer and provide the logs from it? Petrb (talk) 14:46, 14 February 2016 (UTC)[reply]
I ran C:\Downloads\huggle_3.1.19_x64.exe /L*V huggle.txt from the command prompt to create a log, but no log called huggle.txt appears to have been created. -- Rrburke (talk) 15:52, 14 February 2016 (UTC)[reply]
Do you see any errors or something while you install it? Are you sure there is no Huggle folder not even in (x86) dir? Petrb (talk) 16:37, 14 February 2016 (UTC)[reply]
I get an error when I try to run Huggle at the end of the install:
"This application failed to start because it could not find or load the Qt platform plugin "windows". Reinstalling the application may fix this problem"
Other than that, there are no error messages. -- Rrburke (talk) 17:21, 14 February 2016 (UTC)[reply]