No, I haven't located the issue yet. Somehow, the compiled code from a cache file (the $compiled variable I believe) is not a reference, but returns the value "1". I'm going to check out some external issues that might be causing the function to fail reading in the code properly. Although I'm not writing to NFS, I was just informed by a tester that there is a known bug with the virus scanning software my company uses that sometimes causes files to be put under exclusive locking, with serialized access. That's probably what the problem is, assuming we are being affected by the bug.
Thanks for the info though. If it isn't the problem, I'll just have to dig deeper and try and watch the load from the cache file. -Tom -----Original Message----- From: Perrin Harkins [mailto:[EMAIL PROTECTED]] Sent: Friday, March 15, 2002 9:09 AM To: Tom Gioconda Cc: [EMAIL PROTECTED] Subject: Re: [Templates] Templates Cached to Disk Importance: High Tom Gioconda wrote: > I'm having a problem with some templates on my site returning "invalid > template reference: 1" a lot. Hmmm. Did that race condition with writing cache files get fixed? Which version are you running? Are you writing to NFS? > Shouldn't the Template > Toolkit attempt to load from the original source template if its cache > load fails, either in memory or from a disk file? It attempts to load from the original if a cache file is not found, but the code currently assumes that cache files will always be good and that a failure in them indicates that something really bad is wrong. You could change that pretty easilly, but the problem you're experiencing is definitely not normal behavior. - Perrin
