3.4 - how to make right hand toolbar content section dependent?

Thursday 08 July 2004 7:24:45 am

That's the approach I would take. I have successfully used similar setups for section-dependent displays.

Alex
bald_technologist on the IRC channel: #eZpublish
http://www.agrussell.com :: http://www.cuttingedge.com

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

Thursday 08 July 2004 9:02:38 am

Well, you can make it much easier using a switch/case. Something along the lines of:

{switch name=Toolbar match=$DesignKeys:used.section}
  {case match=1}
    <p>Show this content only on the main page</p>
  {/case}	  
  {case match=4}
    <p>Show this for the Services pages</p>
  {/case}	    
  {case match=6}
    <p>Show News stuff here</p>
  {/case}	  
  {case in=array(1,6)}
    <p>Show this on both the main page and the News page, but NOT the Services page</p>
  {/case}
  {case}
    <p>Show this if the page is in a section that doesn't match any of the above.</p>
  {/case}
{/switch}

For this example, let's say the main section of the site has a Section ID of 1, the Services Section has an ID of 4, and the News section an ID of 6. The switch statement will match each of the cases against <i>$DesignKeys:used.section</i> which is the section id of the currently viewed page.

Switch Documentation: http://ez.no/ez_publish/documentation/development/libraries/ez_template/functions/switch
Template Variables Set by eZ publish: http://ez.no/content/search?SearchText=designkeys

Does this help?

Alex
bald_technologist on the IRC channel: #eZpublish
http://www.agrussell.com :: http://www.cuttingedge.com

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

Thursday 08 July 2004 9:46:27 am

You should be fine using this as the pages will indeed by cached. :)

Alex

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

Friday 23 July 2004 2:46:59 pm

What actually happens when you insert the navigation code? Does it display anything?

As far as I know, there isn't any constraint to the amount of code within case tags, nor are there any constrains concerning sections.

Make sure that your variables were created within a <i>let</i> tag encasing this code. If you copied this from a different part of the page, you may need to declare <i>menu</i>...

Alex

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

Wednesday 28 July 2004 1:00:30 pm

Hrrrm, I'm not spotting anything at the moment. I'm still not sure if <i>menu</i> has actually been declared anywhere though. Have you turned on debugging to see if it can provide you additional information? If you have turned it on, and nothing is returned, use the following bit of code to see if the second case statement is being triggered at all:

{switch name=Toolbar match=$DesignKeys:used.section}
{case match=5}
<p>Show this content only on the main page</p>
{/case}
{case}
** Test 1 **
{let root_node=fetch( content, node, hash( node_id, 2 ) )
submenu=fetch( content, list, hash( parent_node_id, $module_result.path[1].node_id,
class_filter_type, include,
class_filter_array, ezini( 'MenuContentSettings', 'LeftIdentifierList', 'menu.ini' ),
sort_by, $root_node.sort_array ) )}
<ul>
{section var=menu loop=$submenu}
<li class="menu-level-0"><a href={$menu.url_alias|ezurl}>{$menu.name|shorten( 25 )}</a></li>
{/section}

{section show=$submenu|count}
<li class="menu-level-0"></li>
{/section}
</ul>

<div class="breakall"></div>
{/let}

** Test 2 **

{/case}
{/switch}

When you test, you should see ** Test 1 ** and ** Test 2 ** show up in your page. That will at least ensure that the switch statement isn't the issue.

Alex

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

Tuesday 03 August 2004 9:11:36 am

Hrrrm, i'm not sure what would be causing the problem. The variables appear to be declared properly... You oculd try declaring them earlier, it wouldn't hurt anything, but as you said, it seems pretty silly to have to do that. If I can think of anything else, I'll post it.

Alex

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

Wednesday 04 August 2004 12:28:39 am

Alex,

Managed to get this working, but by using 'section show' rather than switch. Code that switches between the different menu's is:

{section show=eq($DesignKeys:used.section,5)}
 
 <div id="leftmenu">
<div id="leftmenu-design">

<h3 class="hide">{"Left sub menu"|i18n("design/base")}</h3>

{section show=and( is_set( $module_result.path[1] ), is_set( $module_result.node_id ) )}
{let root_node=fetch( content, node, hash( node_id, 2 ) )
     submenu=fetch( content, list, hash( parent_node_id, 2,
                                         class_filter_type, include,
                                         class_filter_array, ezini( 'MenuContentSettings', 'LeftIdentifierList', 'menu.ini' ),
                                         sort_by, $root_node.sort_array ) )}
    <ul>
    {section var=menu loop=$submenu}
        <li class="menu-level-0"><a href={$menu.url_alias|ezurl}>{$menu.name|shorten( 25 )}</a></li>
    {/section}

    {section show=$submenu|count}
    <li class="menu-level-0"></li>
    {/section}
    </ul>

    <div class="breakall"></div>

{/let}
{/section}

</div>
</div>
 
{section-else}

<div id="leftmenu">
<div id="leftmenu-design">

<h3 class="hide">{"Left sub menu"|i18n("design/base")}</h3>

{section show=and( is_set( $module_result.path[1] ), is_set( $module_result.node_id ) )}
{let root_node=fetch( content, node, hash( node_id, 2 ) )
     submenu=fetch( content, list, hash( parent_node_id, $module_result.path[1].node_id,
                                         class_filter_type, include,
                                         class_filter_array, ezini( 'MenuContentSettings', 'LeftIdentifierList', 'menu.ini' ),
                                         sort_by, $root_node.sort_array ) )}
    <ul>
    {section var=menu loop=$submenu}
        <li class="menu-level-0"><a href={$menu.url_alias|ezurl}>{$menu.name|shorten( 25 )}</a></li>
    {/section}

    {section show=$submenu|count}
    <li class="menu-level-0"></li>
    {/section}
    </ul>

    <div class="breakall"></div>

{/let}
{/section}

</div>
</div>

{/section}

I need to use this in more complex situations soon though, hope it scales up ok...

Steve,

http://www.oneworldmarket.co.uk

Wednesday 04 August 2004 8:48:04 am

Glad you got it working! I am not aware of a way to do the multiple section shows like you demonstrated, I believe that is the purpose of the switch functionality (right back to where we started!) :(

Alex

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

Monday 09 August 2004 3:41:03 am

Steve,

The reason why the switching earlier doesn't work is that you try to use the or operator as a function which takes section as an argument/parameter. This is not supported.

You can use a normaly switch for this:

{switch match=$DesignKeys:used.section}
{case match=4}
    This is in section 4.
{/case}
{case match=3}
    This is in section 3.
{/case}
{case match=2}
    This is in section 2.
{/case}
{case}
    This is the default case, i.e. not in section 2,3 or 4.
{/case}
{/switch}

--bård

Documentation: http://ez.no/doc

Monday 09 August 2004 4:22:30 am

Steve,

no, not at all. We use a switch to do excactly this here on ez.no. A switch is very well suited to show e.g. a menu/graphigs dependant on which section you are in on the site.

--bård

Documentation: http://ez.no/doc