fatal_error showing html as plain text

[shuban]

This is frustrating, I'm trying to add a bit of html to my ban message, but it's displaying all html tags as plain text.

For example:

Code: [Select]

// You banned, sucka!

$ban_text = '<div>'.sprintf($txt[430], $old_name).'</div>';

if(!empty($_SESSION['ban']['cannot_access']['reason']))
$ban_text .= '<div>'.$txt['your_ban_reason'].' '.$_SESSION['ban']['cannot_access']['reason'].'</div>';

if(!empty($_SESSION['ban']['expire_time']))
$ban_text .= '<div>'.sprintf($txt['your_ban_expires'], timeformat($_SESSION['ban']['expire_time'], false)).'<div>';
else
$ban_text .= '<div>'.$txt['your_ban_expires_never'].'</div>';


fatal_error($ban_text, 'user');
Shows as:

<div>Sorry MSDos, you are banned from using this forum.</div><div>Reason: ...</div><div>Expiration: Your ban is not set to expire.</div> 

In the browser. So, what should I do to render the <div>'s?

[SMFHacks]

You would probably need to modify the function fatal_error

htmlspecialchars is used to protect from security issues from errors

[shuban]

Right, but looking at fatal_error in Errors.php,

htmlspecialchars is not found

Code: [Select]

// An irrecoverable error.
function fatal_error($error, $log = true)
{
global $txt, $context, $modSettings;

// We don't have $txt yet, but that's okay...
if (empty($txt))
die($error);

// TinyPortal
if(!isset($context['tp_prefix']))
TPortal_init();
// end

// Log the error and set up the template.
if (!isset($context['error_title']))
{
$context['error_title'] = $txt[106];
$context['error_message'] = $log || (!empty($modSettings['enableErrorLogging']) && $modSettings['enableErrorLogging'] == 2) ? log_error($error) : $error;
}

// If there's not a page title yet, set one.
if (!isset($context['page_title']))
$context['page_title'] = $context['error_title'];

// Display the error message - wireless?
if (WIRELESS)
$context['sub_template'] = WIRELESS_PROTOCOL . '_error';

// Load the template and set the sub template.
else
{
loadTemplate('Errors');
$context['sub_template'] = 'fatal_error';
}

// We want whatever for the header, and a footer. (footer includes sub template!)
obExit(null, true);

/* DO NOT IGNORE:
If you are creating a bridge to SMF or modifying this function, you MUST
make ABSOLUTELY SURE that this function quits and DOES NOT RETURN TO NORMAL
PROGRAM FLOW.  Otherwise, security error messages will not be shown, and
your forum will be in a very easily hackable state.
*/
trigger_error('Hacking attempt...', E_USER_ERROR);
}

[SMFHacks]

Then it would be part of function  log_error(

[shuban]

You were right, I added htmlspecialchars_decode into the errors.template.php to do the opposite of it.