If I add schedules in the schedules configuration, I am able to remove all the added schedules with the remove button, except for task 1. Pushing the remove button for task 1 does not result in any visible action.
Workaround: in sabnzbd.ini I set the variable "schedlines" by hand to: schedlines = ,
That removes task 1.
Hope this a usefull contribution. If not, please tell me.
Version 0.4.4. : task 1 in current schedule (config) cannot be removed
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- 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.
-
- Newbie
- Posts: 4
- Joined: October 2nd, 2008, 12:26 pm
Re: Version 0.4.4. : task 1 in current schedule (config) cannot be removed
Is this a repeatable problem?
I have never seen it before.
I have never seen it before.
-
- Newbie
- Posts: 4
- Joined: October 2nd, 2008, 12:26 pm
Re: Version 0.4.4. : task 1 in current schedule (config) cannot be removed
Yes, this is structural in my version, so repeatable. I made a series of screenshots to show you, but unfortunately I get an error that the upload folder is full.
Re: Version 0.4.4. : task 1 in current schedule (config) cannot be removed
What skin are you using? Default/SMPL/Plush?
-
- Newbie
- Posts: 4
- Joined: October 2nd, 2008, 12:26 pm
Re: Version 0.4.4. : task 1 in current schedule (config) cannot be removed
Lol, I did not even know you can change the skin, so I am using the default.
Re: Version 0.4.4. : task 1 in current schedule (config) cannot be removed
Does this happen with any scheduling that you add, or only when a certain set of schedules are added.
If you can give us your previous schedlines config value that didn't work it might help as I can't reproduce the issue here.
If you can give us your previous schedlines config value that didn't work it might help as I can't reproduce the issue here.
-
- Newbie
- Posts: 4
- Joined: October 2nd, 2008, 12:26 pm
Re: Version 0.4.4. : task 1 in current schedule (config) cannot be removed
The problem occured the first time, when I tried scheduling out for the first time and I added a schedule to resume at 0845 AM with a speedlimit of 250 KB/s. I then saw that I used resume, while I wanted to use speedlimit. So I tried to remove and it did not work. I added various schedules with resume and several with speedlimit, was then able to remove each and everyone but not task 1. So I shut down SABnzbd and searched for config files that had been changed around the time that I made the changes, and I ended up to look into sabnzbd.ini, where i saw "schedlines = 45 8 * resume 250,". I then changed that into "schedlines = ," restarted SABnzbd and task 1 was gone. I added a schedule with speedlimit 250 at 0845AM, tried to remove it, and it refused. Shut down SABnzbd again and looked in sabnzbd.ini and i saw "schedlines = 45 8 * speedlimit 250,", reset it again to "schedlines = ," restarted SABnzbd and task 1 was gone. Tried this again several times with other starting times and speedlimits and the result was the same: task 2 and higher could be removed through the remove button, but never task 1. The only way I could remove task 1 was by changing "schedlines" in sabnzbd.ini.
Is this rather long answer of any help?
Is this rather long answer of any help?
Re: Version 0.4.4. : task 1 in current schedule (config) cannot be removed
hi,
i'm having the same problem here.
I'm not able to remove the first schedule i've made.
A workaround that worked for me is to manually remove the entry in the sabnzbd config file. I hope there is a more convenient way to do so.
regards
EDIT: i just removed 0.4.4 and reinstalled 0.4.3: same thing occured
i'm having the same problem here.
I'm not able to remove the first schedule i've made.
A workaround that worked for me is to manually remove the entry in the sabnzbd config file. I hope there is a more convenient way to do so.
regards
EDIT: i just removed 0.4.4 and reinstalled 0.4.3: same thing occured
Last edited by scallie on October 18th, 2008, 3:35 am, edited 1 time in total.
Re: Version 0.4.4. : task 1 in current schedule (config) cannot be removed
When you have to remove the "schedline" from the INI file, can you post this line on the forum?
I wonder if this line has been damaged somehow.
It would help in finding the problem.
I wonder if this line has been damaged somehow.
It would help in finding the problem.
Re: Version 0.4.4. : task 1 in current schedule (config) cannot be removed
hi,
this is the line i removed manually:
schedlines = "5 1 * resume ",
i'm having this problem on both windows XP Pro sp2 with ie7 and on windows 2000 SP4 with ie6
regards
this is the line i removed manually:
schedlines = "5 1 * resume ",
i'm having this problem on both windows XP Pro sp2 with ie7 and on windows 2000 SP4 with ie6
regards
Re: Version 0.4.4. : task 1 in current schedule (config) cannot be removed
Right!scallie wrote: i'm having this problem on both windows XP Pro sp2 with ie7 and on windows 2000 SP4 with ie6
It's the browser. Switch immediately to Firefox!
Seriously, it's Microsoft standards-breaking browser that's causing this problem.
I'll see if we can come up with a work-around.
Re: Version 0.4.4. : task 1 in current schedule (config) cannot be removed
I had the same problem when using Opera. Had to manually remove the scheduled task in the .ini file.
Re: Version 0.4.4. : task 1 in current schedule (config) cannot be removed
Problem found, will be solved in 0.4.5Final.
It was a typo in the HTML code, that Firefox handles OK, but not Opera and IE.
Our mistake.
(Actually this bug has been present since the old 0.2.5 release by tdian).
It was a typo in the HTML code, that Firefox handles OK, but not Opera and IE.
Our mistake.
(Actually this bug has been present since the old 0.2.5 release by tdian).