MarkupPagerNav::render() method

Render pagination markup

Example

$items = $pages->find("id>0, limit=10"); // replace id>0 with your selector
if($items->count()) {
  echo "<ul>" . $items->each("<li>{title}</li>") . "</ul>";
  $pager = $modules->get("MarkupPagerNav");
  $options = [ 'numPageLinks' => 5 ];
  echo $pager->render($items, $options); // render the pagination navigation
} else {
  echo "<p>Sorry there were no items found</p>";
}

Usage

// basic usage
$string = $pager->render($items);

// usage with all arguments
$string = $pager->render($items, array $options = []);

Arguments

NameType(s)Description
itemsWirePaginatable, PageArray, PaginatedArray

Items used in the pagination that have had a "limit=n" selector applied when they were loaded.

options (optional)array

Any options to override the defaults. See the MarkupPagerNav reference for all options.

Return value

string


Hooking $pager->render(…)

You can add your own hook events that are executed either before or after the $pager->render(…) method is executed. Examples of both are included below. A good place for hook code such as this is in your /site/ready.php file.

Hooking before

The 'before' hooks are called immediately before each $pager->render(…) method call is executed. This type of hook is especially useful for modifying arguments before they are sent to the method.

$this->addHookBefore('MarkupPagerNav::render', function(HookEvent $event) {
  // Get the object the event occurred on, if needed
  $MarkupPagerNav = $event->object;

  // Get values of arguments sent to hook (and optionally modify them)
  $items = $event->arguments(0);
  $options = $event->arguments(1);

  /* Your code here, perhaps modifying arguments */

  // Populate back arguments (if you have modified them)
  $event->arguments(0, $items);
  $event->arguments(1, $options);
});

Hooking after

The 'after' hooks are called immediately after each $pager->render(…) method call is executed. This type of hook is especially useful for modifying the value that was returned by the method call.

$this->addHookAfter('MarkupPagerNav::render', function(HookEvent $event) {
  // Get the object the event occurred on, if needed
  $MarkupPagerNav = $event->object;

  // An 'after' hook can retrieve and/or modify the return value
  $return = $event->return;

  // Get values of arguments sent to hook (if needed)
  $items = $event->arguments(0);
  $options = $event->arguments(1);

  /* Your code here, perhaps modifying the return value */

  // Populate back return value, if you have modified it
  $event->return = $return;
});

See Also


$pager methods and properties

API reference based on ProcessWire core version 3.0.155

Twitter updates

  • This post covers a few of the bigger updates in ProcessWire 3.0.154+3.0.155. This includes new live replacement of text in core and modules, a new method for creating canonical URLs, and some major upgrades to our input->urlSegment() method! More
    24 April 2020
  • A brief look at what's new in ProcessWire 3.0.154 in this forum post: More
    17 April 2020
  • This week we’ve got a few new and interesting core updates in progress, though none quite ready to release just yet. So rather than releasing version 3.0.154 today, I thought we'd instead take a brief look at what’s coming over the next few weeks… More
    3 April 2020

Latest news

  • ProcessWire Weekly #311
    In the 311th issue of ProcessWire Weekly we're going to talk a bit about the latest dev versions of ProcessWire, introduce a couple of new third party modules, and more. Read on!
    Weekly.pw / 25 April 2020
  • ProcessWire 3.0.154 and 3.0.155 core updates
    This post covers a few of the bigger updates in ProcessWire 3.0.154 and 3.0.155 on the dev branch. This includes a new function for live replacement of text in core and modules, a new method for creating canonical URLs, and some major upgrades to our $input->urlSegment() method that I think you’ll like!
    Blog / 24 April 2020
  • Subscribe to weekly ProcessWire news

“The end client and designer love the ease at which they can update the website. Training beyond how to log in wasn’t even necessary since ProcessWire’s default interface is straightforward.” —Jonathan Lahijani