It is a full backtrace. I was hoping someone had encountered it along the way. I spend all day yesterday digging into Rack and how the proxy code works for the streaming HTTP support. I am still digging into it, it looks like something odd possibly in Rails itself, or some config carried over from the old 3.0 app. My next step is to build a 3.2 app from scratch with AS and see if I can find a difference in the two.
Thanks, Michael On Oct 15, 2012, at 1:27 AM, Sergio Cambra <[email protected]> wrote: > On Domingo, 14 de octubre de 2012 09:29:02 Michael Latta escribió: >> I am porting an app that runs under the VHO fork to use the main AS gem >> under tails 3.2. I have the list view working with styling on simpler >> controllers. I have 2 errors that I could use some pointers on: >> >> 1) For controllers trying to use active_scaffold_batch I get an undefined >> method batch_base on the config object. >> >> 2) When trying to use the edit link to access the update form the following >> is generated (presumeably a nil content somewhere): >> >> [2012-10-14 09:15:49] ERROR NoMethodError: undefined method `bytesize' for >> nil:NilClass >> /Users/lattam/.rvm/gems/ruby-1.9.3-p125@vip3/gems/rack-1.4.1/lib/rack/utils >> .rb:281:in `bytesize' >> /Users/lattam/.rvm/gems/ruby-1.9.3-p125@vip3/gems/rack-1.4.1/lib/rack/conte >> nt_length.rb:24:in `block in call' >> /Users/lattam/.rvm/gems/ruby-1.9.3-p125@vip3/gems/activerecord-3.2.8/lib/ac >> tive_record/query_cache.rb:46:in `each' >> /Users/lattam/.rvm/gems/ruby-1.9.3-p125@vip3/gems/activerecord-3.2.8/lib/ac >> tive_record/query_cache.rb:46:in `each' >> /Users/lattam/.rvm/gems/ruby-1.9.3-p125@vip3/gems/activerecord-3.2.8/lib/ac >> tive_record/connection_adapters/abstract/connection_pool.rb:454:in `each' >> /Users/lattam/.rvm/gems/ruby-1.9.3-p125@vip3/gems/actionpack-3.2.8/lib/acti >> on_dispatch/middleware/body_proxy.rb:27:in `method_missing' >> /Users/lattam/.rvm/gems/ruby-1.9.3-p125@vip3/gems/rack-1.4.1/lib/rack/body_ >> proxy.rb:26:in `method_missing' >> /Users/lattam/.rvm/gems/ruby-1.9.3-p125@vip3/gems/rack-1.4.1/lib/rack/conte >> nt_length.rb:24:in `call' >> /Users/lattam/.rvm/gems/ruby-1.9.3-p125@vip3/gems/railties-3.2.8/lib/rails/ >> rack/log_tailer.rb:17:in `call' >> /Users/lattam/.rvm/gems/ruby-1.9.3-p125@vip3/gems/rack-1.4.1/lib/rack/handl >> er/webrick.rb:59:in `service' >> /Users/lattam/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/webrick/httpserver >> .rb:138:in `service' >> /Users/lattam/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/webrick/httpserver >> .rb:94:in `run' >> /Users/lattam/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/webrick/server.rb: >> 191:in `block in start_thread' >> >> Any pointers would be appreciated. >> >> Michael > > Is it the full backtrace? I have no clue > > -- > You received this message because you are subscribed to the Google Groups > "ActiveScaffold : Ruby on Rails plugin" 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/activescaffold?hl=en. > -- You received this message because you are subscribed to the Google Groups "ActiveScaffold : Ruby on Rails plugin" 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/activescaffold?hl=en.
