- March 10, 2006
- 4,434
- 1,897
- Moderator
- #11
I hope somebody will be able to "capture" the moment of corruption in their debug-enabled log files, so that the developers can actually target the source of the problem and fix it.
My best guess is that it is related to thetvdb.com being down, but that's not specific enough to do any good.
So unless somebody can "catch" this problem in the act and have debug-enabled log files to give to the developers, we will be stuck with making backups often, so we can fix it by restoring an older version.
I've tried myself, but I've been unable to replicate this problem ever since it happened to me and I deleted the database out of anger without thinking about the developers. So it is clearly a bug that will be impossible to fix unless somebody is able to replicate it and provide debug-enable log files, or the steps used to cause the problem.
My best guess is that it is related to thetvdb.com being down, but that's not specific enough to do any good.
So unless somebody can "catch" this problem in the act and have debug-enabled log files to give to the developers, we will be stuck with making backups often, so we can fix it by restoring an older version.
I've tried myself, but I've been unable to replicate this problem ever since it happened to me and I deleted the database out of anger without thinking about the developers. So it is clearly a bug that will be impossible to fix unless somebody is able to replicate it and provide debug-enable log files, or the steps used to cause the problem.