Hey Hampton:
I'm having the same type of issues here, where a form_tag is
generating a blank page without any explanations.
I've updated to version 1.4.0 but I still do not see any meaningful
errors.
When I tried the standalone parser, I get this:
----
macximus% ./vendor/plugins/haml/bin/haml --stdout app/views/profile/
mobile.haml
(haml):2: undefined method `image_tag' for #<Object:0x6e9360>
(NoMethodError)
from (eval):8:in `_haml_render'
from ./vendor/plugins/haml/bin/../lib/haml/engine.rb:394:in
`compile'
from ./vendor/plugins/haml/bin/../lib/haml/engine.rb:190:in
`to_html'
from ./vendor/plugins/haml/bin/../lib/haml/exec.rb:150:in
`process_result'
from ./vendor/plugins/haml/bin/../lib/haml/exec.rb:22:in
`parse!'
from ./vendor/plugins/haml/bin/haml:8
----
But this error will not be there when executed within Rails.
What setup to I need to do to remove this error or better yet any way
to
enable haml debugging mode in a view.
Thanks - Martin
On Feb 15, 6:49 pm, Hampton <[EMAIL PROTECTED]> wrote:
> - form_tag(:action => 'create') do
> = render :partial => 'form'
> %hr/
> = submit_tag "Create", :class => 'form-button'
> = link_to 'Back to List', {:action => 'list'}, :class => 'form-
> button'
>
> Are those two space on each line? In you're example code its only one space.
>
> Also, I'll be frank with you. Haml 1.0+ gave terrible errors. When it
> failed, it generally failed silently and painfully.
>
> Haml 1.5 is much more friendly in that respect. It gives helpful and
> useful errors that tell you exactly what is going wrong to make the
> rendering fail.
>
> Haml 1.5 is going to be released.... by my current figuring... next
> friday. We're pairing its release with a new design for the website
> and Sass (read up around here if you want more info on what Sass is).
>
> I'm holding it back so that we can get some good press and really make
> a splash with it, because it is fantastic.
>
> Until then, I'd highly recommend deleting your current
> /vendor/plugins/haml folder and doing this line...
>
> ruby script/plugin installhttp://svn.hamptoncatlin.com/haml/trunk/
>
> That should install the current 'development' version, which is
> incredibly stable, and nearly ready for release anyway. If you do
> that, your errors will be much, much better!
>
> -hampton.
>
> On 2/15/07, Daniel <[EMAIL PROTECTED]> wrote:
>
>
>
> > I am using a _form to capture a text field, nothing new but apparently
> > the partial is not being rendered. Here is my code:
>
> > - form_tag(:action => 'create') do
> > = render :partial => 'form'
> > %hr/
> > = submit_tag "Create", :class => 'form-button'
> > = link_to 'Back to List', {:action => 'list'}, :class => 'form-
> > button'
>
> > I get a blank section where at least one field should be shown.
> > Curiously, if I remove the "= render ..." line I get exactly the same
> > result. Any ideas??
>
> > I almost forgot, when this partial is called for editing from a rhtml
> > it works fine.
>
> > I also tried this but the compiler complains always at the last line.
>
> > = start_form_tag(:action => 'create')
> > = render :partial => 'form'
> > %hr/
> > = submit_tag "Create", :class => 'form-button'
> > = link_to 'Back to List', {:action => 'list'}, :class => 'form-
> > button'
> > = end_form_tag
>
> > Thanks,
>
> > Daniel
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
