This change should not break it. Can you please show us the code that breaks and we will check what is going on? It is possible that one of the auth modules has not been patched correctly.
Massimo On Jul 21, 11:02 am, zeng <zeng...@gmail.com> wrote: > Hey guys, > > I'm currently running version 1.95.1 and have 3 application, > "AppAuth", "AppA", "AppB", AppA and AppB is using "AppAuth" to > authenticate logged in user and it has been working great. > > After upgrading 1.96.1 and cross app authentication no longer works, > some debuging lead to: > ----- web2py.gluon.tools.Auth ---- > self.environment = current > request = current.request > session = current.session > ----- web2py.gluon.tools.Auth ---- > > and "current" is a threading.local() in gluon.globals.py !!! > > In the good'o 1.95.1 the session and auth object is retrieved from > global() , > > Question is, why is this changed? this seems to break the backward > compatibility "feature" of web2py, and what are the recommended > solutions now that global() is no longer used? > > Thanks!
