Anyone familiar with the earlier versions of Vbulletin, will also be familiar with the fact that Chrome doesn’t support the WYSIWG editor. Instead of seeing how the finished product will look you see lots of VBCode all over the place. This makes it VERY hard for people not so code oriented to get anything done in Chrome and, let’s face it, Chrome is faster and better than Firefox. Firefox when running would use over 2GB of my RAM and slow my machine down, which isn;t a good thing for me. As such, this frustration led me to making this code fix for Vbulletin 3.6 but it would likely work on most versions, although I am not guaranteeing it will!
The only file you need to edit is FUNCTIONS.PHP and you need to make two additions.
‘chrome’ => 0,
‘safari’ => 0,
if (strpos($useragent, ‘chrome’) !== false)
preg_match(‘#(chrome)( browser)?/([0-9\.]+)#’, $useragent, $regs);
$is['firebird'] = $regs;
if ($regs == ‘chrome’)
$is['chrome'] = $regs;
if (strpos($useragent, ‘opera’) !== false)
preg_match(‘#opera(/| )([0-9\.]+)#’, $useragent, $regs);
$is['opera'] = $regs;
And that’s it! After that you will see the WYSIWG editor looking all correct within Chrome.