You can set permissions for a table that do not exist. Use 'tablename' instead of db.tablename. If unsure, post your model.
On Oct 14, 9:26 pm, pinwc4 <jau...@gmail.com> wrote: > Thank you for such a quick response. > > I attempted to do just this from within my model file but got the > error KeyError: 'plugin_wiki_page'. My guess was that the table is > not defined before my own model runs so I can not set the permissions > there. > > So I guess my question at this point is what the best way to set these > permissions would be? I have created logic in my model file that > checks whether specific groups exist, and if not it creates them and > grants them the expected the permissions. > > The reason I did this is that so when I deploy the app in a new > environment all expected groups and permissions are created > automatically instead of manually doing the work. > > Is there a better way I should be doing this, preferably in a manner > that will make it simple for others to deploy this without having to > manually set up permissions? > > Also thanks for such a great framework. I was able to go from 0 > knowledge to within a few weeks creating a web application for > management of point series where clubs can securely submit their > results. I reviewed many frameworks before committing to using web2py > and after these past few weeks of work am very happy that I did. > > On Oct 14, 8:52 pm, Massimo Di Pierro <massimo.dipie...@gmail.com> > wrote: > > > > > > > > > You need to create a new group and this this group all crud > > permissions (read,write,delete,select) for all plugin_wiki tables. > > Than make all users members of the group. > > > On Oct 14, 8:49 pm, pinwc4 <jau...@gmail.com> wrote:
