patric99 / remote-torrent-adder

Automatically exported from code.google.com/p/remote-torrent-adder
0 stars 1 forks source link

Username not saved in Localstorage when using auth with Transmission WebUI #76

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What version of Chrome are you using? On what operating system?
Version [30.0.1599.101 m] on Windows 7 Enterprise 32bit

What client (version?) are you connecting to? Are you using SSL?
Transmission WebUI, no SSL

What steps will reproduce the problem?
1. open Options page then select WebUI tab
2. fill in required fields, set Username to "transmission"
3. close Options page
4. add any torrent does not work because bad user/password
5. open Options page again
6. the Username field contains "login" instead of "transmission"

What is the expected output? What do you see instead?
See above

Found a workaround:
1. exit Chrome

2. use sqlite3.exe, load database file 
"chrome-extension_oabphaconndgibllomdcjbfdghcmenci_0.localstorage" and execute 
the following
update ItemTable set value = 
X'7400720061006E0073006D0069007300730069006F006E00' where key = 'login';

3. launch Chrome, open Options page, now Username field contains "transmission"

4. now adding a torrent works ok

Original issue reported on code.google.com by colem...@gmail.com on 22 Oct 2013 at 11:11

GoogleCodeExporter commented 9 years ago
for reference: you can edit settings while you're in the extension's options 
page by hitting ctrl+shift+j, then using the "localStorage" variable. no need 
to use an sqlite query.

this behaviour isn't something i've seen before, or can reproduce. have you 
tried removing and re-adding the extension?

Original comment by jul...@gmail.com on 22 Oct 2013 at 11:45

GoogleCodeExporter commented 9 years ago
Tried looking at localStorage variable in the console and it correctly reflects 
the Username field value.
And guess what? Now it works.
I can even see the login value changing in the database as soon as I insert a 
character in the Username field (no need to focus out of the field). I would 
say that saving at each key hit is too much, but whatever.
Probably there was some quirk that needed a restart of Chrome.

Original comment by colem...@gmail.com on 22 Oct 2013 at 12:42

GoogleCodeExporter commented 9 years ago

Original comment by jul...@gmail.com on 11 Jan 2014 at 12:37