Did something change about the nightly downloads page? I used to be able to just copypasta the link I wanted to my shell and get files via wget but now all it gets is a corrupt file.
I can download the archive via windows and then upload it, but it appears that something is funky.
Also all the links start with http://www.zenphoto.org/pages/nightly-builds?download=4313&
Was that always like that? Anyways, I suppose it could have been something on my shell got screwy, but I don't remember upgrading anything that would have affected wget at all...
It has been for months it is that way actually…:-) Not your fault, the downloads (actually all hosted on our site) use the downloadList plugin so direct downloads are not possible anymore and we also get a download statistic (might be something for your theme downloads btw).
Yeah, I still used to be able to get them via wget, not sure why it's not working now. Oh well, I can just download to my windows box and upload after. I must have changed something without realizing it.
did they always have the double download= in the link though? One never changes if you check the links, and 2nd one does for each file. Is that because it's pointing it at a folder to download from and then 2nd is for the files it points at?
Ok, not sure what changed... but the double ?download= links are gone now and I can wget the files I swear I'm not seeing things.
At the time I started this, they all had:
http://www.zenphoto.org/pages/nightly-builds?download=4313&download=####
Ok so this has sprung up again.
Right now the nightly builds page has links similar to this:
http://www.zenphoto.org/pages/nightly-builds?download=4313&download=4975&download=6245
with the last # being the one that changes based on the link. I see the same thing no matter which browser I use. While I can still click and download the files at home, using wget via shell returns corrupted archives.
My normal browser is Chrome, but when it sprung up again, I downloaded Firefox just to make sure it wasn't Chrome keeping history files somewhere.
This is somehow a caching issue, probably if someone accesses the page while the cache is cleared or something. I cannot reproduce it btw, just tried with Safari (being loggedin on our site) and Firefox (loggeed out).
Btw, I recently tried to contact you via your other mail address and it bounce two times.