That makes sense now and will be very useful in some cases.
I should have just read the source code instead of pestering people as
it is very obvious now that I looked at it. I just assumed that it
would be too complicated for a beginner like me to understand. But
that is the beauty I see with P
In fact you can also set permissions for "tablename"s which are not
tables at all but just name you give to an object.
On Oct 15, 2:27 pm, pinwc4 wrote:
> That is exactly what I needed to know. I did not realize I could
> reference the tables in that manner when setting the permissions.
>
> It w
That is exactly what I needed to know. I did not realize I could
reference the tables in that manner when setting the permissions.
It works for me now.
Thanks your help is greatly appreciated.
On Oct 15, 9:45 am, Massimo Di Pierro
wrote:
> You can set permissions for a table that do not exist
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 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
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
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 wrote:
> I am attempting to use plugin_wiki with an app I have been developing
> but am encountering
6 matches
Mail list logo
