Django 1.3.7 TemplateDoesNotExist error admin/index.html
<p>There are numerous questions asked on this site similar to this one, but I couldn't find one that could explain this particular behavior.</p>

<p>I am relatively new to django and ubuntu, so maybe the explanation is simple.  This is an old (v1.3.7) django project I'm attempting to migrate to a new server.</p>

<p>Here is the full error I am getting in my apache log:</p>

<pre><code>TemplateDoesNotExist at /admin/
admin/login.html
Request Method: GET
Request URL:    http://131.212.123.7:26080/glrimon/admin/
Django Version: 1.3.7
Exception Type: TemplateDoesNotExist
Exception Value:    
admin/login.html
Exception Location: /.../leave_beave/lib/python2.7/site-packages/django/template/loader.py in find_template, line 138
Python Executable:  /.../leave_beave/bin/python
</code></pre>

<p><code>leave_beave</code> is the name of my virtualenv.</p>

<p>Here is the info passed along by the traceback:</p>

<pre><code>Template-loader postmortem

Django tried loading these templates, in this order:
Using loader django.template.loaders.filesystem.Loader:
/glri_mon/siteweb/templates/admin/login.html (File does not exist)
Using loader django.template.loaders.app_directories.Loader:
/glri_mon/siteweb/gps_upload/templates/admin/login.html (File does not exist)
/glri_mon/siteweb/siteapp/templates/admin/login.html (File does not exist)
/glri_mon/siteweb/glrimon_models/templates/admin/login.html (File does not exist)
/glri_mon/siteweb/sdde/templates/admin/login.html (File does not exist)
/glri_mon/siteweb/dv/templates/admin/login.html (File does not exist)
/glri_mon/siteweb/contains/templates/admin/login.html (File does not exist)
/glri_mon/siteweb/sqlwrite/templates/admin/login.html (File does not exist)
/.../leave_beave/lib/python2.7/site-packages/cms/templates/admin/login.html (File does not exist)
/.../leave_beave/lib/python2.7/site-packages/tinymce/templates/admin/login.html (File does not exist)
/.../leave_beave/lib/python2.7/site-packages/mptt/templates/admin/login.html (File does not exist)
/.../leave_beave/lib/python2.7/site-packages/menus/templates/admin/login.html (File does not exist)
/.../leave_beave/lib/python2.7/site-packages/cms/plugins/text/templates/admin/login.html (File does not exist)
/.../leave_beave/lib/python2.7/site-packages/cms/plugins/picture/templates/admin/login.html (File does not exist)
/.../leave_beave/lib/python2.7/site-packages/cms/plugins/link/templates/admin/login.html (File does not exist)
/.../leave_beave/lib/python2.7/site-packages/cms/plugins/file/templates/admin/login.html (File does not exist)
/.../leave_beave/lib/python2.7/site-packages/cms/plugins/snippet/templates/admin/login.html (File does not exist)
/glri_mon/siteweb/cmsplugin_rst/templates/admin/login.html (File does not exist)
</code></pre>

<p><code>glri_mon</code> is the django project directory.
Here's the path to the template in question: <code>/.../leave_beave/django/contrib/admin/templates/admin/index.html</code>. Any thoughts on why django didn't include that path in it's search?</p>

<p>Here are my template loaders from settings.py:</p>

<pre><code>TEMPLATE_LOADERS = (
    'django.template.loaders.filesystem.Loader',
    'django.template.loaders.app_directories.Loader',
#     'django.template.loaders.eggs.Loader',
)
</code></pre>

<p>I received this same error for an earlier problem, and I solved it by creating a symlink from the templates directory in question (<code>.../python2.7/site-packages/lib.../package/templates</code>) to my <code>/project_dir/templates</code> directory, which is the one configured as my template directory in settings.py:</p>

<pre><code>TEMPLATE_DIRS = (
    os.path.join(PATH, 'templates'),
) 
</code></pre>

<p>I did this at the time, since I thought it was a one-off hack solution sort of thing, but now I'm getting the same error for attempting to access the admin page of my site (<a href="http://.../admin/" rel="nofollow">http://.../admin/</a>).  This tells me I'm going about this wrong.  </p>

<p>I suppose I could add a symlink to every template directory that generates this error, but that doesn't seem like a good idea for a production site.</p>

<p>What am I missing here?</p>