[web2py] Re: Not Authorized - but I don't know why

2016-05-09 Thread Anthony
Also, note that there is another problem with your view() function. You are using the first URL arg to identify a record, but the grid doesn't know about this, so when it generates its own internal URLs, it will not preserve the URL arg with the record ID. To tell the grid to preserve existing

Re: [web2py] Re: Not Authorized - but I don't know why

2016-05-09 Thread Manuele Pesenti
Il 08/05/16 20:34, Simon Carr ha scritto: > I found the problem, I had to add > > | > user_signature=False > | > > to the SQLFORM.grid i.e. (SQLFORM.grid(.,user_signature=False) > > This sorted out the problem Now I think you can just decorate your controller function to prevent not

[web2py] Re: Not Authorized - but I don't know why

2016-05-08 Thread Simon Carr
I found the problem, I had to add user_signature=False to the SQLFORM.grid i.e. (SQLFORM.grid(.,user_signature=False) This sorted out the problem On Sunday, 8 May 2016 17:04:52 UTC+1, DenesL wrote: > > >

[web2py] Re: Not Authorized - but I don't know why

2016-05-08 Thread 'DenesL' via web2py-users
http://www.web2py.com/books/default/chapter/29/07/forms-and-validators#login-required-by-default-for-data-updates By default all the URLs generated by the grid are digitally signed and verified. This means one cannot perform certain actions (create, update, delete) without being logged-in. On