This is due to the 'fake' that is the browse new music.  heirarchy is age,
track.  however, 'age' is really just a fake name for album.  This allows the
list to return albums, but then you drop down one level the head is created from
the list of the level above.  So, going down the levels, its called 'album',
going back up, it sees 'age' and thus, no header.

changing line 494 of Pages.pm to:
'nameTransform' => 'age',

fixes the header, but then returns no tracks for the list.
confusing, I know.

ok, the problem is that the header is constructed by looking for the name found
for the level above.  In this case, the level above is 'age'.  however, the
items found are based on 'nameTransform', which is 'album' in this case.  So,
like we do for the find, we can check for 'nameTransform' before we take the
level above.

to fix this, change line 513 of BrowseDB.pm to:
$header = $names{$fieldInfo->{$levels[$level-1]}->{'nameTransform'} ||
$levels[$level-1]};

now...I go back to my lab and eye-straining soldering :)

Fixed in subversion change 3630.

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.