On 17 Sep 12:12, Sergi Almacellas Abellana wrote:
> El 17/09/14 a les 11:24, Cédric Krier ha escrit:
> >On 16 Sep 13:31, Sergi Almacellas Abellana wrote:
> >>>Hi,
> >>>
> >>>I have defined a new One2Many field on sale, which target model it's a
> >>>table_query. I've overridden the write method in order to save the
> >>>modifications in the origin table, but I don't wan't the users to create or
> >>>delete records on the One2Many field, so I didn't override the create and
> >>>delete method.
> >>>
> >>>I also added an ir.model.access record for the model, giving only read and
> >>>write access to all the users (no group defined on the rule).
> >>>
> >>>Despite all, when I open this One2Many field in the client, the create,
> >>>delete and restore buttons are still active, so the user can still create
> >>>and delete records from the client. This is confusing, as the new created
> >>>records dissapear once saved, and the deleted records reapear on saving.
> >>>
> >>>There is something I'm missing in order to disable the create and delete
> >>>buttons?
> >Normally the access right are checked:
> >http://hg.tryton.org/tryton/file/89af0b300c3f/tryton/gui/window/view_form/view/form_gtk/one2many.py#l257
> >
> >What happens if you create a line? Do you have the permission deny?
> Forget it. Now it apears correctly, so i imagine that the cache was giving
> me the wrong access methods.
> 
> Should an update of the module clear the cache?

The cache is in the client.

-- 
Cédric Krier - B2CK SPRL
Email/Jabber: [email protected]
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/

Attachment: pgphAZm9xmbvl.pgp
Description: PGP signature

Reply via email to