Hi,
I could not replicate your error here. I am also adding users via admin interface and the "Staff status" and "Superuser status" are unchecked by default.On Wed, May 1, 2013 at 2:22 PM, Thomas De Reyck <thomas%dereyck.eu@gtempaccount.com> wrote:
Hi Siddharth,
Thanks for your reply. I only create/delete/manage users via the admin itself, so there is no code to show you I guess.
Furthermore, the auth table displays the correct values when queried directly.
Kind regards,
Thomas
Op woensdag 1 mei 2013 10:48:10 UTC+2 schreef siddharth56660 het volgende:-SiddharthIt might help in understanding the problem.Hi Thomas,Can you paste the code snippet where you add the user in your auth table (not the admin).
On Tue, Apr 30, 2013 at 11:45 PM, Thomas De Reyck <thomas%d...@gtempaccount.com> wrote:
Hi everyone,
My very first question here. I hope anyone can help me out with this...
I have created a Django powered site for my company. Everything works perfectly, except in our production environment,
where I have one bug in the admin that is quite annoying:
When I click a user to edit it, the "Staff" and "SuperUser" checkboxes are always checked for every user, even when they
shouldn't be. The database however does record these properties properly, and they work correctly in the application. Only
the admin is displaying them incorrectly in the "edit" page for a user. When looking at the user overview in the admin, the
"staff" property is correctly displayed.
Because of this error we need to be extra cautious when editing users, because we don't accidentally want to make anyone
a staff or superuser.
Does anyone know how I can attempt to debug this? Where should I start?
I am running:
Django 1.5.1 on Ubuntu 12.04 with SQL Server 2008R2 as my database (via pyodbc->UnixODBC->FreeTDS).
Thanks in advance for any hints you can provide!
Kind regards,
ThomasTo unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
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+unsubscribe@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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
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+unsubscribe@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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment