Setting rights on specific attributes

Next topic

Author	Message
Helle Andersen	Thursday 29 April 2010 6:49:17 am In a few cases we would like to set specific rights on specific.attributes. E.g. we would like to add an attribute to all our classes with a metadata/keyword attribute. But we would like this attribute to be filled out only by our Communication department, not by all our ca. 200 users. Has anyone any idea how/if this can be done?
André R.	Thursday 29 April 2010 12:05:34 pm Currently you'll have to check access in edit templates for stuff like this. There is an old patch around to add policy checks to attributes, but no idea when something like this might be part of eZ Publish out of the box. There is also the possibility that policy limitation on class attribute category(4.3 feature) is implemented instead, but both cases would solve your case without having to hard code business logic in templates. eZ Online Editor 5: http://projects.ez.no/ezoe \|\| eZJSCore (Ajax): http://projects.ez.no/ezjscore \|\| eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom
Bertrand Dunogier	Thursday 29 April 2010 12:59:24 pm Andre has summarized the basics correctly. If security is important for you (not sure it is with a department, but whatever), you could also use the same configuration as you would use the customize the template inside a workflow event and reject data that doens't match 'em. Such a configuration could look like this: [global] ; XXX is the Communication department's content object ID AttributePermissions[XXX]=all;deny AttributePermissions[XXX]=keywords;allow Bertrand Dunogier eZ Systems Engineering, Lyon http://twitter.com/bdunogier http://gplus.to/BertrandDunogier

Author

Message

Thursday 29 April 2010 6:49:17 am

In a few cases we would like to set specific rights on specific.attributes.

E.g. we would like to add an attribute to all our classes with a metadata/keyword attribute. But we would like this attribute to be filled out only by our Communication department, not by all our ca. 200 users.

Has anyone any idea how/if this can be done?

André R.

Thursday 29 April 2010 12:05:34 pm

Currently you'll have to check access in edit templates for stuff like this.

There is an old patch around to add policy checks to attributes, but no idea when something like this might be part of eZ Publish out of the box. There is also the possibility that policy limitation on class attribute category(4.3 feature) is implemented instead, but both cases would solve your case without having to hard code business logic in templates.

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Bertrand Dunogier

Thursday 29 April 2010 12:59:24 pm

Andre has summarized the basics correctly.

If security is important for you (not sure it is with a department, but whatever), you could also use the same configuration as you would use the customize the template inside a workflow event and reject data that doens't match 'em.

Such a configuration could look like this:

[global]
; XXX is the Communication department's content object ID
AttributePermissions[XXX]=all;deny
AttributePermissions[XXX]=keywords;allow

Bertrand Dunogier
eZ Systems Engineering, Lyon
http://twitter.com/bdunogier
http://gplus.to/BertrandDunogier

eZ debug

Timing:	Jan 18 2025 05:04:48
Script start
Timing:	Jan 18 2025 05:04:48
Module start 'layout'
Timing:	Jan 18 2025 05:04:48
Module start 'content'
Timing:	Jan 18 2025 05:04:49
Module end 'content'
Timing:	Jan 18 2025 05:04:49
Script end

Main resources:

Total runtime	0.5983 sec
Peak memory usage	4,096.0000 KB
Database Queries	59

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0059	587.9297	152.6250
Module start 'layout'	0.0059	0.0041	740.5547	39.4453
Module start 'content'	0.0100	0.5867	780.0000	578.1953
Module end 'content'	0.5967	0.0015	1,358.1953	12.1563
Script end	0.5982		1,370.3516

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.5552	16	0.0002
Check MTime	0.0015	0.2436	16	0.0001
Mysql Total
Database connection	0.0009	0.1434	1	0.0009
Mysqli_queries	0.5499	91.9098	59	0.0093
Looping result	0.0010	0.1622	57	0.0000
Template Total	0.5638	94.2	2	0.2819
Template load	0.0024	0.3930	2	0.0012
Template processing	0.5615	93.8442	2	0.2807
Template load and register function	0.0003	0.0430	1	0.0003
states
state_id_array	0.0022	0.3617	1	0.0022
state_identifier_array	0.0014	0.2382	2	0.0007
Override
Cache load	0.0020	0.3295	16	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0005	0.0872	3	0.0002
Fetch class attribute name	0.0012	0.1952	5	0.0002
XML
Image XML parsing	0.0011	0.1768	3	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0017	5	0.0000
General
dbfile	0.0007	0.1245	23	0.0000
String conversion	0.0000	0.0018	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
3	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	content/datatype/view/ezxmltags/literal.tpl	<No override>	extension/community/design/standard/templates/content/datatype/view/ezxmltags/literal.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 11 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs