Fatal Error after 4.2.5 upgrade

[HM666]

Hello after upgrading a site to vBulletin 4.2.5 we now have a blank white page with a fatal error.

Fatal error: Call to undefined function mb_detect_encoding() in /home/XXXXXXX/public_html/forum/includes/functions.php on line 729

The code on and around that line deals with the mbstring.


// We need to replace unicode no-break space
if (mb_detect_encoding($text) == 'UTF-8')
{


Any one know how to fix this? From some research I've found info about enabling the mbstring on the server. Will that fix this issue?

[RichieBoy67]

Yeah, I am pretty certain you need that.

[HM666]

Ok Richie that is pretty much what I thought, thanks.

[RichieBoy67]

I believe I had the same issue when setting up my last dedicated server.

Good luck with that brother and let us know how it pans out.

[Brandon Sheley]

Have you checked your requirements, php version and settings?

https://www.vbulletin.com/forum/forum/vbulletin-4/vbulletin-4-installations-and-upgrades/4352364-is-vbulletin-version-4-2-4-beta-3-or-4-2-5-compatable-to-run-on-php-7-0

[TheLastSuperman]

mbstring is not enabled off the bat (not enabled by default) you may simply need to enable it, that can be done via extensions in Easy Apache.

Reference:
http://www.php.net/manual/en/mbstring.installation.php

[HM666]

Have you checked your requirements, php version and settings?

https://www.vbulletin.com/forum/forum/vbulletin-4/vbulletin-4-installations-and-upgrades/4352364-is-vbulletin-version-4-2-4-beta-3-or-4-2-5-compatable-to-run-on-php-7-0

Settings? Which settings? I checked the requirements it seems to be in order.

It seems that when the host enabled mbstring we still get the same error message. So that did not work. :( Any other ideas?

[Brandon Sheley]

Did they reboot apache after?

http://php.net/manual/en/mbstring.installation.php

[HM666]

The host? I would hope they would know to do that. We had to put it back to 4.2.3 for now. :( After I tried to enable it I have restarted Apache several times to no avail. That is why I had the host do it because possibly I missed something in the php.ini file.

[RichieBoy67]

You are still getting the same error? Add a phpinfo.php file so you can check yourself and see if it is enabled.

Make a file and add this code:

<?php

// Show all information, defaults to INFO_ALL
phpinfo();

?>

Then access it and it will show you your php extensions etc.

[HM666]

Sorry for the late reply. This was never fixed just to update and the client's host is pretty crappy. The host enabled it and it still did not work. So there is no way to get it updated on this hosting environment. Long story, short I will not be working on it anymore.

[RichieBoy67]

You verified it was enabled bro using the php info file or using php info under maintenance in the Vbulletin cpanel?

[HM666]

You verified it was enabled bro using the php info file or using php info under maintenance in the Vbulletin cpanel?

Nope, did not get a chance before the client wanted it put back.