Problem with database listing on 2017-03-19 14:50
Posted: Mon Mar 20, 2017 8:07 pm
webfork alerted me to a problem yesterday whereby some old entries were surfacing in the front pages of the default listing.
After some investigation, I have nailed down to 80 entries being affected. There's a field called "display_order" in the database which is updated everytime the entry version string is changed (and the interval between this change and the last is >= 7 days). This field determines the order an entry appears in the listing.
For the affected 80 entries, all of them had their "display_order" changed to '2017-03-19 14:50:01'. This is very strange because another entry called "ver_updated", which is typically changed in tandom with "display_order", is not affected at all.
I have reverted all 80 entries from the db backup. So far, I have not been able to find out what's wrong from either the code or the web server log.
I am posting this for historical reference so that if ever we encounter this again, we can come back to this post.
I will keep trying to look through the code and try to identify any possible bug that might have caused this issue.
After some investigation, I have nailed down to 80 entries being affected. There's a field called "display_order" in the database which is updated everytime the entry version string is changed (and the interval between this change and the last is >= 7 days). This field determines the order an entry appears in the listing.
For the affected 80 entries, all of them had their "display_order" changed to '2017-03-19 14:50:01'. This is very strange because another entry called "ver_updated", which is typically changed in tandom with "display_order", is not affected at all.
I have reverted all 80 entries from the db backup. So far, I have not been able to find out what's wrong from either the code or the web server log.
I am posting this for historical reference so that if ever we encounter this again, we can come back to this post.
I will keep trying to look through the code and try to identify any possible bug that might have caused this issue.