Don't worry about it, I've figured it out. It looks like there are two separate problems: one is a Rails issue and one is a Haml issue. I'm working on a fix for both.
Mislav Marohnić wrote: > On Mon, Sep 22, 2008 at 01:36, Nathan Weizenbaum <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > I'll pull these and look into the render-with-block issue as soon > as I'm > done with what I'm working on now. > > > I've tried to fix this today without success. I barely understand how > Haml buffer works, much less the innerworkings of Rails > rendering/compiling mechanism. > > I > bisected the breakage to Rails 933697a5fc5f4c56c4fd7fbbd31b8973df9c1054 > (replacing _erbout with @output_buffer). > > The exception says that buffer was nil. When I noticed that it comes > from `concat` used in `_render_with_layout`, I tried a hack to > unconditionally overwrite that method: > > ActionView::Base.class_eval do > def concat(string) > haml_buffer.buffer.concat(string) > end > end > > Now I got rid of the exception, but the template doesn't render > properly. I expected (pseudo-code): > > LAYOUT { > layout_content > } > > But this was rendered: > > layout_content > LAYOUT without content > > Naturally, this is an issue with concat-ing to the buffer. After > seeing what important role [EMAIL PROTECTED] plays, I tried to track > down how it works but got lost in depths of ActionView::Renderable#render. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" 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/haml?hl=en -~----------~----~----~----~------~----~------~--~---
