Deluge Forum

oki i get that i need feedparser installed and the feeder's .egg file in the ~/.config/deluge/plugins... but i need the code to install feedparser... i am usin ubuntu server edition (hardy)... i already got the file in the plugin folder.. i see the name comming up in the configuration of the web ui .. in the "enabled plugin" page, and it is enabled... but i dont know how to proceed.. i cant c any link for the feeder's interface...

sk90y wrote:oki i get that i need feedparser installed and the feeder's .egg file in the ~/.config/deluge/plugins... but i need the code to install feedparser... i am usin ubuntu server edition (hardy)... i already got the file in the plugin folder.. i see the name comming up in the configuration of the web ui .. in the "enabled plugin" page, and it is enabled... but i dont know how to proceed.. i cant c any link for the feeder's interface...

I had the same problem. Here's what I eventually figured out:

1) install feedparser:
wget http://feedparser.googlecode.com/files/ ... er-4.1.zip
mkdir temp
cd temp
unzip ../feedparser-4.1.zip
sudo python setup.py install
cd ..
2) install feeder
wget http://feeder.winterbird.org/feeder-0.3-src.tar.bz2
mkdir temp
cd temp
bzip2 -d ../feeder-0.3-src.tar.bz2
sudo python setup.py install
3)
restart deluged
restart deluge webui

Now I see a "feeder" section on the "config" menu of the webui.

@ csbook

Thanxxxxx a million man... you are a lifesaver.......

I updated my deluge this morning, using the new commands from the announcement thread, but now my webui + feeder doesn't work.
So I installed the webui manually, but it still wouldn't start.
So I removed my config folder.
I could then get to the webui.
I setup all of my settings again.
I restarted the webui to make sure it worked, and it did.
I then put the .egg in the plugins folder.
I followed csbook's directions (thanks)
tried to start the webui, and it throws the exact same error as before.

Something with feeder is causing the newest(2/26/09) webui to not start.
I guess updating was a bad idea.

draggy wrote:I updated my deluge this morning, using the new commands from the announcement thread, but now my webui + feeder doesn't work.
So I installed the webui manually, but it still wouldn't start.
So I removed my config folder.
I could then get to the webui.
I setup all of my settings again.
I restarted the webui to make sure it worked, and it did.
I then put the .egg in the plugins folder.
I followed csbook's directions (thanks)
tried to start the webui, and it throws the exact same error as before.

Something with feeder is causing the newest(2/26/09) webui to not start.

Code: Select all

$ deluged
$ deluge -u web
[ERROR   ] 09:42:02 ui:65 Unable to find the requested UI: web.  Please select a different UI with the '-u' option or alternatively use the '-s' option to select a different default UI.
Traceback (most recent call last):
  File "/usr/bin/deluge", line 8, in <module>
    load_entry_point('deluge==1.1.3', 'console_scripts', 'deluge')()
  File "/var/lib/python-support/python2.5/deluge/main.py", line 120, in start_ui
    UI(options, args, options.args)
  File "/var/lib/python-support/python2.5/deluge/ui/ui.py", line 66, in __init__
    sys.exit(0)
NameError: global name 'sys' is not defined

I guess updating was a bad idea.

Read this post, http://forum.deluge-torrent.org/viewtop ... =7&t=15995

basically the different ui's have been separated into different packages in the PPA

Right, that's the command I used to update, and then I installed deluge-webui

After I updated, my webui worked until I installed the feeder/parser sources.

did you also do

I did install that. But I just figured it out.

The feeder plugin works fine. What's broken is ssl, enabling it makes the webui not launch at all, even though I have certificates.

I must've checked it and not realized. Apologies for cluttering this thread.

Does this plugin work when using a daemon too? If so, should I put the egg file on the computer running the daemon or on my client computer (or both)?

negge wrote:Does this plugin work when using a daemon too? If so, should I put the egg file on the computer running the daemon or on my client computer (or both)?

the plugin is meant to be used with the web ui, so you should install the egg in the machine running the daemon, if you use the gtk ui you have to install the Un-official FlexRSS plugin, which must be installed in the machine running the client