--- Dave Howorth <Dave.Howorth at acm.org> wrote:
> > it suggests Maypole::Constants isn't being imported properly.
>
> I think it was imported OK :) because Peter didn't say there was a
> warning when it was used earlier on line 76.
>
Exactly.
> There don't seem to be too many places between there and line 98 where
> things could go awry unless there's been some adventurous overloading.
> My money would have to be on something in custom authentication code.
>
You're in the money.
> Put us out of our misery, Peter! Where was the problem?
>
> Cheers, Dave
>
I took a break to fiddle with car. Thanks for the great ideas, all. I nailed it
down in minutes after reading your emails. Too bad cause i was really looking
forward to using Maypole::CLI, too. guess i'll try that later.
To end the suspense -- Problem was maypole constants weren't imported into
my driver class. In my authenticate sub i was returning OK. i forgot use
strict;, use warnings; in my driver class. DOOHH! (it's in all my other
classes i swear.) So this went by as a bareword. So many of you were right on.
I'm using 2.4.
Now my question is, why doesn't my driver have maypole::constants when i say
use base qw/Maypole::Application Maypole::Authentication::UserSessionCookie/;
I checked the code and Apache::MVC uses maypole as a base so it should have
them. and Maypole::App gets A::MVC pushed on it's @ISA (in my case) so maybe
the problem is what? The more i do this stuff the more i realize i have no
idea what's going on.
=====
pjs
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
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