MySQL error number: 1052
 

Hi, just the other day, the forum started giving me this error, whenever I tried to look at a deleted post (I'm an admin). As far as I know, there have been no changes to any templates or anything like that, I'd much appreciate it if someone could help me sort this. Also, it's not just me who is getting this error, it appears to be every mod/admin.

if possible, can you tell me what I need to change, and in which file.

Regards, Pete C

Have you edited showpost.php at all ?

I'll ask the other admins.

::EDIT::

The person who is likely to have, if anyone has, is not online right now, I'll ask him and get back to you ASAP, Thanks.

I've aked the others who have access and none of them have edited any files at all, only a few template changes, which are superficial.

Have you edited any of the vB tables (i.e added new fields as part of a hack).

Hi, im a fellow admin.

I created a custom login/registration script based off vbulletin, the login just reads data from the sql database, and for the registration I mimicked the forum's register.php file, basically it adds a new row ONLY in the `user` table. Im guessing the problem might be users who have used this custom registration form and have their data only in a `user` row when I needed to add data in some other tables in the database?

I'm not sure, where is data added when a new user signs up using vbulletin (besides `user`)

Can you post the structures of the following tables:

• post
• post_parsed
• user
• userfield
• usertextfield
• icon
• avatar

One or more of these tables seem to have a column named type, which they don't have by default.

My guess is that you added a new column 'type' to the user table.

This is the reason the above query is failing. To fix it change it to the fully qualified name. Ie:
[sql]....... ON(deletionlog.primaryid = post.postid AND deletionlog.type = 'post')[/sql]

PS You can not add a new user by only adding him to the user-table. Registering a new user involves more tables then only the user table.

Ahh, yes, I added a column name "type" in the `user` table. So I have to rename this to something else?

Also, the registration script that I made involves only adding data to the `user` table and it looks it worked because new members are able to register with that form and start posting on the forum. What other tables do I have to modify?

You can either rename the field or modify the query, but i'd suggest to rename to field to avoid further problems.
Tables userfield and usertextfield should at least be filled too.

Hmm, I noticed that the userids in `userfield` and `usertextfield` match with those in `user`. However, all those members that registered using my registration form do not have a row in those two tables... what should I do about that?

Also, im guessing that I just have to increment each of those tables by a row so that a new row with the userid of the user registering is made?

Create the missing rows :)

When you insert a new user into table user you will gat an insert id (=userid).
Use this to fill the other tables.

crap, they're a whole load of ones i'd have to add then... knowing that `userfield` and `usertextfield` are empty, what problems would users be facing? what happens if they try to modify the stuff thats there through the forum?

the userid number is auto_increment, so just creating a new row will create the new id for all the other tables too right (this is on registering a new user).

They can't modify their signature, buddy-/ignorelist, pm-folders, subscription folders, search preferences and custom profile fields like Location, Interests, Occupation and Biography.

Yes. Wherever there is a userid, it is the ID for this user (in table user).

You can fix these problems through ACP / Import & Maintenance / Update Counters by clicking Fix Broken User Profiles.

This could more problems if also new members have been added using standard vB functions.

I'm fixing the broken user profiles, and then modifying the registration script to add a new userid in the `userfield` and `usertextfield` tables. That should solve the problems.