Thanks again. I had been following the same trail as you since my last message, albeit with less knowledge and more confusion. I had already attempted to adopt the autohandler and comment out the check, which did allow the page to render properly. I agree that this is not the best long term solution. Originally, I had no
<a href="http://View.pm">View.pm</a> class at all, but in that case I wasn't seeing my modified wrapper show up for the login/signup/etc. pages. I think the proper solution is to learn how to implement the wrapper in T-D. While I am at it, I probably should convert my other pages too.
<br><br>Ed<br><br><br><div><span class="gmail_quote">On 8/7/07, <b class="gmail_sendername">Andrew Sterling Hanenkamp</b> <<a href="mailto:sterling@hanenkamp.com">sterling@hanenkamp.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
EdF, <br><br>Erm... I only new that answer because I added the basic POD there recently rather than having actually tried it. ;) <br><br>Digging into how use_mason_wrapper() works and then the errors, it looks like you've tripped on a couple bugs. I'm not an authority on these particular parts of Jifty, but it looks like the first problem is that the wrapper method defined in use_mason_wrapper() can't actually work unless the share/web/templates/autohandler is tweaked, but may not need any changes in and of itself.
<br><br>The share/web/templates/autohandler does need at least one update and that is:<br><br>if ($m->base_comp->path =~ m|/_elements/|) {<br> # Requesting an internal component by hand -- naughty<br> $m->redirect("/errors/requested_private_component");
<br>}<br><br>This path "/errors/requested_private_component" may have been a good path at some point in the past, but there's no there there now. This probably needs to be changed to /__jifty/error/requested_private_component or something similar and then a component added there to handle the issue (or maybe it just needs to die here).
<br><br>The other update here needs to be that either the request made by calling Jifty::View::Mason::Handler::handle_comp() needs to fix it up so that base_comp is set correctly to the path of the page being handled by Jifty::View, or needs to set a flag or something to keep the error redirect from happening.
<br><br>I don't know what's best in this particular case. I'll see if I can get a test case put together sometime tomorrow though (unless someone wants to beat me to it or I don't have time or forget, etc.).
<br><br>In the meantime, EdF, I suggest either implementing your wrapper in T-D without Mason (which can be done by overriding various render_* methods), remove your App::View class altogether (which is working on our Metrics application just fine) or doing the following as a hack work-around:
<br><br>bin/jifty adopt web/templates/autohandler<br><br>and modify share/web/templates/autohandler (which was just created in your local application) and modify it so that /_elements/wrapper is let through that if-statement. For development purposes, I don't imagine that's too heinous and it might not hurt you in a production environment, but I'd still want the real fix before I published my app.
<br><br>Anyway, that's my thoughts.<div><span class="e" id="q_1144367e48e1b625_1"><br><br>Cheers,<br>Andrew<br><br><div><span class="gmail_quote">On 8/7/07, <b class="gmail_sendername">Edward Funnekotter</b> <<a href="mailto:efunneko@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
efunneko@gmail.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Thanks for your quick response Andrew. I am working off the latest T::D, so the use_mason_wrapper() method is available.
<br><br>This did change my output a bit. Now my page gets redirected to errors/requested_private_component, which it complains about since it seems that it doesn't exist for me. Do I have to declare wrapper to be publicly available? I will keep digging myself, but if you happen to know the answer it would be appreciated.
<div><span><br><br><br><br><div><span class="gmail_quote">On 8/7/07, <b class="gmail_sendername">Andrew Sterling Hanenkamp</b> <<a href="mailto:sterling@hanenkamp.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
sterling@hanenkamp.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
EdF,<br><br>I think we need to clean up some of the remarks regarding the usability of the Template::Declare stuff. It does not have the maturity of Mason, but I wouldn't say there are bugs crawling all over anymore. (At least not the latest repository version, I'm not sure what state the latest CPAN release is in.) I'd say it's certainly suitable for production use. The big problems now tend to be those that are resolved with more time investment in development.
<br><br>An /_elements/wrapper in Mason ought to work. I'm doing it on one of my applications which was started prior to the TD views being added to Jifty and I've never converted it. <br><br>Do you have a View class defined? If you do, that might be the source of some of the trouble. Since the TD docs are spread across several classes, it might not be clear (and there's no example in this particular case either), but you should be able to call:
<br><br>__PACKAGE__->use_mason_wrapper();<br><br>in your View class to switch it over to requesting /_elements/wrapper from Mason. That's defined in Jifty::View::Declare::BaseClass.<br><br>Again, this is all based on using Jifty from a recent fetch from the Subversion repository. I don't know how different the CPAN release is.
<br><br>Cheers,<br>Andrew<br><br><div><div><span><span class="gmail_quote">On 8/7/07, <b class="gmail_sendername">Edward Funnekotter</b> <<a href="mailto:efunneko@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
efunneko@gmail.com</a>> wrote:</span></span></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><span>
Hi all,<br><br>I have been building an app recently and decided to try to use the Authentication::Password plugin to handle my user authentication. Since the Template::Declare stuff still looked fairly new ('BUGS: Crawling all over, baby. Be very, very careful.") I figured I would stick to Mason templates. My problem is that I have a _elements/wrapper that controls the main elements of each page, except for the views that are inherited from the Authentication::Password plugin. They seem to not get any wrapper that I can see.
<br><br>Some digging shows that they are using the Template::Declare paradigm. My question is, how do I get those pages to use my wrapper. If I can't do that, how do I make a Template::Declare copy of my wrapper and get those pages to use it? I did read through the documentation, but that didn't really clarify anything. If there is a tutorial somewhere for Template::Declare, please just point me to it or point me to some example code.
<br><br>Thanks,<br>EdF<br>
<br></span></div>_______________________________________________<br>jifty-devel mailing list<br><a href="mailto:jifty-devel@lists.jifty.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">jifty-devel@lists.jifty.org
</a><br><a href="http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel</a><br><br></blockquote></div><br>
<br>_______________________________________________<br>jifty-devel mailing list<br><a href="mailto:jifty-devel@lists.jifty.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">jifty-devel@lists.jifty.org
</a><br><a href="http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel</a><br><br></blockquote></div><br>
</span></div><br>_______________________________________________<br>jifty-devel mailing list<br><a href="mailto:jifty-devel@lists.jifty.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">jifty-devel@lists.jifty.org
</a><br><a href="http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel</a><br><br>
</blockquote>
</div><br>
</span></div><br>_______________________________________________<br>jifty-devel mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:jifty-devel@lists.jifty.org">jifty-devel@lists.jifty.org
</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel" target="_blank">http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel</a><br><br></blockquote>
</div><br>