Bug 13857 - Disabled plugins don't work properly via My Apps
: Disabled plugins don't work properly via My Apps
Status: RESOLVED FIXED
Product: SqueezePlay
Classification: Unclassified
Component: SB Server
: unspecified
: PC Other
: P3 normal with 1 vote (vote)
: 7.6.0
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-09-04 12:13 UTC by Andy Grundman
Modified: 2011-05-25 07:54 UTC (History)
6 users (show)

See Also:
Category: Bug


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Grundman 2009-09-04 12:13:18 UTC
If you disable a plugin and still have the app installed, things work properly on the home menu (SC does not serve the menu, SN does, so you get connected to SN).  However since My Apps is a plain OPML menu, SP has no knowledge of whether the server can play something or not, and fails if you are connected to SC and try to play something that would require a disabled plugin.  SC knows what plugin is required for a given menu, so I think we just need a way to signal SP that the current server can't support the requested menu or something like that.

Note this also applies to the ip3k/web My Apps menus.

This is not a P1.
Comment 1 Michael Herger 2010-01-05 23:31:35 UTC
see bug 15412, and bug 15413: the context menu is missing those items too
Comment 2 Michael Herger 2010-01-05 23:32:15 UTC
*** Bug 15413 has been marked as a duplicate of this bug. ***
Comment 3 Michael Herger 2010-01-05 23:32:38 UTC
*** Bug 15412 has been marked as a duplicate of this bug. ***
Comment 4 Mikael Nyberg 2010-01-05 23:38:50 UTC
I got this the otherway around I installed facebook while the plugin was disabled.

Apps should automatically enable needed server plugins
Comment 5 Michael Herger 2010-02-16 21:58:38 UTC
Isn't this fixed by Alan's recent mysb:// protocl handler work?
Comment 6 Chris Owens 2010-03-15 18:05:07 UTC
7.4.x milestone is in the past
Comment 7 Michael Herger 2011-05-25 07:54:20 UTC
We think this issue has been fixed with the help of Alan's mysb:// protocol handler.

Feel free to re-open this bug report if you still can reproduce it. Thanks!