I've just encountered the same problem, I am just wondering either if you
have fixed it somewhere or if the mentioned lazy_auth has been implemented.
Paolo
On Thursday, September 26, 2013 6:27:19 AM UTC+2, Massimo Di Pierro wrote:
>
> You may want to look at the lazy_cache decorator in gluon/cac
You may want to look at the lazy_cache decorator in gluon/cache.py. I think
we need something like that for Auth.
On Wednesday, 25 September 2013 22:45:46 UTC-5, Mandar Vaze wrote:
>
>
> On Wed, Sep 25, 2013 at 7:53 PM, Massimo Di Pierro
>
> > wrote:
>
>> Let me clarify. You currently can pass
On Wed, Sep 25, 2013 at 7:53 PM, Massimo Di Pierro <
massimo.dipie...@gmail.com> wrote:
> Let me clarify. You currently can pass auth to functions in modules and
> they can call auth methods. It is the decorators that would cause problems.
>
Understood - in fact this is what we are doing right no
Let me clarify. You currently can pass auth to functions in modules and
they can call auth methods. It is the decorators that would cause problems.
On Wednesday, 25 September 2013 09:23:10 UTC-5, Massimo Di Pierro wrote:
>
> You cannot with auth. If you pass it to modules you will run into issues
You cannot with auth. If you pass it to modules you will run into issues
with threads.
Open a ticket we can create a lazy_auth decorator that allows something
like what you want.
On Wednesday, 25 September 2013 00:10:45 UTC-5, Mandar Vaze wrote:
>
> Even I have come across such requirements.
> S
Even I have come across such requirements.
Similar to Reza's requirement - we want to allow read operations to anyone,
but insert/update/delete only for logged in user. Moreover, we also want to
check auth.has_membership too.
DB operations could be invoked from several different places, differen
I want to have something like user controller in default.py.
def user():
"""
exposes:
http:///[app]/default/user/login
http:///[app]/default/user/logout
http:///[app]/default/user/register
http:///[app]/default/user/profile
"""
return dict(form=auth()
Can you show the code where you are calling the add_product() method? Using
the @auth.requires_login() decorator is not the only way to control access.
You can also do "if auth.user:" to test for login before allowing a method
to be called.
Anthony
On Sunday, April 14, 2013 7:06:15 AM UTC-4, R
8 matches
Mail list logo
