- 🇺🇸United States Sunny-Lee
Looks good here, the previous error is no longer happening with this patch. Uploaded 2 videos on various content types and both worked well with a 937.7 MB video.
- 🇺🇸United States ramu_bharu Bridgewater, Massachusetts
Thanks very much for sharing the patch. I've tested the patch and it works perfectly and I don't get any issues when i upload larger files (100+MB).
- 🇺🇸United States j-barnes
We’re experiencing this same issue with larger file uploads. When using the widget, files are uploaded directly to S3 client-side. However, the fileInput element still retains the selected file. This means when the form is later submitted via FormData, the file is included again in the request body — even though it was already uploaded — which can cause server-side errors such as exceeding post_max_size.
I think the simple solution is just to clear the fileInput value so that FormData doesn't include the file.
- @j-barnes opened merge request.
- First commit to issue fork.
- 🇫🇷France cedric_a France
I had the same issue so I created the field on another site where the "File upload elements" where available, then copy/pasted the source from there to the site where it was not available, and after saving I got this error :
The 'File' element is unavailable because a private files directory has not been configured and public file uploads have not been enabled.
So I configured the private path in settings.php → , cleared the cache and the "File upload elements" are now available in Webform ;-)