CF claims software problem

[MrJim]

http://www.christianforums.com/t7717511/#post62219447

Is this a legit answer? I'm on easily half dozen other forums from tiny to HUGE and they all post members/guests online numbers at the bottom of the front page.

 

[pgp_protector]

One problem is the Version of the software we're running is an old version.
If I'm correct it's vBulletin 3.7.0
The Current Version is 4.2 (If I'm Correct)

And with all the patching they've done, they're unable (Don't ask me why though) to Upgrade it to the current version.

Me. I'd just pull a copy of the database to an offsite server, and see what's required to get it running with the newest version, once done, take the main site down, upgrade to new version & upgrade the Database.

 

[MrJim]

One problem is the Version of the software we're running is an old version.
If I'm correct it's vBulletin 3.7.0
The Current Version is 4.2 (If I'm Correct)

And with all the patching they've done, they're unable (Don't ask me why though) to Upgrade it to the current version.

Me. I'd just pull a copy of the database to an offsite server, and see what's required to get it running with the newest version, once done, take the main site down, upgrade to new version & upgrade the Database.

Hardware limitation? Money?

 

[pgp_protector]

Hardware limitation? Money?

Well their is a fee to upgrade vBulletin.
The hardware was just upgraded a few years ago, if I remember correctly.

 

[NiobiumTragedy]

I wonder if all the mods and addons also have something to do with it? Some of them may end up getting disabled on a newer version of the software.

I'm guessing they just don't want to pay for the new license though.

 

[Sketcher]

I'm not a vBulletin dev, but it doesn't surprise me considering the sheer volume of traffic and the many users who are on at a time. vBulletin is known to be hard on MySQL as it is, and it is not unheard of for a single SQL query to kill a server (especially when you consider it keeps getting repeated due to high traffic). If that is what happened, you either change the code (which may or may not kill the rest of the site) or nix the feature. For a feature that I and probably a good many other people never found useful, the choice is obvious.

 

[EphesiaNZ]

vBulletin is known to be hard on MySQL as it is, and it is not unheard of for a single SQL query to kill a server (especially when you consider it keeps getting repeated due to high traffic).

PostgreSQL: The world's most advanced open source database