Em Dom, 2008-01-20 às 05:11 -0800, Barry Hart escreveu: > I haven't seen that behavior, but it definitely sounds like a bug. I > believe the visit tracking code is in turbogears/visit/api.py and > turbogears/identity/visit.py. The code is pretty straightforward - if > you don't get an answer from someone, I suggest taking a quick read > of that code and adding some print statements to see what's going on. > > Barry After some tests the behavior I've found is, if last user action was the login, and user refresh the page, a new visit is inserted at database, probably because browser re-send login data and the engine "think" the request is a new login request. otherwise the login page redirect users to urls their passed so the last request should not be "the login" but the requested path. if has a bug, it is at login controller because it needs to "redirect" and/or create a new request after login action, by this way if user refresh the page, the action performed, is only the previously redirected request. I will inspect the login controller trying to fix this issue.
Att, -- Alexandre da Silva Analista de Sistemas - Bacharel em Sistemas de Informação (2003-2007) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
