Reply to thread

Message

<blockquote data-quote="RoChess" data-source="post: 1014908" data-attributes="member: 18896">When you say &quot;reinstall&quot;, are you still using the old db3 file? A lot of settings are stored in there, so if you want to properly test, simply rename that database file to something and fire up MP-TVSeries configuration. Then reconfigure everything, but start simple, just feed it a new folder as import path that only contains a few episodes for 1 or 2 shows. So say you normally use &quot;D:\TV Series&quot; and it contains all your shows, then simply enter import path &quot;D:\TV Series\Single Show Example\&quot; on a show that just started or something with 1 or 2 episodes. This will quickly allow you to verify if things work again.&nbsp;Once you are back to a working situation, then you can decide if you want to try to 'repair' the broken old database or start fresh. My experience is that hunting down what is broken can take much longer, then simply entering the full import path and let it reget everything fresh. It is a pain in the ass, but unless you have a good backup/restore system in place and you are able to go back in time to a backup that you know for sure 'works', then it is easier to just reimport everything.&nbsp;This can be problematic when you are on a small capped ISP plan, but if you are not, just let it reimport your entire collection right when you go to bed or do some other task. Before you know it, it will all be done. On a good collection there is no interaction at all needed during the import process, and everything will match 100% automatic. If not then you will just have to spend a little longer manualy correcting the import wizard.&nbsp;PS: One thing you can safely do is export any custom string replacements from the 'old/broken' database, and import them into your 'new' setup (do this from within MP-TVSeries config before you rename/delete the old database), because that is a seperate export/import process and will save you a lot of work if you are like me and have a ton of entries to auto-correct problematic shows during import.</blockquote>

[QUOTE="RoChess, post: 1014908, member: 18896"] When you say "reinstall", are you still using the old db3 file? A lot of settings are stored in there, so if you want to properly test, simply rename that database file to something and fire up MP-TVSeries configuration. Then reconfigure everything, but start simple, just feed it a new folder as import path that only contains a few episodes for 1 or 2 shows. So say you normally use "D:\TV Series" and it contains all your shows, then simply enter import path "D:\TV Series\Single Show Example\" on a show that just started or something with 1 or 2 episodes. This will quickly allow you to verify if things work again. Once you are back to a working situation, then you can decide if you want to try to 'repair' the broken old database or start fresh. My experience is that hunting down what is broken can take much longer, then simply entering the full import path and let it reget everything fresh. It is a pain in the ass, but unless you have a good backup/restore system in place and you are able to go back in time to a backup that you know for sure 'works', then it is easier to just reimport everything. This can be problematic when you are on a small capped ISP plan, but if you are not, just let it reimport your entire collection right when you go to bed or do some other task. Before you know it, it will all be done. On a good collection there is no interaction at all needed during the import process, and everything will match 100% automatic. If not then you will just have to spend a little longer manualy correcting the import wizard. PS: One thing you can safely do is export any custom string replacements from the 'old/broken' database, and import them into your 'new' setup (do this from within MP-TVSeries config before you rename/delete the old database), because that is a seperate export/import process and will save you a lot of work if you are like me and have a ton of entries to auto-correct problematic shows during import. [/QUOTE]

Verification