Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Make sure you have added your application to settings.INSTALLED_APPS.</p> <p>The django template for the admin app index page reads:</p> <pre><code>{% if app_list %} {% for app in app_list %} ... {% else %} &lt;p&gt;{% trans "You don't have permission to edit anything." %}&lt;/p&gt; {% endif %} </code></pre> <p>That must be your problem.</p> <hr> <p>EDIT: Either that or you are not logged in as the user you say you are. Can you look in the database and make sure that the auth_user.is_superuser for the user in question has a value of 1?</p> <hr> <p>EDIT: If you user is_staff and is_superuser are marked as 1 in the DB, and you are sure you are logged in as that user; is it possible that you are only seeing this in production (i.e. under apache) and that your settings.py for production is different than in development?</p> <hr> <p>EDIT: So you have different behavior in dev and production. I can think of two scenarios:</p> <p>a) You have a different settings.py for production. Can you edit your question showing the relevant portion of your httpd.conf? It should be something like:</p> <pre><code>&lt;Location "/mysite/"&gt; SetHandler python-program PythonHandler django.core.handlers.modpython SetEnv DJANGO_SETTINGS_MODULE mysite.settings PythonOption django.root /mysite PythonDebug On &lt;/Location&gt; </code></pre> <p><strong>Also, what is your PYTHONPATH?</strong></p> <p>What is the SetEnv line saying? Is it pointing to the very same module you have in development? Are you sure in your PYTHONPATH you have <code>mysite.settings</code> as the file you think you have?</p> <p>b) You have a PYTHONPATH problem in production and the apps can't be found. This should generate a much more severe error though...</p> <hr> <p>Questions: </p> <ul> <li>/var/django/gpx has a <strong>init</strong>.py correct?</li> <li>/var/django/gpx/settings.py is the same file used as when you do manage.py runserver?</li> <li>What is the name of your app at /var/django/? </li> <li>Does the user your are running Apache under has permissions to all these directories?</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. PODjango Admin: not seeing any app (permission problem?)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UScethegeek
    1. UScethegeek
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for your answer. All the apps are in the settings, none is showing. I also checked the database and the user has is_superuser on.
      singulars
      1. PO
      1. USFacundo Casco
    2. COIs this happening when you run manage.py runserver?
      singulars
      1. PO
      1. UScethegeek
    3. COOk, celopes, you are close. When I run the development server the Admin shows everything. I just don't get it. I was doing heavy editing on this site, if the settings.py file wasn't correct I shouldn't be able to work on it. However when I see it from Apache it doesn't work but it appears to work from the development server.
      singulars
      1. PO
      1. USFacundo Casco
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload