Hi Victor,
How are you?
Yes, I actually have an idea of what might be wrong.
The function that check for extensions is a different one than that performing a re-check.
I found a bug in the code on line 58 in wpvp-helper-class.php – the path to ffmpeg was not being used in “which” check.
I will update the plugin with a fix shortly, in the meantime you can fix the issue with replacing the following:
public function wpvp_check_extension($ext){
if($this->wpvp_check_function('exec')){
exec("which ".$ext,$output);
return $output;
} else {
return 'exec is disabled on the server';
}
}
with:
public function wpvp_check_extension($ext){
$ffmpeg_path = get_option('wpvp_ffmpeg_path','');
if($this->wpvp_check_function('exec')){
if($ext=='ffmpeg')
$ext = $ffmpeg_path.$ext;
exec("which ".$ext,$output);
return $output;
} else {
return 'exec is disabled on the server';
}
}
Best regards,
Alex
Thanks for the quick reply.
I made the changes you suggested, but I’m still having the same issue.
I enabled debug logging, and it’s finding ffmpeg:
Thu, 21 Aug 2014 05:26:46 +0000 -> FFMPEG found on the server. Encoding initializing...
Thu, 21 Aug 2014 05:26:47 +0000 -> Array
(
[api_key] =>
[video_width] => 640....
But the problem is because the check is saying it can’t find it, it won’t allow me to select other video types.
Hi Victor,
Could you please provide me with the url and admin access to your site so I could do some tests?
You can email me at alex @ alexiz.com.
Best regards,
Alex
I also have the same problem.
Because the path has not been set, this problem has occurred probably
debug code
public function wpvp_check_extension($ext){
$ffmpeg_path = get_option('wpvp_ffmpeg_path','');
if($this->wpvp_check_function('exec')){
if($ext=='ffmpeg')
$ext = $ffmpeg_path.$ext;
exec("which ".$ext . " 2>&1",$output);
foreach($output as $vv){
echo($vv . '<br>');
}
return $output;
} else {
return 'exec is disabled on the server';
}
}
result
which: no /usr/bin/ffmpeg in ((null))
I think the problem is solved if you set the PATH.
Hi Nari,
Yes, you’re right. This was a bug in the code that wasn’t taking into account ffmpeg path specified in the options.
The next plugin’s release will have that fixed.
Best regards,
Alex
