Page 1 of 7

Column setup not saved

Posted: Sat Nov 23, 2013 9:55 am
by tigersoul
The setup for the columns (which visible, how wide) is not saved and the default setting (which are ackward) is always shown upon the next launch. The default setup also looks pretty crappy compared to the more beautiful and thought out webui, why is this?

Re: Column setup not saved

Posted: Sat Nov 23, 2013 7:22 pm
by patrickgmaris
I have the same exact issue. I just got a new mac and still need access to my seedbox via the deluge client. Is there a way to save the interface configuration manually?

Re: Column setup not saved

Posted: Sun Nov 24, 2013 10:56 am
by tigersoul
I doubt there is I tried all ways I could, the web ui looks alot nicer in comparsion :(

Re: Column setup not saved

Posted: Tue Nov 26, 2013 3:32 am
by patrickgmaris
Still bummed by this..

Re: Column setup not saved

Posted: Tue Nov 26, 2013 7:27 am
by tigersoul
Hoping for a reaction by the devs here...

Re: Column setup not saved

Posted: Tue Nov 26, 2013 4:06 pm
by Cas
Are there are any errors in the logs? Do you have screenshots of how it's reverting and also the comparison to webui.

Re: Column setup not saved

Posted: Tue Nov 26, 2013 6:41 pm
by patrickgmaris
Cas wrote:Are there are any errors in the logs? Do you have screenshots of how it's reverting and also the comparison to webui.
http://oi40.tinypic.com/2lsuqgw.jpg
After I customized the layout. Before revert.

http://oi44.tinypic.com/2qulrwy.jpg
After revert.

http://oi43.tinypic.com/24ec2dg.jpg
On WebUI, doesn't revert.

Re: logs, not sure where to find you the logs. Let me know where to find them and i'll supply them here.

Re: Column setup not saved

Posted: Wed Nov 27, 2013 9:57 am
by tigersoul
Experiencing the exact same thing. Cannot add much ;)

Re: Column setup not saved

Posted: Wed Nov 27, 2013 11:41 am
by Cas
Possibly a config issue, try deleting torrentview.state or the entire config (backup first)

Re: Column setup not saved

Posted: Wed Nov 27, 2013 1:11 pm
by tigersoul
I've seen the bug on 3 computers, 2 of them had the client just freshly installed, so I doubt that's it.