The discussion revolves around the issue of a very high number of “Topics with no response” in the last 30 days on the /admin page, with DeanMarkTaylor assuming it’s due to the site content import. However, even after 9 months, the numbers didn’t correct themselves. Mittineague shared a similar experience with SitePoint, but it took ~100 days for numbers to settle.
DeanMarkTaylor provided a screenshot showing an extremely high number, which codinghorror acknowledged as unusual. Yuun reported the same issue on their forum, which wasn’t an import. After an upgrade via /admin/upgrade, DeanMarkTaylor found that the numbers returned to normal.
codinghorror attributed the fix to neil, who confirmed that a number was being interpreted as a string, causing the issue.
/admin page displays very high number for “Last 30 days” for “Topics with no response”.
I assume this has something to do with the site content being imported and numbers will likely correct themselves after a period of time.
Running v1.4.0.beta3 +113
How long ago was the import?
When SitePoint migrated it took ~100 days for numbers to fall into reason.
* not “no response” at that time, but the TL3 requirements were skewed.,
9 months ago or more.
Well, that certainly seems like long enough time for things to have settled.
Sorry, I have no other ideas about this.
That is.. a lot… of topics with no response.
And the new number for today is:
Just to sanity check here - I can assure you that there isn’t even that many topics, posts and private messages combined in the Discourse installation.
eleven quadrillion ,
one hundred eleven trillion ,
two hundred thirteen billion ,
one hundred fifty two million ,
two hundred twenty one thousand ,
one hundred twenty four
My forum is showing this as well, and it’s not an import. Started clean on Digital Ocean a few months ago.
Numbers were still stupid high today when checking earlier, but was ~eleven quadrillion lower.
I just did an upgrade via /admin/upgrade and now things are looking normal.
I believe @neil fixed this, it was a number that was being interpreted as a string.
Yeah, meta had some numbers that were a weeeee bit wrong…
3 sextillion - love that word.