On 13 September 2012 21:51, Kyle A. <[email protected]> wrote:
> Colin Law wrote in post #1075904:
>> On 13 September 2012 21:28, Kyle A. <[email protected]> wrote:
>>>>> My code is posted here: https://gist.github.com/3716160
>>>> Colin
>>>       render(comment) + content_tag(:div, nested_comments(sub_comments),
>>> { #<TreeNode id: 100018, name: "Stinky", ancestry: nil>
>>> { #<TreeNode id: 100018, name: "Stinky", ancestry: nil>}
>>> parent_id is apparently an attribute of comments, how ever in the
>>>
>>> and replace the nested_comments(sub_comments) with 'hello' I get
>>> I am lost.
>> OK, I misunderstood what you had already done.  I think you are saying
>> it is a problem with the ancestry gem itself.  Sorry I have not used
>> that.  Anyone else?
>>
>> Have you tried using the gem in the simplest way possible to make sure
>> you understand how it is supposed to work?
>>
>> Which version of Rails are you using?
>>
>> Colin
>
> Yes. I am 100% sure I understand the full usage of the gem and have
> tripple checked documentation, stack over flow and other blogs, its not
> an issue with the gem, its an issue with my code.
>
> it boils down to two things:
>
> position_id spazzes out if it is not an accessible attribute, which in
> the documentation plus the examples I have read and followed - does not
> need to be.

That could be an issue with the version of Rails you are using, I
asked which one it is.

>
> ancestry seems to always be nil and because of this comments are not
> nesting properly. so I am wondering how to make sure it gets set -
> according to the documentation it should just be set when ever you reply
> to a comment, because it uses the parent comments id to do so.
>
> So I am wondering whats wrong with my code for this to not work >.<

Which line of your code is not doing the correct thing?

Colin

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" 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 https://groups.google.com/groups/opt_out.


Reply via email to