On Jan 16, 9:32 am, Sam Walters <mr.sam...@gmail.com> wrote:
> Hi,
> The production server running centos was just upgraded and in apache
> 1.3 the old httpd.conf file was moved to httpd.conf.bak.
> I had to move my mod_wsgi + virtualhost entry over to the new
> httpd.conf and recompiled mod_wsgi.
>
> Everything works except that when i load my pages none of the .css .js
> .png .gif etc files are being loaded.
>
> when presented with this problem I initially recompiled+installed
> mod_wsgi, then installed python 2.5.4 in /opt/ and looked at paths:
>
> *The project files are in exactly the same place.
> *The virtualhosts entry points to the same locations for these files
> *The settings.py file points to the same template dirs
> *Of course the urls file still points to the same static resources and
> the templates html files still refer to the files form the same
> relative url.
>
> in settings.py:
>
> TEMPLATE_DIRS = ("/home/aero00/aeroclub-beta/Aeroclub/templates",
> "/home/aero00/aeroclub-beta/Aeroclub/templates/css",
> "/home/aero00/aeroclub-beta/Aeroclub/templates/css/admincss",
> # Put strings here, like "/home/html/django_templates" or
> "C:/www/django/templates".
> # Always use forward slashes, even on Windows.
> # Don't forget to use absolute paths, not relative paths.
> )
Why are the CSS paths in TEMPLATE_DIRS? And what are the values of the
actual MEDIA_URL, MEDIA_ROOT and ADMIN_MEDIA settings?
--
DR.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
