I'm working at making repoze.who 2.0 available in the 2.2 tree when using the new auth configuration layer.
Newly quickstarted applications will already be repoze.who v2 based, while past applications will have to be upgraded to the new auth layer (which involves just changing a configuration option in app_cfg.py if you didn't customize authentication) This should also fix this issue. On Sun, Jun 3, 2012 at 2:42 PM, Moritz Schlarb <m...@moritz-schlarb.de> wrote: > This should be because TG2 only works with repoze.who-1.x which has this bug > in opera: http://bugs.repoze.org/issue89 > It doesn't seem to have been fixed up until repoze.who-2.x! > > Am Mittwoch, 23. Mai 2012 11:25:54 UTC+2 schrieb Juan Antonio Ibáñez: >> >> Hello, >> >> I am having one problem usin authentiacation in my proyect. It works ok >> on Firefox and Chrome but not on Opera. When I try to log in using Opera >> browser, authentication always fails but I dont know why. Form data is sent >> ok as I can see. >> >> Any idea? >> >> Regards > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/turbogears/-/fc1xFr3udMYJ. > > To post to this group, send email to turbogears@googlegroups.com. > To unsubscribe from this group, send email to > turbogears+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/turbogears?hl=en. -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to turbogears@googlegroups.com. To unsubscribe from this group, send email to turbogears+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
