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
Development
Improvement Suggestions
Restart on resume
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="HomeY" data-source="post: 1086642" data-attributes="member: 68365"><p>Well, you kinda gave the answer yourself in the last line <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p>When someone wants to release a plugin with a (temp) solution/workaround for the problem, that can't hurt, since it won't touch our core. Our experiences with workarounds is that they tend to stay in the code, instead of being properly fixed, within a specific timeframe after the workaround was added.</p><p>The risk with workarounds is, that when the manufacturer (let's take LightsOut in this example) makes some updates, the 'workaround' code can interfere and cause even more headache.</p><p></p><p></p><p>Nice find <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /> Let's hope you are able to fix the issues with either (or maybe both) your plugins related. This might indeed be the cause of the corrupted databases.</p></blockquote><p></p>
[QUOTE="HomeY, post: 1086642, member: 68365"] Well, you kinda gave the answer yourself in the last line ;) When someone wants to release a plugin with a (temp) solution/workaround for the problem, that can't hurt, since it won't touch our core. Our experiences with workarounds is that they tend to stay in the code, instead of being properly fixed, within a specific timeframe after the workaround was added. The risk with workarounds is, that when the manufacturer (let's take LightsOut in this example) makes some updates, the 'workaround' code can interfere and cause even more headache. Nice find ;) Let's hope you are able to fix the issues with either (or maybe both) your plugins related. This might indeed be the cause of the corrupted databases. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Improvement Suggestions
Restart on resume
Contact us
RSS
Top
Bottom