10/08/2013 at 7:48 pm
#271008
Keymaster
@ Jeff
The only time that I can think of that this might occur is during one of the db update routines but I think it’s been well over a year since there was a db update even still it would only occur once.
Is it a possibility that this occurred that long ago and it is only now being noticed? Actually now that I think about it a little more, you would only see dupes when editing an entry, not displaying it if that update db routine failed.
Since updating fixes the issue, that tells me that the actually data in the db is fine and that somehow the cached data that actually is used for display somehow got out of whack.
If you can isolate the steps that are taken in which this occurs, that will help me figure out what the issue might be.
