Admin/user.php causing errors.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • WizyWyg
    Senior Member
    • Jul 2001
    • 1309
    • 2.3.0

    Admin/user.php causing errors.

    I was experiencing this problem before with member.php and now Im having it with user.php in the admin folder. Basically, if i go to update a user's profile via the admin cp (save changes or update avatar), I get this error:

    Database error in vBulletin Control Panel 2.2.9:
    Invalid SQL: UPDATE userfield SET userid=1,field1='',field2='',field3='',field4='' WHERE userid=1
    mysql error: Unknown column 'field1' in 'field list'
    mysql error number: 1054
    Date: Tuesday 03rd of December 2002 05:10:45 PM
    Script: http://xxx.xxx.xxx.xxx/forums/forums/admin/user.php
    Referer: http://xxx.xxx.xxx.xxx/forums/admin/...t&userid=1
    Now if i go open user.php and comment out this line:

    $DB_site->query("INSERT INTO userfield $userfieldsnames VALUES ($userid$userfields)");
    the error goes away.

    But I dont know if this is related to my earlier problem that I posted earlier today ( new members do not show up in the Admin CP under Users > Find > list all users : http://www.vbulletin.com/forum/showt...threadid=60261 )

    I did a repair on the user and userfield tables in the database and all seems fine.
    I was experiencing this same problem on member.php in the as well on version 2.2.8 and now as well with 2.2.9 for member.php

    The similar problem was posted in this thread:
    http://www.vbulletin.com/forum/showt...threadid=59757 with member.php

    and if I comment out this line:

    $DB_site->query("UPDATE userfield SET userid=$bbuserinfo[userid]$userfields WHERE userid=$bbuserinfo[userid]");
    The error goes away. Is something wrong with my user table? Am I missing a row? Why would these two lines cause the error above?
    There are only 10 types of people in the world: Those who understand binary, and those who don't

  • okrogius
    Senior Member
    • Dec 2001
    • 1149

    #2
    Originally posted by WizyWyg
    I was experiencing this problem before with member.php and now Im having it with user.php in the admin folder. Basically, if i go to update a user's profile via the admin cp (save changes or update avatar), I get this error:



    Now if i go open user.php and comment out this line:



    the error goes away.

    But I dont know if this is related to my earlier problem that I posted earlier today ( new members do not show up in the Admin CP under Users > Find > list all users : http://www.vbulletin.com/forum/showt...threadid=60261 )

    I did a repair on the user and userfield tables in the database and all seems fine.
    I was experiencing this same problem on member.php in the as well on version 2.2.8 and now as well with 2.2.9 for member.php

    The similar problem was posted in this thread:
    http://www.vbulletin.com/forum/showt...threadid=59757 with member.php

    and if I comment out this line:



    The error goes away. Is something wrong with my user table? Am I missing a row? Why would these two lines cause the error above?
    The prime way you woudl get htis is hacking. As you probably know all hacking support is at vbulletin.org.

    But to answer your question, you are missing a column in your database.

    Comment

    • WizyWyg
      Senior Member
      • Jul 2001
      • 1309
      • 2.3.0

      #3
      Okay, what column? And no, there no hacking done to any of the files, so I dont know what or where caused this. This is straight from the zip file member.php and user.php files. Nothing changed in either of them except for the two lines mentioned above.


      I have a test version running as well, just a plain first install with no members, vbulletin install and I can't tell what column is missing. Is it from the User table or the userfield table?
      There are only 10 types of people in the world: Those who understand binary, and those who don't

      Comment

      widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
      Working...