Custom Query (2449 matches)

Deluge sort of freezes and all the torrents disappear. The program remains active as clicking on the tray icon brings up the GUI but with no torrents. The program also refuses to close via normal methods when goofed.

When restarted the torrents are back but Deluge rechecks all active torrents and anything downloaded since the last normal closing is lost.

This only seems to happen when a downloading torrent attains a high download speed

Currently, there are two FAQs (​http://dev.deluge-torrent.org/wiki/Faq and ​http://deluge-torrent.org/faq.php). Each of these has largely the same information as the other but in different formats -- however, there are still significant differences in the quality and type of information on the two FAQs. These two FAQs should be merged into one and the wiki FAQ link (besides being made all caps) should be pointed at the faq.php page, dropped, or (perhaps the better option) the header FAQ link should be redirected to the wiki FAQ. It would make maintaining the FAQ a lot easier and less of a hassle for the users. I'd be glad to do this, but I can't locate anywhere to log into the wiki and change the FAQ contents.

BTW, I classed this under webui in the Component dropdown because I didn't see a particular 'website' component to choose from.

Currently, whenever the user goes initially goes to the login page on the web UI, they have to manually change the focus to the password input box (by clicking on the input box or tabbing through the links). Attached, you will find a diff (against the -current version of deluge) to change the focus to the password input box on window load. You will notice from the diff that I have coded the event within a script element on the login page. I looked through the mootools stuff and site, but it appears that the 'addEvents' method is only included with the mootools event package. Since, I didn't see that this mootools package was included with deluge, I therefore hand-coded the focus for the password input box on window load. If you have a better suggestion on how to implement this, I would be glad to hear and implement it.

BTW, you will note that the diff also includes changes to the login failure error message. This is due to the fact that there is a space missing between the comma and the 'try' word. I would also recommend that the error CSS class declaration (in template_style.css) be expanded beyond 200 pixels. The error phrase, "Password is invalid, try again.", is longer than the error class' tiny 200 pixel length.