Suckerfish Dropdown menu

Tuesday 26 July 2005 5:37:05 am

Hi,

I am trying to install the dropdown menu.
It says that I need to use 'the double_top.tpl file as the navigation template override'
Can someone tell me exactly which tpl file I need to override?
I can't find the double_top file to override with the admin interface....

Thanks for your help

Lydie

Thursday 28 July 2005 4:45:30 am

Lydie,
You only need to override if you are going to make changes to the default template and/or to when it is used.

You have several options:-
1. To override a .tpl in design/base/templates/menu
put the override in either design/base/overrides/templates/menu
or to make it siteAccess specific... in
design/<siteAccess>/overrides/templates/menu
in each case naming the override file the same as the file being overriden.
The above would override the original for all cases i.e. no class, section or node_id conditions.

2nd Option: Open your overrides.ini (or overrides.ini.append.php) in an editor and study its structure. Using the overrides.ini file you can name the overriding template anythingYouLike.tpl, you can put it in special folders, you can optionally add conditions relating to when it should be used such as in certain sections, or only with certain content classes or only with a specific node_id.
Bear in mind that the more specific the override condition the higher up the override.ini file it should be. The rule is... The first condition in the winning overrides.ini[.append][.php] to be met is the winner.
Tip: The bits in square brackets are just arbitrary lables but in the spirit of self-documentation they should be explanatory and/or match the name of the overriding template.
Tip 2: 'Subdir=' is the base or root directory within the site-access (and not a subdirectory of that) i.e. where to start looking for the .tpl . So, if you then place the .tpl in a directory below that you have to specify that in the 'MatchFile=' value e.g.
MatchFile = menu/myDoubleTop.tpl
Subdir = templates

Remember you may need to clear cache.
Enable Template debugging to verify that you are overriding correctly.

The Web Application Service Provider

Thursday 28 July 2005 6:53:32 am

For your information the dropdown menu work fine in 3.6.1 but I have noticed an error..
at the end the closing tags let and section are messed up.

here is the correct file:

{let top_cat=2
     used_node=false()}
        {set used_node=2}
{let node_obj=fetch(content,node,hash(node_id,$used_node))}
<ul id="nav">	

{* FIRST LEVEL *}
{section loop=fetch(content,list,hash(parent_node_id,$top_cat, class_filter_type, "include", class_filter_array, array(1),sort_by,array(array(priority))))}
{let child_check=fetch(content,list,hash(parent_node_id,$:item.node_id, class_filter_type, "include", class_filter_array, array(1)))}<li><a {section show=$child_check|count|gt(0)}{/section} href={concat("/content/view/full/",$:item.node_id,"/")|ezurl}>{$:item.name}</a>

{* SECOND LEVEL *}
		{let openol_check1=fetch(content,list,hash(parent_node_id,$:item.node_id, class_filter_type, "include", class_filter_array, array(1)))}
		                {section show=$openol_check1|count|gt(0)}<UL>{/section} 
								
        {section loop=fetch(content,list,hash(parent_node_id,$:item.node_id, class_filter_type, "include", class_filter_array, array(1),sort_by,array(array(priority))))}
		{let child_check1=fetch(content,list,hash(parent_node_id,$:item.node_id, class_filter_type, "include", class_filter_array, array(1)))}
		                <li><a {section show=$child_check1|count|gt(0)}class="daddy"{/section} href={concat("/content/view/full/",$:item.node_id,"/")|ezurl}>{$:item.name}</a>

{* THIRD LEVEL *}
				{section show=$child_check1|count|gt(0)}<ul>{/section}
                {section loop=fetch(content,list,hash(parent_node_id,$:item.node_id, class_filter_type, "include", class_filter_array, array(1),sort_by,array(array(priority))))}
				{let child_check2=fetch(content,list,hash(parent_node_id,$:item.node_id, class_filter_type, "include", class_filter_array, array(1)))}
		                <li><a {section show=$child_check2|count|gt(0)}class="daddy"{/section} href={concat("/content/view/full/",$:item.node_id,"/")|ezurl}>{$:item.name}</a>
						
{* FOURTH LEVEL *}
						{section show=$child_check2|count|gt(0)}<ul>{/section}
                        {section loop=fetch(content,list,hash(parent_node_id,$:item.node_id, class_filter_type, "include", class_filter_array, array(1),sort_by,array(array(priority))))}
                                <li><a class="path" href={concat("/content/view/full/",$:item.node_id,"/")|ezurl}>{$:item.name}</a></li>
                        {/section}
						{section show=$child_check2|count|gt(0)}</ul>{/section}						
						</li>
					   {/let}
                {/section}
				{section show=$child_check1|count|gt(0)}</ul>{/section}</li>{/let}
               {/section}
		 {section show=$openol_check1|count|gt(0)}</UL>{/section} 
		 </li>{/let}
{/let}
{/section}

 </ul>
{/let}
{/let}

Tuesday 16 August 2005 8:16:32 am

in the code there is

class_filter_type, "include", class_filter_array, array(1) 

which means folder (if I remember well).

all you have to do is change for something like this:

class_filter_type, "include", class_filter_array, array('folder','article') 

you should find somewhere in the documentation all the possible values for class_filter_array

Wednesday 07 December 2005 12:44:56 pm

The array(1) is related the class_filter_array and specifies that it should include class_id=1, which is folder. Thus, all folders are included.

In order to show only certain nodes, replace the whole fetch statement with an array of nodes that you want to display.

{let articles=fetch( content, list, hash(node_id, array( $id1, $id2, $id3 ) ) )}

Something like that should work, but I have not tested the code.

http://www.thinkcreative.com
Turning Ideas Into Strategic Solutions

Friday 09 December 2005 3:58:16 am

Figured it out from this post:

http://ez.no/community/forum/setup_design/excluding_a_node_from_the_left_hand_menu

This is the code I now use to exclude certain nodes from the top level menu:

{* FIRST LEVEL *}
{section loop=fetch(content,list,hash(parent_node_id,$top_cat, class_filter_type, "include", class_filter_array, array(1),sort_by,array(array(priority))))}
{section-exclude match=$:item.node_id|eq(102)} 
{section-exclude match=$:item.node_id|eq(92)} 
{section-exclude match=$:item.node_id|eq(115)} 
{section-include match=$:item.node_id|eq(396)}
{let child_check=fetch(content,list,hash(parent_node_id,$:item.node_id, class_filter_type, "include", class_filter_array, array(1)))}<li><a {section show=$child_check|count|gt(0)}{/section} href={$:item.url_alias|ezurl}>{$:item.name}</a>

http://www.parkroad.co.za

Friday 09 December 2005 5:09:44 am

Thanks Mark - you're right, it's better not to have to change it in the template. I'm going to give your first option a try and will let you know. Would the code to filter on the folder attribute look something like this (I've never done this kind of filtering before...):

{section loop=fetch(content,list,hash(parent_node_id,$top_cat, class_filter_type, "include", class_filter_array, array(1,2,33),attribute_filter, array( array( "folder/nav_include","=", 1 )),sort_by,array(array(priority))))}

http://www.parkroad.co.za