DJANGO_STYLE_MODEL_KIND = False causes the Django Administration fail.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. set DJANGO_STYLE_MODEL_KIND = False in settings.py
2. The datastore entity of admin users in GAE changes from auth_users to Users.
3. .try to login to admin and server error occured. 
What is the expected output? What do you see instead?
The Sample application shows that "there was an error while handling your
request." after setting DJANGO_STYLE_MODEL_KIND = False. It supposed to
show Django Admin pages.

What version of the product are you using? On what operating system?
either 1.1 or 1.0 have the same problem as above. 

Django admin seems not to read the datastore entity "Users" and only read
the original settings. auth_users and any other django style admin model
doesn't work when DJANGO_STYLE_MODEL_KIND = False.

Original issue reported on code.google.com by mfa1...@gmail.com on 17 Aug 2009 at 9:45

[GoogleCodeExporter]

The first time I added DJANGO_STYLE_MODEL_KIND = False to my app and updated 
it, the 
error message in GAE reported a missing index:
- kind: LogEntry
  properties:
  - name: user
  - name: action_time
    direction: desc

Once I ran the app locally (manage.py runserver), it added the missing index to 
my 
index.yaml file. Then when I re-deployed the app (manage.py update --nosyncdb) 
the 
admin interface started working again.

Not sure if we are looking at exactly the same problem, just letting you know 
what 
worked for me.

I am using DJANGO_STYLE_MODEL_KIND = False only because I am converting an 
existing 
non-Django app that was already in GAE with production data.

Original comment by piet.nie...@gmail.com on 15 Nov 2009 at 12:23