Page 1 of 1

Non-default configuration directory results in failed file association

Posted: Mon Dec 26, 2016 5:40 pm
by galneon
I've used a non-default directory for my deluge daemon box for a long time, but just now started using the -c switch with on my client box as well. This seems to work fine, until I try to load a torrent file. Opening a .torrent file through a browser or file manager simply never sends the .torrent file to the daemon. Moving the configuration data back to the default location in appdata and removing the -c switch from my deluge shortcut means file associations work once more.

The daemon's directory polling feature or the "Add torrent" dialogue in the thin client are the only ways to load torrent files when the client is using the -c switch to specify a non-default configuration folder. This, obviously, isn't optimal since I have .torrent links set to open by default in my browser.

I'm using 1.3.13 on both boxes.

Re: Non-default configuration directory results in failed file association

Posted: Sun Jan 08, 2017 7:32 pm
by Cas
Could you create a ticket for this please

Re: Non-default configuration directory results in failed file association

Posted: Sun Jan 08, 2017 8:45 pm
by galneon
Here you go: http://dev.deluge-torrent.org/ticket/2955#ticket

I imagine you'll change the priority from major to minor, but given how impractical this bug makes portable thinclient setups and given the fix is probably trivial, I thought I'd give it a shot. ;)