Hi:
I don’t think that topic is the same as this issue. Plus, it was 5 years ago which was way before my time.
re: “BTW I don’t see how being a premium or non-premium user can affect you fixing..”
With a platinum premium license we log into users sites to troubleshoot issues. With free licenses we can only offer text based forum support.
re: “…you sold me something that at one point stops working….”
Things can stop working for a variety of reasons. One can’t just buy a plugin and expect it to work forever without keeping it updated. WordPress updates, php updates, theme updates, web server and os updates, hosts changes – lots of reasons for a plugin to stop working unless its updated. And even then, updating other plugins and themes can sometimes introduce compatibility issues – that’s just the nature of the WordPress ecosystem. You get lots of choices but you also get unlimited potential combinations of things, some of which just don’t work well together.
If you had kept your Platinum license in place we would be able to log in and check things out.
It would be impossible to know where to put in the pseudo-code you suggested. If we did then we would likely know how to reproduce the issue in the first place. The plugin has more than 10,000 lines of code…
There are a few things we would need to identify and then potentially fix this issue which makes the pseduo-code suggestion not workable:
1. A site where the issue occurs
2. A set of steps to reproduce the issue and
3. The ability to use a debugger on the site to step through the code to try to get to the point of the error.
One potential solution to try would be to log in as the user who is having the problem to see if you can reproduce the issue. Once you can do that, then mark all the users topics as read. Since the query in the image you posted looks is trying to count the number of new posts, maybe a new post was deleted and is causing an issue with the count. So setting all posts as read might solve the issue.
Thanks.