The iZAP Videos plugin also has a maxsize limit for uploads that you can configure on its plugin page (default is 5MB). This separate limit is to allow for setting a smaller limit for video uploads in case you need to allow larger uploads of other files (e.g. with the bundles Files plugin). So, you would have to increase the limit on the iZAP Videos plugin settings page and try again.

Nonetheless, I would suggest to test also with a smaller video file if the upload/processing fails. If it works for a small file but not for a large file the problem is likely some limit. If small video files fail also, there's likely some mis-configuration on the server (e.g. iZAP VIdeo plugin settings options or ffmpeg configuration on server).

I hadn't gone back to the plugin settings and changed that (thank you), I've done that now and the video has uploaded, I tried a small one and the 25MB one and both uploaded.

The video reported as converted successfully, however I get audio only. I tried a CLI conversion with ffmpeg and the outfile file is fine, it just doesn't render through the site. I am just using the basic command /usr/local/bin/ffmpeg -y -i [inputVideoPath] [outputVideoPath] so I may need to play around with that maybe?

OK, so I got it working, seems like the version of ffmpeg I installed didn't have the libx264 codec which is required for HTML5. So I recompiled with the configure option to include.

convert command now :

/usr/bin/ffmpeg -y -i [inputVideoPath] -vcodec libx264 -acodec aac [outputVideoPath]

Thumbnail:

/usr/bin/ffmpeg -y -i [inputVideoPath] -vframes 1 -ss 00:00:10  -s 320x240 [outputImage]

Just uploaded 100MB video and all good

Thank you @iionly for you patience and superb assistance on this matter

Thanks a lot.

please keep in mind "_elgg_services()" is an internal function and changes can be made without the need for backwards compatibility.

Why do you need to run a SQL script? Can't it be solved with the existing methods like an async upgrade?

Hi @Jerome,

I am using a plugin that is not compatible with elgg-3.3.x

The plugin requires two additional tables. that's why I am asking for run_sql_script() equivalent in elgg 3.3.x.

So I just need to run a sql script that will create two database tables.

Regards,