Reply to thread

Message

<blockquote data-quote="RoChess" data-source="post: 719114" data-attributes="member: 18896">I used to rename, move, and delete files with Windows Explorer all the time, and kept getting problems inside MP-TVSeries, eventually leading to full blown database corruption. After deleting the database and starting fresh, I now only do file maintenance from within MP-TVSeries and have never experienced a corruption ever since.Now a lot has changed and the new plugin versions deal with file manipulation outside of the plugin a lot better, but from your explanation it does sound like you did some of those same manipulations as I did. I actually tried to find a scenario that would always lead to corruption, but I would get different results each time I would retry. It is the lack of a reproducable scenario that makes it almost impossible for the developers to then find the problem in their source code.I actually gave up myself, but perhaps you are able to create such a scenario. Just be sure you write down each step required from a fresh install towards the point of corruption, that can be repeated. That way the developer will be able to do the same steps and then trace down the core problem in the source code to fix it.</blockquote>

[QUOTE="RoChess, post: 719114, member: 18896"] I used to rename, move, and delete files with Windows Explorer all the time, and kept getting problems inside MP-TVSeries, eventually leading to full blown database corruption. After deleting the database and starting fresh, I now only do file maintenance from within MP-TVSeries and have never experienced a corruption ever since. Now a lot has changed and the new plugin versions deal with file manipulation outside of the plugin a lot better, but from your explanation it does sound like you did some of those same manipulations as I did. I actually tried to find a scenario that would always lead to corruption, but I would get different results each time I would retry. It is the lack of a reproducable scenario that makes it almost impossible for the developers to then find the problem in their source code. I actually gave up myself, but perhaps you are able to create such a scenario. Just be sure you write down each step required from a fresh install towards the point of corruption, that can be repeated. That way the developer will be able to do the same steps and then trace down the core problem in the source code to fix it. [/QUOTE]

Verification