Massimo Sorry to keep raising the subject of plugin.wiki fields, but could you please patch the 'active' field so we can try and test and use it. Unless I've misunderstood something, it doesn't even exist at the moment!
Thanks, D On Mar 4, 2:12 am, villas <villa...@gmail.com> wrote: > I see what you mean, it could cause a little confusion if people think > it is referring to the table. There again, you were originally happy > to use 'active', so now maybe you are getting too picky :-) > > Maybe 'functional', 'switched_on', 'ready'. > My own previous choice was 'activated' and I'm still happy enough with > that. > > On Mar 3, 9:42 pm, Massimo Di Pierro <massimo.dipie...@gmail.com> > wrote: > > > I do not like > > > db.table.is_active = True > > > although I do not strongly oppose either. > > is this any better? > > > db.table.enabled = True > > > or > > > db.table.disabled = False > > > On Mar 3, 3:08 pm, villas <villa...@gmail.com> wrote: > > > > And of course 'is_active' matches 'is_public'... > > > > On Mar 3, 4:33 pm, Massimo Di Pierro <massimo.dipie...@gmail.com> > > > wrote: > > > > > Suggestions for a better name? > > > > > On Mar 2, 4:21 pm, villas <villa...@gmail.com> wrote: > > > > > > I think you may have deleted field 'active' by mistake. If you re- > > > > > instate it, could you call it something else please :) > > > > > > On Mar 2, 10:02 pm, villas <villa...@gmail.com> wrote: > > > > > > > Thanks for the upgrade. My immediate issues are... > > > > > > > *** Reserved fieldname 'file' is still a problem (change to > > > > > > filename?) > > > > > > *** check_reserved=['all'] -- not working in DAL?? > >
