Raj, thanks a lot for your reply! It really *is* a tight situation, especially since I can only reproduce the error at Bluehost... so debugging is not simple, and definitely not fast.
I believe the user field used to be called "user" first, and later I changed to user_id or something, but honestly I'm now sending the 'user' value from request.user's context. As to changing to a ChangeManipulator, that'd solve part of the problem only, no? In any case, it's another thing to try out. Thanks a million, again! -- Carlos Yoder http://blog.argentinaslovenia.com/ On 10/5/06, RajeshD <[EMAIL PROTECTED]> wrote: > > Disclaimer: I may be totally off the track here but seeing your > desperate plea, I thought I would share this anyway: > > AddManipulator is probably discarding your primary key coming from the > POST. The user field, in your case, serves as a primary key (since it > is defined as a OneToOneField). Try ChangeManipulator and see if that > improves the situation. > > Also, I am not sure if the field name should be user_id or user. So, > try changing it to 'user'. > > Sorry, if this doesn't help. > > -Raj > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
