Hi,
I'm not sure if we're talking about the same thing. The issue I am
describing takes place when the database is modified, but the models,
views and templates are unmodified.
I have a sitemap at the bottom of my website that contains recent
additions to the web page. When records are added to the database,
although most of the pages reflect the change, the sitemap doesn't.
The sitemap is implemented as a template that is included by the
base.html template.
In my mind, it goes against the django philosophy of content/code
spearation to require a server restart when the database is modifies -
I'm pretty sure this is not what you meant.
The caching I was talking about is included templates - that is
templates included with {% include %}.
Are these cached? Is there anyway to purge it?
Cheers,
Peter
On Mar 1, 11:23 pm, Michael Newman <[EMAIL PROTECTED]> wrote:
> The caching is a nice feature on a development site but not so much
> when developing. Generally changes to templates don't stay the same,
> but changes to views and models and definitely the url schema take a
> kick to apache to get reloaded. A force-reload is normally enough to
> get things rolling. The test server should automatically be force
> reloading every few minutes, unless you are booting it without that
> option.
>
> The reason for this is that django settings (your settings.py file)
> are loaded into a mod_python session when you start apache and they
> stay there. This also loads your urls and in turn your views. To my
> knowledge there isn't a better way to purge mod_python then a force-
> reload, which takes a second. I add an alias to my bash and just got
> into the habit of typing 'res' whenever I am about to look at my web
> browser.
>
> On Mar 1, 10:19 am, PB <[EMAIL PROTECTED]> wrote:
>
> > Hi,
>
> > I keep running into an issue with templates not being updated until a
> > server restart. Whilst most pages reflect database modification,
> > templates that are included do not show the changes until I restart
> > the server. This happens on Apache and the testserver.
>
> > Any ideas - am I forgetting something?
>
> > Cheers,
>
> > Peter
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
