cubicweb #1437082 redefine relation definition permission [rejected]
there is no obvious way to redefine a relation definition permission using get_relation is forbidden with a "can't use get_relation for relation with multiple definitions" using: class my_createde_by(RelationDefinition): name = 'created_by' subject = 'Case' object = 'CWUser' __permissions__ = {'read': ('users', 'managers'), 'add': ('users', 'managers'), 'delete': ('users', 'managers')} is forbidden with a yams._exceptions.BadSchemaDefinition: conflicting values {'read': ('users', 'managers'), 'add': ('users', 'managers'), 'delete': ('users', 'managers')}/{'read': ('managers', 'users', 'guests'), 'add': ('managers',), 'delete': ('managers',)} for property __permissions__ of relation 'created_by' | |
priority | normal |
---|---|
type | bug |
done in | <not specified> |
load | 0.000 |
load left | 0.000 |
closed by | <not specified> |
similar entities
- cubicweb #1279547 Include generated doc instead of source files in cubicweb-documentation package
- cubicweb #253867 Contact in footer
- cubicweb #511718 explain why rql expr insertion doesn't work to ease security debugging
- TheCubicWebBook #111853 add howto for simple launch of existing application
- TheCubicWebBook #541389 installation from debian package
[see all]
Comments
-
2011/01/21 14:36, written by acampeas
-
2011/02/02 15:29, written by sthenault
add commentor do we settle on the post_build_callback solution ?
at least this should go in the doc
Let's add documentation about post_build_callback + example on how to solve the pb below with it.