OK, more info... I'm using the vehicleprofiles mod which makes the following changes to php files:
functions_user.php
Original:
Code:
// get extra profile fields
$profilefields = $vbulletin->db->query_read_slave("
SELECT * FROM " . TABLE_PREFIX . "profilefield
WHERE editable IN (1,2)
AND form " . iif($formtype, '>= 1', '= 0'). "
ORDER BY displayorder
");
Modified:
Code:
// get extra profile fields
$profilefields = $vbulletin->db->query_read_slave("
SELECT * FROM " . TABLE_PREFIX . "profilefield
WHERE profilefieldid NOT IN (50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65) AND editable IN (1,2)
AND form " . iif($formtype, '>= 1', '= 0'). "
ORDER BY displayorder
");
member.php
Original:
Code:
// CUSTOM PROFILE FIELDS
$profilefields = $db->query_read_slave("
SELECT profilefieldid, required, type, data, def, height
FROM " . TABLE_PREFIX . "profilefield
WHERE form = 0 " . iif(!($permissions['genericpermissions'] & $vbulletin->bf_ugp_genericpermissions['canseehiddencustomfields']), "
AND hidden = 0") . "
ORDER BY displayorder
");
Modified:
Code:
// CUSTOM PROFILE FIELDS
$profilefields = $db->query_read_slave("
SELECT profilefieldid, required, type, data, def, height
FROM " . TABLE_PREFIX . "profilefield
WHERE profilefieldid NOT IN (50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65) AND form = 0 " . iif(!($permissions['genericpermissions'] & $vbulletin->bf_ugp_genericpermissions['canseehiddencustomfields']), "
AND hidden = 0") . "
ORDER BY displayorder
");
Those are the only changes made to any of the actual source files. The code looks fine (keep in mind I am still learning php, but I have years of experience working with dbs - I am an application developer), but I thought there may be an incompatibility that I'm not aware of. However, if I revert the code to original, all the vehicle profile info shows in "Edit Profile" but NOT any that I add manually.