Plugin: Web UI for v7

[stuckless]

Originally Posted by Slugger

Ah... I bet I know. You also have BMT/phoenix-core installed? If so, I'm pretty sure you've been hit by this issue. Seems it's also auto filling in ratings for tv shows now, too. And the ratings it's filling in don't quite match the names of the images the web ui has.

Originally Posted by Taddeusz

Yes, I have bmt installed. That must be it.

See this post, for phoenix 2.5.2, which addresses these issues.

[wayner]

I am running Diamond and I see these upgrades for Phoenix Core which I haven't applied yet. Should I be applying those upgrades?

[stuckless]

Originally Posted by wayner

I am running Diamond and I see these upgrades for Phoenix Core which I haven't applied yet. Should I be applying those upgrades?

Diamond does use many core parts of Phoenix (including fanart, vfs, etc), so, it probably would be a good idea... and I know that Jusjoken has added Weather stuff to phoenix (the relationship between Phoenix and Gemstone is a very good one). The couple of releases of Phoenix includes weather updates, metadata/fanart updates and stuff for Phoenix 2 UI.

[rickgillyon]

Any chance we can specify our own sage_all.css? It's a bit of a pain to update, restart Sage, then bring it all down again to bang the CSS file in the WAR file. I'm lazy... Would be much better if it could check somewhere else for an alternate CSS before in the extracted folder...

Thanks for all the effort!

[Slugger]

Originally Posted by rickgillyon

Any chance we can specify our own sage_all.css? It's a bit of a pain to update, restart Sage, then bring it all down again to bang the CSS file in the WAR file. I'm lazy... Would be much better if it could check somewhere else for an alternate CSS before in the extracted folder...

Thanks for all the effort!

Sorry, just isn't going to happen most likely. There are just too many places in the legacy code where I'd have to add support. Just when you think you found and fixed them all, something else would pop up. You can open a ticket for it and next time I'm poking around the code I'll investigate and maybe give it a shot, but the legacy code is just too much to try and make this kind of change. If I did I'd inevitably miss one so your new css would load on 90% of the pages but then not load on the one page you probably care about then I have to go on a wild goose chase to try and track down why that one page doesn't work like the rest of them.

[rickgillyon]

Thanks anyway, I'll open ticket and keep fingers crossed...

[KryptoNyte]

Many times when I manually schedule a TV program by clicking on it in the Web UI guide, then clicking "record," I have noticed that the very next screen will immediately show an "unresolved conflict." The conflict clears as soon as I move on ... just wondering if there is something I can do to avoid this.

Using Internet Explorer 10.

[nyplayer]

Originally Posted by KryptoNyte

Many times when I manually schedule a TV program by clicking on it in the Web UI guide, then clicking "record," I have noticed that the very next screen will immediately show an "unresolved conflict." The conflict clears as soon as I move on ... just wondering if there is something I can do to avoid this.

Using Internet Explorer 10.

This happens even if you do not use the web server. If I record manually It sets a conflict flag in Sage until it checks scheduled recordings to make sure there is no conflict.... then it clears the flag.

[KryptoNyte]

Take me through the steps where you see the same activity in the Sage UI.

[Slugger]

Originally Posted by KryptoNyte

Take me through the steps where you see the same activity in the Sage UI.

Go to EPG, select an airing, mark it for manual record. The conflict icon will show up in the EPG for a second or two then goes away (assuming there is no conflict). This is default STV.

I could "fix" the behaviour in the web ui by simply delaying for 3 seconds before reloading the page after scheduling a manual recording, but it's not really anything to be fixed. But more importantly, there's a greater chance I break something more important trying to fix this so I really won't touch it.

Now depending on your server specs, you may not see the same behaviour in the STV. I'm on a Q6600, which is getting long in the tooth (to be fixed this summer with new server build! ). But you see it on the web ui more often because the web request sets the manual status and polls the rec schedule so fast that you are more likely to catch it in that temp conflict state. As I say, the "fix" is to simply delay that poll after scheduling a manual recording. But it's not a fix that I'd try to implement (risk v. reward; risk of doing more damage is too high, imho).

[KryptoNyte]

Understood. Thanks.

[mikejaner]

