操作的 ACL 拒绝访问:读取、uid
Access Denied by ACLs for Operation: read, uid
错误:
odoo.models: Access Denied by ACLs for operation: read, uid: 4, model: product.template, fields: activity_ids
You do not have enough rights to access the fields "activity_ids" on Product Template (product.template). Please contact your system administrator."
即使我在 model.access
中写了这个,我仍然遇到同样的问题:
mail.access_mail_activity,access.mail.activity,mail.model_mail_activity,,1,1,1,1
您是否以某种方式在产品模板上为没有该产品模板读取权限的用户创建了 activity?
或者尝试访问此特定产品模板的 activity_ids
的用户没有这些权限?
活动的访问权限与相关文档本身的访问权限绑定。看看this
def _filter_access_rules_remaining(self, valid, operation, filter_access_rules_method):
""" Return the subset of ``self`` for which ``operation`` is allowed.
A custom implementation is done on activities as this document has some
access rules and is based on related document for activities that are
not covered by those rules.
Access on activities are the following :
* create: (``mail_post_access`` or write) right on related documents;
* read: read rights on related documents;
* write: access rule OR
(``mail_post_access`` or write) rights on related documents);
* unlink: access rule OR
(``mail_post_access`` or write) rights on related documents);
"""
这个话题很复杂,但我希望这仍然有所帮助。
附加信息:对附件进行了类似的操作 (ir.attachment),但它是以另一种方式实现的。
product.template
处的 activity_ids
字段与名为 mail.activity
的对象相关。为了检查该字段的访问权限发生了什么,您可以尝试暂时禁用附加到该对象的所有安全规则:
- 确保激活调试模式。
- 转到设置 -> 技术 -> 数据库结构 -> 模型。
- 找到
mail.activity
模型然后打开它。
- 单击
Access Rights
选项卡,打印屏幕以记住现有规则,然后取消选中所有规则。
- 单击
Record Rules
选项卡并执行与第 4 点相同的操作。
- 再试一次。
错误:
odoo.models: Access Denied by ACLs for operation: read, uid: 4, model: product.template, fields: activity_ids You do not have enough rights to access the fields "activity_ids" on Product Template (product.template). Please contact your system administrator."
即使我在 model.access
中写了这个,我仍然遇到同样的问题:
mail.access_mail_activity,access.mail.activity,mail.model_mail_activity,,1,1,1,1
您是否以某种方式在产品模板上为没有该产品模板读取权限的用户创建了 activity?
或者尝试访问此特定产品模板的 activity_ids
的用户没有这些权限?
活动的访问权限与相关文档本身的访问权限绑定。看看this
def _filter_access_rules_remaining(self, valid, operation, filter_access_rules_method):
""" Return the subset of ``self`` for which ``operation`` is allowed.
A custom implementation is done on activities as this document has some
access rules and is based on related document for activities that are
not covered by those rules.
Access on activities are the following :
* create: (``mail_post_access`` or write) right on related documents;
* read: read rights on related documents;
* write: access rule OR
(``mail_post_access`` or write) rights on related documents);
* unlink: access rule OR
(``mail_post_access`` or write) rights on related documents);
"""
这个话题很复杂,但我希望这仍然有所帮助。
附加信息:对附件进行了类似的操作 (ir.attachment),但它是以另一种方式实现的。
product.template
处的 activity_ids
字段与名为 mail.activity
的对象相关。为了检查该字段的访问权限发生了什么,您可以尝试暂时禁用附加到该对象的所有安全规则:
- 确保激活调试模式。
- 转到设置 -> 技术 -> 数据库结构 -> 模型。
- 找到
mail.activity
模型然后打开它。 - 单击
Access Rights
选项卡,打印屏幕以记住现有规则,然后取消选中所有规则。 - 单击
Record Rules
选项卡并执行与第 4 点相同的操作。 - 再试一次。