I am sure that any update will help others who might have this issue. I have been using the Django admin (on and off) for many years now and have not had this particular problem (yet).
It would also be useful to post more (non-confidential) details in a blog, perhaps. On Sunday, 13 July 2014 01:05:00 UTC+2, Timothy W. Cook wrote: > > Thanks for the reply Derek. This post was just a stab to see if anyone > had seen this before and I just missed the post. > > I guess it is time to roll up my sleeves and take a formal approach at > debugging. This one of VERY few, non-open source apps I work on. > Otherwise I would just point to the repository. > > When (if) I find the issue I will post a solution here. > > Cheers, > Tim > > > > On Sat, Jul 12, 2014 at 1:21 PM, Derek <game...@gmail.com <javascript:>> > wrote: > >> Tim >> >> Hard to tell without code; but what happens when you test without the >> form override? Also, unless you can reproduce the errors they get, then >> you will struggle to debug. Have you tried adding in log statements at key >> points to try & see where things go haywire? >> >> >> On Saturday, 12 July 2014 10:52:37 UTC+2, Timothy W. Cook wrote: >>> >>> Django 1.65, PostgreSQL. >>> >>> Several users of the admin UI in my app have noted that clicking Save or >>> Save and Continue buttons does not always actually save changes to the >>> database. >>> >>> Has anyone else seen this? I do override get_form in admin.py so that I >>> can set some fields as readonly based on a boolean flag. Otherwise my >>> admin.py is pretty generic. >>> >>> Any hint as to where to look for this problem or the best approach to >>> troubleshoot it? >>> >>> --Tim >>> >>> -- >>> >>> ============================================ >>> Timothy Cook >>> LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook >>> MLHIM http://www.mlhim.org >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-users...@googlegroups.com <javascript:>. >> To post to this group, send email to django...@googlegroups.com >> <javascript:>. >> Visit this group at http://groups.google.com/group/django-users. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-users/f22690f1-cd8d-48f0-928d-7fe879efa57f%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-users/f22690f1-cd8d-48f0-928d-7fe879efa57f%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > > ============================================ > Timothy Cook > LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook > MLHIM http://www.mlhim.org > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/02b539d1-b729-46fc-b810-346b2d1d06a5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
