I ended up figuring out what the problem was. I was retrieving the
value from key page_num from GET:
pageNum = request.GET.get("page_num", 0)
That's problematic because I remember it being mentioned in the docs
that a get returns a string. Therefore, I need to do the following
instead:
pageNum = int(request.GET.get("page_num", 0)
On Apr 25, 1:24 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On 4/24/07, Moses Ting <[EMAIL PROTECTED]> wrote:
>
> > Has anyone run into errors with the paginator.has_next_page function?
> > It seems to be returning false even though I am certain that there's a
> > next page.
>
> Could you post some more details about the situation you're
> encountering? Without knowing things like how many objects you have,
> how many you're asking for per page, etc., it's hard to guess at the
> problem.
>
> Off the top of my head, the only explanation that occurs is that you
> might be running into an "orphan"; IIRC a patch went in a while back
> which will munge the pagination a bit if the last page would have only
> one object. So, for example, if you had sixteen objects, displaying
> five per page, you'd only get three pages -- instead of a fourth page
> with one object, the third page would be the last and would have six
> objects.
>
> --
> "Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
