Sure, Russ, I'll be more explicit, hopefully less Zen-like. The cheetsheet model as-is works just as expected with django.views.generic.create_update.create_object, i.e. 1. url kicks off generic view add to template with empty fields as expected 2. I enter data, click save 3. I get whisked back to django.views.generic.list_detail.object_list driven template per post_save_redirect config 3. voila - the new record has been created
Does not work == when I use the second example shown in my initial post, i.e. with a foreign key to the Theater model I made up for testing in the same models.py file: 1. url kicks off generic view create_update.create_object to empty template as expected 2. I enter data, click save 3. The status bar flashes a "Transfering data to local host" message, but the page remains at "add" template. Clearly, something has gone wrong. 4. I check database, no new record Similarly for django.views.generic.create_update.update_object. They work fine on the cheetsheet model, but when a foreign key is added to the Theater model that I made up for testing, changes do not take, browser does not forward. It seemed confusing that foreign keys local to the project or app cause the problem, but not the foreign key to the admin User model. Not sure what that means, but it may be a clue. Have I expressed the issue clearly enough? I've been deep into it for several days, paring it down to the simplest django project I could that would display the problem. Took quite a while to isolate it to the presence or absence of a foreign key (other than admin's User). Thanks, Tom --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
