Can not install StvI

[domc]

Help, for some reason I get this message:

STVi import packages may not be imported into this STV.

Please make a copy of c:\sagetv_stvi\sagetv3.stv and set that copy as our sagetv application package before importing into it.

HUH!!??

As you can see, I've moved the sagetv3.stv package to a different directory and I still get this message.

Am I missing something. Did I miss something in the docs? Dunno....
Latest full release version I'm using.

[gplasky]

Originally Posted by domc

Help, for some reason I get this message:

STVi import packages may not be imported into this STV.

Please make a copy of c:\sagetv_stvi\sagetv3.stv and set that copy as our sagetv application package before importing into it.

HUH!!??

As you can see, I've moved the sagetv3.stv package to a different directory and I still get this message.

Am I missing something. Did I miss something in the docs? Dunno....
Latest full release version I'm using.

The STV is probably read-only. Do what it says and make a copy. Use the copy and make sure it is not read only.

Gerry

[blade]

Why not just use the .xml instead of the .stv? Sage will automatically create a new .xml file anytime you import an stvi. Makes it much simplier to import and easier to rollback if something doesn't work correctly.

[stanger89]

Originally Posted by domc

As you can see, I've moved the sagetv3.stv package to a different directory and I still get this message.

Make a copy, and rename it (the copy). It checks for the STV name.

[Opus4]

BTW: for the latest versions, you want to use the sagetv3.xml file, since that is what is updated & shipped now, not sagetv3.stv. It no longer prevents importing into that default file & as mentioned above, it will create a new xml file as part of the import process.

- Andy

[domc]

Ok, got past my problem. Thanks..

So your saying use the .XML file. I'll try that when I get home today.
The default install of Sage uses the sagetv3.stv file though.

So anytime I install a .stv extra, it makes a NEW sagetv3.xml (or whatever you want to call it)?

[Opus4]

Originally Posted by domc

The default install of Sage uses the sagetv3.stv file though.

Not as of v4.1; it uses sagetv3.xml.

So anytime I install a .stv extra, it makes a NEW sagetv3.xml (or whatever you want to call it)?

Yes, it creates a new xml file instead of overwriting the original when doing an import now.

- Andy

[domc]

I don't know why this is giving me trouble.

Did a search in forums and checked the pdf docs and can't find answer.

When I try to install the .XML file instead of the .STV file, when searching for the .XML file to install (inside SageTV Advanced area), it does not show up as a file that is allowed to be installed. In other words, the only file I see is the .STV file. The .XML file is there when checked in Win Explorer.
By the way, extra features is turned on if that matters.

[gplasky]

Originally Posted by domc

I don't know why this is giving me trouble.

Did a search in forums and checked the pdf docs and can't find answer.

When I try to install the .XML file instead of the .STV file, when searching for the .XML file to install (inside SageTV Advanced area), it does not show up as a file that is allowed to be installed. In other words, the only file I see is the .STV file. The .XML file is there when checked in Win Explorer.
By the way, extra features is turned on if that matters.

Once you install an older .STV file it doesn't recognize the .XML extensions. Easy way is to shutdown Sage, go into sageclient.properties file and edit the line that loads the SageTV3.STV file to read SageTV3.XML and then restart Sage.

Gerry

[domc]

Originally Posted by gplasky

Once you install an older .STV file it doesn't recognize the .XML extensions.
Gerry

I could be wrong but this is the first time changing anything in that area. I did a fresh install (just bought sagetv two weeks ago) of the lastest version and the .STV file was in there already.

Oh well...

[gplasky]

By default on the 4.1 install, the default STV file is SageTV3.xml. If you went in and changed it to a SageTV3.stv that is where your issue is. The only way to get it back to SageTV3.xml is either through editing the client properties file or using Studio. I gave you the easier way.

Gerry

[domc]

Yep, edited the Properties file and all is fine.