Thanks Otila for reporting this problem. I've fixed it ready for the next release.

@dhx: sorry, I'm not sure, but I think your fix is not 100%. Shouldn't the line 181 instead of:

$tpl_show_profiles = config_get( 'enable_profiles' );

be

$tpl_show_profiles = config_get( 'enable_profiles' ) == ON;

???

Nah it's OK without the "== ON" check because $g_enable_profiles=ON|OFF (where ON=1 and OFF=0).

It's like saying if( boolean_variable == true ) instead of just if( boolean_variable).

Just a comment but not beeing a PHP developer:
IMHO this is not clean, because ON seems to be a member of this enum (ON, OFF, AUTO) and could be changed to 0 or 4711 if anyone wants it.
Furthermore code is better readable when checking against ON

I agree once again with Atrol, sorry dhx ;)

Can I ask why anyone would ever decide to do something as silly as:

#define OFF 4711

#define ON 3242

#define AUTO 9281

The convention is (even as low down as within CPUs) that 0 evaluates to false and anything not 0 evaluates to true.

The only use I see for those constants is when you are working with tri-state logic and you want to write things like:

select( $t_tristate ) {

case ON:

something();

break;

case AUTO:

if( check() ) {

something();

}

break;

default:

}

Instead of using magic numbers for ON and AUTO.

maybe a better example which does not look so silly at first moment:
why not define OFF to -1 , AUTO to 0 and ON to 1 ?
Your source will not work any longer.

It's just confusing for me to see at one place: $value = ON;
and at another place: if ( $value == TRUE ) or if ( $value )

If I want to understand your code, I have always to keep in mind that ON is somewhere at another place defined as 1