Wonder how MySQL 5.5 and PHP 5.2.17 got together in bluehost server!
Here is a list of server details for simulation:
# uname -a
Linux box1243.bluehost.com 3.12.35.1418868052 #1 SMP Wed Dec 17 20:04:02 CST 2014 x86_64 x86_64 x86_64 GNU/Linux
# php -m | grep -i "mbstring"
mbstring
# yum update
CRITICAL:yum.cli:Config Error: Error accessing file for config file:///etc/yum.conf
# php -v
PHP 5.2.17 (cgi-fcgi) (built: Oct 2 2013 09:23:52)
Copyright (c) 1997-2010 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2010 Zend Technologies
with Zend Optimizer v3.3.9, Copyright (c) 1998-2009, by Zend Technologies
# mysql --version
mysql Ver 14.14 Distrib 5.5.42-37.1, for Linux (x86_64) using readline 5.1It appears that most hosting providers like justhost.com and hostmonster.com too use the same kernel initramfs-3.12.35.1418868052.img and the files can be seen here.
]]>This is strange. The expression version_compare(PHP_VERSION, "5.3.0") should return -1 if the PHP_VERSION is 5.2.17.
Therefore is should only enter the preg_replace_callback function if the PHP_VERSION was 5.3.0 or higher.
I have no idea why. But we could make it safe by adding the function_exists on the line too, f.i.
if (version_compare(PHP_VERSION, "5.3.0") >= 0 && function_exists("preg_replace_callback"))
For your information the preg_replace with the /e option is deprecated from PHP version 5.3.0.
/Joe
]]>@joe: Need to implement the "include_once" of a separate file for the PHP 5.3+ code in reporting/includes/html_entity_decode_php4.php
]]>Although the if (version_compare(PHP_VERSION, '5.3.0') >= 0) works as expected, the code in the file refers to the function preg_replace_callback() which does not exist in PHP v5.2.17 and the interpreter fails - hence the reversion in this instance.
It is best that the PHP v5.3 bit of code is kept in another file and included inside it's place in the "if" construct here.
This issue has been wikied.
Had to upload the missing fonts (dejavu and FreeSans) into the reporting/fonts folder as they are not part of the FA download.
]]>See this bluehost forum post.
Working on it.
]]>Can you send us a screenshot after showing the progress bar when you click on the submit button.
And also make sure before taking screenshot your chrome developer tools must be enabled.
And for the developer tools press f12
Than take a screenshot and attach here.
What else could cause it to fail? Faulty code or faulty data. Unless you've messed with the code, I would look at the data. Does it get read as it should? Is it in the expected format (encoding)? Did you by any chance import the data from a previous install? Like, say, the 2.4 beta? The one which is supposed to be strictly UTF?
]]>Check it and ping me back.
]]>