We use cookies to help make our site work properly and to analyze how our site is used. Some are optional, but none contain your personal information, and we don't use any for ads. You can view our cookies policy, manage your cookie preferences, or consent and dismiss this banner by clicking agree:

Agree
ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Need to update members_data with SALT for EE 2.3 and cannot do a fresh install...

March 27, 2012 5:18pm

Subscribe [1]

  • #1 / Mar 27, 2012 5:18pm

    Trend Hunter

    81 posts

    This question may be related to these threads: resolved thread and resolved thread.

    I’ve seen a couple related threads on this issue, but they required full re-installs, to properly fix.

    We completed our upgrade from EE1.67 to 2.31 and our member_data table is missing the SALT column.  This means people cannot change their passwords, there are occasional login issues and people can’t benefit from having salted passwords.

    ===================
    A Database Error Occurred

    Error Number: 1054

    Unknown column ‘salt’ in ‘field list’

    UPDATE `exp_members` SET `salt` = ‘L`Y;h3$;En@vD…...............
    =======================

    IF the column is simply added, users end up being able to login once, but then cannot login again (which was what happened in the other ticket) because their passwords get salted and stop working… One of the threads was resolved by the guy reverting back to his old table (Which didn’t have salt)  and others have been resolved by re-installing EE, which doesn’t work for us because we have too many steps related to our install….

    So, we are looking for a way to upgrade / fix our member table.  Any ideas?

  • #2 / Mar 28, 2012 5:42pm

    Dan Decker

    7338 posts

    Hi Trend Hunter,

    I’m sorry this has come up as a problem for you. I’m concerned that if this column is missing, what else was left out of the upgrade process.

    Did you have any errors during the upgrade? That column is added in the 2.2.0 update script, and some other tables are updated as well.

    We need to figure out where the update broke down. In order to do that, you are going to need run some SQL statements for me. In Tools->Data->SQL Manager Database Query Form and run describe on members, sessions, password_lockout and files.

    DESCRIBE exp_members

    Please post the output of those statements with your reply. Then we can start stepping though the process to get you properly upgraded.

    I look forward to your reply.

    Cheers,

  • #3 / Mar 29, 2012 1:24pm

    Trend Hunter

    81 posts

    Thanks for the reply.  Below are the ‘describes’ you requested.  For context, we upgraded everything, which took a couple weeks, and then we had to go back and refresh our member database and articles, which is probably where the problems were created.  

    exp_members

Field Type Null Key Default Extra
member_id int(10) unsigned NO PRI  auto_increment
group_id smallint(4) NO MUL 0 
channel_id int(6) unsigned NO  0 
tmpl_group_id int(6) unsigned NO  0 
upload_id int(6) unsigned NO  0 
username varchar(50) NO MUL  
screen_name varchar(50) NO   
password varchar(40) NO MUL  
unique_id varchar(40) NO MUL  
authcode varchar(10) NO   
email varchar(50) NO MUL  
url varchar(75) NO   
location varchar(50) NO   
occupation varchar(80) NO   
interests varchar(120) NO   
bday_d int(2) NO  0 
bday_m int(2) NO  0 
bday_y int(4) NO  0 
gender varchar(6) YES   
aol_im varchar(50) NO   
yahoo_im varchar(50) NO   
msn_im varchar(50) NO   
icq varchar(50) NO   
bio text NO   
signature text NO   
avatar_filename varchar(120) NO   
avatar_width int(4) unsigned NO  0 
avatar_height int(4) unsigned NO  0 
photo_filename varchar(120) NO   
photo_width int(4) unsigned NO  0 
photo_height int(4) unsigned NO  0 
sig_img_filename varchar(120) NO   
sig_img_width int(4) unsigned NO  0 
sig_img_height int(4) unsigned NO  0 
ignore_list text NO   
private_messages int(4) unsigned NO  0 
accept_messages char(1) NO  y 
last_view_bulletins int(10) NO  0 
last_bulletin_date int(10) NO  0 
ip_address varchar(16) NO  0 
join_date int(10) unsigned NO  0 
last_visit int(10) unsigned NO  0 
last_activity int(10) unsigned NO  0 
total_entries smallint(5) unsigned NO  0 
total_comments smallint(5) unsigned NO  0 
total_forum_topics mediumint(8) NO  0 
total_forum_posts mediumint(8) NO  0 
last_entry_date int(10) unsigned NO  0 
last_comment_date int(10) unsigned NO  0 
last_forum_post_date int(10) unsigned NO  0 
last_email_date int(10) unsigned NO  0 
in_authorlist char(1) NO  n 
accept_admin_email char(1) NO  y 
accept_user_email char(1) NO  y 
notify_by_default char(1) NO  y 
notify_of_pm char(1) NO  y 
display_avatars char(1) NO  y 
display_signatures char(1) NO  y 
smart_notifications char(1) NO  y 
language varchar(50) NO   
timezone varchar(8) NO   
daylight_savings char(1) NO  n 
localization_is_site_default char(1) NO  n 
time_format varchar(2) NO  us 
cp_theme varchar(32) NO   
profile_theme varchar(32) NO   
forum_theme varchar(32) NO   
tracker text NO   
template_size varchar(2) NO  28 
notepad text NO   
notepad_size varchar(2) NO  18 
quick_links text NO   
quick_tabs text NO   
pmember_id int(10) NO  0 
profile_views int(10) unsigned NO  0 
facebook_id bigint(20) YES   
twitter_id int(11) YES   
total_ratings int(11) YES   
last_rating_date int(11) YES   
platform_leader int(11) YES   
CustomEmailAlerts varchar(50) NO  None 
remember_me varchar(32) NO  




exp_sessions
=============
Field Type Null Key Default Extra
session_id varchar(40) NO PRI 0 
member_id int(10) NO MUL 0 
admin_sess tinyint(1) NO  0 
ip_address varchar(16) NO  0 
user_agent varchar(120) YES   
last_activity int(10) unsigned NO MUL 0



exp_password_lockout
====================
Field Type Null Key Default Extra
lockout_id int(10) unsigned NO PRI  auto_increment
login_date int(10) unsigned NO MUL 0 
ip_address varchar(16) NO MUL 0 
user_agent varchar(120) YES MUL  
username varchar(50) NO   




exp_files
=========
Field Type Null Key Default Extra
file_id int(10) unsigned NO PRI  auto_increment
site_id int(4) unsigned YES MUL 1 
title varchar(255) YES   
upload_location_id int(4) unsigned YES MUL 0 
rel_path varchar(255) YES   
status char(1) YES  o 
mime_type varchar(255) YES   
file_name varchar(255) YES   
file_size int(10) YES  0 
field_1 text YES   
field_1_fmt tinytext YES   
field_2 text YES   
field_2_fmt tinytext YES   
field_3 text YES   
field_3_fmt tinytext YES   
field_4 text YES   
field_4_fmt tinytext YES   
field_5 text YES   
field_5_fmt tinytext YES   
field_6 text YES   
field_6_fmt tinytext YES   
metadata mediumtext YES   
uploaded_by_member_id int(10) unsigned YES  0 
upload_date int(10) YES   
modified_by_member_id int(10) unsigned YES  0 
modified_date int(10) YES   
file_hw_original varchar(20) YES   
caption text YES

  • #4 / Apr 02, 2012 10:35am

    Trend Hunter

    81 posts

    Any update on next steps? 😊

  • #5 / Apr 03, 2012 1:58pm

    Dan Decker

    7338 posts

    Hi Trend Hunter,

    Indeed, the context explains everything fairly well. Did you take an exp_members export from a live version of your 1.6.7 database and import that into your 2.3.1 installation? If so, that would have wiped out any changed the updater made to that table on it’s way from 1.6.7 to 2.3.1

    I do sympathize with your situation, but the fix is going to be a good bit of work.

    You will need to open /system/expressionengine/installer/updates/ and start with ud_168.php
    Go through each of the update files and look for the changes that are made to exp_members and apply those changes to your current database by hand.

    Do this for each up_xxx.php file until you are complete at 2.3.1

    Let me know if you have any questions along the way.

    Cheers,

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases

© Packet Tide, All Rights Reserved. Legal Notices

Username

Password

Forgot password?
or Register