ERROR Dragonfly::Job::NothingToProcess: Can't process because temp object has not been initialized. #9
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{{ message }}
I am using the 'activeadmin-dragonfly' gem, I am using rails 4. I have a form in active admin, where there are two fields. One field is a plain input text field while the other is the upload for images. Both fields are required fields. I have written custom validation messages if and when any of the fields is empty. When I upload an image and not enter anything in the text field and I try to submit the form, I get the following error in my console:
ERROR Dragonfly::Job::NothingToProcess: Can't process because temp object has not been initialized. Need to fetch first?
/home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/dragonfly-0.9.15/lib/dragonfly/job.rb:78:in
apply' /home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/dragonfly-0.9.15/lib/dragonfly/job.rb:268:inblock in apply'/home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/dragonfly-0.9.15/lib/dragonfly/job.rb:268:in
each' /home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/dragonfly-0.9.15/lib/dragonfly/job.rb:268:inapply'/home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/dragonfly-0.9.15/lib/dragonfly/response.rb:25:in
to_response' /home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/dragonfly-0.9.15/lib/dragonfly/server.rb:43:inblock in call'/home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/dragonfly-0.9.15/lib/dragonfly/server.rb:39:in
catch' /home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/dragonfly-0.9.15/lib/dragonfly/server.rb:39:incall'/home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/dragonfly-0.9.15/lib/dragonfly/middleware.rb:11:in
call' /home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/rack-cache-1.2/lib/rack/cache/context.rb:136:inforward'/home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/rack-cache-1.2/lib/rack/cache/context.rb:245:in
fetch' /home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/rack-cache-1.2/lib/rack/cache/context.rb:185:inlookup'/home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/rack-cache-1.2/lib/rack/cache/context.rb:66:in
call!' /home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/rack-cache-1.2/lib/rack/cache/context.rb:51:incall'/home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/railties-4.1.1/lib/rails/engine.rb:514:in
call' /home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/railties-4.1.1/lib/rails/application.rb:144:incall'/home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/rack-1.5.2/lib/rack/lock.rb:17:in
call' /home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/rack-1.5.2/lib/rack/content_length.rb:14:incall'/home/kiprosh22/.rvm/gems/ruby-2.1.1@expatinsurer/gems/rack-1.5.2/lib/rack/handler/webrick.rb:60:in
service' /home/kiprosh22/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/webrick/httpserver.rb:138:inservice'/home/kiprosh22/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/webrick/httpserver.rb:94:in
run' /home/kiprosh22/.rvm/rubies/ruby-2.1.1/lib/ruby/2.1.0/webrick/server.rb:295:inblock in start_thread'The text was updated successfully, but these errors were encountered: