Plugin: Web UI for v7

[rickgillyon]

Originally Posted by hoadie

Hi guys, possibly a dumb question but why is the prerequisit for ver 2.30 a beta version of SageTV?

Shouldn't take long to work out that it has features (e.g. Season/Ep numbers) that are part of that Beta. If you're not using the beta, don't upgrade the Web UI.

[hoadie]

Originally Posted by rickgillyon

Shouldn't take long to work out that it has features (e.g. Season/Ep numbers) that are part of that Beta. If you're not using the beta, don't upgrade the Web UI.

I want to install it from scratch, not upgrade it, and because of the prerequisite checking, it won't install.

[Slugger]

Originally Posted by hoadie

I want to install it from scratch, not upgrade it, and because of the prerequisite checking, it won't install.

Not possible. The Sage plugin manager does not support more than one version of a plugin at a time. So once a plugin moves to a prereq of a beta, you can't install it unless you're running that beta.

With that said, there are ways around this, but they aren't fun. Basically, you'd have to construct your own plugin manifest and install it locally, increasing the version number to be higher than that in the actual repository.

Ask jreichen if he has the manifest handy for the version you need. Take it, increase the version number at top to something higher than 2.30 then install it as SageTVPluginsDev.xml on your Sage server. Then go to plugins in the UI and install the "new" version of the plugin. I would probably number it 2.30.0.0.1 so that when the next update appears (presumably 2.31), you will get notified about it.

NOTE: If you actually do this, you will have to completely uninstall this "new" version before you could install the real 2.30 should you upgrade Sage to a supported level and wish to install version 2.30 of the plugin.

[rickgillyon]

Or you could just install the beta, which is pretty stable and seems a damn sight easier than all that...

[lotusvball]

Originally Posted by rickgillyon

Or you could just install the beta, which is pretty stable and seems a damn sight easier than all that...

I beg to differ on pretty stable. There has been some issues between the new beta and some plugins that are causing some of use "Out of Memory Errors" I am getting close to figuring out which plugins, but I don't have the time to dig right now. There is a reason it is beta.

[rickgillyon]

Originally Posted by lotusvball

There is a reason it is beta.

Yes, because it is pre-release. Obviously.

Stable for me, but then I don't sully my install with many plugins.

[hoadie]

Originally Posted by rickgillyon

Or you could just install the beta, which is pretty stable and seems a damn sight easier than all that...

Yeah thanks but no thanks. As per other posts, there's a reason it's in beta and I'm not that desperate to install it.

[rickgillyon]

Originally Posted by hoadie

there's a reason it's in beta

Second time this statement has appeared. The reason it's in beta is because it's in test by a public user base after a number of previous rounds of testing. It's not in beta because it's inherently unstable!

Having said that, I rarely join beta tests on Sage in the earliest rounds because of the potential WAF problems. This one seems fine.

[lotusvball]

Originally Posted by rickgillyon

This one seems fine.

As I stated before, it is not fine when some of us are getting "Out of Memory" issues that are causing instability. It looks like it is a problem with a plugin or 2 but have not found the root cause yet. I will be doing some logging this weekend and sending into sage. It is in Beta because it is not ready for primetime. As a beta tester I am fine with this, but would not say it is fine until it goes live.

[rickgillyon]

Originally Posted by lotusvball

As a beta tester I am fine with this, but would not say it is fine until it goes live.

Fine for me.

[gplasky]

Originally Posted by lotusvball

As I stated before, it is not fine when some of us are getting "Out of Memory" issues that are causing instability. It looks like it is a problem with a plugin or 2 but have not found the root cause yet. I will be doing some logging this weekend and sending into sage. It is in Beta because it is not ready for primetime. As a beta tester I am fine with this, but would not say it is fine until it goes live.

But a problem with a plugin or two is not a problem with the Sage beta. It is a problem with those plugins. And the first rule of troubleshooting is to disable all the plugins and verify if the issue still exists. If it does then bug it with Sage support. If not then you know it's a plugin and you have more troubleshooting ahead for yourself. I'm not seeing these issues in the beta either. Or in the plugins I use.

Gerry

[toricred]

It's been fine for me. I use several plugins and all of the ones I use work perfectly. I had a problem that showed as out of memory, but that was a drive in it's death throes. Once it was removed everything was fine. This was with 7.1.2.

[sundansx]

So, the only version of the web interface available via the plugin manager (7.0 or 7.1) is sage webserver 2.30? if that is the case, it probably needs to be fixed, as this will be bad for new SageTV users that install the standard product and want to use the web interface. Don't we all want new sagetv users to join the party? It is what will keep the product alive (and narflex, for that matter).

Scenario:
New non-technical user installs sagetv 7 demo from the main link on the site and cruises through the plug in manager. He finds a web interface and does one of these: . Installs it and gets "plug-in not compatible, error". Says to self () "Wow, this SageTV is a real piece of carp". "Hmm, maybe I will try this Windows 7 media center thing, its free. Thats odd, I suddenly feel rage and hate and there are small lightning bolts jumping from my fingers."

Look at that, this guy's life is now ruined.

[Fonceur]

Originally Posted by sundansx

if that is the case, it probably needs to be fixed, as this will be bad for new SageTV users that install the standard product and want to use the web interface.

Well, unless they add a new category for SageTV beta plugin, there is no way to make concurrent versions of a plugin available... So the plugin developer's choices are:

- Ignore the beta features until it gets officially released.
- Force the plugin's users to load the SageTV beta.
- Support features based on the SageTV version, which might be more troubles than it's worth...

[rickgillyon]

Originally Posted by sundansx

it probably needs to be fixed, as this will be bad for new SageTV users that install the standard product and want to use the web interface.

Anyone who wants PVR software with an officially-supported web interface needs to look elsewhere. It's up to the author(s) of this plugin what versions they want to support. They don't owe SageTV any business!

[sundansx]

I did not mean to indicate that the plugin devs owe anybody anything. I have done some plugin development in the past, and I posted that stuff to help the community, not out of some need to please Sage, inc. A healthy plugin community is always stated in SageTV reviews I read and is good for the overall health of the product.
I just wanted to point out that a new intrepid user should not be running the beta (talk about clogging up the forums), but might like to enjoy the excellent web plugin. It is one of the most popular plugins for sage.

This was more an effort to express my thoughts to jreichen, as he is the only one that is likely to do anything about it.

Well, unless they add a new category for SageTV beta plugin, there is no way to make concurrent versions of a plugin available... So the plugin developer's choices are

I agree. Maybe Sage need to release a packager that can create a old style "install from disk STVI" file for beta plugins that have beta release dependencies.

[heffneil]

I think the idea of having roll back versions of plugins might not be such a bad idea? I guess if the plugins are like the apple app store then it is just the latest version but in that case it is very hard to get a beta version of the iphone software unless you are a developer...

Neil

[jsin]

Yeah, I would be happy to see a separate "beta plugins" category in SageTV menu or else would prefer to see Plugin Authors put up two version: "Web UI for v7.0" and "Web UI for v7.1". Of course, over time there will be many versions of the same plugins that will clutter up the interface, but I'm sure SageTV will be able to deal with them properly by v7.5 or v8.0

[heffneil]

I would envision it as the latest version always being the default but if you drilled down in to the the plugin it would show you archived versions...

That way we don't have 4000 plugins in a list. The list wouldn't get any larger.

Neil

[Taddeusz]

I realize I've commented on this before but is it possible for the corners of the items on for example, the Sage Recordings page, to be rounded off, be able to fit within the white frame, or be made to show under the white frame? It looks a little off when you hover over an item and a black square box cuts off part of the inside edge of the white border.