I was having something similar happen to me too.  I think it has
something to do with the changes to the way rails sets global
variables.  HAML can't tell if it is parsing a haml template or not
because for me it was trying to render ERB when I used a block.

On Tue, Oct 7, 2008 at 1:28 PM, Sean Santry <[EMAIL PROTECTED]> wrote:
>
> HI Guys,
>
> Problem in a nutshell: In an edge rails app with edge haml, using
> content_for in a helper method fails to yield content to the layout.
> Here's the relevant pastie:
>
>    http://pastie.org/286887
>
>
> I've been using Haml for awhile now, but have never delved into its
> implementation. Recently I was using it with a Rails 2.1.1 app but
> needed to upgrade to Edge Rails for a few bug named_scope bug fixes.
> Upgrading to edge Rails broke a few things in the view and I think
> I've traced it to edge Haml's CaptureHelper#capture_with_haml.
>
> To trace the problem, I created a bare-bones edge rails app with a
> layout that contains a 'yield :sidebar' and a helper method that uses
> 'content_for(:sidebar)' to render a partial into the layout. I noticed
> that if I explicitly set @content_for_sidebar, the output showed up
> correctly. I then put the regular content_for call back in my template
> and manually hacked CaptureHelper#content_for in my frozen edge rails
> to explicitly call capture_without_haml (instead of capture) and once
> again the output showed up correctly.
>
> So I'm pretty sure the problem is in the Haml implementation of
> capture (or further down the callchain) but quickly got lost in Haml's
> internals.
>
> Any ideas?
>
> - Sean
>
>
>
>
>
> >
>



-- 
Dieter Lunn
http://www.coder2000.ca

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to