Re: Admin site doesn't work
Running on linux mint. I'll keep plugging away and see what I can find.
On Thursday, June 12, 2014 3:56:08 AM UTC-4, Sanjay Bhangar wrote:
>
> Hey Glen,
>
> Hm, whatever it is, is not apparent to me, sorry :/. The only thing I
> can think of is possibly inconsistent indentation. Some comments /
> questions inline --
>
> On Thu, Jun 12, 2014 at 3:39 AM, Glen J >
> wrote:
> > urls.py:
> > from django.conf.urls import patterns, include, url
> >
> > # Uncomment the next two lines to enable the admin:
> > from django.contrib import admin
> > admin.autodiscover()
> >
> > urlpatterns = patterns('',
> > # Examples:
> > # url(r'^$', 'mysite.views.home', name='home'),
> > # url(r'^mysite/', include('mysite.foo.urls')),
> >
> > # Uncomment the admin/doc line below to enable admin documentation:
> > # url(r'^admin/doc/', include('django.contrib.admindocs.urls')),
> >
> > # Uncomment the next line to enable the admin:
> > url(r'^admin/', include(admin.site.urls)),
> > )
> >
> >
> > settings.py:
> > # Django settings for mysite project.
> >
> > DEBUG = True
> > TEMPLATE_DEBUG = DEBUG
> >
> > ADMINS = (
> > # ('Your Name', 'your_...@example.com '),
> > )
> >
> > MANAGERS = ADMINS
> >
> > DATABASES = {
> > 'default': {
> > 'ENGINE': 'django.db.backends.postgresql_psycopg2', # Add
> > 'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'.
> > 'NAME': 'mysite', # Or path to database
> file if
> > using sqlite3.
> > # The following settings are not used with sqlite3:
> > 'USER': 'glen',
> > 'PASSWORD': 'P0rchl1ght!',
> > 'HOST': '192.168.122.120', # Empty for
> > localhost through domain sockets or '127.0.0.1' for localhost through
> TCP.
> > 'PORT': '5432', # Set to empty string for
> > default.
> > }
> > }
> >
>
> Please do not post any sort of passwords on a public mailing list -
> even though I realize this is for a local database. Please take the
> time to quickly sanitize your pastes and remove potentially sensitive
> information.
>
> > # Hosts/domain names that are valid for this site; required if DEBUG is
> > False
> > # See https://docs.djangoproject.com/en/1.5/ref/settings/#allowed-hosts
> > ALLOWED_HOSTS = []
> >
> > # Local time zone for this installation. Choices can be found here:
> > # http://en.wikipedia.org/wiki/List_of_tz_zones_by_name
> > # although not all choices may be available on all operating systems.
> > # In a Windows environment this must be set to your system time zone.
> > TIME_ZONE = 'America/Chicago'
> >
> > # Language code for this installation. All choices can be found here:
> > # http://www.i18nguy.com/unicode/language-identifiers.html
> > LANGUAGE_CODE = 'en-us'
> >
> > SITE_ID = 1
> >
> > # If you set this to False, Django will make some optimizations so as
> not
> > # to load the internationalization machinery.
> > USE_I18N = True
> >
> > # If you set this to False, Django will not format dates, numbers and
> > # calendars according to the current locale.
> > USE_L10N = True
> >
> > # If you set this to False, Django will not use timezone-aware
> datetimes.
> > USE_TZ = True
> >
> > # Absolute filesystem path to the directory that will hold user-uploaded
> > files.
> > # Example: "/var/www/example.com/media/"
> > MEDIA_ROOT = ''
> >
> > # URL that handles the media served from MEDIA_ROOT. Make sure to use a
> > # trailing slash.
> > # Examples: "http://example.com/media/";, "http://media.example.com/";
> > MEDIA_URL = ''
> >
> > # Absolute path to the directory static files should be collected to.
> > # Don't put anything in this directory yourself; store your static files
> > # in apps' "static/" subdirectories and in STATICFILES_DIRS.
> > # Example: "/var/www/example.com/static/"
> > STATIC_ROOT = ''
> >
> > #
Re: Admin site doesn't work
= 'mysite.urls'
# Python dotted path to the WSGI application used by Django's runserver.
WSGI_APPLICATION = 'mysite.wsgi.application'
TEMPLATE_DIRS = (
# Put strings here, like "/home/html/django_templates" or
"C:/www/django/templates".
# Always use forward slashes, even on Windows.
# Don't forget to use absolute paths, not relative paths.
)
INSTALLED_APPS = (
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.sites',
'django.contrib.messages',
'django.contrib.staticfiles',
'polls',
# Uncomment the next line to enable the admin:
'django.contrib.admin',
# Uncomment the next line to enable admin documentation:
'django.contrib.admindocs',
)
SESSION_SERIALIZER = 'django.contrib.sessions.serializers.JSONSerializer'
# A sample logging configuration. The only tangible logging
# performed by this configuration is to send an email to
# the site admins on every HTTP 500 error when DEBUG=False.
# See http://docs.djangoproject.com/en/dev/topics/logging for
# more details on how to customize your logging configuration.
LOGGING = {
'version': 1,
'disable_existing_loggers': False,
'filters': {
'require_debug_false': {
'()': 'django.utils.log.RequireDebugFalse'
}
},
'handlers': {
'mail_admins': {
'level': 'ERROR',
'filters': ['require_debug_false'],
'class': 'django.utils.log.AdminEmailHandler'
}
},
'loggers': {
'django.request': {
'handlers': ['mail_admins'],
'level': 'ERROR',
'propagate': True,
},
}
}
On Wednesday, June 11, 2014 8:48:34 AM UTC-4, Sanjay Bhangar wrote:
>
> On 11 Jun 2014 18:04, "Glen J" > wrote:
>
>> Sanjay,
>> Thanks for the reply. I've tried accessing it various ways using both
>> nginx and the included devserver on :8000. I've done both
>> 127.0.0.1/admin and 127.0.0.1/admin/ with the same results. I can post
>> the contents of my urls.py later today when I have access to my machine at
>> home. FWIW, I didn't think the example.com entry was the issue, but at
>> this point I'm kinda grasping at straws as I've checked my urls.py and
>> settings.py about a hundred times and synced with the database many times
>> as well and don't get a hard error, only the django welcome page.
>>
>>
> Hah, it's almost definitely something silly -- have you added
> django.contrib.admin to your INSTALLED_APPS in settings.py?
>
> No worries - post your urls.py and other things that maybe relevant when
> you have access and we'll try and figure it out.
>
> Cheers,
> Sanjay
>
--
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/7c64f8e5-f202-428b-9c64-aa5fe831ac80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Admin site doesn't work
Sanjay, Thanks for the reply. I've tried accessing it various ways using both nginx and the included devserver on :8000. I've done both 127.0.0.1/admin and 127.0.0.1/admin/ with the same results. I can post the contents of my urls.py later today when I have access to my machine at home. FWIW, I didn't think the example.com entry was the issue, but at this point I'm kinda grasping at straws as I've checked my urls.py and settings.py about a hundred times and synced with the database many times as well and don't get a hard error, only the django welcome page. On Wednesday, June 11, 2014 7:27:12 AM UTC-4, Sanjay Bhangar wrote: > > hey Glen, > > Sorry if this is a silly question - but are you sure you are visiting > /admin on your site? > If you are and still getting this error, can you please paste the > contents of your urls.py > > On Wed, Jun 11, 2014 at 4:24 PM, Glen J > > wrote: > > I've tried it both on the development server you indicate below as well > as > > on a my own web server (nginx using uwsgi) and get the same results. No > > errors are displayed, simply the welcome page for Django. Syncdb works > fine > > (using Postgresql) and shows output when I do it. One thing I did spot > in > > the database that I wasn't sure of is in my django_site table it has > > example.com. Not sure why it is there as I never did that. > > > > Django creates a default site called example.com. You are expected to > change this to your correct site URL when you deploy. This should not > be the cause of your troubles though - AFAIK, this is only used when > generating full url permalinks, like in RSS feeds, etc. > > HTH, > Sanjay > -- 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/792938fd-3bbc-4ea6-bc46-91bd9e3d2052%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Admin site doesn't work
I've tried it both on the development server you indicate below as well as on a my own web server (nginx using uwsgi) and get the same results. No errors are displayed, simply the welcome page for Django. Syncdb works fine (using Postgresql) and shows output when I do it. One thing I did spot in the database that I wasn't sure of is in my django_site table it has example.com. Not sure why it is there as I never did that. On Tuesday, June 10, 2014 10:10:47 PM UTC-4, Glen J wrote: > > I read another post on here about how their Django site admin site would > not come up. In their case, they had failed to edit the urls.py and > settings.py to enable the site. I have done that and also done a syncdb > after making those changes and the admin sited does not come up. All that > displays is the welcome site indicating that Django is working. Like the > other person posting, I am simply following along (or trying) with the > Django tutorial. What else can I look at to get to the bottom of this? > Any help would be much appreciated! > > Glen > -- 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/07e72ea8-2bf9-4654-bb3a-d913d3d1b10f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Admin site doesn't work
I read another post on here about how their Django site admin site would not come up. In their case, they had failed to edit the urls.py and settings.py to enable the site. I have done that and also done a syncdb after making those changes and the admin sited does not come up. All that displays is the welcome site indicating that Django is working. Like the other person posting, I am simply following along (or trying) with the Django tutorial. What else can I look at to get to the bottom of this? Any help would be much appreciated! Glen -- 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/12a96433-60d9-4f63-a3e0-0aa7685f33d9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Cant get to admin login page
I have this exact same problem. I'be checked both settings.py and urls.py and done a syncdb and still get nothing but the welcome page. Any other ideas on what to check? On Thursday, June 6, 2013 5:53:12 PM UTC-4, Rebecca wrote: > > I'm on part 2 of the django book tutorial ( > https://docs.djangoproject.com/en/dev/intro/tutorial02/) and am trying to > get onto the admin login page in my browser. When I go to the admin site > on my local domain (http://127.0.0.1:8000/admin/), I dont get to the > login screen. I get to something else from django > > " > It worked!Congratulations on your first Django-powered page. > > Of course, you haven't actually done any work yet. Here's what to do next: > >- If you plan to use a database, edit the DATABASES setting in >myproject/settings.py. >- Start your first app by running python manage.py startapp [appname]. > > You're seeing this message because you have DEBUG = True in your Django > settings file and you haven't configured any URLs. Get to work!" > > > > but not the login screen it said i would get in the tutorial. Anyone know > why? or how to get to the login page? > > > Thanks!! > -- 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/f73e1fd5-6737-4d79-925e-a1c8c365b95c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
