Created attachment 2802 [details]
Blank screen with missing error message.

anyone know if this ever worked?

after getting SC to forget my SN login, I turned on comet debugging and dropped into the pandora menu.

When there's no SN information Jive/SC get stuck in a feedback loop and endlessly request the item. Here's one of the thousands that hit the console--

[10:31:21.6737] Slim::Web::Cometd::handler (145) Cometd request: [
  {
    channel => "/slim/request",
    data => {
          request  => [
                        "00:04:20:06:33:d0",
                        ["pandora", "items", 0, 200, "menu:pandora", "item_id:0"],
                      ],
          response => "/85757cac/slim/request",
        },
    id => 1101,
  },
]
[10:31:21.7219] Slim::Buttons::XMLBrowser::_cliQuery_error (1968) Error: While retrieving [http://www.squeezenetwork.com:3000/api/pandora/v1/opml/stations]: [A SqueezeNetwork account is required for this service. Please access SqueezeCenter Settings -> SqueezeNetwork with a web browser to configure.]
[10:31:21.7223] Slim::Web::Cometd::handleRequest (778) Request for /85757cac/slim/request / 1101 is not async
[10:31:21.7227] Slim::Web::Cometd::Manager::deliver_events (209) Sending event on channel /85757cac/slim/request to 85757cac
[10:31:21.7236] Slim::Web::Cometd::Manager::deliver_events (223) Delivering events to 85757cac:
[
  {
    channel => "/85757cac/slim/request",
    data => {
          # tied Tie::IxHash
          count => 0,
          networkerror => 1,
        },
    ext => { priority => "" },
    id => 1101,
  },
]

OK I guess this never worked, since that particular error is handled like an HTTP error which Jive has no knowledge of, it just gets a 'networkerror' key back.  This may be able to be fixed by letting SC request the real URL and having SN return the proper error message in OPML.  I can try to fix this if you want.

There is still another bug here and that is that any kind of HTTP error is not going to be displayed on Jive.

On second thought, it doesn't make sense to change the SN code here.  Jive needs to handle the networkerror case anyway, so I'll see about making the networkerror key return the actual error string though, instead of just a 1.

Change 17170 fixes the networkerror key.

along with Andy's fix in change 17170, jive r1812 fixes this issue

Description: add textarea window when data.networkerror comes down the browse sink
also fixes endless loop of requests when networkerror occurs

Created attachment 2816 [details]
screenshot of bug fix

This bug has recently been fixed in the latest release of SqueezeCenter 7.0.1

Please try that version, if you still see the error, then reopen this bug.

To download this version, please navigate to: http://www.slimdevices.com/su_downloads.html