DirectAdmin automatic changed php.ini

[ditto]

When I upgraded ioncube loaders in custombuild, I suddenly discovered that custombuild automatically at the same time changed my php.ini at /usr/local/lib/php.ini

Before upgrade of ioncube in custombuild I had these two settings in php.ini:

session.bug_compat_42 = Off

session.bug_compat_warn = Off

After doing ./build ioncube custombuild changed those two setting in php.ini to this:

;session.bug_compat_42 = Off

;session.bug_compat_warn = Off

I don't like that custombuild changes my php.ini without warning! Also I am not sure if those changes are good or not. Default production value is reccomended to be "Off", but default value is "On".

I test every change I do, when custombuild changes automatically like this, I have not been given time to test. So I don't like that.

So two questons:

1: Is those changes good and recommended or not? And why was they changed?

2: Why did custombuild change any setting like that in php.ini when I did ./build ioncube? It should not happen.

I don't feel good about this. Edit: I am running cb 2.0, mod_php and mod_ruid2

 

[smtalk]

A quote from http://php.net/manual/en/session.configuration.php:

session.bug_compat_42 "1" PHP_INI_ALL Available since PHP 4.3.0. Removed in PHP 5.4.0.
session.bug_compat_warn "1" PHP_INI_ALL Available since PHP 4.3.0. Removed in PHP 5.4.0.

I hope that answers your question. These 2 settings are not available in PHP 5.4 or 5.5, that's why they are commented out. There are more settings that are removed in PHP 5.4/5.5 (and are deprecated in PHP 5.3). I may add an option (not to comment removed settings in php.ini) to the options.conf file if that's what you would like to have.

 

[ditto]

Thank you for information about the changes.

[cut] I may add an option (not to comment removed settings in php.ini) to the options.conf file if that's what you would like to have.

I was always under the assumption that custombuild would never change existing settings in php.ini unless I did ./build php-ini - I now understand that I was wrong about that. So it took me on surprise.

If custombuild never change existing custom settings I have changed in php.ini, then I would not feel the need for a setting for this in options.conf. As long as I am aware that small changes like this can happen, I will look out for it.

I just was surprised and confused of why it happen without running ./build php-ini. Thanks.

 

[smtalk]

It shows you a message:

Making PHP 5.4 installation compatible with php.ini file

And then it comments out these options (all are removed/deprecated in PHP 5.4):

safe_mode
register_globals
register_long_arrays
allow_call_time_pass_reference
define_syslog_variables
highlight.bg
session.bug_compat_42
session.bug_compat_warn
y2k_compliance
magic_quotes_runtime
magic_quotes_sybase

 

[ditto]

No, it did not show me that. I did not recompile php. All I did was ./build ioncube

I did not recompile php. Edit: here is the output:

[root@server custombuild]# ./build ioncube
File already exists:    ioncube_loaders_lin_x86-64.tar.gz
ionCube loader has been installed.
Stopping httpd:                                            [  OK  ]
Starting httpd:
[root@server custombuild]#