MediaSignage support forum

community support => Open source Digital Signage => Topic started by: frengix on February 24, 2016, 10:23:07 AM

Title: White Label Issues with mediaSERVER
Post by: frengix on February 24, 2016, 10:23:07 AM
Hi,

As I discovered the hard way that StudioLIte version that comes with mediaSERVER is not the same version as the OpenSource release, I continue finding out some issues. Please check my latest findings:

1. Company name does not appear on title bar instead I see "StidioLite" and the default mediaSignage Logo as a favicon.

2. Footer shows mediasignage inc

3. logout redirects to digitalsignage.com (http://www.digitalsignage.com/msgetstarted/msgetstarted.html#logout)

4. Logo doesn't get changed to one assigned in white label options in Provider Studio.

5. Login page doesn't show company name and logo.

Here is a screenshot of what I mean:
http://oi65.tinypic.com/8x51qq.jpg (http://oi65.tinypic.com/8x51qq.jpg)
Title: Re: White Label Issues with mediaSERVER
Post by: admin on February 25, 2016, 08:24:36 AM
You can update the version on your server anytime directly from the latest fork on Github:
https://github.com/born2net/signagestudio_web-lite

regards
Title: Re: White Label Issues with mediaSERVER
Post by: frengix on February 25, 2016, 10:21:19 AM
AFAIK and as per my chat with support earlier this won,t work.
I am using mediaSERVER not mediaCloud. StudioLite on Github is for mediaCLOUD.
MediaSERVER has its own unique version of StudioLite.
So, What do you suggest?

Regard
Title: Re: White Label Issues with mediaSERVER
Post by: admin on February 26, 2016, 08:52:20 AM
Hi
Actually I think CS maybe have been misinformed so I am making sure they are aware, we only have ONE version of StudioLite.
The one on Github should work just fine...

regards

Sean.
Title: Re: White Label Issues with mediaSERVER
Post by: frengix on February 26, 2016, 09:11:19 AM
Hi

I already have StudioLite from GitHub. It is installed under IIS  with a home directory of
lite-dev/studiolite and only accepts mediaCLOUD users.
The one that comes with media server has the home directory
 studiolite-dist/studiolite
and only accepts mediaSERVER's users.

Also notice that if I use the version from GitHub how would it know the IP of my mediaSERVER to authenticate the user logging in. Instead it defaults to
galaxy.mediasignage.com server.
I hope you get what I mean now.
Title: Re: White Label Issues with mediaSERVER
Post by: admin on February 28, 2016, 10:26:39 AM
the new version once copied to the local mediaSERVER will notice that the URL path is different and should authenticate with your own server.