folder_max_length affects files since 0.7.17
Posted: April 22nd, 2014, 5:45 pm
since 0.7.17, folder_max_lengthstarted truncating file names
I've set it at 64 instead of default 128, using sabnzbd on Windows 7 SP1.
When I download this NZB, and after post-processing is done (it's extracted in my Completed Download Folder), some file names are truncated, their extension and some characters at the end are gone.
This doesn't happen when I reset the value of folder_max_length to 128 (only tested for the NZB listed above)
When it is has the default value (128) and I download this NZB it'll fail, so that's why I was using a lower setting of 64
--------
Some suggestions
I've set it at 64 instead of default 128, using sabnzbd on Windows 7 SP1.
When I download this NZB, and after post-processing is done (it's extracted in my Completed Download Folder), some file names are truncated, their extension and some characters at the end are gone.
This doesn't happen when I reset the value of folder_max_length to 128 (only tested for the NZB listed above)
When it is has the default value (128) and I download this NZB it'll fail, so that's why I was using a lower setting of 64
--------
Some suggestions
- why not make sabnzbd smart about total path length, the folder_max_length is only used for folders, not for files inside those folders, this isn't really fool proof.
I'm not saying it should rename the files, but if the total length of the path is longer than the technical 260 limit, it should truncate the folder some more. - separate the Temporary Download Folder name structure from the Completed Download Folder, this will allow to store the names and/or structure of what is being downloaded while using smaller temporary folder & file names.
- use the \\?\ prefix, which should be supported by python