Upon doing some data mining of our registered users, I discovered that on a certain day, all of the profile information stopped being stored in the profile_values table, they are stored in the data field in the users table. That was the same day I installed loggintoboggin. Was there a bug that caused this? Will it be fixed if I upgrade? How can I get my user data back into the right table?

Thanks.

Comments

hunmonk’s picture

Assigned: Unassigned » hunmonk
Category: support » bug
Status: Active » Fixed

yes, unfortunately, logintoboggan and profile module have never played well together, due to the fact that profile module has hardcoded checks for the 'user/register' path in its code, and LT uses different paths. i thought i had put enough hacks in LT to work around these problems, but apparently i missed one... :)

this has been fixed in the latest CVS version of 4.6 (tarball will take about a day to update), and isn't an issue at all in 4.7, because the regular user paths are used. upgrading to either one of these will solve this issue for future user registrations. unfortunately, there's no easy way to migrate the already existing data from the user table to the profile_values table. you'll either need to write a custom script to do that, or just do it by hand.

hunmonk’s picture

Title: profile values aren't being stored in profile_values » move profile values into profile_values table
Version: 4.6.x-1.x-dev » 4.7.x-1.x-dev
Category: bug » task
Status: Fixed » Active

on second thought, i may have figured out a relatively easy way to script a fix for this. i'll work on it over the next few days and commit it to the 4.7 upgrade path if all goes well. you'll obviously need to upgrade to 4.7 if you want to take advantage of the script. :)

hunmonk’s picture

Status: Active » Fixed

ok, i've embedded the fix for this problem into the LT updates for 4.7--the data is now extracted from the data column and inserted into its correct location in the profile_values table. i've spent a fair amount of time testing to make sure it works properly, but _please_ make sure you back up your database before trying this upgrade! (something you should always do anyways). also, you may want to read the important note i posted at http://drupal.org/project/logintoboggan -- it details a bug in the previous upgrade code that may interfere with this particular fix, and data in the data column of the user table in general.

Anonymous’s picture

Status: Fixed » Closed (fixed)