On Mon, Jan 11, 2010 at 2:59 PM, kkerbel <kker...@gmail.com> wrote: > When viewing the admin pages for a travel request app we wrote, the > admin page shows the record links, however, when you click to view the > details of any record, I get an error stating "DoesNotExist: Employee > matching query does not exist." I've looked at the database and the > employee does indeed exist and all of the related tables' keys link > properly to each other. I recently upgraded from Django 1.0 to 1.1.1, > might there be a change between those versions that could cause this > issue? Any direction would be appreciated...i'm just failing to see > what could be causing this. > > It would help people help you if you were a bit more specific about what admin pages are displaying these links, what their values are, what admin definitions exist for the models(s) in question, etc. Given that the recommended way of specifying admin urls changed from 1.0 to 1.1 it might also be helpful to include exactly what admin url pattern you are using (though the old way should still work).
The basic admin function of listing all the objects on the change list page with links to an edit page for each certainly still works in 1.1.1, so it's a little hard to know what is going on in your case without more information. Karen--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
