Hi Folks
I've been trying to follow the guidance on using pylons templating
from the authkit part of the stack. I've written that up at
http://home.badc.rl.ac.uk/lawrence/blog/2008/01/03/walking_the_leonardo_file_system_in_pylons
To solve the problem I allude to there (needing the c global
stackedproxy after it's been modified in the base controller for my
template) I'll need to end up importing the pylons base controller out
in the authkit stack (I think, or something similar).
Wouldn't it be easier to get the pylons stack to return a 404 *with* a
rendered signin page, and for authkit to use that? Am I being obtuse?
Bryan