On 10/22/07, Rufman <[EMAIL PROTECTED]> wrote: > > So this means I cannot pass a context object as well?
No, not with a redirect. I think you may want to rethink your design here. You've got one bit of information about what data to retrieve (page number) as part of the URL. You'e got other information (whatever the limiting criteria is) elsewhere (form fields?). This seems to be leading you into a problem area, where the information contained in the limiting criteria makes the requested URL invalid, so you are trying to figure out how to change the requested URL, but that strikes me as not the right approach. Instead perhaps you should change your design so that you never get into this situation. I'm not sure how you are doing the limiting with forms, but perhaps the page number should also be part of the form data , along with the filtering criteria, instead of embedded in the URL? An alternative approach is what the Django admin does with filters and pagination: all of the filter/page number information is in the url as query data (e.g. "?p=4&filter_field=val"). The links to change the filter specifications do not include any "p=n" values, so they implictly reset the page to the first page when you select a filter, regardless of what page you were on when you made the selection. Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
