Download the PHP package mimmi20/mezzio-navigation-laminasviewrenderer without Composer

Mezzio Navigation ViewHelper

Code Status

Installation

Run

Render the navigation

Calling the view helper for menus in your layout script:

Using multiple navigations

Once the mezzio-navigation module is registered, you can create as many navigation definitions as you wish, and the underlying factories will create navigation containers automatically.

Add the container definitions to your configuration file, e.g. config/autoload/global.php:

Container names have a prefix

There is one important point to know when using mezzio-navigation as a module: The name of the container in your view script must be prefixed with Mezzio\Navigation\, followed by the name of the configuration key. This helps ensure that no naming collisions occur with other services.

The following example demonstrates rendering the navigation menus for the named default, special, and sitemap containers.

View Helpers

The navigation helpers are used for rendering navigational elements from Mimmi20\Mezzio\Navigation\Navigation instances.

There are 5 built-in helpers:

• Breadcrumbs, used for rendering the path to the currently active page.
• Links, used for rendering navigational head links (e.g. <link rel="next" href="..." />).
• Menu, used for rendering menus.
• Sitemap, used for rendering sitemaps conforming to the Sitemaps XML format.
• Navigation, used for proxying calls to other navigational helpers.

All built-in helpers implements the interface Mezzio\Navigation\LaminasView\View\Helper\Navigation\ViewHelperInterface, which adds integration with laminas-acl or laminas-rbac and laminas-i18n. This interface Mimmi20\Mezzio\Navigation\Helper\Navigation\HelperInterface, which defines the following methods:

In addition to the method stubs from the interface, the abstract class also implements the following methods:

If a container is not explicitly set, the helper will create an empty Mimmi20\Mezzio\Navigation\Navigation container when calling $helper->getContainer().

Proxying calls to the navigation container

Navigation view helpers use the magic method __call() to proxy method calls to the navigation container that is registered in the view helper.

The call above will add a page to the container in the Navigation helper.

Translation of labels and titles

The navigation helpers support translation of page labels and titles. You can set a translator of type Laminas\I18n\Translator\TranslatorInterface in the helper using $helper->setTranslator($translator).

If you want to disable translation, use $helper->setTranslatorEnabled(false).

The proxy helper will inject its own translator to the helper it proxies to if the proxied helper doesn't already have a translator.

Sitemaps do not use translation

There is no translation in the sitemap helper, since there are no page labels or titles involved in an XML sitemap.

Integration with ACL

All navigational view helpers support ACLs. An object implementing Laminas\Permissions\Acl\AclInterface can be assigned to a helper instance with $helper->setAcl($acl), and role with $helper->setRole('member') or $helper->setRole(new Laminas\Permissions\Acl\Role\GenericRole('member')). If an ACL is used in the helper, the role in the helper must be allowed by the ACL to access a page's resource and/or have the page's privilege for the page to be included when rendering.

If a page is not accepted by ACL, any descendant page will also be excluded from rendering.

The proxy helper will inject its own ACL and role to the helper it proxies to if the proxied helper doesn't already have any.

The examples below all show how ACL affects rendering.

Navigation setup used in examples

This example shows the setup of a navigation container for a fictional software company.

Notes on the setup:

• The domain for the site is www.example.com.
• Interesting page properties are marked with a comment.
• Unless otherwise is stated in other examples, the user is requesting the URL http://www.example.com/products/server/faq/, which translates to the page labeled FAQ under "Foo Server".
• The assumed ACL and router setup is shown below the container setup.

In addition to the container above, the following router setup is added to the configuration file of the module, e.g. module/MyModule/config/module.config.php

The setup of ACL can be done in a module class, e.g. module/MyModule/Module.php:

Navigation Proxy

The navigation() helper is a proxy helper that relays calls to other navigational helpers. It can be considered an entry point to all navigation-related view tasks.

The Navigation helper finds other helpers that implement Mezzio\Navigation\Helper\Navigation\HelperInterface, which means custom view helpers can also be proxied. This would, however, require that the custom helper path is added to the view.

When proxying to other helpers, the Navigation helper can inject its container, ACL and optionally role, and a translator. This means that you won't have to explicitly set all three in all navigational helpers, nor resort to injecting by means of static methods.

Methods

Breadcrumbs

Breadcrumbs are used for indicating where in a sitemap a user is currently browsing, and are typically rendered like the following:

The breadcrumbs() helper follows the Breadcrumbs Pattern as outlined in the Yahoo! Design Pattern Library, and allows simple customization (minimum/maximum depth, indentation, separator, and whether the last element should be linked), or rendering using a partial view script.

The Breadcrumbs helper finds the deepest active page in a navigation container, and renders an upwards path to the root. For pages, the "activeness" of a page is determined by inspecting the request object, as stated in the section on pages.

The helper sets the minDepth property to 1 by default, meaning breadcrumbs will not be rendered if the deepest active page is a root page. If maxDepth is specified, the helper will stop rendering when at the specified depth (e.g. stop at level 2 even if the deepest active page is on level 3).

