I’m relatively new to Bubble and not a coder so would appreciate some help if possible please.
For the image sharing site I’ve created, I’ve been deleting records from the ‘things’ database but have noticed that the images are still recorded in the storage.
Do I need to manually click the ‘delete’ link one by one (for all 500 test images)?
Is there a way for the workflow to delete the file when it deletes the record in the ‘thing’?
It seams odd that deleting the record doesn’t also delete the file?
Looks like repetative strain injury will be the route forward.
I can’t run an API on a list that doesn’t exist. ie. I can create a backend workflow to run on the list of things… but I don’t have a list of things - I need it to run on the list in the storage but there ian’t a way to generate it.
This is indeed a problem, I’ve also a lot of orphans files, it’s a nightmare to delete. If at least the file manager section contained checkboxes, that would really help when manual deletion is required…
I’m not sure that would be desirable, since multiple things could potentially be referencing the same file. I agree, though, that it could somehow be made more clear that the onus is on the Bubble developer to manage uploaded files. There are a number of related posts. Just search the forums for “orphaned files”.
With regard to image handling, specifically, this post might be helpful. If your site is image-centric and you’re interested in optimizing your Bubble storage, a plugin like Upload Buddy might come in handy.