HMENU

For every menu level, that should be rendered, an according entry must exist. It defines the menu object that should render the menu items on the according level. 1 is the first level, 2 is the second level, 3 is the third level and so on.

The property "1" is required!

The entry 1 for the first level always must exist. All other levels only will be generated when they are configured.

Example:

temp.sidemenu = HMENU
temp.sidemenu.1 = TMENU
temp.sidemenu.1 {
  # Configuration of that TMENU here...
}
temp.sidemenu.2 = TMENU
temp.sidemenu.2 {
  # Configuration of that TMENU here...
}
temp.sidemenu.3 = TMENU
temp.sidemenu.3 {
  # Configuration of that TMENU here...
}

This creates a menu with up to three levels: Each TMENU level can hold a different menu configuration.

TYPO3 offers a variety of menu objects.

The number of seconds a menu may remain in cache. If this value is not set, the first available value of the following will be used:

1. cache_timeout of the current page
2. config.cache_period defined globally
3. 86400 (= 1 day)

See cache function description for details.

Defines at which level in the rootLine the menu should start.

Default is "0" which gives us a menu of the very first pages on the site.

If the value is < 0, entryLevel is chosen from "behind" in the rootLine. Thus "-1" is a menu with items from the outermost level, "-2" is the level before the outermost...

Note: entryLevel does not show a menu of a certain level of pages (use special = directory for that) but it means that it will start to be visible from that level on.

So, for example if you build a simple "sitemap" menu like this one:

page.10 = HMENU
page.10 {
  entryLevel = 4
  1 = TMENU
  1.wrap = <ul> | </ul>
  1.NO.wrapItemAndSub = <li> | </li>
  1.expAll = 1
  2 < .1
  3 < .2
  4 < .3
  5 < .4
  6 < .5
  7 < .6
}

it will start to be visible from the 4th level (and will contain only the subpages from that level). Please note also that this affects also the menu generated with MenuProcessor. Example:

page.10 {
   dataProcessing {
    10 = TYPO3\CMS\Frontend\DataProcessing\MenuProcessor
    10 {
       special = list
       special.value.field = pages
       levels = 7
       entryLevel = 4
       as = menu
       expandAll = 1
       titleField = nav_title // title
    }
  }
}

Lets you define special types of menus.

See the section about the .special property!

List of page uid's to use for the special menu. What they are used for depends on the menu type as defined by ".special"; see the section about the .special property!

The minimum number of items in the menu. If the number of pages does not reach this level, a dummy-page with the title "..." and uid=[currentpage_id] is inserted.

Note: Affects all sub menus as well. To set the value for each menu level individually, set the properties in the menu objects (see "Common properties" table).

The maximum number of items in the menu. Additional items will be ignored.

Note: Affects all sub menus as well. (See "minItems" for a notice.)

The first item in the menu.

Example:

This results in a menu, where the first two items are skipped starting with item number 3:

begin = 3

Note: Affects all sub menus as well. (See "minItems" for a notice.)

This is a list of page uids to exclude when the select statement is done. Comma-separated. You may add "current" to the list to exclude the current page.

Example:

The pages with these uid-numbers will not be within the menu! Additionally the current page is always excluded too.

excludeUidList = 34,2,current

Enter the list of page document types (doktype) to exclude from menus. By default pages that are "backend user access only" (6) or "folder" (254) are excluded.

If set, pages with the checkbox "Page enabled in menus" disabled will still be included in menus.

This is a list of page UID numbers that will always be regarded as active menu items and thereby automatically opened regardless of the rootline.

If set, then for each page in the menu it will be checked if an Alternative Page Language record for the language defined in "config.sys_language_uid" exists for the page. If that is not the case and the pages "Localization settings" have the "Hide page if no translation for current language exists" flag set, then the menu item will link to a non accessible page that will yield an error page to the user. Setting this option will prevent that situation by adding "&L=0" for such pages, meaning that they will switch to the default language rather than keeping the current language.

The check is only carried out if a translation is requested ("config.sys_language_uid" is not zero).

Keyword: "all"

When set to "all" the same check is carried out but it will not look if "Hide page if no translation for current language exists" is set - it always reverts to default language if no translation is found.

For these options to make sense, they should only be used when "config.sys_language_mode" is not set to "content_fallback".

Note: This works only for special=language.

If "if" returns false, the menu is not generated.

Wrap for the HMENU.

(Executed after ".wrap".)