Plugin Author
gioni
(@gioni)
Please enable a “PHP mbstring” extension on the website. You can do that in your hosting control panel.
Thread Starter
fromoz
(@fromoz)
Hi – thanks for follow up. I have enabled the PHP mbstring module on our server and it is OK now. The strange thing is that the server, and WP Cerber, have both been happily running for months without mbstring being enabled. It only caused a problem now with this new version.
Also, fortuitously, installing mbstring also solved a problem I had running the WP Cerber Site Integrity Security Scanner (that I hadn’t got round to investigating) which always used used to crash running a scan. Obviously it also needs the mbstring module.
It might be of benefit to put a list of required PHP modules in the WP Cerber installation documents to ensure the server is fully up to spec.
Glad WP Cerber is running OK again — can’t consider having the WordPress site running without it 🙂
Plugin Author
gioni
(@gioni)
Yes, sure there will be a precheck and an admin notification if mbstring is not loaded.
Thread Starter
fromoz
(@fromoz)
It may still be the case that mbstring is not actually loaded on the web server. That was the situation on my CentOS server because I am using PHP 7.x and the default PHP on CentOS is still 5.x. When installing PHP 7.x the various modules have to be specially found, installed and loaded. I thought mbstring was active – it had been downloaded and installed – but it wasn’t.
Iron clad way to check if mbstring is actually active is to write a temp phpinfo page
https://mediatemple.net/community/products/dv/204643880/how-can-i-create-a-phpinfo.php-page
and double-check that mbstring is loaded. Of course don’t leave the info page on your WordPress site as it reveals a lot of things.
HTH.
Plugin Author
gioni
(@gioni)
@satheeshraj Check the server error log.
Enabling mbstring did the trick, Ubuntu:
`apt-get install php-mbstring
Like others have mentioned, this has been running flawlessly w/o this extension and out of the blue have me issues.
Anyhow, it’s fixed now, thank you!