please open an issue about this so we track it and fix it.
On Monday, 19 October 2015 05:58:37 UTC-5, sunny wrote:
>
> actually, I don't care if the record is deleted or not. ;-)
> I want to be able to remove memberships and reset them later with the same
> mechanism (auth.add_membership, auth.de
actually, I don't care if the record is deleted or not. ;-)
I want to be able to remove memberships and reset them later with the same
mechanism (auth.add_membership, auth.del_membership, auth.add_membership).
is this considered a bug?
or is there a different handling I have to use with auth.signa
nope, the recent version (2.12.3) have the same auth.signature that work
like that.
if you realy want to delete the data (not just set the is_active into False
when user delete it from web application), i think you can disable
auth.signature in your table definition, or simply just remove it fro
thanks, stifan.
this will be my work around but how is it supposed to work?
or is this fixed in a newer version of web2py?
> Am 19.10.2015 um 11:34 schrieb 黄祥 :
>
> the web2py version is quite old :)
> btw, i think it's about how auth.signature work. the auth.signature contain
> table field is_
Hi,
I ran into a problem with memberships:
When I add a membership to a user and delete it afterwards
the record is not actually removed from the table but is_active is set to 'F
'.
I can check with has_membership and it is False.
But now I'm unable to add the same membership again, because it
5 matches
Mail list logo
