I don't know if it's your only problem, but you need to change push (@output, { 'row' => \@columns }); to push (@output, { 'day' => \@columns }); at least. The format you need to be returning from your sub is as follows:

return [ { day => [ { day => '' }, { day => '' }, { day => 1 }, { day => 2 }, { day => 3 }, { day => 4 }, { day => 5 } ] }, { day => [ { day => 6 }, { day => 7 }, { day => 8 }, { day => 9 }, { day => 10 }, { day => 11 }, { day => 12 } ] } ];

Update: After reverse engineering the data structure you're outputting from your subroutine, I do believe that is the only change you need to make (the one s/'row'/'day'/). It should then be fine as long as the match involved with your row/columing is correct.


In reply to Re: Nested loops in HTML::Template by Coruscate
in thread Nested loops in HTML::Template by jdtoronto

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.