Drop down class list

Next topic

Author	Message
Nicolas Gommenginger	Thursday 14 January 2010 7:59:38 am Hi, In the back-office, I would to limit the drop down class list for the creation of a new element functions of the current node. For exemple, I have a class "articles_root", if the admin goes to this node and would like to create a new article in it, I would like that the drop down class list contains only the class articles. Thanks. Nico
Nicolas Pastorino	Thursday 14 January 2010 11:38:11 pm Hi Nicolas, The usual way of restricting the list of allowed content classes for creation at a given location in the tree is to use the access control system. The content \| create policy accepts such limitations. But your case seems to be more of a functional use case than a security question, and the method exposed above might not be suitable. A possible solution would be to build this drop down by hand, in the template you are using for this. I would advise to always verify the list you are building against the authorized one, for security reasons. The latter is available in a node template as follows: $node.object.can_create_class_list which takes into account the currently logged in user and the context (location, type of object viewed, section number, ...). You could then further filter this variable. Hope that helps, cheers! -- Nicolas Pastorino Director Community - eZ Member of the Community Project Board eZ Publish Community on twitter: http://twitter.com/ezcommunity t : http://twitter.com/jeanvoye G+ : http://plus.tl/jeanvoye

Author

Message

Thursday 14 January 2010 7:59:38 am

Hi,

In the back-office, I would to limit the drop down class list for the creation of a new element functions of the current node.

For exemple, I have a class "articles_root", if the admin goes to this node and would like to create a new article in it, I would like that the drop down class list contains only the class articles.

Thanks.

Nico

Nicolas Pastorino

Thursday 14 January 2010 11:38:11 pm

Hi Nicolas,

The usual way of restricting the list of allowed content classes for creation at a given location in the tree is to use the access control system. The content | create policy accepts such limitations.
But your case seems to be more of a functional use case than a security question, and the method exposed above might not be suitable. A possible solution would be to build this drop down by hand, in the template you are using for this. I would advise to always verify the list you are building against the authorized one, for security reasons. The latter is available in a node template as follows:

$node.object.can_create_class_list

which takes into account the currently logged in user and the context (location, type of object viewed, section number, ...). You could then further filter this variable.

Hope that helps, cheers!

--
Nicolas Pastorino
Director Community - eZ
Member of the Community Project Board

eZ Publish Community on twitter: http://twitter.com/ezcommunity

t : http://twitter.com/jeanvoye
G+ : http://plus.tl/jeanvoye

eZ debug

Timing:	Jan 18 2025 11:35:09
Script start
Timing:	Jan 18 2025 11:35:09
Module start 'layout'
Timing:	Jan 18 2025 11:35:09
Module start 'content'
Timing:	Jan 18 2025 11:35:10
Module end 'content'
Timing:	Jan 18 2025 11:35:10
Script end

Main resources:

Total runtime	0.9440 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0051	588.9297	152.6094
Module start 'layout'	0.0051	0.0031	741.5391	39.4141
Module start 'content'	0.0083	0.9343	780.9531	525.6563
Module end 'content'	0.9426	0.0014	1,306.6094	8.1875
Script end	0.9440		1,314.7969

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0040	0.4287	16	0.0003
Check MTime	0.0015	0.1635	16	0.0001
Mysql Total
Database connection	0.0008	0.0868	1	0.0008
Mysqli_queries	0.8953	94.8399	54	0.0166
Looping result	0.0006	0.0617	52	0.0000
Template Total	0.9061	96.0	2	0.4530
Template load	0.0026	0.2741	2	0.0013
Template processing	0.9035	95.7052	2	0.4517
Template load and register function	0.0003	0.0282	1	0.0003
states
state_id_array	0.0016	0.1643	1	0.0016
state_identifier_array	0.0018	0.1857	2	0.0009
Override
Cache load	0.0022	0.2331	16	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0009	0.0991	2	0.0005
Fetch class attribute name	0.0026	0.2702	3	0.0009
XML
Image XML parsing	0.0006	0.0638	2	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0011	3	0.0000
General
dbfile	0.0023	0.2446	16	0.0001
String conversion	0.0000	0.0007	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
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
4	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.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: 7

Time used to render debug report: 0.0001 secs