OT: form and multiple pics......pic included!

rubyonrails-talk
1

Hi...

koloa wrote:

hi, oad photo option down by one, so the user can upload additional photos.

the problem with this is that the user has not submitted the recipe yet. but i guess i can get around this by associating each uploaded photo with a form recipe ID. but if the user decides to cancel the recipe, i may need to add a cleanup for the photo that was uploaded? would this be worth pursueing, or maybe it would just be easier that in each user account, i can just give the user a gallery section where they can upload photos one by one under each recipe?. what would be the best solution for this?

I prefer to save the main record first and then get the user to upload the pictures one by one. What you showed in the picture you posted to the list will also work. IMO, this is a good design if the user *must* submit at least one picture. Your style makes it easy to add that.

On the other hand, if I allow them to upload multiple pictures, I would usually get the main record in first. Then, when I display the main recipe, I would give them links to: [Edit this record] | [Add pictures] ... and so on. The link to add pictures would include the parent ID that would be stored in a hidden field and posted back from the form that allowed them to upload the picture.

Cheers Mohit.

2

koloa wrote:

hi mohit, thanks for the reply. that sounds like a good idea and it would also make things much easier to maintain and implement. acts_as_attachment is a cool plugin. i will modify that + the logingenrator and walaa, i should have that capability.   

You are most welcome. Just to let you know, I did the implementation using FileColumn instead of acts_as_attachment and saved images to the file system. That said, I stored the pictures outside of a public directory so that they could not be accessed by users who were not logged in. My understanding is that you will probably not need to 'protect' the images if in real fact, they actually are pictures of food items (and recipes was not your way of simplifying the idea for us to respond).

Anyway, if you do need to protect the images, store them to a different directory (i.e., outside your public directory) and have a controller action that uses send_file to actually stream the file to the browser.

Cheers Mohit.