Also to all posters in here: can you all confirm you got php 5.2.4 with that problem ?

I'm suspecting a bug in the php interpreter of that version on some texts, as this suddenly appeared since that php release.

Don't see an easy workaround yet. Maybe try adding a '@' (without the quotes) in front of that function like this:

[code:1]
if(defined($text)) $returnText = @constant($text);
[/code:1]

It could calm down the error a bit. If yes, try this too as workaround:

If it stops the fatal error, try changing in that file at that lines this function:

[code:1]
function getLangDefinition($text) {
if(defined($text)) $returnText = constant($text);
else $returnText = $text;
return $returnText;
}
[/code:1]

to:

[code:1]
function getLangDefinition( $text ) {
if ( defined( $text ) ) {
$returnText = @constant( $text );
if ( $text && $returnText ) {
return $returnText;
}
}
return $text;
}
[/code:1]

This is *not* a bug-fix of CB, but a trial to work-around this probable bug in PHP 5.2.4.

Installed same php 5.2.4 version on my test-system, but still couldn't reproduce. I also checked the bug-tracker of php 5.2.4 for this bug, but didn't see it reported yet.

Please report back as precisely as possible in this thread, I will check in a few hours again.

EDIT for non-significant code indenting fix

Post edited by: beat, at: 2007/10/11 01:51

censor wrote:

I changed my language files name (I guess this has the same effect as deleting it).

And now things are working again. Does changing the file have any impact I should be aware of?

Interesting... I can't tell you more, than that it's very probably a php bug which I'm taking seriously, and would like as much as possible info as asked in my post above (exact PHP version in particular (it's in system info menu)).

Have you kept have a copy of the old "bugging" language file for analysis and trying to reproduce ? If yes, could you please attach it to the post reply ?

What was the character-set of the old language file and what is the character-set of your website ?

If you put back the old file, does the bug re-appear ?

Did you try the code-workarounds I proposed above ?