Probably a bug, not difficult to fix, but unfortunately I have no bandwidth for fixes right now.
These problems will be eliminated with the switch to MySQL for messages, which will probably be dBoard 3.0. We're currently at 1.0. The 2.0 release will be for the switch to MySQL for the member database, which I hope to complete over Christmas.
The problem with a non-database approach, which is what dBoard 1.0 uses, is that new features that require new cuts on the data usually require a new datafile. That's why there are functions at Board Central for rebuilding member message lists, rebuilding member message files, rebuilding forum data, and so forth. These separate data files are necessary because it takes too long to create them at the time of request, but it is easy for them to fall out of sync with the primary data (the primary data is member files at one per member, and the thread files at one per thread) because of occasionally failing processes and bugs. And adding a new datafile, along with the code to rebuild it from scratch from Board Central, is just too time intensive for developers like me.
So when we move to dBoard 3.0 then the data from which the "All Topics" page (and all other pages) is constructed will be fetched on the fly with a single database request and will always be accurate.
In other words, a solution is coming.
-- | Percy |
| EvC Forum Director |