Thanks for the responses everyone.
"attr_accessible :name" didnt work. I thought it would but it didnt.
So I basically hardcoded a work-around in the update action. Since
there is only one thumbnail per picture, after I update the picture I
do a find for its thumbnail and update it with the same information.
Its not a big deal Im sure I will figure it out in due time. I am
going to checkout Paperclip on my next rails project thanks for the
heads up.
Take Care
Barry
On Oct 22, 3:20 pm, Anthony Eden <
anthonye...@gmail.com> wrote:
> I'll second using Paperclip, if that's an option. Just keep in mind
> that if you ever have any reasonable amount of traffic that uploads
> files then trying to process images inline is probably not a good
> idea.
>
> Anthony
>
>
>
>
>
> On Thu, Oct 22, 2009 at 9:17 AM, Greg Pederson <
greg.peder...@gmail.com> wrote:
> > Is the name field being created by the plugin or in the new form? If it's
> > created by the plugin maybe make sure your model/controller code isn't
> > taking precedent over the plugin edit functionality....just a thought. You
> > may need to declare the name attribute in your model???
> > attr_accessible :name
>
> > Just a long shot guess.
>
> > If you can't work it out or find yourself spending too much time you might
> > consider using paperclip as it's really easy to integrate...IMHO
>
> >
http://ruby-toolbox.com/categories/rails_file_uploads.html
>
> > Greg
>
>
http://anthony.mp- Hide quoted text -
>
> - Show quoted text -