Bug 1067 – All Songs Called '1' on Browser Interface

Bug 1067 - All Songs Called '1' on Browser Interface

Summary:

All Songs Called '1' on Browser Interface

Status:	RESOLVED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Web Interface
Version:	6.0.0
Platform:	PC Linux (other)

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Dan Sully

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-03-13 06:36 UTC by Dave Pilgrim
Modified:	2011-03-16 04:19 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
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 Dave Pilgrim 2005-03-13 06:36:09 UTC

In the browser interface all songs on all albums by all artists have the same
name: '1'.  This is the case whether browsing by Artist or Album, or going via
Browse Music Folder. Opening existing playlists also produces a list with all
songs called '1'.  

Artist and album info appears to be correct; all songs are correctly named on the 
Squeezebox itself.

Comment 1 Dan Sully 2005-03-13 09:43:29 UTC

Dave - can you please upload your slimserversql.db file to this bug?

Thanks.

Comment 2 Dan Sully 2005-03-13 09:45:05 UTC

Also - what skin are you using?

Comment 3 Dave Pilgrim 2005-03-14 03:13:01 UTC

The reported fix did not fix it for me amd I continue to have all songs with the
same name in my library - album and artist data is correct and drilling down to
the lowest leve by clicking on an individual song reveals that the tags and path
are OK. As before the Squeezebox display is unaffected only the browser info
shows this behaviour.  Seems to be with any skin. Running 03-14 nightly.

Comment 4 Dave Pilgrim 2005-03-14 06:04:13 UTC

Identified as caused by introduction of stray format in Slimserver
(Settings-Title Format) which did not reference the song title tag data.

Comment 5 Chris Owens 2006-06-16 14:41:05 UTC

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.