I would use "pry" for this case.
"binding.pry" in user-layout.html.erb and find out what is the problem

On 05/07/2014 01:52 PM, Alfredo Barrero wrote:
No. In case that would be the problem I could use any other route but that is not the case. I cannot use any other route in the custom layout...


El 07/05/2014, a las 12:50, bertly_the_coder <[email protected] <mailto:[email protected]>> escribió:

it's users_path

On Wednesday, May 7, 2014 1:44:26 PM UTC+3, Alfredo Barrero wrote:

    Yes, I'm trying all the routes and no one works. It says 'cannot
    find user_path'. These are the routes that I have.

     user GET    /users/:id(.:format)         users#show
                    PATCH  /users/:id(.:format) users#update
                    PUT    /users/:id(.:format) users#update
                    DELETE /users/:id(.:format) users#destroy

    In the application.layout those routes are working, I have to
    specify any special route tu use a different layout?.


    Thanks


    El miércoles, 7 de mayo de 2014 12:40:28 UTC+2, Gitted escribió:

        does the route exist? what is the error you get?

        try rake routes to see if user_path exists.


        On Wed, May 7, 2014 at 6:27 AM, Alfredo
        Barrero<[email protected]>wrote:

            Hi guys, can someone tell me why I can't use routes like
            "user_path" in custom layouts like 'user-layout.html.erb' ???

            Thanks & regards.

            --
            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 [email protected].
            To post to this group, send email
            [email protected].
            To view this discussion on the web
            
visithttps://groups.google.com/d/msgid/rubyonrails-talk/989a71d9-1b0c-43e6-a5d4-b7d0e180ce1a%40googlegroups.com
            
<https://groups.google.com/d/msgid/rubyonrails-talk/989a71d9-1b0c-43e6-a5d4-b7d0e180ce1a%40googlegroups.com?utm_medium=email&utm_source=footer>.
            For more options, visithttps://groups.google.com/d/optout
            <https://groups.google.com/d/optout>.



--
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, visithttps://groups.google.com/d/topic/rubyonrails-talk/fE1n2Fsq0oU/unsubscribe. To unsubscribe from this group and all its topics, send an email [email protected] <mailto:[email protected]>. To post to this group, send email [email protected] <mailto:[email protected]>. To view this discussion on the web visithttps://groups.google.com/d/msgid/rubyonrails-talk/f2b9cb5e-3b18-483e-af68-850fc21e7a62%40googlegroups.com <https://groups.google.com/d/msgid/rubyonrails-talk/f2b9cb5e-3b18-483e-af68-850fc21e7a62%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visithttps://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 [email protected] <mailto:[email protected]>. To post to this group, send email to [email protected] <mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/5A2CD767-1661-4052-ABBD-6AA0D89EECD2%40gmail.com <https://groups.google.com/d/msgid/rubyonrails-talk/5A2CD767-1661-4052-ABBD-6AA0D89EECD2%40gmail.com?utm_medium=email&utm_source=footer>.
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-talk/536A13CA.4050001%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to