PHP 클래스 Neos\FluidAdaptor\ViewHelpers\Widget\PaginateViewHelper

= Examples =



use {paginatedBlogs} as you used {blogs} before, most certainly inside
a  loop.



This example will display at the maximum 10 links and tries to the settings
pagesBefore and pagesAfter into account to get the best result

= Performance characteristics = In the above example, it looks like {blogs} contains all Blog objects, thus you might wonder if all objects were fetched from the database. However, the blogs are NOT fetched from the database until you actually use them, so the paginate ViewHelper will adjust the query sent to the database and receive only the small subset of objects. So, there is no negative performance overhead in using the Paginate Widget.

상속: extends Neos\FluidAdaptor\Core\Widget\AbstractWidgetViewHelper

파일 보기 프로젝트 열기: neos/flow-development-collection

보호된 프로퍼티들

프로퍼티	타입	설명
$controller	Neos\FluidAdaptor\ViewHelpers\Widget\Controller\PaginateController

공개 메소드들

메소드	설명
render ( Neos\Flow\Persistence\QueryResultInterface $objects, string $as, array $configuration = ['itemsPerPage' => 10, 'insertAbove' => false, 'insertBelow' => true, 'maximumNumberOfLinks' => 99] ) : string	Render this view helper

메소드 상세

render() 공개 메소드

Render this view helper

public render ( Neos\Flow\Persistence\QueryResultInterface $objects, string $as, array $configuration = ['itemsPerPage' => 10, 'insertAbove' => false, 'insertBelow' => true, 'maximumNumberOfLinks' => 99] ) : string
$objects	Neos\Flow\Persistence\QueryResultInterface
$as	string
$configuration	array
리턴	string

프로퍼티 상세

$controller 보호되어 있는 프로퍼티

protected PaginateController,Neos\FluidAdaptor\ViewHelpers\Widget\Controller $controller
리턴	Neos\FluidAdaptor\ViewHelpers\Widget\Controller\PaginateController