Forum Stats issue with clean install of vBulletin

[webgeek247]

Incorrect Forum Statistics

I have one topic with one post reply

and it showed

Topics: 1 Posts: 2 Members: 1 Active Members: 1
Welcome to our newest member, Admin.

After I run "Rebuild Forum Information" it showed incorrect stats, so I deleted the topic with replies but still wrong stats. It now shows

Topics: 10 Posts: 10 Members: 1 Active Members: 1
Welcome to our newest member, Admin.

And no matter how many times I run "Rebuild Forum Information" it stays like it?

Is that a bug or something?

I restored complete cPanel backup from earlier today, and the same happens every time. Even if I delete the only 1 topic and 1 post, so it shows "Topics: 0 Posts: 0 Members: 1 Active Members: 1"

And then use "Rebuild Forum Information" it somehow adds exactly 10 topics and 10 posts even though there is no topics or posts at all on a new forum. Why is it adding 10 topics and 10 posts after using "Rebuild Forum Information"?

Such as basic thing isn't working properly and puts me off using vB5 already.

[Paul M]

Incorrect Forum Statistics

I have one topic with one post reply

and it showed

Topics: 1 Posts: 2 Members: 1 Active Members: 1

How is that incorrect ?

[webgeek247]

The stats are correct until I ran "Rebuild Forum Information". As soon as I run that the stats are then incorrect. Just thought I'd try running it and noticed the issue!?

[webgeek247]

Hi Paul, I sent you PM with detailed information of screenshots etc. Hopefully, you know what's going on because I don't. Seems like a bug or something.

[Paul M]

The stats are correct until I ran "Rebuild Forum Information". As soon as I run that the stats are then incorrect. Just thought I'd try running it and noticed the issue!?

Ok, I thought you ran it becasue you considered the stats to be wrong initially.

Hi Paul, I sent you PM with detailed information of screenshots etc. Hopefully, you know what's going on because I don't. Seems like a bug or something.

Sorry, I dont support vB5, so I cannot help you.
If the issue is reproducible, then your best bet is to log it in Jira as a bug.