Django ошибка not found

My project is named homefood, and when I runserver I get this error.Anybody have any clue how to fix this error.

Page not found (404)

Request Method: GET

Request URL:    http://127.0.0.1:8000/

Using the URLconf defined in homefood.urls, Django tried these URL patterns, in this order:

^foodPosts/

^admin/

The current URL, , didn't match any of these.

You're seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page.

My settings.py file looks like this…

import dj_database_url
"""
Django settings for homefood project.

# Build paths inside the project like this: os.path.join(BASE_DIR, ...)
import os
BASE_DIR = os.path.dirname(os.path.dirname(__file__))
STATIC_ROOT = 'staticfiles'


# SECURITY WARNING: keep the secret key used in production secret!


# SECURITY WARNING: don't run with debug turned on in production!
DEBUG = True

TEMPLATE_DIRS = (

    os.path.join(BASE_DIR, 'templates'),
)


TEMPLATE_DEBUG = True

ALLOWED_HOSTS = ['*']       # Allow all host headers


# Application definition

INSTALLED_APPS = (
    'django.contrib.admin',
    'django.contrib.auth',
    'django.contrib.contenttypes',
    'django.contrib.sessions',
    'django.contrib.messages',
    'django.contrib.staticfiles',
    'django.contrib.humanize',
    'django.contrib.sites',
    'foodPosts',
    'registration',
    'profiles',
    'homefood',
)

MIDDLEWARE_CLASSES = (
    'django.contrib.sessions.middleware.SessionMiddleware',
    'django.middleware.common.CommonMiddleware',
    'django.middleware.csrf.CsrfViewMiddleware',
    'django.contrib.auth.middleware.AuthenticationMiddleware',
    'django.contrib.messages.middleware.MessageMiddleware',
    'django.middleware.clickjacking.XFrameOptionsMiddleware',
)

ROOT_URLCONF = 'homefood.urls'

WSGI_APPLICATION = 'homefood.wsgi.application'

#=  dj_database_url.config()
#'default': dj_database_url.config(default='mysql://localhost')}
DATABASES = {
'default': {
    'ENGINE': 'django.db.backends.mysql',
    'NAME': 'django_db',
    'USER': 'root',
    'PASSWORD': '',
    'HOST': '',
    'PORT': '',
}
}#= dj_database_url.config()

# Honor the 'X-Forwarded-Proto' header for request.is_secure()
SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')

LANGUAGE_CODE = 'en-us'

TIME_ZONE = 'America/New_York'

USE_I18N = True

USE_L10N = True

USE_TZ = True

#Django-registration additions, for account registration
ACCOUNT_ACTIVATION_DAYS=7
EMAIL_HOST = 'localhost'
EMAIL_PORT = 102
EMAIL_HOST_USERNAME = ''
EMAIL_HOST_PASSWORD = ''
EMAIL_USE_TLS = False
DEFAULT_FROM_EMAIL = 'testing@example.com'

STATIC_URL = '/static/'

STATICFILES_DIRS = (
    os.path.join(BASE_DIR, 'static'),
)                                           #static asset configuration

and my urls.py in my homefood folder is

from django.conf.urls import patterns, include, url

from django.contrib import admin
admin.autodiscover()

urlpatterns = patterns('',
    # Examples:
    # url(r'^$', 'homefood.views.home', name='home'),
    # url(r'^blog/', include('blog.urls')),

    url(r'^foodPosts/',include('foodPosts.urls')),
    url(r'^admin/', include(admin.site.urls)),
)

I think my problem is either in my urls.py, or my settings.py but I am unsure. Any help would be greatly appreciated. Thanks.

from django.conf import settings
from django.urls import re_path
from django.views.static import serve

# ... the rest of your URLconf goes here ...

if settings.DEBUG:
    urlpatterns += [
        re_path(
            r"^media/(?P<path>.*)$",
            serve,
            {
                "document_root": settings.MEDIA_ROOT,
            },
        ),
    ]

from django.core.exceptions import PermissionDenied


def edit(request, pk):
    if not request.user.is_staff:
        raise PermissionDenied
    # ...

Back to Top

Page Not Found

If you try to access a page that does not exist (a 404 error), Django directs you to a built-in view that handles 404 errors.

You will learn how to customize this 404 view later in this chapter, but
first, just try to request a page that does not exist.

In the browser window, type 127.0.0.1:8000/masfdfg/ in the address bar.

You will get one of two results:

1:

2:

If you got the first result, you got directed to the built-in Django 404
template.

If you got the second result, then DEBUG is
set to True in your settings, and you must set it to False to get directed to
the 404 template.

This is done in the settings.py file, which
is located in the
project folder, in our case the my_tennis_club folder,
where you also have to specify the host name from where your project runs from:

.
.
# SECURITY WARNING: don't run with debug turned on in production!
DEBUG = False

ALLOWED_HOSTS = ['*']
.
.

In the browser window, type

127.0.0.1:8000/masfdfg/
in the address bar, and you will get the built-in 404 template:

Customize the 404 Template

Django will look for a file named 404.html in the
templates folder, and display it when there is a 404 error.

If no such file exists, Django shows the «Not Found» that you saw in the
example above.

To customize this message, all you have to do is to create a file in the templates folder and name it
404.html, and fill it with whatever you
want:

In the browser window, type

127.0.0.1:8000/masfdfg/
in the address bar, and you will get the customized 404 template:

If you are developing a web application, then most probably you will come across situations where you need to show the 404 (not found) page. We will talk about this in this article.

When you should return 404

It is a good practice to use a 404 page in cases when users are accessing the wrong URLs, for instance, when the link you used to access the page is broken. We will also talk about how to use the right status code for this situation. You should return 404 HTTP error if one of the following is true:

• The page does not exist.
• The requested page was deleted.
• Page not found.

Python Django provides a number of functions to customize the 404 page. Using them you can easily configure your 404 page without having to write a new view function. Let’s have a look at how to return a 404 error in Django.

First, import Http404 from django.http module. Next, raise the Http404 exception within your view. For example, here is views.py file for the view which always returns 404:

from django.http import Http404

def not_found(req):
    raise Http404

Remember to route the not_found view. To do it, write the following to urls.py:

from . import views
from django.urls import path

urlpatterns = [
    # ...your other routes...
    path('nowhere/', views.not_found), # for 404 demo
]

You should not do this in production apps. We do it now just for the sake of demonstration. Now, restart your application. If you go to the routed URL /nowhere/, you will see one of the following:

• If you have DEBUG=True set in settings.py you will see Django app traceback.
• Otherwise, you will see the 404 error template you specified in settings.py or templates/404.html

Using get_object_or_404 function

Sometimes you need to retrieve a model from a database and return 404 error if the model does not exist. Of course, you can use an if-else statement, but you can use a shortcut, get_object_or_404 function. See the code example below:

from django.shortcuts import get_object_or_404, render

# example model - use models.py to create one
from app.models import Page

def get_page(req, page_id):
    page = get_object_or_404(Page, id=page_id)
    return render(req, 'app/page.html', { 'text': page.text })

We used an imaginary template ‘app/page.html’, which renders the text variable we passed. If the Page model with id page_id does not exists, Django will return the 404 not found error.

Conclusion

To return 404 in Django Framework, you should include the Http404 exception and raise it within a view function. Also you can use get_object_or_404 function from django.shortcuts if you retrieve a model from a database in your view. You learned how to return 404 error and get it handled correctly.