You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then I should see "speed.txt" within "#ticket .asset"
Unable to find '#ticket .asset' (Capybara::ElementNotFound)
./features/step_definitions/web_steps.rb:29:in `with_scope'
./features/step_definitions/web_steps.rb:36:in `/^(. within ([^:]+)$/'
features/creating_tickets.feature:45:in `Then I should see "speed.txt" within "#ticket .asset"'
If you inspect the parameters in the controller for ticket, namely the asset parameter, you'll see this:
"asset"=>["The blink tag can blink faster if you use the speed=\"hyper\" attribute."]
In previous versions of Rails, this always came through as a Tempfile object, and I think Paperclip is still expecting it to be that because it's not saving that file anywhere.
The text was updated successfully, but these errors were encountered:
Hey @radar, we are close to Rails 3.1 release and there are a lot of issues. If you can help us pinpoint exactly were is the error, it would be great! I know it should be working automatically, but can you confirm if the form is being set to multipart?
The form is automatically being set to multipart. If I set :html => { :multipart => true } in the form it does the same thing, but :html => { :multipart => false } (as expected) sends through the file names, not the content.
Hello again,
I have a project at https://github.com/rails3book/edge-ticketee/tree/chapter_8 which has the
features/creating_tickets.feature
feature failing because files are not being passed correctly. You can duplicate this by running:It will give this error:
If you inspect the parameters in the controller for ticket, namely the asset parameter, you'll see this:
In previous versions of Rails, this always came through as a
Tempfile
object, and I think Paperclip is still expecting it to be that because it's not saving that file anywhere.The text was updated successfully, but these errors were encountered: