Hi

I suggested almost the same for eZ 3.9 It could be done on class level too (for example images under each image gallery).

I'll definitely try your code. Thanks for sharing it with us!

A slightly modified version for eZ publish 3.7 of Muu Sle's code with support for defaults specified by the content class identifier:

    <select name="ClassID" title="{'Use this menu to select the type of item you wish to create and click the "Create here" button. The item will be created within the current location.'|i18n( 'design/admin/node/view/full' )|wash()}">
    {def $DefaultClassMapByNode=ezini('DefaultCreateHere','DefaultClassMapByNode','content.ini')
         $DefaultClassMapByClass=ezini('DefaultCreateHere','DefaultClassMapByClass','content.ini')
         $prefered_class=null}
        {if is_set($DefaultClassMapByClass[$node.class_identifier])}
            {set $prefered_class = $DefaultClassMapByClass[$node.class_identifier]}
        {/if}

        {if is_set($DefaultClassMapByNode[$node.node_id])}
            {set $prefered_class = $DefaultClassMapByNode[$node.node_id]}
        {elseif is_set($prefered_class)|not}
            {if is_set($DefaultClassMapByNode[$node.parent_node_id])}
                {set $prefered_class = $DefaultClassMapByNode[$node.parent_node_id]}
            {elseif is_set($DefaultClassMapByNode[$node.parent.parent_node_id])}
                {set $prefered_class = $DefaultClassMapByNode[$node.parent.parent_node_id]}
            {/if}
        {/if}
        {section var=CanCreateClasses loop=$can_create_classes}
              <option{eq($prefered_class, $CanCreateClasses.item.identifier)|choose( '', ' selected' )} value="{$CanCreateClasses.item.id}">{$CanCreateClasses.item.name|wash()}</option>
        {/section}
    {undef $DefaultClassMapByNode $prefered_class}
    </select>

Example INI settings:

[DefaultCreateHere]
DefaultClassMapByClass[gallery]=image
DefaultClassMapByClass[forum]=forum_topic
DefaultClassMapByClass[forum_topic]=forum_reply
DefaultClassMapByNode[]
DefaultClassMapByNode[2]=folder

First it looks for a default for the class of the current node, then this choice can be overriden for specific nodes. If then still no default is found, it will look for a node default of either the parent node, or the grandparent node.

Modified on Tuesday 20 June 2006 2:58:52 pm by Kristof Coomans

Nice!
Agreed, it would be complete when adding support for doing this at class level, very handy!

Hi,

Cool ! This is exactly what I was looking for. Do you know if this code exists as an extension ? Or if I have to create mine ?

Cheers.

It's not in an extension yet, but feel free to create one and to post it as a contribution, as long as you give us some credits

In fact, I was searching a way to limit available "create here" choices, not only suggest one.

I thought it was in eZ settings, but can't find where, then I found this post. I'll try to change this code a little to add a way to limit available classes as well in the "create here" function.

I know we can do this with roles & policies, but I want to do this in a more efficient and global manner. I think this is the way. But correct me if I'm wrong or if it already exists.

Cheers.

Apparently, I have 2 profiles with the same email

By the way, I made the extension, with the possibility to define available classes by node or class.

Modified on Tuesday 31 October 2006 11:32:54 am by Guillaume Contival

I've packed the modified template for eZ 3.9.0 in an extension and it's in svn now:
http://pubsvn.ez.no/community/trunk/extension/defaultcreatehere