Bug 1337 - when sb2 requires firmware update, web interface links to firmware.html
: when sb2 requires firmware update, web interface links to firmware.html
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Web Interface
: 6.0.1
: All All
: P2 critical (vote)
: ---
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-08 11:08 UTC by Kevin Pearsall
Modified: 2008-08-18 10:54 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 Kevin Pearsall 2005-04-08 11:08:12 UTC
according to dean firmware.html is incompatible with sb2.
Comment 1 Kevin Pearsall 2005-04-19 10:30:06 UTC
i really think this should be changed, since it's very confusing and should be
very simple to fix, right?
Comment 2 Blackketter Dean 2005-06-07 15:28:22 UTC
Yes, this is confusing and wrong for our new SB2 customers.
Comment 3 KDF 2005-06-24 01:16:46 UTC
is the link really needed?  The player always seems to be happy to take the
remote input.  The simple fix here is to just wipe out the link part of the text.
Comment 4 Kevin Pearsall 2005-06-24 12:32:32 UTC
yeah that's what i figured, when it's an sb2 just remove that click here bit...
Comment 5 KDF 2005-06-24 19:19:09 UTC
I tried to do that, but the detection for that is only 'slimp3' vs 'squeezebox'.
 We have to create a new detection (since playermodel is used for other things)
or remove the link for all cases. I'm wondering what cases need the link?
Comment 6 Blackketter Dean 2005-07-05 14:44:09 UTC
Let's remove the link.  It's only for SB1 players that have pre-10 firmware AND the firmware gets 
corrupted.
Comment 7 KDF 2005-07-05 15:22:57 UTC
I'll deal with that tonight if no one gets to it before me.
Comment 8 KDF 2005-07-05 19:24:46 UTC
done at change 3621
Comment 9 Chris Owens 2008-03-11 11:28:08 UTC
This bug was marked resolved in Slimserver 6.1, which is several versions ago.  If you're still seeing this bug, please re-open it.  Thanks!