Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings.
Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Not really a bug, but Beta2 reports as 0.7.0Beta instead of 0.7.0Beta2. I normally wouldn't have noticed but an auto-update script I have is going crazy trying to get the ever elusive Beta2
It checks the version against the newest build version on sourceforge, and if a newer one is found it downloads it. Everything goes good until it verifies the version and see's its still at 0.7.0Beta.
No big deal, I simply stopped the script for now. Just thought I'd let you know. Being a beta its pretty much a non-issue as it won't stay too long anyway
Last edited by Influence on April 12th, 2012, 12:17 am, edited 1 time in total.
2012-04-11 12:57:13,784::DEBUG::[misc:583] Checked for a new release, cur= 70042, latest= 61599 (on http://sourceforge.net/projects/sabnzbdplus/files/sabnzbdplus/sabnzbd-0.6.15)
2012-04-11 12:58:11,651::INFO::[SABnzbd:1528] Starting SABnzbd.py-0.7.0Beta2
So can you explain what you did? And are you sure you're running Beta 2 ... ?
Ok, this is embarrassing. I didn't even think about my script to check for updates cuts after a certain number of characters, and....you guessed it, it cuts right at the "a" in 0.7.0Beta, so while sabnzbd was reporting correctly, my script wasn't catching the 2.
