Thanks for the suggestion. The odd thing is that it works if I disable javascript, so it probably has something to do with rendering the responses to XHR requests. The app has a lot of customizations, view overrides, etc. But, what I have tested works without javascript, so the rendering is not really the issue. It could be something to do with rack/gem versions, I basically just blew away version restrictions to use the newest version of each gem. No plugins at all, all gems. I will verify no vho gems involved. I even tried using the debugger to look at what is happening and am still not sure what is happening with so many layers of Rails and Rack providing minimal functions. There are like 10 layers of objects passing each down the chain of middleware just to look at the body of the request. While 3.x may be more modular, it has a lot of overhead.
Michael On Oct 15, 2012, at 2:02 PM, Nick Rogers <[email protected]> wrote: > FWIW, I was in the same situation as you a while back and do not recall > seeing that error. Definitely something weird going on. > > How customized is your use of active_scaffold. Are you using any > active_scaffold plugins? Any view overrides or custom action links? > > You could try making sure your asset pipeline is correct. Recompile publics > assets if running production or remove them entirely if running in > development. Make sure your asset manifest has all the necessary requires. > > Try removing all config lines from your scaffold's controller and see if you > still get the error. If it works, add back config until it breaks, etc. > > Make sure you don't have some remnants of VHO active_scaffold in > vendor/plugins, Gemfile, etc. > > Just some shot in the dark suggestions based on my experience with AS. > > On Mon, Oct 15, 2012 at 12:43 PM, Michael Latta <[email protected]> wrote: > 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. > > > > -- > 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.
