Is this some kind of global template that you're working with here? What you're currently doing is forcing the next component in the chain to return a URL, which seems like it probably isn't what you want since the next one in the chain is likely either another autohandler, a dhandler, or a page.
First off, why use frames at all when you're using Mason? You can simply turn the footer into a component that outputs HTML, and call it from the autohandler like so:
<html>
<head>
<title><% $m->base_comp->attr('title') %></title>
</head>
<body>
<% $m->call_next() %>
<& /template/footer.comp &>
</body>
</html>
Come to think of it, I think it's highly likely you'll get caught in some type of endless recursion unless you configure Mason so that it handles only files of type .mhtml, and then have your next component return links to files of type html which wouldn't be handled by Mason.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|