Tuesday, April 1, 2014
On Tue, Apr 1, 2014 at 2:04 PM, Colin Law <clanlaw@gmail.com> wrote:
Actually the variable name is not @Object. Its some thing else. Have checked spelling, copied and pasted it. But nope. It won't work.
On 1 April 2014 06:11, Karthikeyan A K <77minds@gmail.com> wrote:Does using @object,name also work (not @bject which you have written above)?
> Hello people,
>
> I am developing an app with Rails 4.0.x and I have a strange bug in its
> view. Say I have a partial like this
>
> %p= @bject,name # would work perfectly
Actually the variable name is not @Object. Its some thing else. Have checked spelling, copied and pasted it. But nope. It won't work.
What do you mean it will not fetch the relation? What is the error message?
>
> = render @object.friends # It won't fetch this relation
There shows no error, it just returns nil object. If I give @obj.friends.first.name , it would say undefined method first for nil object!
Then @object is nil. Perhaps you should be using @bject.
>
> %p= @object,name # It would say can't find name for nil class
Note that when posting code it is better to copy/paste then there will
be no confusion about what the code actually is.
Yup copied, pasted and banged my head on desk a 1000 times.
Say if in the action if I keep @object2 = Person.find params[:id] and if I use @object2 in code, it works perfectly everywhere. This bug is repeatable on server and my local system running ruby 2.1.0 and Rails 4.3.
Some how rails is forgetting what @object is in the middle of view.
>
> For some reason the above stuff happens. However in the rails console, all
> would work fine. Kinda confused.
>
> Would be great if any one could throw light on this. Don' know if this is a
> Rails bug where state of instance variable gets forgotten after some time.
> For some reason the above stuff happens. However in the rails console, all
> would work fine. Kinda confused.
>
> Would be great if any one could throw light on this. Don' know if this is a
> Rails bug where state of instance variable gets forgotten after some time.
My experience is that bugs in compilers/frameworks/OSs are very rarely
the cause of problems. 99.999% it is one's own code that is at fault.
Colin
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLtqbxQr719tqtxd_CO6%2BSPRDJRt-KzVooZRL33UsaR%3D-A%40mail.gmail.com.
--
You received this message because you are subscribed to a topic in the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rubyonrails-talk/UaWUMHoGo90/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAJR%2B9ka8uuKv3LY67C-B49h5%2BJ61z4fsG0CjABhFks8SE4N2Kw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment