1. Yeah, I thought it'd be problematic. At this point, auth.signature is part of the init process. That means I cannot write write auth.signature.is_active.writeable = False before auth - Auth because auth does not exist yet.
I can pass it as an argument to the Auth init function, but It feels like a very big overkill. An argument just to deal with the small issue of showing "is_active" on forms? I could not find a better solution for this problem. Anyone else? 2. Fine with me. On Aug 9, 7:50 pm, Massimo Di Pierro <massimo.dipie...@gmail.com> wrote: > on a second thought... it should be > > auth.signature.is_active.writable = False > > On Aug 9, 11:30 am, Massimo Di Pierro <massimo.dipie...@gmail.com> > wrote: > > > > > > > > > I am sorry, I cannot take this patch for two reasons: > > > 1) it moves self.signature to after tables are defined. that prevents > > custom auth_* tables which are signed. Some users do that. > > 2) Why > > auth.settings.is_active_writable = False > > is better than > > db.auth_user.is_active.writable = False > > ? > > It is one more api to remember and provides an exception since other > > fields will be treated differently. > > > On Aug 9, 2:02 am, Yair Eshel <guruy...@gmail.com> wrote: > > > > This is a patch that allows you to adds auth.settings.is_active_writable > > > It is set to True by default, for backword compatablity, but I took the > > > liberty of turning it off in the welcome app, by defalt. > > > > I Hope it'll bring you joy. > > > > -- > > > Get Freebiz - השיגו פריביזhttp://www.fribiz.com/referrer/guruyaya > > > > is_active_write.diff > > > 6KViewDownload
