1) Panel pages need to be Comcode pages if you want to use the Composr menu features, but otherwise there is nothing stopping you constructing panel pages as HTML or modules if you wish to.
2) You will very rarely want to put new menus onto anything other than a panel page, although there is nothing stopping you putting them anywhere Comcode or Tempcode is supported.
[title="2"]Permissions[/title]
The "Only display if has permission" option can only check zone and page permissions, not category permissions.
There is a little trick if you want to apply arbitrary "permission" checks to individual branches. Under the "Advanced" options, you can put Tempcode into the "Restrict link visibility" option.
Here are a couple of examples:
- [tt]{$?,{$IS_GUEST},_never_}[/tt] -- Do not show the branch to guests
- [tt]{$?,{$NOT,{$IS_ADMIN}},_never_}[/tt] -- Only show the branch to super-administrators
- [tt]{$?,{$NOT,{$IS_IN_GROUP,2-3,7}},_never_}[/tt] -- Only show the branch to members within usergroups #2-#3 or usergroup #7
The trick works by only showing the branch on a zone named "_never_" (i.e. this is never going to happen).
@@ -15,7 +15,7 @@ ENTRY_POINTS_DESCRIPTION=‘Entry points’ are a special kind of &lsquo
BRANCHES_DESCRIPTION=Menus consist of ‘branches’. Branches may hold child branches, or may just be links. Whether branches with children may have links of their own, or are allowed, depends on the type of menu.<br />Note that this menu editor does not define the style a menu is displayed in or its box title – this is defined separately, according to what parameters are used with the <kbd>menu</kbd> block (usually edited in the Zone Editor).</p><p>Note that menu structure (what's on what menus) is entirely separate from site structure (zones) and category/Comcode page structure. To control site structure, use the <a href="{1}">Sitemap Editor</a>. Category/Comcode page structure is controlled from the add/edit screens of individual categories/Comcode pages.
CAPTION_LONG=Tooltip
MENU_ENTRY_CAPTION_LONG=The tooltip for the branch (may be blank).
MENU_ENTRY_MATCH_KEYS=A comma-separated list of match-keys that list which screens this menu link will show on, or leave blank for the menu link to always show. For example, <kbd>_WILD:_WILD:add</kbd> then the link will only show on ‘ad’ screens.<br /><br />If you want to prevent guests seeing this link, you can do a little trick of entering some Tempcode in here that limits their viewing of this link to an unmatchable match-key, e.g. <kbd>{$?,{$IS_GUEST},_never_}</kbd>.<br /><br />Note that use of this field setting probably means you need to disable block caching on the menu block – this is covered in the “Customising what's on the menus” tutorial.
MENU_ENTRY_MATCH_KEYS=A comma-separated list of match-keys that list which screens this menu link will show on, or leave blank for the menu link to always show. For example, <kbd>_WILD:_WILD:add</kbd> then the link will only show on ‘ad’ screens.<br /><br />If you want to prevent guests seeing this link, you can do a little trick of entering some Tempcode in here that limits their viewing of this link to an unmatchable match-key, e.g. <kbd>{$?,{$IS_GUEST},_never_}</kbd><br /><br />Note that use of this field setting probably means you need to disable block caching on the menu block – this is covered in the “Customising what's on the menus” tutorial.
MENU_ENTRY_URL=An URL, or a page-link/entry-point (which you can pick to the right).
MENU_ENTRY_BRANCH=May just link to a page, or be initially expanded/contracted with children. Will be ignored for <abbr title="These menu types: zone, embossed, select, top">flat menu types</abbr>.
