The default in SME10 appears to have moved to /etc/opt/remi/php74/php.ini.
Because PHP 7.3 is about EOL/deprecated.
As far as I can make out, the template system updates /etc/php.ini, as it used to in SME 9
It isn't that simple as we use PHP pools as explained above.
Please read the wiki:
https://wiki.koozali.org/PHPSome additional older notes here:
https://wiki.koozali.org/Php-fpmLots of forums threads if you search. Read JPs post above carefully and then have read through templates.
saves having to liven up phpinfo();
You can enable phpinfo per ibay, along with lots of other settings. phpinfo by default is a disabled function because it is insecure, and we try to ensure that SME is secure by default as is is used by a lot of non technical users.
It can be re-enabled via DisabledFunctions - I'd add them all except the one you require.
my $disabled_functions = $pool->prop('DisabledFunctions') || 'system,show_source,' .
'symlink,exec,dl,shell_exec,' .
'passthru,phpinfo,' .
'escapeshellarg,escapeshellcmd';
After editing the file in /etc/opt/remi/php74,
Please don't do that. It won't work. Please learn to use the system as it was designed. Also, use custom-templates so you don't break your system.
I've yet to find a way to re-load the ini file without restarting the server.
The following had no effect:
systemctl restart php-fpm.service
systemctl restart httpd-e-smith.service
Any other suggestions welcome.
Usually signal-event smeserver-phpupdate or signal-event webapps-update should do it.
Help yourself by looking in the /etc/e-smith directory structure and see how some of this works. It will make far more sense.
Yes, there are lots of changes from v9. That is because lots of things have changed. Using PHP pools is far more flexible so you can run different PHP versions with different settings for different apps - take a look at Nextcloud as a good example.
Those who helped test as we built it will have learned about it already.......