On Wed, Sep 12, 2012 at 2:21 PM, Thomas Orozco <tho...@orozco.fr> wrote:
> Here's an example:
>
> from django.template import loader
> l =
> loader.find_template_loader('django.template.loaders.app_directories.Loader')
> # Or W/E loader you happen to use
> l.load_template_source(somewhere/'your_template.html')
>
> This will return a tuple (template string, template_path).
>
> This way you should be able to troubleshoot your issue.
> You could always try wich each loader using:
>
>
> from django.conf import settings
> for loader_name in settings.TEMPLATE_LOADERS:
> l = loader.find_template_loader(loader_name)
> l.load_template_source(somewhere/'your_template.html')
I tried that, but I got:
ImportError: Settings cannot be imported, because environment variable
DJANGO_SETTINGS_MODULE is undefined.
So I tried setting that, first to the absolute path to my setting
file, and I got:
Import by filename is not supported.
Then to the relative path:
relative imports require the 'package' argument
Then to just settings.py:
No module named settings.py
>
> 2012/9/12 Thomas Orozco <tho...@orozco.fr>
>>
>> Can you being up a manage.py shell and load the template from there to
>> identify where's Django is pulling the template from?
>>
>> You should be able to go step by step and identify where you're pulling the
>> old template in!
>>
>> If you don't find anything, it's probably because your template actually
>> isn't different from the older one.
>>
>> You should be able to do that using pdb and the Django code base :-)
>> There might be a quicker way though, I'll have a look at it.
>>
>> Thomas
>>
>> On Sep 12, 2012 5:59 PM, "Larry Martell" <larry.mart...@gmail.com> wrote:
>>>
>>> On Wed, Sep 12, 2012 at 11:56 AM, Thomas Lockhart
>>> <tlockhart1...@gmail.com> wrote:
>>> > On 9/12/12 8:27 AM, Larry Martell wrote:
>>> >>
>>> >> On my Mac, I changed a template, and the change was picked up, no
>>> >> problem. I checked my change into git, went to another machine, a
>>> >> CentOS box, pulled the change down, but django is not picking it up.
>>> >> I've tried everything I can think of - bounced the server, restarted
>>> >> the browser, cleared the cache and cookies, tried 3 different
>>> >> browsers, deleted it, re-pulled from git, but when I look at the code
>>> >> in the debugger, it's clearly using the old template. There are no
>>> >> errors in the apache log, permissions are fine, I'm tearing my hair
>>> >> out here. Anyone have any ideas as to what's preventing it from
>>> >> picking up the new template, or what I can check to figure out what's
>>> >> going on?
>>> >>
>>> > Need to collect static content for your production server?
>>>
>>> I had already tried that (even thought this change did not effect the
>>> static content).
>>>
>>> --
>>> 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
>>> django-users+unsubscr...@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/django-users?hl=en.
>>>
>
> --
> 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
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
--
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
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
