Hi Karen, I am sorry, the previous post is irrelevant. What you have seen is a result of changing of results view that I was doing before, to test what is going on. (btw, I've noticed that firefox caches an error output, can I do something about it?) Thanks
So relevant error output looks like this: Environment: Request Method: GET Request URL: http://127.0.0.1:8000/polls/1/results/ Django Version: 1.0-final-SVN-unknown Python Version: 2.5.2 Installed Applications: ['django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'mysite.polls', 'django.contrib.admin'] Installed Middleware: ('django.middleware.common.CommonMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware') Template Loader Error: Django tried loading these templates, in this order: Using loader django.template.loaders.filesystem.load_template_source: /home/misha/www/djcode/templates/polls/results.html (File does not exist) Using loader django.template.loaders.app_directories.load_template_source: /usr/lib/python2.5/site-packages/django/contrib/admin/templates/polls/ results.html (File does not exist) Traceback: File "/usr/lib/python2.5/site-packages/django/core/handlers/base.py" in get_response 86. response = callback(request, *callback_args, **callback_kwargs) File "/home/misha/www/djcode/mysite/../mysite/polls/views.py" in results 34. return render_to_response('polls/results.html', {'poll': p}) File "/usr/lib/python2.5/site-packages/django/shortcuts/__init__.py" in render_to_response 18. return HttpResponse(loader.render_to_string(*args, **kwargs), **httpresponse_kwargs) File "/usr/lib/python2.5/site-packages/django/template/loader.py" in render_to_string 102. t = get_template(template_name) File "/usr/lib/python2.5/site-packages/django/template/loader.py" in get_template 80. source, origin = find_template_source(template_name) File "/usr/lib/python2.5/site-packages/django/template/loader.py" in find_template_source 73. raise TemplateDoesNotExist, name Exception Type: TemplateDoesNotExist at /polls/1/results/ Exception Value: polls/results.html On Oct 22, 11:57 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > On Wed, Oct 22, 2008 at 5:15 PM, gryzzly <[EMAIL PROTECTED]> wrote: > > > Hi, > > I was following tutorial from official docs step by step. > > > So on part 4, at writing and processing simple form I am stuck with > > something. (here — > >http://docs.djangoproject.com/en/dev/intro/tutorial04/#write-a-simple... > > ). > > > I am writing my results view and pointing at it from polls/urls.py. > > And I am getting 500 error. Whatever I write in results view. Now, if > > I point matching regex from urls.py to some other view, like "details" > > that I've created before that, then it works. > > > Here is the code: > > > polls/urls.py: > > > from django.conf.urls.defaults import * > > > urlpatterns = patterns('mysite.polls.views', > > (r'^$', 'index'), > > (r'^(?P<poll_id>\d+)/$', 'detail'), > > (r'^(?P<poll_id>\d+)/results/$', 'results'), > > (r'^(?P<poll_id>\d+)/vote/$', 'vote'), > > ) > > > relevant view from polls/views.py (and it doesn't really matter what > > do I write there, anyway I get 500 error): > > > def results(request, poll_id): > > p = get_object_or_404(Poll, pk=poll_id) > > return render_to_response('polls/results.html', {'poll': p}) > > > Here is an output of error message: > > > Traceback (most recent call last): > > > [shipped] > > File "/usr/lib/python2.5/site-packages/django/template/loader.py", > > line 73, in find_template_source > > raise TemplateDoesNotExist, name > > > TemplateDoesNotExist: 500.html > > > Please suggest what I could do. > > Well that traceback is not very helpful because it is just reporting that in > attempting to generate an error page the code ran across a 2nd error -- you > haven't created a 500.html template. You need one of these, just like the > 404.html template that the 3rd section of the tutorial mentions. > > However, neither of those templates is particularly helpful when debugging, > since they just present generic "not found" or "error" pages. For debugging > what's really going on you want to set DEBUG to True in your settings.py > file. Then when you go to the page that is causing the error, you will get > a traceback showing where the original error is occuring, which will make it > much easier to figure out what is going wrong. > > Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
