[web2py] Re: revised plugin_wiki

2011-03-06 Thread villas
On Mar 6, 10:13 pm, Massimo Di Pierro wrote: > This is patched. There is not more "active." I think we must be talking about different things. This following code is from cube2py controllers/plugin_wiki.py def index(): w = db.plugin_wiki_page if plugin_wiki_editor: pages = db(w.

[web2py] Re: revised plugin_wiki

2011-03-06 Thread Massimo Di Pierro
This is patched. There is not more "active." it is auth.signature.is_active and the latest plugin_wiki uses auth.signature On Mar 6, 12:42 pm, villas wrote: > Massimo > > Sorry to keep raising the subject of plugin.wiki fields, but could you > please patch the 'active' field so we can try and tes

[web2py] Re: revised plugin_wiki

2011-03-06 Thread villas
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 wrote: > I see what you mean, it could

[web2py] Re: revised plugin_wiki

2011-03-03 Thread villas
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

[web2py] Re: revised plugin_wiki

2011-03-03 Thread Massimo Di Pierro
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 wrote: > And of course 'is_active' matches 'is_public'... > > On Mar 3, 4:33 pm, Massimo Di Pierro > wrote: >

[web2py] Re: revised plugin_wiki

2011-03-03 Thread villas
And of course 'is_active' matches 'is_public'... On Mar 3, 4:33 pm, Massimo Di Pierro wrote: > Suggestions for a better name? > > On Mar 2, 4:21 pm, villas wrote: > > > I think you may have deleted field 'active' by mistake.  If you re- > > instate it, could you call it something else please  :)

[web2py] Re: revised plugin_wiki

2011-03-03 Thread villas
Well I used 'activated'. I suppose 'visible' or 'live' might also be suitable (but I didn't check those yet). On Mar 3, 4:33 pm, Massimo Di Pierro wrote: > Suggestions for a better name? > > On Mar 2, 4:21 pm, villas wrote: > > > I think you may have deleted field 'active' by mistake.  If you

[web2py] Re: revised plugin_wiki

2011-03-03 Thread Massimo Di Pierro
Suggestions for a better name? On Mar 2, 4:21 pm, villas 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 wrote: > > > > > > > > > Thanks for the upgrade. My immediate issues are.

[web2py] Re: revised plugin_wiki

2011-03-02 Thread villas
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 wrote: > Thanks for the upgrade. My immediate issues are... > > *** Reserved fieldname 'file' is still a problem (change to filename?) > *** check

[web2py] Re: revised plugin_wiki

2011-03-02 Thread villas
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?? I did notice that you'd changed the field 'public' to 'is_public'. I'm not sure what happened with 'active' but that problem