Weave Code
Paginator Bundle Laravel Package
facile-it/paginator-bundle
Facile IT PaginatorBundle is a Symfony bundle for paginating Doctrine ORM/ODM queries and arrays. It offers a simple paginator service, Twig helpers, and configurable navigation to add efficient pagination to listings and search results.
Facile PaginatorBundle is a Symfony bundle that adds simple, flexible pagination to your Doctrine queries and arrays. It wraps your data in a paginator service, handling page calculation, limits, and offsets so controllers stay clean.
Configure pagination once and reuse it across your application with minimal boilerplate.
- Works with Doctrine ORM/DBAL queries and plain arrays
- Supports page-based and offset-based navigation
- Configurable default page size and per-request overrides
- Provides total item and page counts for building pagers
- Lightweight integration with Symfony's service container and Twig
Frequently asked questions about Paginator Bundle
- Can I install facile-it/paginator-bundle in a Laravel application?
- No. It is a Symfony 2 bundle that registers through AppKernel and Symfony service-container XML/YAML definitions, and it provides no Laravel service provider, facade, config file, or publishable assets. Composer will also likely fail on Symfony and PHP version constraints against a modern Laravel stack.
- Does facile-it/paginator-bundle support Laravel 9, 10, or 11?
- No. The last release was in February 2017 and targets PHP 5.x/7.0-era constraints with Symfony 2.3 through 3.x. Laravel 9, 10, and 11 require PHP 8.1+ and modern Symfony components, so there is no supported overlap.
- What is facile-it/paginator-bundle used for?
- It is a Symfony bundle that adds pagination to Doctrine queries and array results with configurable page sizes. It also includes Twig helpers for rendering page navigation in Symfony templates. Those integration points are Symfony-specific and do not map to Laravel.
- Is there a Laravel equivalent to facile-it/paginator-bundle?
- Yes. Laravel ships first-class pagination through LengthAwarePaginator and CursorPaginator, plus Eloquent and query-builder methods such as paginate, simplePaginate, and cursorPaginate. Blade templates and API resources can render paginated results without any third-party bundle.
- How do I paginate Doctrine queries in Laravel?
- Laravel does not use Doctrine by default, so most applications should use Eloquent or the query builder with Laravel's native paginators. If you genuinely use Doctrine, use Doctrine's own paginator or a maintained Doctrine-Laravel bridge rather than an archived Symfony bundle. facile-it/paginator-bundle is not a viable integration path.
- Is facile-it/paginator-bundle maintained or archived?
- It is archived and read-only. The last release was 2017-02-23, the repository has very few stars and no dependents, and there are no patches, security advisories, or PHP 8 validation. That means any defect you encounter becomes your responsibility permanently.
- Will facile-it/paginator-bundle work on PHP 8.1 or PHP 8.3?
- No, not reliably. The 2017 code targets PHP 5.x/7.0 and is likely to hit fatal errors from PHP 8.x strictness, including deprecated dynamic properties, Countable and Iterator signature changes, and removed functions such as each(). It has not been validated against modern PHP runtimes.
- What are the best alternatives to facile-it/paginator-bundle for Laravel?
- Use Laravel's native pagination first: paginate, simplePaginate, or cursorPaginate for Eloquent and query-builder results. For non-Eloquent sources, manually construct LengthAwarePaginator or CursorPaginator from the sliced result set and total count. For collections, use Collection::forPage with AbstractPaginator::resolveCurrentPage, which is roughly 15 lines of owned, testable code.
- Can I use the Twig helpers from facile-it/paginator-bundle in Laravel Blade templates?
- No. The bundle's helpers are Twig extensions tied to Symfony's templating integration, and Laravel Blade has no equivalent auto-wiring for them. In Laravel you should render pagination with Blade's $paginator->links() or serialize paginated data through API resources.
- What should I do if I need to paginate external or in-memory results in Laravel?
- Build a small internal paginator using LengthAwarePaginator or CursorPaginator, passing the sliced items, total count, per-page value, and current page. This keeps the implementation testable and framework-native without adding an archived Symfony dependency. Cursor pagination is preferable for large or frequently changing datasets.
Weaver
How can I help you explore Laravel packages today?