Yes, it is still accurate.
Thread Starter
am450
(@am450)
I’m quite hesitant to do anything in .htaccess.
I installed the plugin an got this message:
“EWWW Image Optimizer requires exec(). Your system administrator has disabled this function.”
Are their any laymen step-by-step instructions on how to fix this?
thanks
I doubt very much your problem is in the .htaccess file (possible, but very unlikely). The user from that thread had a vhost specific config file where they finally found the problem.
If you are not comfortable (or even able to) finding and changing the disabled functions list, then you should be speaking with your system administrator or webhost about how to enable exec().
Thread Starter
am450
(@am450)
Thanks nosilver4u
Its my website, so I’m the system admin.
That’s why I Googled the message.
Hosting provider is Network Solutions and they are useless.
Seems this plugin is not for basic WordPress users.. but more for advanced authors?
Upon searching threads for the same issue, I keep seeing the need to write/edit or move php.ini
Thread Starter
am450
(@am450)
I guess I didn’t ask for more help on that last post..
Generally php.ini is the place to be, unless suhosin is enabled, which is what that other thread was about specifically. There are several things that can disable the exec() function, but generally it is in your php.ini.
To go any further, I need to know if this is shared hosting (where your website is one of many hosted on the same server), some sort of VPS (where you’re still sharing a server, but you have dedicated ram, cpu, hard disk, etc.), or a fully dedicated server?
Thread Starter
am450
(@am450)
Definitely shared hosting/UNIX.
php.ini has the following:
memory_limit = 64M
output_buffering = 2048
max_input_vars = 5000
Its in cgi-bin at the root.
There is a subdirectory called .php and in it there is a file
php.coalesced.ini
Thanks
Found this thread: http://forums.networksolutions.com/script-help-perl-php-asp-net-f50-nshosting-shared-and-php-ini-changes-t8174.html
If it isn’t clear (I try not to make assumptions as to what others know or understand), it says that your php.ini, and the server’s php.ini are combined to create the php.coalesced.ini that you saw in that subdirectory.
So, the proper way to fix this ought to be to simply add this line to your php.ini, and it will then cause the php.coalesced.ini to be recreated:
disable_functions =
That should make it so that nothing is disabled. If you want to only enable exec(), you should look at the disable_functions line in php.coalesced.ini to see what the defaults are, and just remove exec from the list in your custom php.ini.
Also per that other thread, if it doesn’t seem to take affect, delete php.coalesced.ini, and it will get regenerated when you refresh your webpage.
Thread Starter
am450
(@am450)
Just a note to say thank you and I think it works!
I’ll be testing it later this week.
Much appreciated.