Hi Bubble community
I am using “Picture uploader input ” to upload an image in my application.
But sometimes user might accidentally uploads the wrong picture then immediately decided to change the picture then the problem is both images are getting stored in my file manager.
This unnecessarily increases my storage
1 Like
There’s a handful of solutions discussed in these threads
Consider a user profile page that allows the user to update their picture. As a UI requirement, the updated profile picture gets saved only when the user explicitly hits the Save button.
Now, if the user changes their mind and hits Cancel instead of Save, the uploaded image is already in Bubble’s storage. To practice good housekeeping, the uploaded image should be deleted, and the previous profile image should be restored. That should be possible with a workflow on the Cancel button.
However, …
I have an app whereby people can create new job (thing) posts. Users can also edit the posts they created. Previously I was thinking about handling both the “create new” (thing) and “edit existing” (thing) on a single page. The decision was based on UI and also the DRY principal. After reading a few posts on the forum, the consensus seems to be that creation pages should be separate to edit pages, simply because of the data type, which is set on the edit page.
I’m wondering if anyone has though…
@ladd0393 Thanks
Hi @sudsy
Consider a user profile page that allows the user to update their picture. As a UI requirement, the updated profile picture gets saved only when the user explicitly hits the Save button.
Now, if the user changes their mind and hits Cancel instead of Save, the uploaded image is already in Bubble’s storage. To practice good housekeeping, the uploaded image should be deleted, and the previous profile image should be restored. That should be possible with a workflow on the Cancel button.
However, …
But i am bit lost in the solution.
@sudsy Can you please help me?
