#2967 closed bug (Fixed)
AutoAdd error with magnet & AutoAdd-1.5-py2.7.egg
Reported by: | enrienri | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 1.3.14 |
Component: | Plugin | Version: | 1.3.13 |
Keywords: | AutoAdd | Cc: |
Description (last modified by )
AutoAdd plugin with Magnet link produce errors.
test16.magnet content
magnet:?xt=urn:btih:<magnet> magnet:?xt=urn:btih:<magnet> magnet:?xt=urn:btih:<magnet>
Of the 3 magnet links above, the Webgui only show up 1 item with error:
Name: <hash> Hash: <hash> Path: /downloads/Deluge Total Size: # of files: 0 Comment: Status: unsupported URL protocol: Mac OS X 2°âATTRÝöâ¨*¨*$com.apple.metadata:_kMDItemUserTagsbplist00 This resource fork intentionally left blank ÿÿ Tracker:
The plugin processed above file and returned a file called .magnet
magnet:?xt=urn:btih:<magnet>
The log are below
[INFO ] 12:18:57 torrentmanager:723 Saving the state at: /data/state/torrents.state [INFO ] 12:18:57 torrentmanager:531 Torrent <hash> added by user: localclient
Attachments (1)
Change History (11)
comment:1 by , 8 years ago
Resolution: | → Fixed |
---|---|
Status: | new → closed |
Version: | other (please specify) → 1.3.13 |
comment:2 by , 8 years ago
I retest with my Mac with Deluge 1.3.13 (client+server), lilbtorrent 1.0.9.0
it does not add the tasks, no error are there, but no tasks are added. It is not working.
I do not see the test1.....magnet.added
I look for the log but not able to see them on my Mac.
comment:3 by , 8 years ago
You need to delete the Autoadd plugin in 1.3.13 package and use the attached plugin.
by , 8 years ago
Attachment: | AutoAdd-1.5-py2.7.egg added |
---|
comment:4 by , 8 years ago
Could you tell me how to properly remove the old default plugin on Mac and Linux? I did a search and did not get how to do it properly.
On my Mac, I delete off the old 1.4 from /Applications/Deluge.app/Contents/Resources/lib/python2.7/deluge-1.3.13-py2.7.egg/deluge/plugins
The entry is still there in the app. I removed the app and get a fresh copy, but the old settings are still there - i.e. I do not know where the config file and previously 1.5 are located.
The behaviour are the same - it take the test.magnet file and do nothing. after the above delete action
comment:5 by , 8 years ago
If you remove the plugin from /Applications/Deluge?.app/Contents/Resources/lib/python2.7/deluge-1.3.13-py2.7.egg/deluge/plugins
then it should not appear at all.
Check you config for any plugins loaded: ~/.config/deluge/plugins
Are you connecting to a daemon? Have you also switched the plugin there?
comment:6 by , 8 years ago
I think I got it working, tested on Mac. A reboot help.
Can you tell me where is the config in Ubuntu? I updated my docker image to ubuntu, but I am not able to see where to delete the old plugin. Strange thing is the one I got default before update is AudoAdd 1.4, after update the docker image show up 1.04, .magnet file does not work at all, even I updated the 1.5 present in the plugins folder / show up in WebGUI
comment:7 by , 8 years ago
After a few restart of my docker image, the AutoAdd plugin should be active, and the "test.magnet" got processed. But it won't return any meaningful results. No log, no item added
The ".magnet" file processed returned the 3rd link.
comment:8 by , 8 years ago
After installing a copy of ubuntu desktop and deluge on it, I get the path of the built-in version of plugin, deleted the AutoAdd 1.04 (yes, 1.04 listed there) and restart the docker, then the .magnet can be recognized properly
The only item missing is from the webgui, the Download > AutoAdd will not be selected on each start, I looked from the thin-client and learnt that there should be a new menu called AutoAdd and should be configure from there. I do not have the thin-client connect to my docker with success, but at this point all are good now. Thanks for solving this for me.
comment:9 by , 8 years ago
Would you mind deleting the magnet link in the ticket? I am not able to delete them. thanks
comment:10 by , 8 years ago
Description: | modified (diff) |
---|
I don't think you are actually running the new version of the AutoAdd plugin. The old plugin is still being loaded.
I have tested with those examples and with latest 1.3-stable code they are all added properly:
1.3-stable commits: [8a3f15e5c0], [b52de1549], [2d4dec669]