This site has been archived and you can no longer log in or post new messages. For up-to-date community resources please visit

eZ Community » Forums » General » [edit] NOT Bug in "drop down" menu

[edit] NOT Bug in "drop down" menu

[edit] NOT Bug in "drop down" menu

Wednesday 26 May 2010 10:06:05 am - 4 replies

The drop down menu you get when clicking on the icon of the object i admin2 is not considering the rights of the current user.. I get all the classes, and all though i am not able to create objects i still see all the classes available..

Is there a quick fix to this problem? Do the ez guys know about this?

Modified on Wednesday 26 May 2010 11:36:59 am by Håvard Bergersen

Wednesday 26 May 2010 11:02:34 am

This is actually by design, you can change it with [TreeMenu]CreateHereMenu=full in contentstructuremenu.ini.


# The "Create here" menu when clicking the node icon in the administrator interface.
#   disabled   - Not having the menu.
#   full       - Having the menu with the necessary permission checks - this will most likely slow down the interface.
#   simplified - Having the menu without the necessary permission checks
#                (in other words: the menu will include all classes regardless
#                 if the logged in user is allowed to create all those classes at that exact location).
#                Some users might get ACCESS DENIED, but it might just work for the most typical/usual cases
#                (where only one admin or a bunch of admins without limitations are using the interface).

Wednesday 26 May 2010 11:33:39 am

Aaaahhhhh.. happy.gif Emoticon

Thanks André, did not know this...

Tuesday 14 June 2011 9:42:42 am

I've just tried this in the latest version (eZ Publish Community 2011.5) and it makes matters even worse!

Using a user account that can create content (it has the 'Editor' role), the 'Create Here' menu ends up with no items. Also, the 'Create New' drop-down menu is empty too. But if I add a policy 'content/create/*' to the role, both these menus get fully populated.

It seems that the following fetch in children_detailed.tpl is the culprit:

{def $can_create_classes = fetch( 'content', 'can_instantiate_class_list', hash( 'parent_node', $node,
                                                                                     'filter_type', 'exclude',
                                                                                     'group_id', $group_id,
                                                                                     'group_by_class_group', true() ) )}

If the user has the policy 'content/create/*' then it returns a list of class groups, but if any other kind of content/create then it returns nothing! Any ideas? Is this a bug? How to fix it?

Modified on Tuesday 14 June 2011 9:43:36 am by Andy Caiger

Friday 17 June 2011 8:54:13 am

Am I right in thinking that there is a bug in the fetch code?

Anyway, we fixed the problem by replacing it with code from the ezwt extension.


You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from