Users reported that the ‘solved count’ displayed in profile summaries was incorrect after a recent Discourse update. dr460nf1r3 provided examples showing discrepancies between the summary page and the profile popup, noting that the summary showed inflated numbers (e.g., 485 vs. 475, 90 vs. 40). nat initially suspected the issue stemmed from counting solutions linked to deleted topics, but later identified the real bug: the definition of ‘solved count’ had changed from “how many times a user’s post was marked as solved” to “how many times the user accepted a solution” — effectively swapping the roles of answerer and accepter. This caused large mismatches in displayed counts. nat confirmed the fix and noted that inconsistencies existed even before the migration. The issue was resolved and standardized in this pull request nat, ensuring consistent behavior across Discourse and plugins. dr460nf1r3 thanked the team for the quick resolution.
Hey everyone,
After updating our Discourse instance, we seemingly have incorrect solved amounts when looking at profile summaries. Example:
I already noticed there were a couple of changes lately, including a breaking bug:
The correct amounts are obviously still available so there was likely something happening while migrating the data to the new tables?
Thanks for writing in. I’ll have a look.
There are some discrepancies in counting solutions in Discourse where we were including topics and posts that have already been deleted.
Before the migration, we were indicating:
John has 27 solutions because people marked his post as solution 27 times.
This is stored in the UserActions table.
After the migration, we are now counting:
John has 20 solutions because there are 20 topics where his posts are solutions
This is stored in the SolvedTopics table, and has a direct link to an existing, non-deleted topic.
There’s a subtle difference here - in the first scenario there were no validations in checking if the solution post or its topic still existed.
I’ll check in with our team which is the better number to display. Personally I am leaning counting solutions for topics that still exist.
I’m quite sure that this can’t be the issue — as it would only cause fewer numbers rather than more in some cases, correct? There is another example I have for you:
→ Wrong: Profile - SGS - Garuda Linux Forum
→ Right:
It seems impossible to me that this counting mechanism would more than double the amount of solved post counts. Besides that (of course unconfirmed) I highly doubt that the number of deleted posts was this high in my previous example.
Thanks!
Hmmm yes 485 and 90 are too wide apart.
I believe just found the bug (though the statement about discrepancy I mentioned above is still true) –
In the previous implementation, the solution count in John’s summary is counted by the number of times anyone marked the John’s post as solution
def solved_count
UserAction.where(user: @user).where(action_type: UserAction::SOLVED).count
end
In the new implementation, the solution count in John’s user summary is the number of times John marked a post as solution
def solved_count
DiscourseSolved::SolvedTopic.where(accepter: @user).count
end
This explains the large difference. “solved count” changed definitions from ‘how many times you answered’ to ‘how many times you accepted’.
Will fix the bug, thanks again for the report!
I’ll also update the different counting methods used in profile popup and user summary.
Props to @ondrej for also mentioning Solution badge not working? to me. It looks like some discrepancies were already happening before this migration. Good thing is that we’ll be migrating to a more consistent number across Discourse and our plugins.
Wonderful, thank you very much! 
This is now fixed and standardised - FIX: Standardise the definition of what a solution is by nattsw · Pull Request #352 · discourse/discourse-solved · GitHub
This topic was automatically closed after 2 days. New replies are no longer allowed.