PHP Class 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.
Afficher le fichier
Open project: neos/flow-development-collection
Protected Properties
Свойство |
Type |
Description |
|
$controller |
Neos\FluidAdaptor\ViewHelpers\Widget\Controller\PaginateController |
|
|
Méthodes publiques
Méthode |
Description |
|
render ( Neos\Flow\Persistence\QueryResultInterface $objects, string $as, array $configuration = ['itemsPerPage' => 10, 'insertAbove' => false, 'insertBelow' => true, 'maximumNumberOfLinks' => 99] ) : string |
Render this view helper |
|
Method Details
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 |
|
Résultat |
string |
|
Property Details
$controller protected_oe property
protected PaginateController,Neos\FluidAdaptor\ViewHelpers\Widget\Controller $controller |
Résultat |
Neos\FluidAdaptor\ViewHelpers\Widget\Controller\PaginateController |
|