Quick question. I access the SageTV web plugin via my Phone, Tablet, Laptop etc... on a constant basis, and am so tired of putting a username and password. I tried to figure this out myself, but short of starting to jack up the jetty.xml, and realm.properties to an unusable state, I am wondering if somebody can help me with just disabling authentication altogether. I don't plan on my SageTV Server web interface being accessible from outside my house, so I am not worried about security.
Thanks ahead for any input or help.

[Slugger]

Originally Posted by mikejaner

Quick question. I access the SageTV web plugin via my Phone, Tablet, Laptop etc... on a constant basis, and am so tired of putting a username and password. I tried to figure this out myself, but short of starting to jack up the jetty.xml, and realm.properties to an unusable state, I am wondering if somebody can help me with just disabling authentication altogether. I don't plan on my SageTV Server web interface being accessible from outside my house, so I am not worried about security.
Thanks ahead for any input or help.

You have to modify the context xml file for the app to disable the auth, there's no other way.

[mikejaner]

Originally Posted by Slugger

You have to modify the context xml file for the app to disable the auth, there's no other way.

That worked thanks!

[waynedunham]

Originally Posted by Slugger

Go to EPG, select an airing, mark it for manual record. The conflict icon will show up in the EPG for a second or two then goes away (assuming there is no conflict). This is default STV.

I could "fix" the behaviour in the web ui by simply delaying for 3 seconds before reloading the page after scheduling a manual recording, but it's not really anything to be fixed. But more importantly, there's a greater chance I break something more important trying to fix this so I really won't touch it.

Now depending on your server specs, you may not see the same behaviour in the STV. I'm on a Q6600, which is getting long in the tooth (to be fixed this summer with new server build! ). But you see it on the web ui more often because the web request sets the manual status and polls the rec schedule so fast that you are more likely to catch it in that temp conflict state. As I say, the "fix" is to simply delay that poll after scheduling a manual recording. But it's not a fix that I'd try to implement (risk v. reward; risk of doing more damage is too high, imho).

Even a few seconds may not be enough. I do manual recordings a LOT (stupid networks that can't tell time causing all kinds of conflicts) and depending on how many things are recording and how "deep" you are into the schedule (i.e. 6-7 days) it may take up to a minute to resolve and update on the schedule and the conflicts ticker at the top of the menu screens. If it is something in today's EPG it usually gets resolved pretty quickly, so even a simple browser refresh within a few seconds should do the trick.

It isn't a web UI problem, it is just one of those nitpicky things that were never fully fixed in SageTv.

[rdefino]

I loaded the sagetv web interface, restarted sagetv and cannot login.

I;m using the address: http://localhost:8080/sage/home

I'm trying this from the sage server itself and useing the sage/frey account and I'm getting:

HTTP ERROR: 503

Problem accessing /sage/home. Reason:
SERVICE_UNAVAILABLE


--------------------------------------------------------------------------------
Powered by Jetty://

[JerryB]

Originally Posted by rdefino

I loaded the sagetv web interface, restarted sagetv and cannot login.

I;m using the address: http://localhost:8080/sage/home

I'm trying this from the sage server itself and useing the sage/frey account and I'm getting:

HTTP ERROR: 503

Problem accessing /sage/home. Reason:
SERVICE_UNAVAILABLE

For some reason, at least on my computer, case is important. Try

http://localhost:8080/sage/Home

and see if that works.

[nyplayer]

If you install via plugin you have to configure the Jetty webserver... and the way to access it is below. If you want to setup port, user or password you have to configure the jetty plugin in the Sage UI... the default is sage the password is frey port 8080

try
http://localhost:8080/apps

[rdefino]

Originally Posted by JerryB

For some reason, at least on my computer, case is important. Try

http://localhost:8080/sage/Home

and see if that works.

That worked. Guess it wanted a capital H for home.

thanks

[JerryB]

Great. Now that we know that you can access the Web UI, may I suggest that you use nyplayer's url if you are also using any other web-based apps such as BMT. That url will open a menu with all your web-based SageTV apps from which you can then select the particular app that you want. For example, if you select SageTV Web Interface from the menu, then it will launch the url that I gave you. If you are only using one web-based app, then you might as well just enter the url for that app directly.