Logged in LightHouse with a working patch attached
http://merb.lighthouseapp.com/projects/7433-merb/tickets/1204

Also applied to my merb fork so fix should be easy to pull in
http://github.com/merbjedi/merb/commits/1.0.x

On Jan 24, 4:48 pm, Jacques Crocker <[email protected]> wrote:
> Not sure what changed, but I'm seeing this issue as well. I tracked it
> down to Haml 2.0.4 (lib/haml/engine). It's trying to do an options
> merge on a Hash and a Mash, and failing miserably. So any options you
> add via the config will be overwritten by the symbols that are defined
> as defaults on Haml.
>
> Also, you need to put that definition outside of the before_app_loads
> since the template compilations seem to trigger before that config
> block gets executed.
>
> The fix is to modify merb-haml so that it converts the Mash to a hash
> (and symbolizes the keys) when sending the configuration settings to
> the Haml Engine.
>
> line 16 of merb-haml/lib/merb-haml/template.rb
> template = ::Haml::Engine.new(io.read, config) #breaks
>
> here's the fix:
> template = ::Haml::Engine.new(io.read, config.to_symbolized_hash)
> #to_symbolized_hash needs to be added to Mash
>
> -Jacques
> twitter: merbjedi
>
> On Jan 24, 4:07 pm, cult hero <[email protected]> wrote:
>
> > I think some kind of idiom has changed somewhere, or my recent
> > inactivity with merb is catching up with me.
>
> > I have this in in before_app_loads:
>
> > Merb::Plugins.config[:haml][:attr_wrapper] = '"'
>
> > It used to work, in 1.0.6, but in 1.0.8.1 it doesn't. Is there a
> > better way/place of setting plugin attributes? Or has the name of this
> > attribute changed or something?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"merb" 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/merb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to