This doesn't sound right at all... I've got many forms using form_for and f.file_field, etc... and this isn't an issue for me. Nothing special I'm doing to prevent it... are you sure you're not setting that field to something somewhere in a before filter or something?
On Oct 19, 2009, at 8:32 PM, James West wrote: > > Hi all, > I have a really really annoying problem that's driving me nuts with > file_field and paperclip and having to upload images everytime a > form is > edited even though the user is quite happy with the currently uploaded > image or loose the previously uploaded image. > > This seems to be caused by the rails file_field helper not storing the > data that has been read in from the db in the same way that other > field > helpers do and therfore unless an image is uploaded everytime the form > is updated the data for the current image does not get sent back to > the > controller in the params hash. > This in turn causes the model to believe that the data has been > deleted. > > This is obviously a problem with the rails helper as it should work > the > same way as all the other field helpers do and retain the data somehow > but right now I need a work around. > > Javascript is not an option as the site is a W3C AAA compliant site > and > creating a seperate form is just plain wrong as the user has enough to > do without adding more button clicks. > > Any ideas would be greatly appreciated. > -- > Posted via http://www.ruby-forum.com/. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
