Network location path bug (0.7.0)

[waryo]

Since upgrading to 0.7.0, I've run into the following bug:

In my category settings, I have certain categories set to download to a network path such as "\\server\temp" Since upgrading to 0.7.0, rather than moving my download to this network location, the directory structure \server\temp is created in my default completed download folder. For example, the files would end up in C:\downloads\server\temp.

Has anyone else experienced this problem?

[aluXogen]

This is happening to me as well

[shypike]

Will be investigated.

[shypike]

Cannot reproduce your problem. Works fine here.
Please email screenshots of your Config->Folders and Config->Categories to [email protected]

[shypike]

The current code relies on folder joining by a Python library that doesn't have fully predictable behaviour
over various Python and/or Windows versions.
I'll work around this and try to get a solution in release 0.7.1

[miles267]

Noticed similar bug in 0.7.1 (windows):

Under Config > Folders, am only able to enter local folder paths as opposed to share names as I once could \\server\foldername. If you enter a \\server\sharename and SAVE, it will revert back to \incomplete, etc.

Even if you map a drive letter - for example - F to \\server\sharename, it will not allow a folder to then be F:\incomplete. The only work around I've found thus far is creating a symbolic link to c:\usenet point to \\server\sharenamehere.

If this could be corrected it would be appreciated.

[shypike]

"incomplete" is the one path that doesn't support UNC.
The reason is simple: par2 does not support it.
The way the issue is reported, is a bit awkward.

[miles267]

incomplete supports UNC if you use a symbolic link of a local path (i.e. C:\incomplete) that points to \\network\incomplete.