Paginate Eloquent collection

Exemple :

$users = User::where('votes', '>', 100)->paginate(15);

You can find more results http://laravel.com/docs/5.1/pagination#paginating-eloquent-results

@bluepenlabs : As I said in the topic, it's on a Collection, after the DB query. Here you talk about the classic paginate() on the query. If you prefer I need to paginate the result from :

$users = User::where('votes', '>', 100)->get();

You can create your own pagination object after it

$users = User::where('votes', '>', 100)->get();

$page = Input::get('page', 1); // Get the ?page=1 from the url
$perPage = 15; // Number of items per page
$offset = ($page * $perPage) - $perPage;

return new LengthAwarePaginator(
    array_slice($users->toArray(), $offset, $perPage, true), // Only grab the items we need
    count($users), // Total items
    $perPage, // Items per page
    $page, // Current page
    ['path' => $request->url(), 'query' => $request->query()] // We need this so we can keep all old query parameters from the url
);

@bobbybouwmann : Thanks for example. I'll try this. Feel kind of weird not to have it directly available in the Collection class.

@bobbybouwmann do you realize how many paginators you have written for people? Just think a little bit of study, understanding the MySQL limit clause, and a little math and they could write their own. But that is so 2015.

@jlrdw : Agreed but knowing how others do and not always code on our own way, open your mind to new methods, technics, patterns, etc... If not there is no point of using a Framework, working with Open Source and be part of this community. But it's just my opinion.

One of my points is ts been answered before, it just seems no one is willing to do a search. https://laracasts.com/search?q=Paginate+collection&q-where=lessons

@jlrdw Is this a good thing? I'm just helping out :P

Yes I realize just don't hurt to search first.

@bobbybouwmann ,thanks, you helped me out also!

bobbybouwmann: I suggest replacing $users->toArray() with $users->all().

"toArray also converts all of the collection's nested objects to an array. If you want to get the raw underlying array, use the all method instead."

@leber My code is written almost a year ago! The collection class has since been changed a bit.

Sure. It's for people that googled this thread and receive error ;).

In my opinion this is a better way to paginate a Collection, using the Collections forPage method as an alternative to array_slice:

function collection_paginate($items, $per_page)
{
    $page   = Request::get('page', 1);
    $offset = ($page * $per_page) - $per_page;

    return new Illuminate\Pagination\LengthAwarePaginator(
        $items->forPage($page, $per_page)->values(),
        $items->count(),
        $per_page,
        Illuminate\Pagination\Paginator::resolveCurrentPage(),
        ['path' => Illuminate\Pagination\Paginator::resolveCurrentPath()]
    );
}

This simply keeps $items as a Collection because in Illuminate\Pagination\LengthAwarePaginator's constructor, $this->items is going to get transformed into a Collection anyway:

$this->items = $items instanceof Collection ? $items : Collection::make($items);

So basically this is just less overhead.

@JEITNIER - This right here is fire!