I haven't dealt with this problem either. I had a quick look at TurboGears 2 to see if they had a solution for it in a quickstarted app (they use repoze.who/repoze.what) but they don't display an error message for failed logins either.
A session based flash message (as suggested by TJ Ninneman) is probably the way to go, but any recommendations from repoze.who experts would be handy. Cheers, Chris Miles On 27/01/2009, at 5:42 AM, Tom Longson (nym) wrote: > Have you managed to deal with the problem of login handlers and error > messages, that is what happens if a user tries to log in and for > whatever reason, fails? > > I'm currently using repoze.who, and haven't managed to overcome this > major point, even though I've discussed it at length with Chris > McDonough. > > Cheers, > Tom > > On Fri, Jan 23, 2009 at 5:51 PM, Chris Miles <[email protected]> > wrote: >> >> For my first stab at authentication in Pylons I used repoze.who and >> was very satisfied with it. It is complete (enough for me) but also >> very customisable. For authorization I just rolled my own, as the >> requirements were extremely simple. >> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
