have you tried it without update_page? It would look like this:

def cancelar_link(nueva_calificacion)
  link_to_function 'Cancelar', visual_effect(:blind_up,
"nc_detalle_#{nueva_calificacion.id}")
end

update_page has done some really unexpected things for me before, like
automatically create <script> tags and wrap contents in CDATA blocks
where it hadn't before.

On 4/4/07, Nex3 <[EMAIL PROTECTED]> wrote:
>
> I've got no idea what's causing this, except that it's not Haml. The
> same thing happens if you use RHTML:
>
>   <%= cancelar_link(nc) %>
>
>   You have a nil object when you didn't expect it!
>   The error occurred while evaluating nil.bind
>
>   1: <%= cancelar_link("foo") %>
>
> The issue seems to be with either PrototypeHelper or the ActionView
> core extensions.
>
> Your English is excellent.
>
> - Nathan
>
> On Apr 4, 12:02 pm, "luisfelipehurtado" <[EMAIL PROTECTED]>
> wrote:
> > I've the following helper method:
> >
> >   def cancelar_link(nueva_calificacion)
> >     link_to_function 'Cancelar', update_page do |page|
> >       page.visual_effect(:blind_up,
> > "nc_detalle_#{nueva_calificacion.id}")
> >     end
> >   end
> >
> > ... which is called as below in the haml view file..
> >
> > = cancelar_link(nc)
> >
> > It does not work at all... why?
> >
> > In the development log I've this:
> >
> > ActionView::TemplateError (You have a nil object when you didn't
> > expect it!
> > The error occurred while evaluating nil.bind) on line #20 of app/views/
> > operador/revision/_detalle.haml:
> >
> > 20: = cancelar_link(nc)
> >
> > Thanks for your help and for Haml.
> >
> > Sorry about my english (it's some poor)..
>
>
> >
>

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