Bug 11275 - InfoBrowser items not accessible via Controller
: InfoBrowser items not accessible via Controller
Status: CLOSED FIXED
Product: SB Controller
Classification: Unclassified
Component: UI
: unspecified
: PC Windows XP
: -- normal with 1 vote (vote)
: 7.3.3
Assigned To: James Richardson
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-07 01:43 UTC by Simon Turner
Modified: 2009-06-17 09:37 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Turner 2009-03-07 01:43:27 UTC
Version: 7.3.3 - 25259 @ Tue Mar 3 03:04:31 PST 2009
XP Pro

The InfoBrowser addons I've installed via Extention Downloader (BBC News & Sport, TVGuide.co.uk, SlimForums) do not sem to work on the SBC (controller), whereas the only one I have downloaded seperately to my server/plugins/InfoBrowserAddons (BBC Weather feed) directory does work.

A vagary is I have also added an rss feed to InfoBrowser via the web gui and this does not work correctly either (http://www.anglersnet.co.uk/forums/rss-1.html).

By "not work" I mean that when I try to select the main body of the news item or post I receive the message: "No Information feeds found. Please use the Squeezecenter interface to add information feeds under Extras/Info Browser". The posts/items are listed but it is not possible to view the actual items.

All the feeds work correctly via the Squeezebox/Boom interfaces and the web gui.

This has been verified as a problem with both SC 7.3 and 7.4, Controller firmwares 3993 & 4154.
Comment 1 Moonbase 2009-03-13 06:36:32 UTC
Confirm. Since upgrading from SC 7.4-25192 (Windows, SBC r4154) to 25416, then 25502, (still r4154 on SBC) many feeds show this message.

Some samples in forum thread:
http://forums.slimdevices.com/showthread.php?p=406011#post406011
Comment 2 Adrian Smith 2009-03-18 10:04:30 UTC
This is due to an update on the server code - I've updated the controller code in change 4842.  Hopefully this will be fixed with the next controller upgrade.
Comment 3 Moonbase 2009-03-20 07:04:26 UTC
Ok, so where to find the current jive.bin builds in order to test?
Comment 4 Moonbase 2009-03-20 07:13:18 UTC
Ok, found it again :-)

jive.bin is only at 4824, not at 4842 -- a typo? Should I test using 4824?
Comment 5 James Richardson 2009-03-20 08:18:54 UTC
7.3 r4673 is the latest release beta version for 7.3.3
7.4 r4824 is the latest release beta version for 7.4
=======================================================
7.3 r4842 is the latest build version for 7.3.x
7.4 r4882 is the latest build version for 7.4
=======================================================
I sent you an email on where to download the build versions, email me if you don't get that or can't access
Comment 6 Simon Turner 2009-03-21 04:33:36 UTC
Sorry to add to noise on this bug but is it likely I'll see this fix as I'm running 7.3.3? Will I need to upgrade to 7.4 for Infobrowser to work correctly again? I'm getting a bit lost with the versions now. I thought 7.4 was going to include some massive changes that would make it unstable at some point so have been very reluctant to use it.
Comment 7 Moonbase 2009-03-23 16:13:41 UTC
Only got 7.3 r4842, can confirm bug fixed using this against SC 7.4-25680.

Would be interested in checking latest 7.4 build too, since the problems from bug 11421 seem also fixed.
Comment 8 James Richardson 2009-03-24 08:43:47 UTC
Let me help clear up the confusion.  A fix is going to be done for 7.3.3 as well as 7.4

Thanks Moonbase for helping to qualify the (unpublished) 7.3.3 firmware.  I will work on getting both a 7.3 & 7.4 version of firmware published to the nightly for everyone to play with.
Comment 9 Anoop Mehta 2009-04-16 12:45:58 UTC
verified fix in SC 7.3.3 r25948
Comment 10 James Richardson 2009-06-17 09:37:11 UTC
This bug has been fixed in the 7.3.3 release version of SqueezeCenter!

If you haven't already. please download the new version from http://www.logitechsqueezebox.com/support/download-squeezecenter.html 

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.