I did notice the expat error, and thinking that the xml may be invalid,
I actually renamed the auto-generated (which remained untouched
for this test) to login.xml and login.xhtml... I could bring both those
files under firefox/linux without any problem. They get rendered
to display the login page... indirectly implying the content was
valid xml....
I can't understand what is causing the kid engine at runtime to fail
working with the login.pyc that got created from the login.kid... If
the
template was not proper xml, the login page would not have been
rendered the first time around...
It looks like it is failing to:
. convert the exception_handler's exception text into valid xml,
. and/or substitute it for the placeholder in the login.kid template
Unclear how I can track the cause... The runtime tracebacks don't
seem to be helping much...
You are aware that the login mechanism tries to redirect you to the page you
wanted to visit the first place? Even if it was the index?
So I presum it's one of your other templates, that should be rendered after
successful login.
Diez
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
