Change Log:
- Feature: Update member parser to parse image count.
- Feature: Update search parser to parse image count.
- Bug Fix: Update web client to handle url ended with period.
- Bug Fix: Update https handler.
- Bug Fix: Update batch job runner.
- Add test case for parsers.
Download link for nijie downloader 1.0.7.0, Source Code in GitHub.
Please report any issue on GitHub Issue Tracker
Donation Link on the side bar ==> 😀
Hi!
Nijiedownloader 1.0.7.0 stopped working : it does not download anymore but does not return any error. It’s like it doesn’t see the images on Nijie website and therefore, doesn’t find any image to download.
Download by Tags is not working << Can you create github ticket?
I don’t know why I can’t reply to your last post but I’m using it on my local drive.
can try to run it from c: drive? e.g. c:temp?
Tried it and it still the gives the same error. I’ll just DL the pictures manually since I think I’m the only one getting this error, thanks for your time.
OK, if possible , try to run as admin or run it on other pc.
Does nijie downloader have a “list” feature like pixivutil yet?
You can save the list in xml format in the Batch Download page
Damn xml…
Got tired and just made a java app to make the list.txt -> xml
Crappy fix but hey it works.
😛 share2
It’s really.. shitty right now. I couldn’t figure out how to go to the parent directory of the user-set root(.. didn’t work) and the save directory is always H:nijie”userinput”{memberId}({memberName}){imageId} – {imageTitle} or H:nijie”userinput”{memberId}({memberName})\{imageId} – {imageTitle}\{page} for manga.
Nijiedownloader is written in C# right? I might actually make a real solution…. Otherwise I’ll just improve my makeshift code to pull the config files off nijiedownloader(Might break when you update though)
It is on c#, just pull the github and send the push request with the modified feature 😛
Oh I just noticed that using …. to save in a directory two levels above the specified root DOES work, but it saves the path weirdly in the database.. For example if root was C:UserDownloads and you specified ….Nijie{memberId}({memberName})\{imageId} – {imageTitle} the messages that show up while processing batch downloads/database entry for filename would be:
C:UserDownloads….Nijie{memberId}({memberName})\{imageId} – {imageTitle}
When expected entry was maybe
C:Nijie{memberId}({memberName})\{imageId} – {imageTitle}
Hopefully this doesn’t break anything later.
I chose not to push a new build because didn’t want to mess with the UI.
Also.. config files are in appdata 🙁
it is the behaviour for .Net userSettings to allow runtime changes.
I am getting this error http://i.imgur.com/eknV4dR.jpg is there a way to fix it?
Have you install Microsoft SQL Compact 4.0 SP1 (http://www.microsoft.com/en-sg/download/details.aspx?id=30709)
Yes, I already have before running it.
Try to rerun and can you upload the latest log file (log-.txt) to pastebin/mediafire?
http://pastebin.com/eCwx8gWK
Do save the application on the shared drive/usb drive? For some reason, the application throwing System.Security.SecurityException: Request failed.
Try to copy the app to the local drive?
Thanks so much for another update!
Is there a way to speed up the batch downloading? I feel like it could use some improvement. >8 threads don’t work properly. Some member job that contains 20 images (that are already downloaded) takes almost 2 minutes.
I know there is no DB support yet, but I really think it should be possible to determine if some image is already downloaded without fetching each image page, using just filenames. What do you think?
Btw, you said you’d change the [add job] dialog as I’ve suggested previously (move [member] option up in the dropdown list). Can you do it for the next update? I think this really shouldn’t need an entry on GitHub.
>> Image already downloaded
On Settings -> Download, try to enable ‘Save Image Info to DB’ and ‘Skip if already downloaded in DB’?
>> change the [add job] dialog
You better add it to GitHub issue tracker so I don’t forget it 😛
That’s it. I totally forgot that I had Save to DB option disabled due to some old bug. And now it’s working just great as far as I can see. Except there are few exceptions in the log, which I’ll post on GitHub.
Thanks.