Closed timelsass closed 5 years ago
to test you need to disable shell_exec in your environment.
These are instructions for using the latest VVV running php7.2-fpm, which may or may not be how you do it in your own environment:
vagrant ssh && echo "disable_functions=exec,passthru,shell_exec,system,proc_open,popen,curl_exec,curl_multi_exec,parse_ini_file,show_source" | sudo tee --append /etc/php/7.2/fpm/conf.d/99-security.ini && sudo service php7.2-fpm restart
The disabled_functions is just a common set of disabled functions hosts usually add to make it more realistic of an environment.
As a result you should see an admin notice with the fatal displayed:
Afterwards, you may want to remove this and restart php-fpm to go back to how things were:
sudo rm -rf /etc/php/7.2/fpm/conf.d/99-security.ini && sudo service php7.2-fpm restart
This looks good to me :+1: I tried to make a prettier error messages, but the activation ones (I think) are out of our control. We can look into it but for now this is good 🙂
to test you need to disable shell_exec in your environment.
These are instructions for using the latest VVV running php7.2-fpm, which may or may not be how you do it in your own environment:
The disabled_functions is just a common set of disabled functions hosts usually add to make it more realistic of an environment.
As a result you should see an admin notice with the fatal displayed:![image](https://user-images.githubusercontent.com/11907254/54875213-e7436200-4dd0-11e9-8012-abf3762bbd94.png)
Afterwards, you may want to remove this and restart php-fpm to go back to how things were: