Bug 6645 – Backtrace for custom language when loading home page.

Bug 6645 - Backtrace for custom language when loading home page.

Summary:

Backtrace for custom language when loading home page.

Status:	CLOSED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Player UI
Version:	7.0
Platform:	Macintosh All

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Michael Herger

URL:	https://slimdevices.campfirenow.com/r...
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-01-18 00:42 UTC by KDF
Modified:	2008-12-18 11:12 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
custom strings file in use at the time. (1.33 KB, text/plain) 2008-01-18 00:44 UTC, KDF	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description KDF 2008-01-18 00:42:52 UTC

Seems to be related to use of SBG on network.  URL linked is the transcript on campfire for the discussion I had with Michael.

Comment 1 KDF 2008-01-18 00:44:30 UTC

Created attachment 2686 [details]
custom strings file in use at the time.

for certain words, I use a custom setup.  My language is set to Canadian (CA)

Comment 2 Michael Herger 2008-01-18 04:19:46 UTC

pre SB2 player with a language not considered failsave doesn't correctly initialize the client strings hash

we should probably make the failsafe check configurable by the strings file itself. This would allow to make a custom language like your CA being recognized as failsafe. But that's for the next S::U::Strings rework. See bug 4828

Comment 3 Michael Herger 2008-01-21 01:58:41 UTC

change 16506 - don't delete failsafe value when processing custom strings file.

Comment 4 Chris Owens 2008-03-07 09:04:34 UTC

This bug is being closed since it was resolved for a version which is now released!  Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html

If you are still seeing this bug, please re-open it and we will consider it for a future release.