upgraded phoenix & stv, now views not loading

[JonTom]

Last night I upgraded all my phoenix plugins, and the default stv, and now none of my custom views are being loaded. BMT and Phoenix don't show them as views anymore (the default views are there but none of mine are in the list). The xml file is still there and seems to be complete, but I guess isn't being read for some reason. Has the location for user vfs changed? My xml file is in C:\Program Files (x86)\SageTV\SageTV\userdata\Phoenix\vfs

[JonTom]

<view-source name="phoenix.view.primary.recordedtvarchived"/>
<view-source name="phoenix.view.primary.recordedtv"/>

Are these still valid?

[bialio]

Yes, those are still in the x-vfs.xml file.
btl.

[JonTom]

Originally Posted by bialio

Yes, those are still in the x-vfs.xml file.
btl.

On my server, the menu file is being processed (because my custom menu showing my views is showing) but the views are not listed within phoenix or BMT. What would cause the views to not be read? Is it a cache issue of some sort?

They work fine on my PC client (which has not been updated yet).

[stuckless]

Originally Posted by JonTom

On my server, the menu file is being processed (because my custom menu showing my views is showing) but the views are not listed within phoenix or BMT. What would cause the views to not be read? Is it a cache issue of some sort?

They work fine on my PC client (which has not been updated yet).

All vfs files are merged (automatically on startup) into a file SAGE_HOME/Phoenix/cache/vfs-cached.xml. The first few lines of that file will show ALL the files that go into creating that file, so you should be able to see if it's including your views or not.

[JonTom]

Originally Posted by stuckless

All vfs files are merged (automatically on startup) into a file SAGE_HOME/Phoenix/cache/vfs-cached.xml. The first few lines of that file will show ALL the files that go into creating that file, so you should be able to see if it's including your views or not.

It is listed there.

[JonTom]

Should I just delete the whole cache and let it rebuild?

[stuckless]

Originally Posted by JonTom

Should I just delete the whole cache and let it rebuild?

deleting the cache, and restarting sagetv will force rebuilt... and I think, using BMT's Refresh menu will do the same.

[JonTom]

Originally Posted by stuckless

deleting the cache, and restarting sagetv will force rebuilt... and I think, using BMT's Refresh menu will do the same.

no change... what is going on?

[JonTom]

Well, my PC client has a copy of the vfs file, so I renamed my server's copy of the file and put the client's version in place (it has a different name). This seems to have fixed it as the views are working again.

Now to do a compare on the two vfs files.

[JonTom]

The only difference between the two files is the following view:

<view name="JW_recentartists" label="Recently Added Artists" visible="true">
<tag value="music"/>
<view-source name="phoenix.view.source.music"/>
<presentation level="1">
<group by="artist"/>
<sort by="recentactivity">
<option name="sort-order" value="desc"/>
</sort>
</presentation>
<presentation level="2">
<group by="album"/>k
<sort by="track"/>
</presentation>
</view>

Which existed in the old, non-working version but hadn't been added into the client version yet. When I add that code the working vfs file on the server, all the views stop working and showing up in BMT/Phoenix.

That view worked fine until the latest updates, which included:

• phoenix core and/or api?
• phoenix
• groovy
• sagetv web interface
• the latest default stv (which I understand was supposed to help witn online videos but didn't)
• latest java update

Anybody see a reason for that behaviour?

[stuckless]

Originally Posted by JonTom

The only difference between the two files is the following view:

<view name="JW_recentartists" label="Recently Added Artists" visible="true">
<tag value="music"/>
<view-source name="phoenix.view.source.music"/>
<presentation level="1">
<group by="artist"/>
<sort by="recentactivity">
<option name="sort-order" value="desc"/>
</sort>
</presentation>
<presentation level="2">
<group by="album"/>k
<sort by="track"/>
</presentation>
</view>

Which existed in the old, non-working version but hadn't been added into the client version yet. When I add that code the working vfs file on the server, all the views stop working and showing up in BMT/Phoenix.

That view worked fine until the latest updates, which included:

• phoenix core and/or api?
• phoenix
• groovy
• sagetv web interface
• the latest default stv (which I understand was supposed to help witn online videos but didn't)
• latest java update

Anybody see a reason for that behaviour?

Zip up all your logs and your vfs files from the server and send them to me (metadatatools at gmail dot com)

[JonTom]

Originally Posted by stuckless

Zip up all your logs and your vfs files from the server and send them to me (metadatatools at gmail dot com)

Which logs?

[Fuzzy]

Originally Posted by JonTom

The only difference between the two files is the following view:

<view name="JW_recentartists" label="Recently Added Artists" visible="true">
<tag value="music"/>
<view-source name="phoenix.view.source.music"/>
<presentation level="1">
<group by="artist"/>
<sort by="recentactivity">
<option name="sort-order" value="desc"/>
</sort>
</presentation>
<presentation level="2">
<group by="album"/>k
<sort by="track"/>
</presentation>
</view>

Which existed in the old, non-working version but hadn't been added into the client version yet. When I add that code the working vfs file on the server, all the views stop working and showing up in BMT/Phoenix.


That view worked fine until the latest updates, which included:

• phoenix core and/or api?
• phoenix
• groovy
• sagetv web interface
• the latest default stv (which I understand was supposed to help witn online videos but didn't)
• latest java update

Anybody see a reason for that behaviour?

You've got an lonely k mucking up your xml there. delete that, and it should work. This was likely causing the XML parse to fail.