Thanks for your response. I am creating a product (custom data type). Product has things - Front image, back image, nutrition image and so on. I want the cropped and compressed image to upload to the Bubble’s file manager and get attached to that product’s respective image thing.
Without your plugin involved, I achieve this by using the workflow Create a new data type.
If you try to create this prototype you will see that everything happens with very good performances because every processing (with the exception of sending the file and creating the new thing) is done directly client side from the browser
Thanks for the detailed info. The part the drove me nuts was the fact that I was trying to use the field “Attach the file to”. Now I know that its applicable only in case I want the file to be private and attached to user.
Anyhow, my set up is a bit different and based on the demo you created. Loader → Reducer-> Popup->Cropper (in popup)- > Uploader (for each picture). Cropper’s image are set as preview.
I want the uploads to begin after user clicks “save product”. This will give users an option to change their mind before uploading to bubble.
When you click on Save Product you cannot have in the same workflow a remote upload and a Create Thing which refers to the upload (even if you pause for 10 minutes!).
Check my example and you will see that Create Thing is put in a specific Uploader → bubble upload is complete event, which occurs as soon as a file has been stored by Bubble so as to return the remote url.
However, it makes no sense to do two or more consecutive uploads in the same workflow.
If you need to store multiple images that need to be manipulated first, I suggest you re-engineer your app by building a sort of multi-step wizard in which to make a series of successive uploads by storing all the images (url) loaded in an image list state.
When the user presses “Save” button the workflow will contain only one Create Thing that will store the stored URLs in the appropriate fields.
This, in my opinion, is the most efficient way to do it. There are also other ways but always keep in consideration the “events” that are generated.
“Only when” conditions are not appropriate, as you are evaluating states (bubble upload pending) and not events.
The state is evaluated at a given time and the workflow does not wait for the state to become false. You can use states to manage interface conditions to show the user for example that an upload is pending. Conversely, an event is able to trigger a workflow as soon as it occurs.
Here, however, we enter the fundamentals of programming.
I hope I was helpful.
If you have other difficulties write me PM
I may have found an issue with the cropper component.
In my use case, users upload avatars, they can change / crop them at any time.
When an avatar is loaded, the image url is stored in a custom state. No problem to use the Image cropper with the image url stored in this state. The user can then validate and the new / cropped avatar is stored in DB.
If a user want to crop an avatar already stored in the db, I don’t use custom state, the source image for the image cropper is the image url stored in the db. But in this case, it seems the cropper never retrieves this image…
Are you able to get it working using images stored in the db?
Hi @Christophe_HK ,
There should be no difference between a url stored in a custom state and a url of an image in the db.
I tried to use as Initial image a retrieved image through a “do search for” and the Cropper loads it correctly.
To check what happens in your specific app write me in PM, if you like sharing a link to the editor so that I can take a look.
I also tried to modify the image in the db used as Initial image by the Cropper through a separate workflow, and the Cropper automatically updated the displayed image correctly. I can’t reproduce your issue.
I always remain at your disposal in PM
I’ve found the root cause of the cropper issue, and it’s incredible…
I’m using the Microsoft Edge browser on my laptop, and since yesterday I received a notification about an available update. This morning, I updated Edge and since : no more issue with the cropper element.
I really don’t understand why it was working fine before the “Edge update notification”, no more while the notification was there, and again fine now the browser has been updated !
No matter : my problem is now fixed and your plugin is awesome !
Any plan to support multiple image upload / resize with this plugin ?
This plugin works really well, and it’s fast, it’s perfect. Nevertheless, I offer my users the possibility to upload several images to create galleries, but uploading the images one by one is not really efficient. So f there’s any plan to manage several images at a time, it would be awesome, I would use only this plugin to manage my use cases (1 image vs several images) !
this plugin was designed for image manipulation and requires saving one image at a time for several reasons:
bulk operations involving files are very slow in Bubble and can create difficult situations
a large number of images in the client side memory can make the browser very slow
the plugin allows a cascade manipulation and some elements (such as the Cropper) require user interaction, not very compatible with bulk operations.
In my apps I prefer to create interfaces that allow the user to “compose” a gallery by displaying its “progress” in order to have control over every single element (which allows for example to delete files individually if the user decides to use a different image).
Having said that, it seems to me that you only need to resize (with Reducer element?) the images and upload them, if you explain to me how you imagine the functioning of your gallery, maybe I can help you.
Structurally modifying a complex code like that of the suite requires an important commitment so I need to understand better
Many thanks for your feedback @gm.zumbo, and it’s crystal clear, the objective is not to degrade the processing of your plugin which is, once again, great.
I plan to make my users creating or modifying their images galleries :
first, they upload their images, or new images if they are updating their gallery. At this time, I do need upload + size reduction.
When loaded, the users can add caption to each image (optional)
When the images + caption are okay, they validate all the changes and the new gallery is created in DB (or updated, in case of modification).
But no worry. I guess I can use the Image compression plugin by ezcode to upload and compress multiple images. Then I should be able to use your plugin to crop these images, and upload them in db. Should be okay!
this is my approach to your problem using only Bubble standard code and ImagePro Plugin Loader + Reducer in Repeating Group (with Toolbox free plugin used only to create an incremental list of items). The demo works with single uploads.
If you are interested I can share the demo in PM
I’ve taken a similar approach as I don’t want to loose the benefits of the plugin. So I do ‘t provide my users with bulks of images, they upload them one by one. And using the image pro loader + reducer components, it’ s fast.
More over this approach is coherent with the fact that my users can provide captions with their images. So this operation will take time.
Yes, solved, sorry!
I had an issue with the slider element when used in a pop-up with a data type. The slider didn’t kept its value. I have changed the app design and removed the data type of the pop-up, the slider now takes its value from DB using a custom states, and it works like a charm.
obviously as background color you can enter the color you prefer (HEX code).
As for the second suggestion, I could technically try to develop these features but I have to understand well what impact it could have in responsive interfaces.
In Instagram the problem does not arise because the image format is fixed.