SMF Support > SMF 2.0.x Support

Database Error from manual version transition

(1/3) > >>

Liv42dayOK:
In order to upgrade from v 2.0 RC1.2 to 2.0.2 I've had to transfer the database info manually from a lot of the old tables.  It just wouldn't happen using the package manager because I modified the existing site so extensively.  So, I made another folder on my host and built the new site from scratch.  Most of everything went well with copying the old MySql Db info into the new one and all the "settings" I just simply re-did on the new site manually.  However, there are a couple of exceptions due to a change in table names.  (I.E.  smf_cf_fields  to smf_custom_fields - if there IS any way to get past that, I'd greatly appreciate knowing how!)

Anyway, everything on the site works except when I try to access a member's profile.  When I try to access one, I get the following database error message:

Unknown column 'mem.pm_receive_from' in 'field list'
File: /XXXXX/XXXX/public_html/XXXXX/Sources/Load.php
Line: 1005

The code occurs here:

--- Code: ---elseif ($set == 'profile')
{
$select_columns = '
IFNULL(lo.log_time, 0) AS is_online, IFNULL(a.id_attach, 0) AS id_attach, a.filename, a.attachment_type,
mem.signature, mem.personal_text, mem.location, mem.gender, mem.avatar, mem.id_member, mem.member_name,
mem.real_name, mem.email_address, mem.hide_email, mem.date_registered, mem.website_title, mem.website_url,
mem.openid_uri, mem.birthdate, mem.icq, mem.aim, mem.yim, mem.msn, mem.posts, mem.last_login, mem.karma_good,
mem.karma_bad, mem.member_ip, mem.member_ip2, mem.lngfile, mem.id_group, mem.id_theme, mem.buddy_list,
mem.pm_ignore_list, mem.pm_email_notify, mem.pm_receive_from, mem.time_offset' . (!empty($modSettings['titlesEnable']) ? ', mem.usertitle' : '') . ',
--- End code ---

Db version:  MySql 5.1.63-community-log

Any way to fix this?  - Thanks!

Arantor:
It's not supposed to happen via the package manager, for upgrades like that you're supposed to use the Large Upgrade package, because that needs to change various parts of the database. The upgrader will even fix the custom fields for you.

Liv42dayOK:
Well, that's what I tried and it wouldn't happen.  The large upgrade.  I got errors on the database when I did.  I sure wish it would have worked because it would have saved me the time already invested. 

Arantor:
How, exactly, did you perform the large upgrade?

The correct procedure is to upload all the files on top of the old ones, then go to upgrade.php to finish the database work.

Liv42dayOK:
I think I tried to use the package manager.  So, if I run this, it will overwrite all my files, erase all the mods, add-ons (gallery - store) etc?

Navigation

[0] Message Index

[#] Next page