It's the official 6.5.2 build no nighly or other build.
It's in Slim/Web/Pages/Search.pm
The original code is:
# Normalize the string queries
#
# Turn the track_title into track.title for the query.
# We need the _'s in the form, because . means hash
key.
if ($newKey =~
s/_(titlesearch|namesearch|value)$/\.$1/) {
$params->{$key} = { 'like' =>
Slim::Utils::Text::searchStringSplit($params->{$key}) };
}
# Wildcard searches
if ($newKey =~ /comment/ || $newKey =~ /lyrics/) {
$params->{$key} = { 'like' =>
Slim::Utils::Text::searchStringSplit($params->{$key}) };
}
The line "if ($newKey =~ s/_(titlesearch|namesearch|value)" catches the
comments_value (was comments in 6.5.1) and produces the hash. If you
change to the following it works again:
# Normalize the string queries
#
# Turn the track_title into track.title for the query.
# We need the _'s in the form, because . means hash
key.
if (!$newKey =~ /comment/ && $newKey =~
s/_(titlesearch|namesearch|value)$/\.$1/) {
$params->{$key} = { 'like' =>
Slim::Utils::Text::searchStringSplit($params->{$key}) };
}
# Wildcard searches
if ($newKey =~ /comment/ || $newKey =~ /lyrics/) {
$params->{$key} = { 'like' =>
Slim::Utils::Text::searchStringSplit($params->{$key}) };
$newKey =~ s/_(value)$/\.$1/;
}
Ok, it's not beautiful but it works.
And this is a change in 6.5.2 that I don't understand. It's simply
renamed from comments to comments_value without considering the side
effects of the "_"/"." and hashing.
--
slutz
------------------------------------------------------------------------
slutz's Profile: http://forums.slimdevices.com/member.php?userid=11171
View this thread: http://forums.slimdevices.com/showthread.php?t=35737
_______________________________________________
discuss mailing list
discuss@lists.slimdevices.com
http://lists.slimdevices.com/lists/listinfo/discuss
