Opened 14 years ago

Closed 14 years ago

Last modified 13 years ago

#692 closed defect (invalid)

TemplateSyntaxError in admin with development server

Reported by: danlipsitt+djangotrac@… Owned by: Adrian Holovaty
Component: Core (Management commands) Version:
Severity: major Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


I have replicated the error I described in this newsgroup posting on a different machine running a different Linux distribution, so I am filing it as a bug.

Error Description

As soon as log in to the admin interface (running on the development server), I get a traceback ending in this error:

  File "/usr/lib/python2.4/site-packages/django-1.0.0-py2.4.egg/django/core/template/", line 627, in do_load
    raise TemplateSyntaxError, "'%s' is not a valid tag library" % taglib

TemplateSyntaxError: 'log' is not a valid tag library

Steps to Replicate

  1. Delete old django egg directory from site-packages.
  2. svn update to current trunk (I have tried [992] on one machine and [1006] on the other. I was using ~[882] before. This means I am updating to the admin changes of #627).
  3. clean, build, and install
  4. startproject myproject
  5. edit myproject/ (use sqlite3, add admin to INSTALLED_APPS)
  6. enable admin in myproject/
  7. cd myproject
  8. startapp myapp
  9. rm -r myapp/settings
  10. init
  11. createsuperuser
  12. runserver my external ip:8000 --settings='myproject.settings'
  13. log in to the admin site

Change History (2)

comment:1 Changed 14 years ago by danlipsitt+djangotrac@…

I checked out a fresh copy of the django code from svn and everything works now. So the problem is that svn update left me with an inconsistent source tree. This ticket should be closed, but first I want to ask: is this a peril that should be mentioned in the install docs? Is there a flag that I should have used for svn update?

comment:2 Changed 14 years ago by sune.kirkeby@…

Resolution: invalid
Status: newclosed

It is mentioned in the docs. See BackwardsIncompatibleChanges:

Delete django/templatetags/*.pyc and django/templatetags/*.pyo, just to be safe.

Note: See TracTickets for help on using tickets.
Back to Top