Don't store the Image block as base64 and add support for all file adapters #5314
dimaip
started this conversation in
Feature requests
Replies: 3 comments
-
@mitchellhamilton is this something we can expect in new interface? image adapter for uploading? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you for the suggestion @dimaip. |
Beta Was this translation helpful? Give feedback.
0 replies
-
could you tell me how to increase the upload limit? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It's a bit unfortunate that the default
fields-content
Image block tries to base64 encode the images.That leads to
PayloadTooLargeError: request entity too large
when trying to save. And even thought it's possible to increase the upload limit, it would be a very strange solution performance-wise trying to store all images inside a database...Currently there exists a Cloudinary image block, but I couldn't find any blocks for S3 or the file adapter.
I think it would have been a much nicer API if the default image block just supported different adapters, with a config like this:
Beta Was this translation helpful? Give feedback.
All reactions