Dang VBulletin V2.2.1

[Aldures]

I just installed vbb tonight and I am having problems with the database. I have never had this problem before and I have done many installs.

Here is the error.

Database error in vBulletin Control Panel 2.2.1:

Invalid SQL: SELECT COUNT(*) AS users FROM user,usergroup WHERE user.usergroupid=usergroup.usergroupid AND usergroup.cancontrolpanel=1 AND user.userid<>
mysql error: You have an error in your SQL syntax near '' at line 1

mysql error number: 1064

It happens when I go to the users area of the cpanel and try and save. I don't have to change any settings, I can even select the admin account and it just doesn't save.

There is also another problem with the templates.

When I expand all, all it says is

CHANGE ORIGINAL

Thats nice and all but there is nothing bound to it so I cannot modify any templates. Grrrr, I hate having stupid problems like this. Hopefully somebody will be able to help me.

Thanks in advance.
T

[Aldures]

Oh there is one thing I want to add. I still don't have my www resolved yet so I am using the IP address in the settings. I don't think this should cause a problem but who the heck knows.

Thanks

[jason]

It sounds like there's a problem with MySQL on your server. You shouldn't be getting MySQL errors inside CPanel, which if I understand you correctly, is what's happening...

If you haven't already, I would open a support ticket on this.

Not having your domain name resolving shouldn't affect anything, but an improper account setup may be to blame...

--Jason

[Julian Muñoz]

I don't remember any problem when I first installed 2.2.1 on my server (that was over a year ago).

Maybe you've modified some files... try to re upload all the files again.

Oh, and try to get the lastest version from the vbulletin site. You will be upgrading your forums to patch some very nasty security bugs.

[Aldures]

GRRRRRRRRRR!!!!!

Well I found the problem last night and was rather miffed on what I found. The problem is V2.2.1 and a newer version of PHP, they aren't compatible. The solution according to Vbulletin is simple, UPGRADE TO V2.2.6 or later. It upsets me that I have to upgrade to a newer version but atleast I know that I am not crazy.

Thanks for the responses folks!!!

[Julian Muñoz]

Oh yeah... I remember some post about it, over vb.com....

Anyway, try to upgrade as soon as possible... You will fix a lot of security problems too