Re: Paginating search results

It's all firing well, thanks for the heads up and the help. On May 11, 9:26 am, Nuno Maltez wrote: > Great, Just make sure you don't end up with multiple "page" arguments > on your query string when navigating through the results (click next; > click next again...). > >

Re: Paginating search results

Great, Just make sure you don't end up with multiple "page" arguments on your query string when navigating through the results (click next; click next again...). Nuno On Tue, May 11, 2010 at 2:41 PM, Nick wrote: > The POST thing was the result of late night meltdowns and

Re: Paginating search results

The POST thing was the result of late night meltdowns and desperation. I tend to just try stupid things when i'm working through an issue like this, just seeing what the application is capable of doing. I've switched it all back to GET. I found the answer around 1 this morning. You are exactly

Re: Paginating search results

You need to pass the current search paramters in your query string (?party=D== ) when you create the links to all the pages, and you need to be able to retrieve them from request.GET in order to recreate the object list (reps) when rendering a specific page (any particular reason why are you using

Paginating search results

I'm trying to paginate results from a search with multiple options. The only problem is, once I hit the next button it clears the query and I'm left paginating all the objects in the DB. Here is my view: def filter_search(request): if request.POST: reps = Rep.objects.all() else: