Jump to content

Recommended Posts

Posted

Hi,

 

There are differences in the Media Browser Server depending on it being addressed through app.mediabrowser.tv or locally on localhost:8096/web.

 

OSX version: 10.9.5

Media Browser Server3.0.5518.7 (and previous version(s))

Web Browser: Google Chrome, Safari and Firefox. No difference.

 

It is very easily reproduced as simply using the different addresses to access it gives the different behaviour.

 

So far I have found three differences:

  1. The settings menu has icons when accessing locally, no icons via app.mediabrowser.tv
  2. The setting menu has sync option when accessed locally, not via cloud
  3. The setting menu->Plugins does not work for launching plugins when addressed from cloud, but works fine when addressed locally

Here's a picture of items 1 & 2. Item 3 is addressed separately.

 

Viewed from localhost:

 

54e8966738d56_ScreenShot20150221at152009

 

Viewed from app.mediaserver.tv:

54e8969e011ab_ScreenShot20150221at151931

 

I have extracted logs but cannot find any difference anywhere that could be useful. And since it's so super easy to reproduce I have for now not added logs. Please advise if that is needed anyway, and if so what exactly I should do.

 

 -Florux

 

Posted

This is because the app.mediabrowser.tv version will always line up with the current stable release and you were running a beta server.  So you will see differences depending on how you access it.

Posted

Thanks again!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...