You are getting the 404 because you haven’t defined a url pattern for http://127.0.0.1:8000/ yet. You should be able to view the admin site at http://127.0.0.1:8000/admin/ and your food posts at http://127.0.0.1:8000/foodPosts/. To add a url pattern for the homepage, uncomment the following entry in your urls.py, and replace homefood.views.home with the path to the … Read more
Did you set TEMPLATE_DIRS in your settings.py? Check and make sure it is set up correctly with absolute paths. This is how I make sure it is properly set: settings.py PROJECT_ROOT = os.path.abspath(os.path.dirname(__file__)) 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 … Read more
You can use the URL resolver directly in a template, there’s no need to write your own filter. E.g. {% url ‘admin:index’ %} {% url ‘admin:polls_choice_add’ %} {% url ‘admin:polls_choice_change’ choice.id %} {% url ‘admin:polls_choice_changelist’ %} Ref: Documentation
You are getting the 404 because you haven’t defined a url pattern for http://127.0.0.1:8000/ yet. You should be able to view the admin site at http://127.0.0.1:8000/admin/ and your food posts at http://127.0.0.1:8000/foodPosts/. To add a url pattern for the homepage, uncomment the following entry in your urls.py, and replace homefood.views.home with the path to the … Read more
Write a custom context processor. e.g. def get_current_path(request): return { ‘current_path’: request.get_full_path() } add a path to that function in your TEMPLATE_CONTEXT_PROCESSORS settings variable, and use it in your template like so: {{ current_path }} If you want to have the full request object in every request, you can use the built-in django.core.context_processors.request context processor, … Read more
Check the docs for include here. What you’ve done is not an acceptable way of passing parameters to include. You could do: url(r’^reviews/’, include((‘reviews.urls’, ‘reviews’), namespace=”reviews”)),
If you want a list of all the urls in your project, first you need to install django-extensions You can simply install using command. pip install django-extensions For more information related to package goto django-extensions After that, add django_extensions in INSTALLED_APPS in your settings.py file like this: INSTALLED_APPS = ( … ‘django_extensions’, … ) urls.py … Read more
In the view, you can access the URL args and kwargs as self.args and self.kwargs. class MyView(View): def my_method(self): this_name = self.kwargs[‘this_name’] If you only want to access the value in the template, then you don’t need to make any changes in the view. The base get_context_data method adds the view to the context as … Read more
You can try the Class Based View called RedirectView from django.views.generic.base import RedirectView urlpatterns = patterns(”, url(r’^$’, ‘macmonster.views.home’), #url(r’^macmon_home$’, ‘macmonster.views.home’), url(r’^macmon_output/$’, ‘macmonster.views.output’), url(r’^macmon_about/$’, ‘macmonster.views.about’), url(r’^.*$’, RedirectView.as_view(url=”<url_to_home_view>”, permanent=False), name=”index”) ) Notice how as url in the <url_to_home_view> you need to actually specify the url. permanent=False will return HTTP 302, while permanent=True will return HTTP 301. Alternatively … Read more
From Django documentation for url url(regex, view, kwargs=None, name=None) This function is an alias to django.urls.re_path(). It’s likely to be deprecated in a future release. Key difference between path and re_path is that path uses route without regex You can use re_path for complex regex calls and use just path for simpler lookups