Methods in the breadcrumbs helper:

Basic usage

This example shows how to render breadcrumbs with default settings.

In a view script or layout:

The call above takes advantage of the magic __toString() method, and is equivalent to:

Output:

Specifying indentation

This example shows how to render breadcrumbs with initial indentation.

Rendering with 8 spaces indentation:

Output:

Customize output

This example shows how to customize breadcrumbs output by specifying multiple options.

In a view script or layout:

Output:

Setting minimum depth required to render breadcrumbs:

Output: Nothing, because the deepest active page is not at level 10 or deeper.

Rendering using a partial view script

This example shows how to render customized breadcrumbs using a partial vew script. By calling setPartial(), you can specify a partial view script that will be used when calling render(). When a partial is specified, the renderPartial() method will be called when emitting the breadcrumbs. This method will find the deepest active page and pass an array of pages that leads to the active page to the partial view script.

In a layout:

Contents of module/MyModule/view/my-module/partials/breadcrumbs.phtml:

Output:

Links

The links() helper is used for rendering HTML LINK elements. Links are used for describing document relationships of the currently active page. Read more about links and link types at:

• Document relationships: the LINK element (HTML4 W3C Rec.)
• Link types (HTML4 W3C Rec.)

There are two types of relations; forward and reverse, indicated by the kewyords rel and rev. Most methods in the helper will take a $rel param, which must be either rel or rev. Most methods also take a $type param, which is used for specifying the link type (e.g. alternate, start, next, prev, chapter, etc).

Relationships can be added to page objects manually, or found by traversing the container registered in the helper. The method findRelation($page, $rel, $type) will first try to find the given $rel of $type from the $page by calling $page>findRel($type) or $page>findRel($type). If the $page has a relation that can be converted to a page instance, that relation will be used. If the $page instance doesn't have the specified $type, the helper will look for a method in the helper named search$rel$type (e.g. searchRelNext() or searchRevAlternate()). If such a method exists, it will be used for determining the $page's relation by traversing the container.

Not all relations can be determined by traversing the container. These are the relations that will be found by searching:

• searchRelStart(), forward start relation: the first page in the container.
• searchRelNext(), forward next relation; finds the next page in the container, i.e. the page after the active page.
• searchRelPrev(), forward prev relation; finds the previous page, i.e. the page before the active page.
• searchRelChapter(), forward chapter relations; finds all pages on level 0 except the start relation or the active page if it's on level 0.
• searchRelSection(), forward section relations; finds all child pages of the active page if the active page is on level 0 (a chapter).
• searchRelSubsection(), forward subsection relations; finds all child pages of the active page if the active pages is on level 1 (a section).
• searchRevSection(), reverse section relation; finds the parent of the active page if the active page is on level 1 (a section).
• searchRevSubsection(), reverse subsection relation; finds the parent of the active page if the active page is on level 2 (a subsection).

Allowed relation types

When looking for relations in the page instance ($page->getRel($type) or $page->getRev($type)), the helper accepts the values of type string, array, Traversable, or Mezzio\Navigation\Page\PageInterface:

• PageInterface instances are used directly.
• If a string is found, it will be converted to a Mezzio\Navigation\Page\Uri.
• If an array or Traversable is found, it will be converted to one or several page instances. If the first key is numeric, it will be considered to contain several pages, and each element will be passed to the page factory. If the first key is not numeric, the value will be passed to the page factory directly, and a single page will be returned.

The helper also supports magic methods for finding relations. E.g. to find forward alternate relations, call $helper->findRelAlternate($page), and to find reverse section relations, call $helper->findRevSection($page). Those calls correspond to $helper->findRelation($page, 'rel', 'alternate') and $helper->findRelation($page, 'rev', 'section'), respectively.

To customize which relations should be rendered, the helper uses a render flag. The render flag is an integer value, and will be used in a bitwise and (&) operation against the helper's render constants to determine if the relation that belongs to the render constant should be rendered.

See the example below for more information.

The LinksInterface helper defines the following constants:

