Toby Corkindale wrote:
> If there is just one thing about Maypole that really makes it hard to work
> with, it's the error handling - or lack thereof.
>
> When working with Maypole, I find it silently dropping errors, leaving me
> staring at a Error 500 web page with no apparent cause.
> As a result, I seem to be ending up back at the old "print lots of warn
> messages" so I can see how far into a subroutine the code executed before
> suffering from alien abduction and just... disappearing without a trace.
>
> Is there something I'm missing, which I could use to try and re-enable error
> reporting? There is nothing that I can find in the FAQs, although I have
> noticed other people mentioning the problem via Google, albeit without a fix.
Does anything appear in your error logs?
You could also turn on debugging, either by defining &debug in your
driver class:
package MyApplication;
use base 'CGI::Maypole';
sub debug { 1 }
...
or by adding '-Debug' to the Maypole::Application import list:
package MyApplication;
use Maypole::Application ('-Debug');
...
Let us know how you get on.
--simonflk
_______________________________________________
maypole mailing list
maypole at lists.netthink.co.uk
http://lists.netthink.co.uk/listinfo/maypole
This archive was generated by hypermail 2.1.3 : Thu Feb 24 2005 - 22:25:57 GMT