Deluge Forum

feffe wrote:Updated the first post with the new 0.4 release.

Version 0.4

• fixed sorting of feeds and filters
• Filter history (thanks to dack for the patch)
• removed all configuration in the gtk-ui
• fixed speed settings
• fixed a bug where some filters would not run if some other filters where deactivated
• implemented stop/remove at seed ratio

Some notes about the filter history:

The history is saved on a clean shutdown, meaning if deluge crashes or is forcefully killed it may want to download some torrents again... No major issue, but I thought I should mention it. A somewhat more important issue is that a URL is always added to the history on the first match, regardless if the torrent was successfully added to deluge or not, so if the torrent file is temporary unavailable when it's first matched it won't be downloaded. At the moment I can't see any good way to work around this...

now enjoy the new version and let me know if you find any undocumented features

Thanks, gonna try this!

Is the max connections bug fixed now?

Kwb wrote:Is the max connections bug fixed now?

Should be...

feffe wrote:

Kwb wrote:Is the max connections bug fixed now?

Should be...

Wonderful, gonna try then!! So happy for this

Is it just me, or does only the first feed added work? I haven't tested this extensively, but I've definitely added additional feeds and associated filters, the feeder config implies that these will work, but the torrents are not added to my queue.

I have two feeds and feeder can download just fine from any of them... Are you sure that all your feeds link directly to .torrent files?

feffe wrote:... Are you sure that all your feeds link directly to .torrent files?

That is definitely my problem, thanks!

It is kinda odd, though -- feeder does see something on these feeds, just not the actual torrent files. It lists a number of torrents in parentheses next to each feed, too, which was misleading. When I click on one of the feeds in question and mouse over the listed files, the link target is not to a .torrent file. This explains it. Thanks again!

I just tried to put a Max Connection number and it works fine.
Thank you for this new release, works great! Good job, keep doing so!

Hi,

I am porting my little server over from windows/utorrent over to linux/deluge. So I just installed deluge with feeder today and are controlling the thing with the webui. Everything goes fine. But I think i found a little bug.

I tried to just plain copy my rss filters from utorrent over to feeder. So I tried to copy this one : *True?Blood*

I thought de add filter was already the regx command so, I gave it the name *True?Blood*
After that I discovered it was supposed to be the name, but now I cann't delete the filter anymore and get errors in the webinterface. Looking at the error I think it goes wrong at the ? character in de name.

The first part of the error is : I deleted the config file and tried again without the * and ? in de name, but in the filter, but it goes wrong. Can/should I use regx in the filter settings or does it only support plain text

marnixk wrote:Hi,

I am porting my little server over from windows/utorrent over to linux/deluge. So I just installed deluge with feeder today and are controlling the thing with the webui. Everything goes fine. But I think i found a little bug.

I tried to just plain copy my rss filters from utorrent over to feeder. So I tried to copy this one : *True?Blood*

I thought de add filter was already the regx command so, I gave it the name *True?Blood*
After that I discovered it was supposed to be the name, but now I cann't delete the filter anymore and get errors in the webinterface. Looking at the error I think it goes wrong at the ? character in de name.

The first part of the error is :

Code: Select all

--Deluge Error--
Fault : <Fault 1: "<type 'exceptions.KeyError'>:'*True'">
path : /feeder/filter_settings/*True
file : /usr/lib/pymodules/python2.5/deluge/xmlrpclib.py in close, line 786

I deleted the config file and tried again without the * and ? in de name, but in the filter, but it goes wrong. Can/should I use regx in the filter settings or does it only support plain text

Hello,

I somewhat knew about this... I've had the same problems with a filter with strange characters in the name. There will probably be some sort of fix for that next release (whenever I get round to it).