Exception errors

[bits]

I am and have been having a long standing issue with getting backgrounds to show on my SageTV server desktop and on my HD200. This problem goes back to when I was still running v6. I am currently running v7 and have all of the latest everything installed.

Robogeek was nice enough to take a look at my my sagetv_0.txt, bmt log and phoenix log. He noticed that I had a lot of exception errors in the sagetv log and suggested that I post here to get more specific help.

[stuckless]

I'm out of town until monday... so touch base with me again on sunday evening or monday, and I try to help you through this. I can see that the API call HasFanartBackground() is throwing an error, but I'm not why. It could be a jar mismatch issue. When you are in the web ui, what does the phoenix version show as?

[robogeek]

Originally Posted by stuckless

I'm out of town until monday... so touch base with me again on sunday evening or monday, and I try to help you through this. I can see that the API call HasFanartBackground() is throwing an error, but I'm not why. It could be a jar mismatch issue. When you are in the web ui, what does the phoenix version show as?

I'm pretty sure the errors were related to a phoenix property that bits had in his sage.properties file. Somehow the fanartSupportClass was defined as:

phoenix/mediametadata/fanartSupportClass=sagex.phoenix.fanart.SageMCFanartSupport

instead of:

phoenix/mediametadata/fanartSupportClass=sagex.phoenix.fanart.PhoenixFanartSupport

The question is, was that setting changed by a v7 plugin like the SageMC STV or possibly the Phoenix Fanart for Malore Menus plugin, or was that setting set prior to bits upgrading to SageTV v7? If bits had Phoenix and SageMC installed prior to upgrading to v7, then I would presume that is where the setting came from. If that's the case, then the Phoenix plugin should check that property and upgrade it to the proper setting during its installation...if that is possible to do with the new v7 plugin system. But, if it's another v7 plugin changing that value, then we'll have to identify which plugin is causing it and have that plugin author fix the property setting or fix the code in the fanart support class to be compatible with the current version of Phoenix.

[stuckless]

Phoenix will default the property if it's not set. But if it was set previously, then it will do nothing. It would see that if bits had it set, then was set intentionally, since nothing that I'm aware of, will change that value.

[bits]

Originally Posted by stuckless

Phoenix will default the property if it's not set. But if it was set previously, then it will do nothing. It would see that if bits had it set, then was set intentionally, since nothing that I'm aware of, will change that value.

robogeek is correct, when I changed the sage.properties file to match his, everything started working.

I tried to get fanart working months back when I was running v6 but could not and gave up. I then upgraded to v7 and tried to make it work but could not. I do not specifically recall the details of how I went about installing bmt initially so it is possible that I set something wrong. I am pretty sure that I did not mess about directly with the sage.properties file.

I am currently running phoenix version 2.0.3, sagex.api v 7.0.11.0 and SageTV v 7.0.11.232. It would be useful to know how that line got messed up.

robogeek, thanks again for helping me with this problem.

stuckless, thank you for looking at this as well.