• Mezzio\Navigation\Helper\Navigation\LinksInterface::RENDER_ALTERNATE
• Mezzio\Navigation\Helper\Navigation\LinksInterface::RENDER_STYLESHEET
• Mezzio\Navigation\Helper\Navigation\LinksInterface::RENDER_START
• Mezzio\Navigation\Helper\Navigation\LinksInterface::RENDER_NEXT
• Mezzio\Navigation\Helper\Navigation\LinksInterface::RENDER_PREV
• Mezzio\Navigation\Helper\Navigation\LinksInterface::RENDER_CONTENTS
• Mezzio\Navigation\Helper\Navigation\LinksInterface::RENDER_INDEX
• Mezzio\Navigation\Helper\Navigation\LinksInterface::RENDER_GLOSSARY
• Mezzio\Navigation\Helper\Navigation\LinksInterface::RENDER_COPYRIGHT
• Mezzio\Navigation\Helper\Navigation\LinksInterface::RENDER_CHAPTER
• Mezzio\Navigation\Helper\Navigation\LinksInterface::RENDER_SECTION
• Mezzio\Navigation\Helper\Navigation\LinksInterface::RENDER_SUBSECTION
• Mezzio\Navigation\Helper\Navigation\LinksInterface::RENDER_APPENDIX
• Mezzio\Navigation\Helper\Navigation\LinksInterface::RENDER_HELP
• Mezzio\Navigation\Helper\Navigation\LinksInterface::RENDER_BOOKMARK
• Mezzio\Navigation\Helper\Navigation\LinksInterface::RENDER_CUSTOM
• Mezzio\Navigation\Helper\Navigation\LinksInterface::RENDER_ALL

The constants from RENDER_ALTERNATE to RENDER_BOOKMARK denote standard HTML link types. RENDER_CUSTOM denotes non-standard relations specified in pages. RENDER_ALL denotes standard and non-standard relations.

Methods in the links helper:

Basic usage

Specify relations in pages

This example shows how to specify relations in pages.

Default rendering of links

This example shows how to render a menu from a container registered in the view helper.

In a view script or layout:

Output:

Specify which relations to render

This example shows how to specify which relations to find and render.

Render only start, next, and prev:

Output:

Render only native link types:

Output:

Render all but chapters:

Output:

Menu

The menu() helper is used for rendering menus from navigation containers. By default, the menu will be rendered using HTML UL and LI tags, but the helper also allows using a partial view script.

Methods in the Menu helper:

The following are options recognized by the renderMenu() method:

Basic usage

This example shows how to render a menu from a container registered/found in the view helper. Notice how pages are filtered out based on visibility and ACL.

In a view script or layout:

Or:

Output:

Calling renderMenu() directly

This example shows how to render a menu that is not registered in the view helper by calling renderMenu() directly and specifying options.

Output:

Rendering the deepest active menu

This example shows how renderSubMenu() will render the deepest sub menu of the active branch.

Calling renderSubMenu($container, $ulClass, $indent) is equivalent to calling renderMenu($container, $options) with the following options:

Usage of renderSubMenu method:

The output will be the same if 'FAQ' or 'Foo Server' is active:

Rendering with maximum depth

Output:

Rendering with minimum depth

Output:

Rendering only the active branch

Output:

Rendering only the active branch with minimum depth

Output:

Rendering only the active branch with maximum depth

Output:

Rendering only the active branch with maximum depth and no parents

Output:

Rendering a custom menu using a partial view script

This example shows how to render a custom menu using a partial view script. By calling setPartial(), you can specify a partial view script that will be used when calling render(); when a partial is specified, that method will proxy to the renderPartial() method.

The renderPartial() method will assign the container to the view with the key container.

In a layout:

In module/MyModule/view/my-module/partials/menu.phtml:

Output:

Using additional parameters in partial view scripts

Starting with version 2.6.0, you can assign custom variables to a partial script.

In a layout:

In module/MyModule/view/my-module/partials/menu.phtml:

Output:

Using menu options in partial view scripts

In a layout:

In module/MyModule/view/my-module/partials/menu.phtml:

Output:

Using ACLs with partial view scripts

If you want to use an ACL within your partial view script, then you will have to check the access to a page manually.

In module/MyModule/view/my-module/partials/menu.phtml:

View Helper - Sitemap

The sitemap() helper is used for generating XML sitemaps, as defined by the Sitemaps XML format. Read more about Sitemaps on Wikipedia.

By default, the sitemap helper uses sitemap validators to validate each element that is rendered. This can be disabled by calling $helper->setUseSitemapValidators(false).

Sitemap XML elements

Validation only when enabled

If you disable sitemap validators, the custom properties (see table) are not validated at all.

The sitemap helper also supports Sitemap XSD Schema validation of the generated sitemap. This is disabled by default, since it will require a request to the schema file. It can be enabled with $helper->setUseSchemaValidation(true).

Methods in the sitemap helper:

Basic usage

This example shows how to render an XML sitemap based on the setup we did further up.

Notice how pages that are invisible or pages with ACL roles incompatible with the view helper are filtered out:

Rendering using no ACL role

Render the sitemap using no ACL role (should filter out /community/account):

Output:

Rendering using a maximum depth

Render the sitemap using a maximum depth of 1.

Output:

UTF-8 encoding used by default

By default, laminas-view uses UTF-8 as its default encoding. If you want to use another encoding with Sitemap, you will have do three things:

1. Create a custom renderer and implement a getEncoding() method.
2. Create a custom rendering strategy that will return an instance of your custom renderer.
3. Attach the custom strategy in the ViewEvent.

See the example from the HeadStyle documentation to see how you can achieve this.

License

This package is licensed using the MIT License.

Please have a look at LICENSE.md.