Ruby on Rails Sunday, May 29, 2011



On Sun, May 29, 2011 at 8:29 AM, Colin Law <clanlaw@googlemail.com> wrote:
On 29 May 2011 13:17, amritpal pathak <amritpalpathak1@gmail.com> wrote:
>
>
> On Sun, May 29, 2011 at 7:16 AM, amritpal pathak <amritpalpathak1@gmail.com>
> wrote:
>>
>>
>> On Sun, May 29, 2011 at 4:12 AM, Chris Kottom <chris@chriskottom.com>
>> wrote:
>>>
>>> This should be everyone's starting point when first learning about Rails
>>> routing: http://guides.rubyonrails.org/routing.html
>>>
>>> Read it a couple of times at least.  If you're still unsure, at least
>>> you'll have enough context to come back and ask specific questions about the
>>> parts you don't understand.
>>> I followed Section 2.9.1 for adding a  route  to single action of
>>> controller as:
>
>          resources :posts do
>         member do
>         get 'click'
>         end
>         end
>                                      But it still gave routing error
>            No route matches {:controller=>"posts", :action=>"click"}
> Thank you

It seems clear from posts recently that Amritpal Pathak and John
Shelfer are one and the same.  He has been posting the same questions
under both names.  Readers may find it interesting to read
http://www.ruby-forum.com/topic/1610794
where he posts under both aliases, thanking himself for support.  It
is clear that the guy is not genuine.
I only posted one question twice from both aliases.The reason was when i posted it from amrit aliase due to any network problem or something else ,it didn't show at mailing list.So i was worried and posted it from other aliase too.
    I apologize for it.Next time i will careful about it. 
 


   

--
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 rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.

No comments:

Post a Comment