Bugzilla – Bug 606
add some text to 'Player Not Found' screen for troubleshooting/suggestions
Last modified: 2009-01-28 10:20:43 UTC
I get tons of e-mails (increasingly more, after maximum pc started recommending our software to people w/o hardware players) saying 'I get this screen that says my player was not found, what do i do'. Quite often they don't have Squeezeboxen, and are just using software players. Dean's idea was to have the Player Not Found screen link to possibly the remote streaming documentation, and possibly a short FAQ about how the Squeezebox works (and has to connect first, before the player not found message will go away)... So something like: Player Not Found - If you do not have a Squeezebox or SLIMP3, click here for more information. - If you have a Squeezebox or SLIMP3, click here for more information.
how about this: add the following to line 513 of Pages.pm: $params->{'additionalLinks'} = \%additionalLinks; then this to status_noclients.html: <h4>[% "HELP" | string %]</h4> <ul> [% IF additionalLinks.help %] [% FOREACH link = additionalLinks.help %] <li> <a href="[% link.value %]player=[% player | uri %]">[% link.key | string %]</a> </li> [% END %] [% END %] This is a very simple patch and it places the help links under the "player not found" warning. Granted, they could just use the help link, but this makes it more obvious and it does include the link for Softsqueeze.
Created attachment 174 [details] add standard help links to no_clients page patch for simple fix described in previous comment. patches Fishbone skin only for now.
The latest nightly has this fixed for the default skin. Please confirm. KDF: Feel free to update your skin (and others)...
I can confirm. changes to Fishbone skin shoudln't be needed as it already used that same string. I'll dobule check tonight as I have a fix for safari to put in as well.
most skins already used the string that has been changed for this. All but Gordon.
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006. I am setting them to targets of 6.2.1 to keep them from showing up in my queries.
Routine bug db maintenance; removing old versions which cause confusion. I apologize for the inconvenience.