Opened 12 years ago
Closed 12 years ago
#1370 closed bug (Fixed)
Deluge 1.3.0 WebUI doesn't save preferences properly
Reported by: | Alienfreak | Owned by: | damoxc |
---|---|---|---|
Priority: | major | Milestone: | 1.3.2 |
Component: | Web UI | Version: | 1.3.1 |
Keywords: | Cc: |
Description
Behavior: WebUI Settings (numberic ones only as it seems) are only saved when edited via the up and down arrows not when typed in. Also the Automanaged (and so on) checkbox in the Torrentoptions are always greyed out, even if active. Tested with Chrome & Safari
Expected: Typed in Values to be saved. Correct checkboxes shown.
Reproducable: Yes, just put in some values.
Attachments (1)
Change History (7)
comment:1 Changed 12 years ago by damoxc
- Resolution set to fixed
- Status changed from new to closed
Changed 12 years ago by baltazor
comment:2 Changed 12 years ago by baltazor
- Resolution fixed deleted
- Status changed from closed to reopened
This bug do not fix for me..... I install FreeBSD 8.1 and deluge 1.3.1 (with port) and libtorrent-rasterbar 0.15.1. When I try change settings in Preference: if I write value - settings save, but if I use up/down button - settings save. I use deluged + deluge-web from user torrent Command: deluged --port=9988 --ui-interface=xx.xx.xxx.xxx --logfile=/home/torrent/deluged.log --loglevel=debub deluge-web --fork --port=9989 --logfile=/home/torrent/deluge-web.log --loglevel=debug
I try change: port , max. connect., max. uploads slot et.c.
comment:3 Changed 12 years ago by Cas
- Milestone changed from 1.3.1 to 1.3.x
- Type changed from defect to bug
comment:4 Changed 12 years ago by Cas
- Milestone changed from 1.3.x to 1.3.2
- Version changed from 1.3.0 to 1.3.1
comment:5 Changed 12 years ago by Cas
- Status changed from reopened to pending
Can you append '?dev=true' to the webui url and see if it works correctly.
localhost:8112?dev=true
comment:6 Changed 12 years ago by Cas
- Resolution set to fixed
- Status changed from pending to closed
Two users confirmed fixed with dev option so closing as will be fixed for 1.3.2
This has been fixed in the commit r7fb483adde.