RE: [Slashcode-development] caching vs updating templates

[Howell, M. <ho...@ra...>]

Hello Randall,

From what I know (or think I know), each httpd process contains it's own
local cache of templates.  You can force a refresh on un*x systems with a
simple 'killall -HUP httpd' command.  This sends a HUP signal to all httpd
processes which causes them to refresh their cache and vars (constants).

The failed template lookup comes from one process loading a fresh copy of a
template that references a new template (that you just created) that it
doesn't yet have in it's cache.  A simple killall -HUP will fix this.

Good luck,
-Mark

-----Original Message-----
From: Randall Hansen [mailto:li...@so...]
Sent: Monday, March 17, 2003 7:55 PM
To: sla...@so...
Subject: [Slashcode-development] caching vs updating templates


Folks ~

I've been doing plugin development and I'm having trouble with what appears
to be Slash's template caching.  I've tried this in several browsers (Moz,
Konq, Lynx) with identical results.

When I make a change to a template, often the site doesn't update.  Say I
remove some text or a button from a template.  Template-tool updates the
template successfully, the changes appear correct in the Admin interface,
but when I browse the page they don't always appear.  I say "always"
advisedly, because sometimes they do and sometimes they don't.  I can hit
the browser's "Refresh" 10 times and get 3 different versions of the page,
even after clearing the browser cache.

The second weird thing that happens is that sometimes Slash doesn't find the
template at all.  Here's a sample line from the site's error log:

[Tue Mar 18 01:37:55 2003] [error]
/n4n4.pl:Slash::Display::Provider:/usr/local/lib/perl/5.6.1/Slash/Display/Pr
ovider.pm:81:Failed template lookup on
'edit_org;n4n4[misc];default[default]', callers: Slash::Display line 228,
Apache::ROOTrancid::n4n4_2epl line 66, Apache::ROOTrancid::n4n4_2epl line 43

This happens although every tool I can use (the Admin interface,
template-tool, querying the database directly) shows me the template just as
it should be.  It often happens after I update a template.

I've managed to avoid these errors somewhat (but not completely) by setting
'cache_enabled' to 0, but I've not spent enough time in the code to
understand exactly how caching works.  Is this behavior expected, or
abnormal?  Does anyone have any help, or pointers to other resources?

Thanks muchly,

Randall


-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
Slashcode-development mailing list
Sla...@li...
https://lists.sourceforge.net/lists/listinfo/slashcode-development
[ALERT] -- Access Manager: This email is intended only for the person or
entity to which it is addressed and may contain information that is
privileged, confidential or otherwise protected from disclosure.
Dissemination, distribution or copying of this e-mail or the information
herein by anyone other than the intended recipient, or an employee or agent
responsible for delivering the message to the intended recipient, is
prohibited. If you have received this e-mail in error, please immediately
notify us by calling our North American Help Desk at (972)506-3939.