Hi! Using SABnzbd 0.6.5 and my sorting in configured like this (selected for tvshow category):
/mnt/HDD2/Series/%ext/%sn/S%0s/
But every time I download a tvshow a different directory is created because of the replaceable value %ext, e.g.:
/mnt/HDD2/Series/5xt/Sanctuary/S01
or
/mnt/HDD2/Series/1xt//Alphas/S01
the correct folder/extension should be "mkv" (or "avi").
TIA!
Folder Sorting and directory extension
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: Folder Sorting and directory extension
%ext is bit of a poor choice for extension.
In this context, %e has precedence, being the episode.
I'll see if I can fix that for a future release.
In this context, %e has precedence, being the episode.
I'll see if I can fix that for a future release.
Re: Folder Sorting and directory extension
I was unaware of this precedence rule and this explains the issue. Just to let you know that when you fix this issue we will be able to, for example, archive/organize tv shows pertaining to several categories (say e.g. HDTV and SDTV) into their own folders (mkv and avi, respectively). Looking forward to your fix... thanks.
Re: Folder Sorting and directory extension
shypike, how about making %ep the replaceable value for episode number and keep %ext as extension for version 0.7? I know, this will break backward compatibility... in this case could you please point out the right py source file(s) that one has to modify in order to make that change (%e -> %ep)? TIA.
Re: Folder Sorting and directory extension
It's already fixed in the development version.
But the next release isn't around the corner just yet.
But the next release isn't around the corner just yet.

