[becafuel]

Originally Posted by TheMilkCarton

... depending on what template. ... <snip>... It really all just depends on the template.

Originally Posted by Marco van Herwaarden

$vbulletin->userinfo will in most cases contain the information of the user browsing the page (ie. the logged in user).

"in most cases" and "depending on templates" : that's exactly what I've found out


In this tutorial, we can see that

VARIABLES ENABLED FOR TEMPLATES
$vboptions['x'], $bbuserinfo['x'] and $session['x'] do work in the template system without running legacy_enable()

And if we look in the legacy_enable() code, we can see that

/**
* Reenable the various legacy variables. This is not recommended for long term compatibility.

Finally, and just in case the message was not clear enough , here's what we can find in includes/functions_misc.php

PHP Code:

/**
* Replaces legacy variable names in templates with their modern equivalents
*
* @param    string    Template to be processed
* @param    boolean    Handle replacement of vars outside of quotes
*
* @return    string
*/
function replace_template_variables($template, $do_outside_regex = false)
{
    // matches references to specifc arrays in templates and maps them to a better internal format
    // this function name is a slight misnomer; it can be run on phrases with variables in them too!

    // include the $, but escape it in the key
    static $variables = array(
        '\$vboptions' => '$GLOBALS[\'vbulletin\']->options',
        '\$bbuserinfo' => '$GLOBALS[\'vbulletin\']->userinfo',
        '\$session' => '$GLOBALS[\'vbulletin\']->session->vars',
    ); 


That's why I wanted to use the $vbulletin->userinfo variable. But this one, and may be others, do not work in at least postbit and postbit_legacy.

So I think there are some troubles out there