Ahh but that's the challenge :)
On 09/09/2008, at 4:07 PM, AssimovT wrote: > > Steve could you help us with this fix? > > Tair > > On Sep 9, 2:45 am, Raavin <[EMAIL PROTECTED]> wrote: >> I had a look and realized I don't know rails very well. There are a >> whole lot of twists and turns with this one. Basically there is one >> 'feed_item' for each activity and one corresponding 'feed' for for >> the >> inviter and invited. The status is taken from 'freinds' but should >> really be in 'feeds' but not sure whether it can be done without a >> significant rewrite of this bit. As I say, I understand my >> limitations >> a bit more now. I'l take a better look at Insoshi (which seems to use >> similar table with different model controller stuff) to see what they >> do. >> >> Jason >> >> On Sep 8, 8:20 pm, AssimovT <[EMAIL PROTECTED]> wrote: >> >>> Thanks for reply.. yeah its definitely worth of fixing up.. >>> i tried to find the way, but too difficult for me without knowing >>> lovd >>> internals much :/ >> >>> would it be possible not to create the 3rd feed when status changes >>> from PENDING->ACCEPTED but instead only update the fields (status, >>> etc). Then when one stops being friends the status could be changed >>> back? >> >>> just an idea.. >> >>> Tair >> >>> On Sep 8, 4:44 am, Jason Keenan <[EMAIL PROTECTED]> wrote: >> >>>> I haven't looked at the code but it seems that it's not that >>>> there are >>>> duplicates, it is the status of the relationship has changed and >>>> the feed >>>> is based on that. Not a bug so much as an oversight I think. If >>>> you stop >>>> being freinds, the feed shows three identicle recent activity >>>> listings. >>>> This doesn't show a true history, but I haven't got the code in >>>> front of me >>>> to see what's happening. In this case the relationship status >>>> should >>>> possibly be stored in the feeds table in the database. >> >>>> Definitely worth fixing up. >> >>>> Jason >>>> On Sat, 6 Sep 2008 00:55:02 -0700 (PDT), AssimovT >>>> <[EMAIL PROTECTED]> >>>> wrote: >> >>>>> I have also attached the data. Please check "!!!" marks near >>>>> the rows >>>>> that are duplicate. I also understand those might be needed to >>>>> enable >>>>> remaining a follower after friendship is broken ... >> >>>>> http://www.pastie.org/267133 >> >>>>> On Sep 6, 10:41 am, AssimovT <[EMAIL PROTECTED]> wrote: >>>>>> Actually, I have found another bug.. >> >>>>>> Consider, l have two test users, not friends yet: Peter and Mike. >> >>>>>> - Peter starts following Mike. Mike's dashboard shows: Peter >>>>>> is now a >>>>>> follower of Mike. >>>>>> - Mike becomes a friend with Peter. Mike's dashboard shows: >>>>>> Peter is >>>>>> now a friend of Mike x 2 times. And it doesn't show the previous >>>>>> feed(that he is a follower). >> >>>>>> Do you know why this is happening? >> >>>>>> Tair >> >>>>>> On Sep 1, 9:47 pm, "Steven A Bristol" <[EMAIL PROTECTED]> >>>>>> wrote: >> >>>>>>> On Fri, Aug 29, 2008 at 6:41 AM, AssimovT >>>>>>> <[EMAIL PROTECTED]> wrote: >> >>>>>>>> Hi >> >>>>>>>> I am trying to add pagination to feed_items and have noticed >>>>>>>> that >>>>>>>> method: >> >>>>>>>> def partial >>>>>>>> item.class.name.underscore >>>>>>>> end >> >>>>>>>> sometimes returns nil, even if there is already the same >>>>>>>> type of >>>>>>>> feed_item. This causes unequal paging results. >> >>>>>>>> Is there any way to fix it? And why is it happening? >> >>>>>>>> Thanks, >> >>>>>>>> Tair. >> >>>>>>> I'm not sure why that would ever return nil. Can you give a code >>>>>>> example with data? >> >>>>>>> steve > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lovd by Less" 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/lovdbyless?hl=en Who loves ya baby? -~----------~----~----~----~------~----~------~--~---
