Bug 8969 - After upgrading to 7.1 the web UI is corrupt
: After upgrading to 7.1 the web UI is corrupt
Status: RESOLVED WONTFIX
Product: Logitech Media Server
Classification: Unclassified
Component: Web Interface
: 7.1
: PC Other
: -- normal (vote)
: 7.x
Assigned To: Michael Herger
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-31 11:22 UTC by Dan Evans
Modified: 2009-07-31 10:26 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Evans 2008-07-31 11:22:49 UTC
We're getting a number of calls from customers who've upgraded to 7.1 who say the web UI is messed up.  It appears corrupt in the browser.

Sometimes a reload fixed it.  Sometimes clearing the browser cache fixes it.  So far there's been no report where we could not fix it with one of these workarounds.  (although we have not tried clearing the server cache if need be.  we will if it comes to that.)

Also, I personally saw this when I upgraded from 7.01 to 7.1.  Reloading the page did not fix.  Clearing browser cache did fix it.
Comment 1 KDF 2008-07-31 11:44:47 UTC
probably not much SC can do here, save for abandonning the browser interface.  Browsers seem to be moving to heavier caching. It's worse for the fancier stuff like ajax.  Then again, you could maybe do really ugly things like adding timestamps to every url
Comment 2 James Richardson 2008-08-01 10:32:17 UTC

*** This bug has been marked as a duplicate of bug 8905 ***
Comment 3 Dan Evans 2008-08-01 12:42:47 UTC
James-- I disagree that this is a duplicate of bug 8905.  They sound nothing alike.

KDF-- True, but we don't see this kind of problem every time we upgrade.  From 7.0 to 7.0.1 we never got these calls/emails.  Was something different this time around?
Comment 4 James Richardson 2008-08-01 13:19:33 UTC
Dan: What browser / OS versions are involved in this error.
Comment 5 Michael Herger 2008-08-02 05:11:31 UTC
As Kevin said - there's not much we can do. As soon as we change one line of JavaScript/HTML/CSS code, the browser should reload it. Some browsers cache too aggresively, ignoring timestamps or whatever. As you mention: a full reload will fix this.

We didn't see this in the 7.0.x series as not much was changed. But in 7.1 most of the JS has been rewritten, ExtJS has been updated from 1.1 to 2.1 etc. If a browser doesn't reload the new files it just can't work.

And this is not a dupe of 8905. Bug 8905 was a real bug.

Unless somebody can point me to the real bug, I'll close this as "wontfix".
Comment 6 Michael Herger 2008-08-06 01:13:54 UTC
That's the way web browsers work.
Comment 7 Chris Owens 2009-07-31 10:26:17 UTC
Reduce number of active targets for SC