Bug 13732 - Player setting page stuck displaying Russian
: Player setting page stuck displaying Russian
Status: CLOSED FIXED
Product: MySqueezebox.com
Classification: Unclassified
Component: Web UI
: Test
: PC Windows XP
: P1 normal (vote)
: INXS
Assigned To: Michael Herger
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-27 17:48 UTC by Mickey Gee
Modified: 2009-10-05 16:44 UTC (History)
2 users (show)

See Also:
Category: Bug


Attachments
Screenshot of issue (102.74 KB, image/jpeg)
2009-08-27 17:48 UTC, Mickey Gee
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mickey Gee 2009-08-27 17:48:30 UTC
Created attachment 5735 [details]
Screenshot of issue

The Player setting page got stuck showing Russian strings. I was using IE7 and
first switched to displaying Russian for web pages, and then chose the Players
tab (or whatever it says in Russian). I then chose on Transporter, which
displayed the tab in Russian. 

I then selected the web pages to display in English. The Transporter settings
page was still showing Russian strings. I then clicked on a Boom player which
displayed strings in English. I then switched back to the Transporter and it's
still in Russian.

I can't figure out how to display this page in English!

Screen shot enclosed.
Comment 1 Michael Herger 2009-08-27 19:36:23 UTC
This is IE, isn't it? Which version? I wonder whether it caches content even when AJAXing...
Comment 2 SVN Bot 2009-08-28 01:58:56 UTC
 == Auto-comment from SVN commit #7146 to the network repo by michael ==
 == https://svn.slimdevices.com/network?view=revision&revision=7146 ==

Fixed Bug: 13732 +0.5
Description: prevent caching when doing AJAX background calls

Mickey - those calls were indeed done without cache-prevention. I assume this is now fixed - tested with IE8 only. Please re-open if you can still reproduce this issue.
Comment 3 James Richardson 2009-10-05 16:44:02 UTC
This bug has been fixed in the latest release of MySqueezebox.com (formally known as SqueezeNetwork)!

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.