1
0

This at least fixes some issues in the frontend.

I get errors only in my PHP 5.2 installation, PHP 5.4 is different.
In my backend now I do get a STRICT STANDARDS error still, even if it should be muted.
I don't understand this, needs more thorough investigation.
This commit is contained in:
Garvin Hicking
2013-01-19 15:49:42 +01:00
parent 7143f43cf0
commit de2188ed0b

View File

@ -100,10 +100,17 @@ if (!function_exists('errorToExceptionHandler')) {
echo '</pre>'; // if throw new ... endtag is not set, it still looks better and browsers don't care
}
if ($serendipity['production'] !== true) {
$args = func_get_args();
// Several plugins might not adapt to proper style. This should not completely kill our execution.
if ($serendipity['production'] !== 'debug' && preg_match('@Declaration.*should be compatible with@i', $args[1])) {
#if (!headers_sent()) echo "<strong>Compatibility warning:</strong> Please upgrade file old '{$args[2]}', it contains incompatible signatures.<br/>Details: {$args[1]}<br/>";
return false;
}
$e = new Exception;
echo '<p> == TESTING ERROR MODE == </p>';
echo '<pre>';
print_r(func_get_args());
print_r($args);
print_r($e);
throw new ErrorException("Serendipity error: " . $errStr); // tracepath = all;
echo '</pre>'; // if throw new ... endtag is not set, it still looks better and browsers don't care