I have updated the plugin and tested by clearing cache, but unfortunately I still see the same issue. SVG is not converted to webp(png) as you can see in here:
Anyway, if you could let us decide image types selectable, that would definitely solve this issue tho. Can you implement this feature like the Picture uploader can restrict image types to upload? (but the feature does not solve the issue unless you exclude SVG completely.)
Thank you and your engineering team for your efforts in tackling this issue.
Hello @rio,
We hope this message finds you in good spirits.
I have updated the plugin and tested by clearing cache, but unfortunately I still see the same issue. SVG is not converted to webp(png) as you can see in here:
Yes we understand that it is frustrating to deal with the way Bubble processes SVG files, we asked our devs to look once more if the set-up from the test page you shared with us is possible to adjust to avoid issues with SVG format and they informed us of the fact that:
When using Image Compressor, it’s important to note that SVG files are recognized as XML files with the mime type “image/svg+xml” by browsers. This can cause certain display or compatibility issues.
maybe this isn’t relevant to my issue, but worth mentioning if you find it useful.
Well you can experiment with Imgix also but take into account that Bubble has its specific limitations, we are doing our best to help you, but unfortunately, we cannot change how the
Svg file gets seen by browsers.
Anyway, if you could let us decide image types selectable, that would definitely solve this issue tho. Can you implement this feature like the Picture uploader can restrict image types to upload? (but the feature does not solve the issue unless you exclude SVG completely.)
Thank you for the suggestions, we will check if it’s feasible and if the plugin library allows us to implement these changes - we will notify you once there are any updates but can’t provide any timeframes.
Thank you very much for you patience and understanding through this process.
Best regards,
Zeroqode Support Team
Uncompressed base64 is only for regular images but not for SVG ??
No worries, we are glad to help and make things clearer. Some context should be offered so that the plugin’s logic will be clearer.
Uncompressed base64 encoding is typically used for regular images like JPEG, PNG, or GIF because these formats are inherently binary data that need to be encoded to be included in HTML or CSS files.
It works perfectly fine by simply selecting compressed base64 , but Not a Uncompressed64.
SVGs, on the other hand, are text-based XML files that describe images using vector data. Since SVGs are text files, they can be directly embedded or included without the need for base64 encoding.
Using uncompressed base64 encoding for SVGs is unnecessary and can increase file size, making it less efficient.
I hope this clarifies why uncompressed base64 is only recommended for regular images and not for SVGs. If you have any further questions, feel free to ask!
Best regards,
Zeroqode Support Team.
Where is the workflow EVENT for Compressor Uploaded MULTIPLE to S3 so I can continue the workflow after this event, however the only action there is for a single Upload to S3.
Hi, this is similar to NicolasMM’s question above, which does not appear to have been answered:
I’ve read the documentation and this thread, and I’m throwing up errors after the transform and upload (and changes) shown below. Any ideas what needs to change?
Thanks for reaching out to us, we have already discussed via email previously and will write here as well to make sure you will see the message.
For your use-case, when you use the action “Upload multiple to S3”, you can use the event “Done multiple uploads” to know when the files are successfully uploaded and to continue your workflow from there.
Could you please give it a try and let me know if everything is working fine for you? If you will have any further concerns, please share more details such as screenshots or a screencast of how you set up the workflows, plugin element, and the problem you’re experiencing.
From the images you provided, it appears that you’re selecting, uploading, and saving to the database all within the same workflow. This could lead to problems, as the states you’re referencing may not yet be available at the time of the action.
To avoid this, we recommend using the plugin events “Done Compression” and “Image Uploaded” to ensure the file has fully compressed or uploaded before proceeding to the next workflow action.
