Bug 4333 - Mixerlinks taken out of browse years
: Mixerlinks taken out of browse years
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: MusicIP
: 6.5.0
: PC Windows (legacy)
: P2 normal (vote)
: ---
Assigned To: Dan Sully
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-10-10 12:07 UTC by KDF
Modified: 2006-10-21 14:08 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments
proposed patch (4.45 KB, patch)
2006-10-10 18:25 UTC, KDF
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description KDF 2006-10-10 12:07:12 UTC
removed in change 8679.  from the comment on that change, it is not clear why the code was removed.  presumably it was accidental: Description: Make Years be their own object, to remove special cases.

diff to add back in:
Index: Slim/Schema/Year.pm
================================================== =================
--- Slim/Schema/Year.pm (revision 10266)
+++ Slim/Schema/Year.pm (working copy)
@@ -46,6 +46,15 @@
my ($self, $form, $descend, $sort) = @_;

$form->{'text'} = $self->name;
+
+ my $Imports = Slim::Music::Import->importers;
+
+ for my $mixer (keys %{$Imports}) {
+
+ if (defined $Imports->{$mixer}->{'mixerlink'}) {
+ &{$Imports->{$mixer}->{'mixerlink'}}($self, $form, $descend);
+ }
+ }
}

1;

If there is still time, it might be nice to get this back into 6.5.1
Comment 1 KDF 2006-10-10 18:25:21 UTC
Created attachment 1634 [details]
proposed patch

add back the mixerlinks under browse year.  Also add src_mix params for the pwdlist, and a couple of trivial fixes for other src_mix cases, and removal of extra &'s in mixerlink query url.
Comment 2 Chris Owens 2006-10-11 11:34:41 UTC
I would be concerned about adding this patch at this late date, but perhaps Dan has another opinion.
Comment 3 KDF 2006-10-12 21:15:56 UTC
added into trunk at change 10309. at least this way it will see more open use.
Comment 4 KDF 2006-10-21 12:59:28 UTC
dan, is this something we can put back into 6.5.1? or shoudl I close this as something that is only going to be back when it comes to 7.0?
Comment 5 Dan Sully 2006-10-21 13:54:59 UTC
Since the plugin has been fixed, I'm ok with putting it back.
Comment 6 KDF 2006-10-21 14:08:48 UTC
in 6.5.1 at change 10434, with changelog note moved from 7 to 6.5