Good test.  The user that can't edit without superuser status *is* able to 
edit the model with superuser status.  Not sure where that leaves me, but 
at least we ruled out one potential issue.  Thanks.

On Tuesday, October 16, 2012 6:24:04 PM UTC-5, Nikolas Stevenson-Molnar 
wrote:
>
>  Out of curiosity (obviously it wouldn't be a good solution), if you give 
> the account which *doesn't* work superuser status, is that account then 
> able to edit content?
>
> _Nik
>
> On 10/16/2012 2:08 PM, Shawn H wrote:
>  
> I have, as far as I can tell.  I've created a group with add, edit, and 
> delete permissions on the model, and made the user a member of that group. 
>  The user can't edit anything.  I've deleted the group and just assigned 
> add, edit, and delete privileges to the user, and the user still can't edit 
> anything.  The super user can edit no problem, just not any other user.
>
> On Monday, October 15, 2012 11:23:07 AM UTC-5, Nikolas Stevenson-Molnar 
> wrote: 
>>
>> Being 'staff' only means that the user can access the admin area, not 
>> that they can do anything there. Double check that they have permissions 
>> (or are a member of a group which has permissions) to edit each content 
>> type you want them to be able to edit. 
>>
>> _Nik 
>>
>> On 10/12/2012 2:02 PM, Shawn H wrote: 
>> > I'm new to django, and using the admin site for user management.  I've 
>> > created a new user, issued app | model | permission of add, change, 
>> > and delete to this user for the app I've built, but when I logon as 
>> > that user, I get the "you don't have permission to edit anything". 
>> >  The user is active (obviously as I can logon as that user) and is 
>> > staff, but the permissions don't seem to be working.  What might I be 
>> > missing?  Thanks. -- 
>> > You received this message because you are subscribed to the Google 
>> > Groups "Django users" group. 
>> > To view this discussion on the web visit 
>> > https://groups.google.com/d/msg/django-users/-/5zMO9ZPGel4J. 
>> > To post to this group, send email to django...@googlegroups.com. 
>> > To unsubscribe from this group, send email to 
>> > django-users...@googlegroups.com. 
>> > For more options, visit this group at 
>> > http://groups.google.com/group/django-users?hl=en. 
>>
>>  -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/django-users/-/3f7cDH1EMcAJ.
> To post to this group, send email to django...@googlegroups.com<javascript:>
> .
> To unsubscribe from this group, send email to 
> django-users...@googlegroups.com <javascript:>.
> For more options, visit this group at 
> http://groups.google.com/group/django-users?hl=en.
>
>
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/cJGrqPxe8P0J.
To post to this group, send email to django-users@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.

Reply via email to