Add by file path uses a url of "api?mode=addlocalfile&value=full/local/path/to/file.ext&pp=1&script=script.cmd&priority=-1" which uses value instead of name which the source uses.
Should be:
api?mode=addlocalfile&name=full/local/path/to/file.ext&pp=1&script=script.cmd&priority=-1
Bug in API reference
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.
Re: Bug in API reference
Thanks,
I had fixed it in the text of example link, just not in the url of the link
I had fixed it in the text of example link, just not in the url of the link
Re: Bug in API reference
No prob, i've spotted another error in the docs which isn't worth opening up a new topic:
In http://wiki.sabnzbd.org/directory-setup there is the sentence below that i dont think applies to linux installs as my install takes relative paths from the home directory.
In http://wiki.sabnzbd.org/directory-setup there is the sentence below that i dont think applies to linux installs as my install takes relative paths from the home directory.
All relative paths you set in the INI file, will be relative to the location of the INI file.
Re: Bug in API reference
I am pretty sure it is still relative to the location of the ini (which by default is inside the home directory)
Re: Bug in API reference
There's a subtle difference in how you start SABnzbd.
When you do not use the -f parameter, then all folders will be in ~/.sabnzbd
(so relative to the ini file), except the "incomplete" and "complete" folders.
When you do use the -f parameter, all folders will be relative to the ini file.
When you do not use the -f parameter, then all folders will be in ~/.sabnzbd
(so relative to the ini file), except the "incomplete" and "complete" folders.
When you do use the -f parameter, all folders will be relative to the ini file.
Re: Bug in API reference
Not too sure i understand your post shypike as my ini file is in ~/.sabnzbd both with and without -f switch would be relative to my ini.shypike wrote: There's a subtle difference in how you start SABnzbd.
When you do not use the -f parameter, then all folders will be in ~/.sabnzbd
(so relative to the ini file), except the "incomplete" and "complete" folders.
When you do use the -f parameter, all folders will be relative to the ini file.
Adding:
logging.info('Dirscanner ' + cfg.DIRSCAN_DIR.get())
logging.info('Dirscanner ' + cfg.DIRSCAN_DIR.get_path())
to dirscanner.py yeilds:
dougle@local:~$ tail -f /home/dougle/.sabnzbd/logs/sabnzbd.log | grep Dirscanner
2010-03-01 19:38:52,211::INFO::[dirscanner:268] Dirscanner Download
2010-03-01 19:38:52,211::INFO::[dirscanner:269] Dirscanner /home/dougle/Download
This was an install from the repos
I knew i wasn't crazy.....
Last edited by dougle on March 1st, 2010, 2:50 pm, edited 1 time in total.
Re: Bug in API reference
We don't create the repository release, that's done by JCFP.
He runs his own board on this forum.
He runs his own board on this forum.
Re: Bug in API reference
I get your point now dougle, only the log_dir, nzb_backup_dir and cache_dir on that page are relative to the ini. I have updated the wiki to reflect that. Thanks
Last edited by switch on March 1st, 2010, 7:04 pm, edited 1 time in total.