Ok, next problem. Again, I'm just using the example generated apps. The generated full app has a static index.html file with <a href="/">click here</a>. Now, naturally, that will get handled by the mounting app and not the mounted app. And surely there's nothing that can be done about that because the link was for / which is not a request for a resource in a mounted app.
Any thoughts on this observation? On Sun, Feb 15, 2015 at 8:01 PM, Stefan Adams <[email protected]> wrote: > > On Sun, Feb 15, 2015 at 7:50 PM, sri <[email protected]> wrote: > >> Thanks, fixed. >> >> >> https://github.com/kraih/mojo/commit/d9ea48e354e0b94b412eecdb4eb25aa45d7dde14 >> > > Awesome!! Thanks!! Wow -- this is a big one for me. I've been having > this problem for over a year now and figured Mounting apps was just too > advanced for me to figure out how to use them properly. > > >> Afraid I was unable to figure out what the new url_for call in the >> template was supposed to illustrate though, can you elaborate? >> > > I can. I wanted to be as clear as possible about what I was doing that > wasn't working. Additionally, I don't understand tests well enough. So in > the process of getting my test to work I built that up. I didn't know if > it would be necessary for a proper test or not. I'm glad that it wasn't > necessary to modify the template! > > Super great. Tested it out in my original case that I emailed about and > it works like a charm!! Thanks again! > -- You received this message because you are subscribed to the Google Groups "Mojolicious" 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]. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
