Replies
Okay, so I have a question with that being the case. Would it make sense for you to implement that code into your design as the default rather than what you have if it is more universally compatible? My concern is that you’ll release an update in the future rendering my setup broken. Thank you for your help!
I ran this in terminal, FYI:
grep disable_functions /opt/cpanel/ea-php73/root/etc/php.ini
and got this result:
disable_functions =
shell_exec is definitely not still disabled. I’ve checked and double-checked. I cleared my logs (both PHP and WordPress debug) this morning, and it’s not showing any new errors for either one.
So for the sake of trying everything, I installed another transcoder plugin called “Spreebie Transcoder” and activated it. When I went to the settings of that plugin, it has the status of “FFMPEG: Found”.
FFmpeg:
Server: Apache
PHP: 7.3.31
EXEC: ENABLED
FFMPEG: FOUNDI believe it’s your plugin that is having the issue in my case.
That’s not it either. I had already disabled it for the specific domain (and globally) using that method.
That’s what I did already to enable shell_exec, but it didn’t change anything. It still doesn’t work. I also restarted Apache/PHP-FPM and the VPS itself. Still nothing…
Update:
I found an error log with the following info:[07-Oct-2021 22:14:36 UTC] PHP Warning: shell_exec() has been disabled for security reasons in /home/lindseylockett/public_html/community/wp-content/plugins/mpp-local-transcoder/src/core/class-mpplt-process.php on line 63