search

sbussetti / deluge-siphon

A Chrome extension for sending torrents to your Deluge server.
http://sbussetti.github.io/deluge-siphon/
82 stars 22 forks source link

Downloads defaulting to ~/Downloads #22

Closed kev12345 closed 7 years ago

kev12345 commented 8 years ago

When I add torrents with deluge siphon they default to downloading to ~/Downloads even though my settings are set to download to a different location. I'm running the latest deluge daemon and web ui and have tried re-installing Raspbian and deluge from fresh.

Any ideas?

sbussetti commented 8 years ago

Where are you setting the alternate download location? My extension checks for and uses the value of download_location which is set via the web ui in Settings -> Downloads -> Download to:

sbussetti commented 8 years ago

Also, what is the actual version number of Deluge you're running?

kev12345 commented 8 years ago

Yes that's how mine is set. I confirmed the location in the core.conf

I downloaded a similar chrome extension to yours last night, 'remote torrent adder'. This appears to works fine and downloads go into the correct location.

To confirm, i have the latest deluge siphon (0.66.6)

On Thursday, 31 March 2016, Steve Bussetti notifications@github.com wrote:

Where are you setting the alternate download location? My extension checks for and uses the value of download_location which is set via the web ui in Settings -> Downloads -> Download to:

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/sbussetti/deluge-siphon/issues/22#issuecomment-204144036

kev12345 commented 8 years ago

Deluge v1.3.10 installed

On Thursday, 31 March 2016, Steve Bussetti notifications@github.com wrote:

Also, what is the actual version number of Deluge you're running?

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/sbussetti/deluge-siphon/issues/22#issuecomment-204144297

kev12345 commented 8 years ago

Just a thought,

The deluge developers released some new instructions recently on how to install deluge as a service rather than have it open using init.d and other auto-start methods and so i reinstalled deluge using these instructions. Having done this i noticed the deluge config (core.conf) now lives in /var/lib/deluge/.config/deluge and I also believe there is another core.conf elsewhere which my deluge isn't using.. Perhaps deluge siphon is accessing that other core.conf for the download_location..? As i said, 'remote torrent adder' is working fine for me so there's obviously a way around it somehow...

On Thursday, 31 March 2016, Steve Bussetti notifications@github.com wrote:

Where are you setting the alternate download location? My extension checks for and uses the value of download_location which is set via the web ui in Settings -> Downloads -> Download to:

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/sbussetti/deluge-siphon/issues/22#issuecomment-204144036

kev12345 commented 8 years ago

Just to clarify, when i say i reinstalled deluge i mean i installed it afresh, after wiping my Pi and reinstalling Raspbian. So any core.conf files existing are there as part of the install and aren't old historic files..

On Friday, 1 April 2016, Kevin Kennedy kevkennedy87@gmail.com wrote:

Just a thought,

The deluge developers released some new instructions recently on how to install deluge as a service rather than have it open using init.d and other auto-start methods and so i reinstalled deluge using these instructions. Having done this i noticed the deluge config (core.conf) now lives in /var/lib/deluge/.config/deluge and I also believe there is another core.conf elsewhere which my deluge isn't using.. Perhaps deluge siphon is accessing that other core.conf for the download_location..? As i said, 'remote torrent adder' is working fine for me so there's obviously a way around it somehow...

On Thursday, 31 March 2016, Steve Bussetti <notifications@github.com javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:

Where are you setting the alternate download location? My extension checks for and uses the value of download_location which is set via the web ui in Settings -> Downloads -> Download to:

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/sbussetti/deluge-siphon/issues/22#issuecomment-204144036

ghost commented 8 years ago

Having the same issue - i have deluge core set to download to /downloads/ - yes it shows that way in webui - yet the siphon is defaulting to ~/Downloads - adding torrent files manually works fine n defaults to right folder - siphon fails - using deluge docker from linuxservers.io -- versions below deluge: 1.3.13 libtorrent: 1.0.9.0 siphon 0.66.6

oshotton commented 7 years ago

I'm having the same issue here with deluge running in the LinuxServer Docker container. It always tries to download to the default location of /root/Downloads rather than the download location I have set in Preferences -> Downloads -> Download To. I have also confirmed that it is the same value in the /config/core.conf file. There is no /var/lib/deluge directory in this container though so it's not getting mixed up with other core.conf file.

Adding torrents manually and via the Remote Torrent Added Extension work as expected and download to the directory specified.

Deluge: 1.3.13 Siphon: 0.66.6

sbussetti commented 7 years ago

just released version 0.70.0 please let me know if you're still experiencing this issue