On Feb 19, 7:08 pm, cyberjack <[EMAIL PROTECTED]> wrote: > Thanks for the suggestion, but there has got to be a simple way to > solve this problem. Does anyone else have an idea for solving this > problem?
It's just a regular Django view that's doing the work here. Take a look at the `change_stage` view [1] -- lines 355 to 369 in particular -- you'll see the redirects are hard-coded. All the simple solutions will be workarounds because of that. .. [1] http://code.djangoproject.com/browser/django/trunk/django/contrib/admin/views/main.py?rev=6991#L310 A complex solution would be to make a copy of that view somewhere, modify it to suit your needs, and point at your version with an URLconf that has higher precedence than your Admin URLconf (since Django stops at the first matching pattern). I can't guess about many potential pitfalls here, but it looks like it could be fairly straightforward if you get all your imports right. > Baring that, is there a way I can diff the the newforms-admin and see > what's changed? > Maybe I can figure out how the do the URL redirection if it's included > in the new branch. I misspoke by suggesting newforms-admin; I don't know for sure that this is possible. It is far more flexible than the current Admin, so I have high hopes, and other people also want this same functionality [2]. .. [2] http://code.djangoproject.com/ticket/6002 - whiteinge --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
