Hi Malcom, and thanks for the reply. > The admin interface isn't really designed to be customised like that. > Rather, the principle is that if you can edit one record, you can edit > them all.
OK, I guessed that I would get that answer, but I took a chance anyhow. > However, a bit of reading of the source -- in particular, > contrib.admin.views.main -- will reveal some approaches that could be > used if you really wanted to. For example, the change_stage view (which, > along with add_stage() is used to process a model submission) sends the > user back to "../" upon success. So you could write a custom URLConf > entry that overrides that URL (admin/<app_name>/<model>/) and presented > them with the page you want to show them. That could be a solution to my problem. If I understand you right here, I should write a URLConf that in my case intercepts the URL / admin/publications/publication/ and points to a view that redirects the user to the page he started from before editing the record in the admin interface. I guess the address of the starting point has to be stored as a session parameter, if I want it to be dynamic. I also believe that I have to find a clever URL capturer for my custom view, since I also want to be able to point back to the original / admin/publications/publication/ list, if the user did not start from the custom list, but actually came from the /admin/publications/ publication/, but I don't want it to loop, of course. It looks as if the admin list view accepts the URL both with or without an ending slash, but the edit form always returns to the list with an ending slash, so maybe that little difference in the URLs could do the trick. I'll get back with a report, if I get it working. Thanks for your help, Ulf --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
