PDA

View Full Version : Database error : can't view any social groups?



funinthesun
Mon 12th Jan '09, 7:02am
I'm getting this database error when I try to view any of the social groups:

Database error in vBulletin 3.8.0:

Invalid SQL:

SELECT SQL_CALC_FOUND_ROWS
gm.*, user.*, gm.ipaddress AS messageipaddress
,deletionlog.userid AS del_userid, deletionlog.username AS del_username, deletionlog.reason AS del_reason
,avatar.avatarpath, NOT ISNULL(customavatar.userid) AS hascustomavatar, customavatar.dateline AS avatardateline,customavatar.width AS avwidth,customavatar.height AS avheight, customavatar.width_thumb AS avwidth_thumb, customavatar.height_thumb AS avheight_thumb, filedata_thumb, NOT ISNULL(customavatar.userid) AS hascustom

FROM groupmessage AS gm
LEFT JOIN user AS user ON (gm.postuserid = user.userid)
LEFT JOIN avatar AS avatar ON(avatar.avatarid = user.avatarid) LEFT JOIN customavatar AS customavatar ON(customavatar.userid = user.userid)
LEFT JOIN deletionlog AS deletionlog ON (gm.gmid = deletionlog.primaryid AND deletionlog.type = 'groupmessage')

WHERE gm.groupid = 12
AND (gm.state IN ('visible','moderation','deleted'))

ORDER BY gm.dateline DESC
LIMIT 0, 10;

MySQL Error : Unknown column 'gm.groupid' in 'where clause'
Error Number : 1054
Request Date : Monday, January 12th 2009 @ 11:59:43 AM
Error Date : Monday, January 12th 2009 @ 11:59:44 AM
Script : http://www.myforum.com/group.php?groupid=12
Referrer : http://www.myforum.com/groups/
IP Address : **.**.***.***
Username : ********
Classname : vB_Database
MySQL Version : 5.0.67-community


Does anyone know what is causing this? :confused:

Wayne Luke
Mon 12th Jan '09, 12:00pm
This is most likely caused by your installation of vBSEO. Contact them for an upgraded version to fix this issue.

funinthesun
Mon 12th Jan '09, 12:26pm
No it wasn't because of vBSEO. Thanks anyway. Problem now fixed.

Zachery
Mon 12th Jan '09, 12:39pm
What was the issue so we can refrence this for other future users who expirence the same problem?

budg63
Fri 23rd Jan '09, 10:54am
I'd like to know how it was solved as well. Just did the upgrade from 3.7.2 to 3.8.0 this morning and I'm getting the same error. I don't use vBSEO. Any guesses?

Zachery
Fri 23rd Jan '09, 3:28pm
Do you have the vBSEO Sitemap generator?

budg63
Fri 23rd Jan '09, 7:16pm
No, I haven't installed any vBSEO software.

budg63
Sat 24th Jan '09, 10:49pm
Apparently, social groups calls a column named "groupid" and there is no such field in my groupmessage table. Should that column have been added to the table in the 3.8.0 installation I just did?

budg63
Sun 25th Jan '09, 11:05am
Helloooooooo??? (echo)

Anyone here? Any ideas?...aside from vBSEO?

Steve Machol
Sun 25th Jan '09, 11:53am
For future reference, please start your own thread rather than hijacking someone else's.

There is no 'groupid' field in the database anymore, That was replaced with 'gmid'. That error is either from an add-on or an old file.

To troubleshoot this, first reupload all the original vB non-image files (except install.php). Make sure you upload these in ASCII format and overwrite the ones on the server. Also be sure to upload the admincp files to whichever directory you have set in your config.php file. Then run 'Suspect File Versions' in Diagnostics to make sure you have all the original files for your version and that none show 'File does not contain expected contents':

Admin CP -> Maintenance -> Diagnostics -> Suspect File Versions

[Note: In some cases you may also need to remove any of the listed .xml files in the includes/xml directory.]

Next, disable all plugins.

Note: To temporarily disable the plugin system, edit config.php and add this line right under <?php

define('DISABLE_HOOKS', true);

Then if you still have this problem, create a new style and choose no parent style. This will force it to use the default templates. Finally empty your browser cache, close all browser windows then try again. Make sure you change to the new style and view your forums with it.

budg63
Tue 27th Jan '09, 8:15pm
Re-uploading all of the 3.8.0 upgrade files did the trick. Thanks.