Member.php File change from vbulletin.com

[hotwheels]

I am not sure if anyone else has noticed, but in vbulletin 3.6, there is a change in the member.php file that affect's how mod's are going to be written, and i am not sure if this is the case in 3.6.1 since i am not running that version.

Anyways, in the past our member.php and a few other file's had this:

PHP Code:

// *********************
// CUSTOM PROFILE FIELDS
$profilefields = $db->query_read("
 SELECT profilefieldid, required, title, 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
"); 


This above example is from 3.5, 3.0, etc. (please notice the word title in the above query), now in 3.6

PHP 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
"); 


As you can see, the word "title" no longer exist's and therefore is not available to modify when it come's to running a query for your profilefield.

I asked over at vbulletin.com about how to go about reinstalling this word back into our Vbulletin 3.6 version's and this was the response i recieved:

Originally Posted by feldon23

This kind of question is reserved for vBulletin.org.

My response back:

Originally Posted by hotwheels

That is an interesting thought, but .org didn't write the member.php. The line used to be in our vbulletin 3.5, but i am not seeing it in 3.6. So i figured it was moved to a different php file and i was just overlooking something.

Final vbulletin.com response:

Originally Posted by feldon23

Modification or dependance upon the behavior of the vBulletin code, at an underlying level, such as database access, is the purview of vBulletin.org. The fact that it is affecting you means that you are writing a program, plug-in, or other module which depends upon this table to have certain columns. I certainly understand your plight.

vBulletin.org is all about modifying and leveraging the vBulletin source code to add functionality to vBulletin.

Anyone using vBulletin without plugins, products, or code changes would not even be aware of the database change.

So, here i am.......can anyone explain how we can go about adding custom fields via an .xml file, when the word "title" is no longer a fieldset? There have been a few mod's i have been looking to redo, but with no body at this point answering my question, i am at a loss on what to do.
If this can't be put back in, is there a new field set we look at writting when it come's to performing query write's (Insert Into)......?

Thanks, doug