Exec() Error Won't Go Away

Please turn on EWWW’s debugging option, and post your debug information from the settings page (use pastebin.com if you like).

When looking at the debuggging, PHP is telling EWWW that ‘disable_function’ is set to this:

disable_functions: mail, apache_child_terminate, apache_setenv, define_syslog_variables, escapeshellarg, escapeshellcmd, eval, exec, fp, fput, ftp_connect, ftp_exec, ftp_get, ftp_login, ftp_nb_fput, ftp_put, ftp_raw, ftp_rawlist, highlight_file, ini_alter, ini_get_all, ini_restore, inject_code, mysql_pconnect, openlog, passthru, php_uname, phpAds_remoteInfo, phpAds_XmlRpc, phpAds_xmlrpcDecode, phpAds_xmlrpcEncode, popen, posix_getpwuid, posix_kill, posix_mkfifo, posix_setpgid, posix_setsid, posix_setuid, posix_setuid, posix_uname, proc_close, proc_get_status, proc_nice, proc_open, proc_terminate, shell_exec, syslog, system, xmlrpc_entity_decode

As you can see, exec() is listed in there, so your webhost has something odd setup that is preventing the php.ini in your home folder from overriding it. In fact, from my experience, if it is set at the system level, it CANNOT be overridden by a user-specific config file (php.ini).

I wouldn’t say “nothing”, but their support folks may not be able/allowed to override something at the system level. Your web host could most definitely enable exec() on the server if they wanted to, but their policy may prevent the support team from doing such a thing.

I generally recommend that folks find a webhost that doesn’t feel the need to limit the functionality of php to achieve security. There are plenty of solid webhosts out there that permit exec(). If that isn’t an option, the EWWW IO API is rather cheap, and will work even without exec(): https://ewww.io/plans/