[Alan @ CIT]

Hi,

(your right, it was $vboptiions - typo on my part )

You can use $vboptions in the code, it is defined here:

includes\class_core.php(892): $vboptions      =& $vbulletin->options;

Same goes for $bbuserinfo

includes\class_core.php(894): $bbuserinfo     =& $vbulletin->userinfo;

But as vBulletin is moving over to object-orientated code, you should access these vars using the registry ($vbulletin->). In my opinion, that goes for $db as well, you should access that via the registry (ie, $vbulletin->db), but again - it's really personal choice, just as you can still use $bbuserinfo and $vboptions in your PHP code if you want

Also, with regards to looking for queries, that's not a problem for me as all my queries are in the format

PHP Code:

$var_q = "..query.." 


, so a quick search for "_q =" would find them all

Incase anyones wondering I use _r for the sql resultset, and _a for the array eg:

PHP Code:

$fetch_posts_q = "...sql to fetch posts...";
$fetch_posts_r = $vbulletin->db->query_read($fetch_posts_q);
while ($fetch_posts_a = $vbulletin->db->fetch_array(...))

// I find this easier to read/understand when looking back at old code than

$query = ...
$result = ...
$array = ... 


Descriptive variable names are the key!

Thanks,
Alan.