Smarty

[ndorphin]

Hi,

i use Smarty 3.0.7 with caching. All runs fine but after exactly a 10 days period (compared to my server logs) i get massive fatal errors "Call to a member function on a non-object". I've all things checked, the problem is only solvable by deleting all files in templates_c only (i don't delete cache dir). After deleting all is running fine until the next "crash". It must definitly be a bug, the 10 days are very strange (at least one times i remember that i've deleted the template_c dir between the 10 days after updating something). My caching time is definitly not set to 10 days (vary between 1 month or unlimited). The error occurs ever in smarty_internal_template.php (line 518) with a message like this:

PHP Fatal error: Call to a member function getProperty() on a non-object in
../smarty3/sysplugins/smarty_internal_template.php(518) : eval()'d code on line ...

I know that the my object function "getProperty()" will be called within an {nocache} block if the error occurs, i've tested it. So the bug must have something to do with {nocache}. I know what happens if you call a function on an non existing object within an {nocache} block, the error message is different then, not with "eval()'d"...

I hope that my problem is solved now by deleting templates_c one time per day with cron... The problem was on 3.0.6 too. I've updated to .7 in hope that solves the problem

Any ideas about that?

Thanks
ndorphin

[U.Tews]

It looks like that the object variable which is calling the getProptery() method was not assigned.

The error occured in a case when Smarty wanted to write a new cache file.

Hard to tell the reasion without seeing your PHP script and template files.

[ndorphin]

Hi, as i said, i know whats happens when a (object) variable was not assigned. The described problem occurs after 10 days with *all* my cached files, wich running the days before fine. The error message with the eval'd message is different from the error message you'll get if you try to access an non setted object (i know this error). If i had a non setted object then only deleting the template_c dir would not help, but in my case only delteing it solves my problem..

My template files are so complex - i cant show this here.

I guess that my problem is a bug within the hashing (strings like SmartyNocache:4330926474dd1a3b9a6c2d7-93241468) inisde the template files. After deleting my template_c folder only the hashes within the files are changed. But i don't undertand the hashes & what they have to do...

Thanks for your help!

[U.Tews]

The SmartyNocache hash value can't be the cause for this problem.
It's value is new each time a template compiles and is a protection against code injection.

It's strange that this error occours after 10 days if cache_liftetime is as large like a month, as the error occurs when a cache file is recreated. Have the source files for some reasion got a new modified date?

Do you assign the object variable in dependence of an isCached() condition?

[ndorphin]