Beautiful, but tricky to implement
I love how the cropping tool looks and feels, and once I got it working, I love how it works too. However, it took me forever to figure out how to get the resulting cropped image saved to Bubble Storage and be saving the URL to that file in my database, but I think I have it now. It is confusing that there are two places in the various workflows where you can choose yes or no for upload, and it isn't clear why one doesn't overrule the other. It also isn't clear WHAT you are uploading or to where. When I tried saving the Cropped Image (not Cropped Image Save) to Bubble Storage, the resulting link had AWS info in the url and a time out date. I think saving the Cropped Image Save (which evaluates to a URL) to the database is a URL to the image in Bubble's Storage. Or I hope it is, because it seems to be working that way. And for others coming across this, I set upload to "no" in the initializer action, but "yes" in the setup. No clue why it works that way, but it does.