Hi

which on server says its enable and path all ok.

Plugin dont work for me,because.

@Gexor Are you really sure that the path to php entered on the settings tab is correct? The default "/usr/bin/php" might not be the correct path on your server. For example it could also be "/usr/local/bin/php". If in doubt, ask the support of your hoster. If you have command line access on your server, you can also enter the command "which php" to find out the path to the php executable.

If the path to php is correctly entered, the other "Fails" might vanish on their own already (especially for exec()). If there's still a Fail for ffmpeg, the path for ffmpeg set on the Settings tab in the convert commands is likely wrong, too.

found the error :-)

was simple problem in php.ini disable_functions

now it works

@iionly this not working in elgg 1.8.16 . why u mentioned as 1.8-1.10?

@sathishkumar The versions mentioned in the plugin project title refer to the Elgg versions for which a compatible release of the iZAP Videos plugin is available. It's not possible to indicate the compatible Elgg version specifically for each release.

If you would have gone to the plugin project main page (https://community.elgg.org/plugins/1913474), you would have seen that version 1.8.4 (https://community.elgg.org/plugins/1913474/releases/1.8.4) of the iZAP Videos plugin is currently recommended for Elgg 1.8.

ATTENTION:

Youtube turned of their API version 2 recently. This got me by surprise. I have to update the iZAP Videos code for the fetching of videos from youtube (including the video thumbnail) to work again. Already existing video entries from youtube should continue to work without issues. It's only the adding of new videos that's currently broken.

The new version 3 of the API also seems to require an API key. So, I'll have to include the handling of API keys, too. I hope to be able to release a new versios of iZAP Videos with youtube support fully working again soon. API documentation of version 3 is not as nicely structured as for version 2 though, so I might need a little bit of time to understand how it works now with version 3 as opposed to version 2.

/usr/local/bin/ffmpeg -y -i [inputVideoPath] [outputVideoPath]

cant upload mp4 because dont convert... goes to trashcan allways

where the problem?

@Gexor

• I guess you have the Elgg cronjobs defined (otherwise it wouldn't even start converting),
• what about the php variables memory_limit, post_max_size and max_execution_time? Are they appropriate for processing the video files?
• server logs: php and Apache error logs and possibly also Apache access log. Check for the output of ffmpeg. Does it tell you what's wrong? It should. Fix the problem (ffmpeg has many, many options and it's beyond the scope of support I can provide solutions to all issues that might arise).
• Test converting a video on the command line (shell) directly. If a conversion command works there it will also work when using as command in iZAP Videos (using [inputVideoPath] and [outputVideoPath] then as placeholders).
• Does the php.ini on your server defines anything for the "disable_functions" variable? In case the exec function is included in the list of disable_functions you would need to remove it for the conversion to work.