Done - issue 1706
On Friday, October 4, 2013 11:28:08 PM UTC+4, Massimo Di Pierro wrote:
>
> Can you please open a ticket an point it to this thread?
>
> On Friday, 4 October 2013 12:20:42 UTC-5, Andy W wrote:
>>
>> Thanks for that Massimo.
>> Using lazy tables seems to be the cause (although it d
Can you please open a ticket an point it to this thread?
On Friday, 4 October 2013 12:20:42 UTC-5, Andy W wrote:
>
> Thanks for that Massimo.
> Using lazy tables seems to be the cause (although it did work with prior
> versions). Switching to lazy_tables=False under GAE fixes the problem. My
> c
Thanks for that Massimo.
Using lazy tables seems to be the cause (although it did work with prior
versions). Switching to lazy_tables=False under GAE fixes the problem. My
code now looks as follows:
# -*- coding: utf-8 -*-
Something is resetting auth.settings.table_user. Do you have that your
code. Do you use lazy tables?
On Wednesday, 2 October 2013 23:06:09 UTC-5, Andy W wrote:
>
> Version 2.6.4
> Upgrade seemed to go OK. Soon after the upgrade I added
> auth.settings.extra_fields in db.py to add an extra field
Version 2.6.4
Upgrade seemed to go OK. Soon after the upgrade I added
auth.settings.extra_fields in db.py to add an extra field to the user. This
seemed to trigger the login error, and removing that extra field has not
resolved the problem.
On Thursday, October 3, 2013 3:18:12 AM UTC+4, Massimo
Which web2py version? Was this on upgrade of what triggered the problem?
On Tuesday, 1 October 2013 23:48:18 UTC-5, Andy W wrote:
>
> My application works fine locally with rocket/SQLlite but on GAE it now
> fails when a user logs in.
> It was working previously. The problem appeared when I added
6 matches
Mail list logo
