To get WUU 1.8.605 and up to work on Windows, you might need to install Visual C++ 2008 SP1 Redistributable Package separately. (Typically, if you get a "manifest" error or "Windows side-by-side" error this is the cause)
hello a virus is detetec whith the news version why please?
I've had no other reports of a virus in any version since the problems last year, but the process I use to make a Windows program out of the Python source (py2exe) might trip up some virus scanners. As funkydude said, please tell me which virus scanner you use :)
Anyhow, Jncl has changed WUU to work a bit cleaner with WoWI/Curse now (i.e. helping you check which addons need update, and assist you in updating them manually), so I'll probably build a version from that tomorrow, then we'll look at what else can be done to make the updating process as streamlined as possible within the current limitations.
It's sad that WoWMatrix has caused this to happen as these updaters have the potential to cut their bandwith in half if they would implement an efficient API for querying and downloading updates.
Checking this stuff from here has made me realize something: The Curse web pages are HUGE - go to a random addon page and check page info for the size of the HTML.
iThis is got to be frustrating for you. I really appreciate the time you put into this. Try not to see this as a end. I think we knew they were going to do something at some point. Now its done with and good to get it overwith. Now hopefully a permanent solution can be come up with in your new updater.
Looks like the option of popping up the download page in the users' browsers and having them click the download button is the best bet so far :( I was hoping to keep everything inside WUU to "isolate" it - for security - but now you'll probably have to load the page in whatever default browser you have (and I just have to hope it's not unpatched IE5 or somesuch)
EDIT: Looking at it some more, it seems I can't do much from my current connection (I get my real connection back tomorrow, or Saturday at the latest), but at least I've got a feeling for what changes need to be done to WUU; most noticeably, there'll be a new field for Curse (and possibly WoWI - does it still work?) where you specify what the addon's file name typically looks like (e.g. Recount on Curse has filenames like "Recount-v3.1d_stable.zip", so you specify that WUU should look for files that start with "Recount"), and a new global setting where you specify your default download folder (e.g. Chrome on Windows 7 here downloads to "C:\Users\lejordet\Documents\Downloads\").
In most browsers you can save to a default folder with a few clicks, and WUU can then watch C:\Users\lejordet\Documents\Downloads\ for a new file appearing called something like "Recount*.zip" (or .rar) and act appropriately. It's not very "clean", but it works. This also means I'll try to bring back support for wowui too, as they had the same problems with WUU as Curse had with WoWMatrix (though I removed support for it, since they blocked it anyhow - they got mad when I didn't answer their emails (sent at midnight local time for me) within a few hours).
This was a long edit, but I'm just trying to say that some things will change, and there's opportunity to make WUU better from it, even if it's less simple as a user (though just going through the 5-6 tabs in your browser for the updated addons to click "Manual install" doesn't sound that bad.
To sum up what I've written elsewhere:
I will not try to dodge these buttons, or more dishonest practices to get past them - for more reasons than one, really, not least of which is that WUU is open source, and I don't think I'd like to have my name attached to code that does click-forging or stuff like that. (Not to mention that'd give the WoWmatrix guys "free" code to circumvent these measures - I can't know for sure, but I'd be surprised if they're not at least in part based on one of the open source updaters like WUU).
I do have some ideas though, to make sure WUU isn't totally worthless:
1) WUU can still check whether addons have new versions on Curse, and get the link to the download page. WUU could open your browser and ask you to download the file (either by clicking the button or typing the CAPTCHA), then monitor your download folder (assuming your browser downloads to the same folder every time, otherwise ask you to select the zip file) and do the installation. It's one more step, and a bit more tedious when many addons are updated, but I feel it's a good compromise given the circumstances.
2) Later, then maybe integrate the browsing session into WUU itself, so you enter the CAPTCHA without having to leave WUU.
tl;dr: Personally, I don't think I'm ever going to use the Curse/WoWI updaters myself (you decide whether you want to call me stubborn or stupid :P ), so I'll make WUU do "something" useful with the sites :) - but it might take more than a week, I'm on a crappy GPRS connection until the weekend.
I have python 2.5.1 installed, too -- I'm a python developer by profession. I'm not sure whether these problems I'm having are particular to my situation or not. I wouldn't think so, but I'm having lots of dumb problems, so I don't know. :/
Well, if you're a python developer, it's actually better to run it from source :) you only need 2-3 libraries - wxPython, ezPyCrypto (if you want to auto-update) and optionally Psyco (which I'm not sure how much helps)
Lately -- by which I mean the last couple releases -- I've been sporadically getting an error on update like this:
I'm not sure what would be causing this -- I don't have threads enabled or anything, but this /looks/ like some kind of race condition.
Also, following advice upthread, I had to enable "Preserve newlines as-is" in the newest version of WUU; for at least a year, I've been using it without (looking at) that option. Did something change in the most recent version that affects end-of-line handling? The problem seemed to be with addons that were using backslash-escaped newlines to build large strings, e.g. for an in-game FAQ or credits panel. Postal is the addon that comes to mind most immediately.
I built the latest version using python 2.6, which has a ton of changes over 2.5; it might seem like I have to enforce that setting to on then :P