home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Area 51 - Testing Area
Skin engine enhancements (themes, guide colors, skin functions, weather settings...)
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="ajp8164" data-source="post: 830877" data-attributes="member: 64375"><p><strong>Re: Skin engine enhancements (themes, guide colors, skin functions, weather settings.</strong></p><p></p><p></p><p></p><p>Hi Mark,</p><p></p><p>Just went through several rounds of very specific testing and I cannot reproduce MP picking up MediaPortal.xml.bak. This is what I do know though:</p><p></p><ul> <li data-xf-list-type="ul">The error message "Exception while attempting to read upgrade xml file Input string was not in a correct format." definitely comes from the Avalon plugin. When I loaded Avalon first (used the Config tool to set the skin) I got the error. When I switched to DefaultWide (again using the Config tool) and start MP I did not get the error message. I search the entire MP code base for this error string; not there. Google'd the string (maybe it was coming from a 3p library), no hit's aside from MP forums. All MP forum hits had to do with skin plugins (similar to Avalon, though not Avalon - must have shared source code at some point). Thought about it for a few minutes and decided to change the label in avalon.version.xml from "Avalon v1.0.0.0 FEAT-3779" back to "Avalon v1.0.0.0"... this single change made the error message go away. During all of these tests I had the genre string you provided in MediaPortal.xml.</li> <li data-xf-list-type="ul">Parsing a MediaPortal.xml string with an apostrophe in it is not a problem. MP uses the standard, out of the box xml parse library supplied in the sdk and there is nothing in the string handling that would cause MP to revert to using the bak file.</li> <li data-xf-list-type="ul">I never observed MP selecting the bak file.</li> <li data-xf-list-type="ul">I am running an updated build (I'll post immediately following this post).</li> </ul><p></p><p>Perhaps there is some other syntax problem in your MediaPortal.xml file that is preventing MP from being able to create the internal representation of the xml document. The only reason MP will try to read the bak file (and subsequently delete the initial xml file) is if it is syntactically incorrect. Make sure you have full closure on all your tags and pay attention to "/" in the closing tags (I know you know this already ;-)</p></blockquote><p></p>
[QUOTE="ajp8164, post: 830877, member: 64375"] [b]Re: Skin engine enhancements (themes, guide colors, skin functions, weather settings.[/b] Hi Mark, Just went through several rounds of very specific testing and I cannot reproduce MP picking up MediaPortal.xml.bak. This is what I do know though: [LIST] [*]The error message "Exception while attempting to read upgrade xml file Input string was not in a correct format." definitely comes from the Avalon plugin. When I loaded Avalon first (used the Config tool to set the skin) I got the error. When I switched to DefaultWide (again using the Config tool) and start MP I did not get the error message. I search the entire MP code base for this error string; not there. Google'd the string (maybe it was coming from a 3p library), no hit's aside from MP forums. All MP forum hits had to do with skin plugins (similar to Avalon, though not Avalon - must have shared source code at some point). Thought about it for a few minutes and decided to change the label in avalon.version.xml from "Avalon v1.0.0.0 FEAT-3779" back to "Avalon v1.0.0.0"... this single change made the error message go away. During all of these tests I had the genre string you provided in MediaPortal.xml. [*]Parsing a MediaPortal.xml string with an apostrophe in it is not a problem. MP uses the standard, out of the box xml parse library supplied in the sdk and there is nothing in the string handling that would cause MP to revert to using the bak file. [*]I never observed MP selecting the bak file. [*]I am running an updated build (I'll post immediately following this post). [/LIST] Perhaps there is some other syntax problem in your MediaPortal.xml file that is preventing MP from being able to create the internal representation of the xml document. The only reason MP will try to read the bak file (and subsequently delete the initial xml file) is if it is syntactically incorrect. Make sure you have full closure on all your tags and pay attention to "/" in the closing tags (I know you know this already ;-) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Area 51 - Testing Area
Skin engine enhancements (themes, guide colors, skin functions, weather settings...)
Contact us
RSS
Top
Bottom