[Fixed] Front page and 'Last Poster' data wrong...

[DDreslough]

Hi!

I've got Vbulletin 2.0.3 running, and for a long time, everything was fine. Recently, though, the board's first pages (the index which would show which areas have new posts, and any pages like this) have started showing incorrect data.

For instance, if I post a new post to Forum 6, it will say that I posted it in Forum 7 and put the 'New Posts Available' marker there. However, when you click on the 'go to last post' button, it takes you to Forum 6's last post.

I've checked and repaired the tables via myisamchk -r and -o. They didn't find anything wrong with the tables themselves. I tried recalibrating the counters, wondering if that would update something. The Update Counters for Threads works fine. But, the Update Counters for Forums keeps crapping out on me.

Any ideas? Run into this before? What should I do now? Thanks!!

I'm going to take down teh board tonight and try myisamchk again, but I'm hesistant to use the extended check because mysql's manual says it can add garbage data to my tables. (I'm using the medium setting so far.) For now, I'm just trying ot reset the counters...We have heavy traffic on weeknights and I don't want to lock them out of their discussions!

www.sportsmogul.com/vbulletin is the forum in question. If you post to the Online Games' category's 'Rants and Raves' section, the new post shows up as having been made in the Leagues section right below it...But, when you click the 'Go to last post' arrow, it takes you to Rants and Raves.

-Dee Dreslough (www.sportsmogul.com)
very satified vBulletin customer, btw. This is the first real problem I've bumped into that wasn't fixable with myisamchk.

[eva2000]

1. make sure you shut down mysql too before myisamchk
2. upgrade to 2.2.x versions since we provide support only for the latest versions

[Icicle Spider]

I just had this same problem with our bulletin board and traced it down to a bug in the updateforumcount($forumid) function in admin/functions.php. I verified that this bug still exists in 2.2.5.

The problem is in this part of updateforumcount:

if ($lastposts['lastpost']>$lastpost) {
$lastposts=$DB_site->query_first("SELECT lastpost,lastposter FROM thread WHERE lastpost='$lastposts[lastpost]'");
$lastpost=$lastposts['lastpost'];
$lastposter=$lastposts['lastposter'];
}
the above select statement should be:

$lastposts=$DB_site->query_first("SELECT lastpost,lastposter FROM thread WHERE forumid=$forumid AND lastpost='$lastposts[lastpost]'");We had the case where two forums had the exact same lastpost timestamp causing the wrong lastposter name to show up.

Let me know if you need any further clarification...

[eva2000]

moved for bug verification :)

[Freddie Bingham]

Seems reasonable to me.

[Floris]

Originally posted by eva2000
2. upgrade to 2.2.x versions since we provide support only for the latest versions

Uhm, I am sorry, but .. When I purchased vB 2.2.1 this year, I read that I had lifetime support for free. And that the renewal option is only optional and gives you access to download latest version. If I do not use this option to renew, I still have the lifetime free support. So even if I can't upgrade to vB 5.x in 3 years, I should get support for 2.2.1 (now 2.2.5) .. or am I reading things wrong? I understand you wish to support only the latest version. But then allow us to get the latest version, which in the above situation should be for free, since we have a lifetime free support. (now I am lost in my own mind)

[Paul]

Does this explain the errors I was seeing when moving the latest thread that was posted? It was not upgrading the counters on the main forum page and would require an update forum counters call through the admin cp.

Paul

[Joshua Clinard]

So am I correct in assuming this will be fixed in 2.2.6?

[Steve Machol]

Yes, anything in the Bugs forum labeled 'Fixed' will be corrected in the next release.

[Paul]

Is the problem I described above with inaccurate "last post" data in the forum home page related to this error? Or should I open another thread in troubleshooting?

Paul

[eva2000]

Originally posted by xiphoid


Uhm, I am sorry, but .. When I purchased vB 2.2.1 this year, I read that I had lifetime support for free. And that the renewal option is only optional and gives you access to download latest version. If I do not use this option to renew, I still have the lifetime free support. So even if I can't upgrade to vB 5.x in 3 years, I should get support for 2.2.1 (now 2.2.5) .. or am I reading things wrong? I understand you wish to support only the latest version. But then allow us to get the latest version, which in the above situation should be for free, since we have a lifetime free support. (now I am lost in my own mind)

when you purchase a owned vB license you have the

- right to use it for life
- official support is for the latest stable/secure version
- members area access payment guarantees you access to upgrades and updates

[Floris]

Originally posted by eva2000


when you purchase a owned vB license you have the

- right to use it for life
- official support is for the latest stable/secure version
- members area access payment guarantees you access to upgrades and updates

Thank you kindly for clearing that up !