-
Notifications
You must be signed in to change notification settings - Fork 13
Configuration
- Field: The text field the component fills in the form.
- Label: The label for the field.
- Max Size: The maximum size of a file in bytes.
- Max Number of Files: The maximum number of files that can be stored in the field.
- Accepted File Extensions: A list of extensions seperated by commas that are acceptable input types. For example: ".jpg,.png,.pdf"
- On Change: A callback for whenever the files inside of the form change.
- Encoding Protection: Fixes error caused by Budibase Bug #8826. The bug should only affect SQL databases, however having this checked will not affect non-SQL DBs either. Note that you must use the same encoding protection setting for all of your file fields. Otherwise, there will be errors parsing your stored files.
- Use BlobURL: This allows the tab that open when you click on a file to be a blobURL link. If this is not checked, an iFrame will be opened with a DataURL inside. The use of an iFrame is necessary as DataURLs cannot be directly opened in many modern browsers. However, an iFrame may be blocked because it may violate Content Security Policy, so it is better to keep this checked. Note that whether or not this is checked, data in the DB is still stored in the same manner, so you can alter this property for the same column in different forms.
Before we discuss configurations you might need to allow for large files sizes, note that the data you upload with this plugin is encoded into a String and serialized into JSON in the browser, which is not the most efficient process. Thus, it may not be practical to use this with very large files. My tests show that the page will freeze for about a second when uploading a 40mb file. A 160mb file freezes the page for about 5 seconds, so the processing time is roughly proportional to the file size. Note that these tests were done on a desktop computer and may vary based on the device running the page. As such, note that allowing larger files will come at the expense of minor freezes when uploading.
If your will be uploading large files, you may run into issues with payload size limits (Payload Too Large error). Both Budibase, your database, and your reverse proxy (if you are using one) may restrict the size the data you upload, so here are some changes you may need to make to them:
By default, Budibase has a 10 mb limit. You can modify this with the HTTP_MB_LIMIT environment variable[^1], which you set in the .env file for self-hosted solutions. See here for more on environment variables. This is not available for Budibase Cloud. From my tests it seems file upload work for Budibase Cloud apps up to around 3MB (maybe the limit is lower for the hosted version?).
Depending on what database you use, it may have limits on the max allowed packet size, which you will have to change in the database configurations. For MySQL this is set with the max_allowed_packet variable (see here for how to change it).
Finally, your reverse proxy may also limit you file upload size. For Nginx, this is set with client_max_body_size, as described here.