I found Dancer to swallow error messages and die messages, and also to swallow output when warnings are issued during the runtime.
The workaround I've used in anger is to wrap my code in my own eval and the output the caught information myself. Which defeats the point of using a framework.
In your case, I would look closely at whether the code could die (maybe $rootdir doesn't exist, etc.) or whether it could output warnings (which doesn't seem to be likely).
Update: See CountZeros reply, which is the more propable cause I guess - your handler needs to return the proper content through template, so template should be mostly called as
return template ...;
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.