Phoenix Error after deleting Phoenix UI

[wayner]

I was having problems with my system so I started removing Plugins. I tried Phoenix a while ago but didn't use it full time. So I deleted Phoenix from the FUll UI section of Plugins. Now when I start Sage I get the following error:

Mon Jan 02 00:20:36 GMT-500 2012 - Phoenix Error

Error in VFS File: .\STVs\Phoenix\vfs\x-vfs.xml; .\STVs\Phoenix\vfs\vfs.dtd (The system cannot find the file specified)

How do I fix this?

In the all section of Installed Plugins I have the following Phoenix plugins:

Phoenix API
Phoenix Compatibility Features for Default STV
Phoenix Core Services
Phoenix Fanart for SageTV
Phoenix Fanart for SageTV V7

[sflamm]

Edit sagetv.properties and set standard STV instead of Phoenix.
Likely you still have Phoenix set even though you removed files.

[wayner]

I haven't used the Phoenix UI in months - where would I change this setting? There are hundreds of instances of "phoenix" in my sage.properties.

In sageclient.properties on my server I do have:
last_custom_stv=C\:\\Program Files\\SageTV\\SageTV\\STVs\\SageTV7\\Phoenix STV.309.xml

Should I just delete that line? Does the service have to be stopped to do that?

[sflamm]

Not Phoenix specific - this is whenever you load a custom STV.

Don't need to delete line - just delete value. But deleting line is fine too.
Just make sure SageTV service is stopped first then restart.

[sflamm]

If I remember currently there is also a "current STV" line - that is the one you really want. The "last custom" is for reloading the last custom.

[Fuzzy]

The line is conspicuously called "stv=". That said, this doesn't necessarily sound like the culprit. You wouldn't have a functioning UI if this was still set to load phoenix and phoenix.xml is no longer there. More than likely this is an artifact left over causing the Phoenix API (which you are likely still using with BMT and other fanart related plugins) to parse through the vfs folder.

[jusjoken]

I would disable this one...

Phoenix Compatibility Features for Default STV

As you will not need this if you are not using the Phoenix UI. I think it is just there for when you switch from Phoenix to Sage Default while using the Phoenix UI.

May not solve your problem but you don't need it ( I think )

k

[Fuzzy]

I believe the vfs is parsed for the BMT ui as well, so if there is a problem in those xml files, or those files are missing, it will still probably present that error.

[stuckless]

Originally Posted by Fuzzy

I believe the vfs is parsed for the BMT ui as well, so if there is a problem in those xml files, or those files are missing, it will still probably present that error.

This error, which I see from time to time, is sometimes caused by a timing issue (I haven't looked into it much, to be honest). The x-vfs.xml file is valid, but it requires the DTD to be available when it parses it, and sometimes, the dtd is missing (not sure why) yet it appears there later.

If you have bmt installed and then you will also have an x-vfs.xml file as well. You can delete the file, but phoenix will re-fetch it when it starts up. Pheonix UI is just the visual aspect of Phoenix. "Phoenix" iteself is a library that is used by many other plugins, including BMT.

I have some work that I need to complete on Phoenix (probably next month) and I'll try to tackle this as well, since I have run into this error myslef (but not very often). Typically you are only going to see this when you restart sagetv and I only restart sagetv every 3-4 months, so it's not something that bothers me all that much

[wayner]

Since I found my memory issue (it was caused by too many extenders) I have reinstalled the Phoenix UI and the error did not reappear upon a Sage restart.