Hi Guys,
You can delete this whenever you want!
I only wanted to remark that going from 1.6.1 to 1.7.0 image files are not treated as images, but as ordinary files.
Some assistance is helpfull in figuring out why file types are possibly not recognized.
Regards.
Also see:
Thanks for any reaction!
this hints the error (allthough type=>image - the CardFilesController is called, instead of the CardImagesController
Processing CardController#new (for 192.168.1.211 at 2011-08-03 14:37:34) [POST]
Parameters: {"content_to_replace"=>"", "card"=>{"name"=>"", "type"=>"Image", "content"=>""}, "home_view"=>"open", "context"=>"main_4545e8a", "_update"=>"true"}
Completed in 46ms (View: 34, DB: 2) | 200 OK [http://.../card/new/?context=main_4545e8a&]
Processing CardFilesController#new (for 192.168.1.211 at 2011-08-03 14:37:34) [GET]
Parameters: {"card_file"=>{"attachment_uuid"=>"400808304404338413592206492752"}}
Rendering /attachments/new
Completed in 22ms (View: 10, DB: 2) | 200 OK [http://.../card_files/new?card_file[attachment_uuid]=400808304404338413592206492752]
--Pieter Vijfvinkel.....Wed Aug 03 08:47:23 -0700 2011
Hi Pieter,
I'm having trouble reproducing this behavior. I was able to create a new image on the sandbox wagn by going to http://sandbox.wagn.org/new/Image. And I just went to edit the card above where you were having a problem and it worked just fine.
I know this is an annoying request, but could you take me step-by-step through what you're doing?
--Ethan McCutchen.....Fri Aug 05 14:32:17 -0700 2011
Thanks for the follow-up emails. patched, committed, and deployed!
--Ethan McCutchen.....Wed Aug 10 14:38:08 -0700 2011